Hi David,
Many operational errors can interrupt job execution, so I strongly recommend that when setting up a job, you select all parts (CTRL+A and right mouse button) in the Placement list and change the Error Handle option from the default Alter to Defer. This will cause common errors to be skipped initially, allowing the placement of subsequent components to continue. Once the job is complete, you can click “RUN” again to re-execute the placements that were skipped previously.
Common causes of job interruptions:
-
Vacuum sensor readings exceed the threshold: The vacuum sensor threshold follows the tip and can be set for each tip; when readings exceed the threshold, the component will be discarded. For standard components with minimal leakage (such as resistors and capacitors with flat surfaces and stable vacuum readings), vacuum detection can be enabled; for components with unstable vacuum readings, vacuum measurement for the corresponding tip can be disabled (None). If BCAM recognition is enabled, disabling vacuum detection will not have a significant impact.
-
BCAM fails to detect the component: When no pick, or significant deviation in visual recognition occurs, BCAM recognition will fail with messages like “No part on Nozzle”.
Normally that works well, and I can continue on, but occasionally on START there is a great banging and crashing which sounds like the carriage is trying to break through the top end of the Y axis
This issue was caused by a driver failure and has been resolved by replacing the driver: Y Axis Stalling during Job
The Marlin firmware does impose limits on maximum position, but this likely isn’t a firmware issue since there is some margin built in.
What version of the XY drivers does your CC1 (OR A1?) machine use (do they have a black heat sink on the bottom)? Typically, when drivers recover from a half-current state, there may be a slight initial vibration, but there shouldn’t be any abnormal displacement. A 50% speed setting shouldn’t cause the motor to lose steps (a lose step would produce a rattling noise).
First, please try the initial method: change the component error handling in the job to “defer,” then run the job without frequent interruptions to see if the issue persists. If it is a driver problem, I will provide you with replacements.