Y-axis Crash on job restart

I’m on my first production run, with two arrays of BlindsFeeders, three reels and a couple of trays. Occasionally I’ll get a “No vacuum detected” on pick, or “No part seen” on bottom cam, and the machine then refuses to proceed, with messages like “No part on Nozzle”, so I do a job STOP, and then a START.

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, and I have to spend the next hour sorting the components which have flipped around in or fallen out of the BlindsFeeders.

Then I have to power everything down, and start over.

I would have thought Marlin would have prevented travel past the soft-limit/switch limit in Y, so perhaps there is some other cause for the vibration?

I’m only running slowly, speed set at 50%.

I don’t know if my problem is related to this one or not?
https://forum.pandaplacer.com/t/y-axis-stalling-during-job/38

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:

  1. 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.

  2. 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.

Hi Leo,

Thanks for the quick feedback, I’ll try what you have suggested once I have some time with the machine again - probably not until I get back from Brazil in early May.

BTW it is an A1, not a CC - PD_MC_V2.2.

I’ve also updated my WebserverQR script, made some fixes to OpenPnp code, and added features to the BlindsFeeder scad, some specific to the PP. I’ll try and get them up on GitHub before I leave, in case they are useful to others.

Cheers,
David

Hi,

Okay, if it’s an A1, drive issues are more likely, smaller drives are easy to overheating, which can cause problems. Please provide more feedback later so I can help the fix.

For the A1 configuration with dual Z-axis nozzles, you can also add nozzle switching (or reverse the Z-axis direction), which also compatible with a single Z-axis, that would be even better. Besides, adding more control commands over the actuators could be an option, but this would limit its universal applicability, making it suitable only for specific machine models.

Once you’ve finished updating WebserverQR and uploading to github, feel free to share the link; I can also link it on the docs download page. Thank you for the great tool!