When carriage is already at Y limit, $H will not work - crashes carriage & causes belt to slip gears
This has happened to me twice now, and I think I can see why.
When the carriage is already at the maximum Y (but not maximum X) and you issue a $H, the carriage travels along the X axis until the X limit switch is triggered. It's then supposed to travel up the Y axis until the Y limit switch is triggered, however it doesn't - it just keeps skipping gears while at the home position as the carriage bounces back along the X axis (and you have to panic and power cycle it to stop the noise).
I think the logic problem is that because of the shape of the top of the Emblaser, as it's been homing along the X axis, the Y limit switch has been triggered by the curve of the top of the working area. The firmware is not expecting this (as it's only been moving the carriage in the X axis), and then still tries to move further up along the Y axis - which it's already at ... causing the belt to slip on the gears and crash. Since the slipping causes the carriage to travel back along the X axis, it's no longer ever going to trip the Y axis limit switch ... and the only way to stop it is to switch it off.@darklylabs
please verify and fix this firmware bug! I can take a video if necessary as it seems quite reproducible. Firmware is A3 Ver1.8