Topics created by Jos_mosa

@Jos_mosa and now that 3.6.0 stable is released, it is visible in the DWC Object Model Browser too.

@jos_mosa in RRF 3.4.x a driver-stall event is generated instead, and the driver number is passed as a parameter to the event handler macro. See https://docs.duet3d.com/en/User_manual/RepRapFirmware/Events.

@jos_mosa No, there is no failsafe for "stupid" moves; on another machine, such a move may be perfectly valid. Generally tools are free to move around in the space defined by M208, once homed. On IDEX machines, you usually set each carriage up as a separate tool, and one gets parked while the other is printing. You can also set them up for simultaneous 'duplicate' and 'mirror' mode printing. In these modes you usually set them to use half the bed area each (and possibly less in mirror mode) so the carriages don't crash. See https://docs.duet3d.com/User_manual/Machine_configuration/Configuration_IDEX#configuring-tools

We are working on separate gcode streams for RRF, so it's possible that each carriage could move independently (though they will always have to be synchronised in Y), but it would still be advisable to limit the print area of each tool to half the bed.

Ian

@jos_mosa you'll have to split the axis in 2 for homing, set the position and then rejoin them into 1 axis at the end
https://docs.duet3d.com/User_manual/Connecting_hardware/Z_probe_auto_levelling#axis-levelling-using-endstops
like the example here for RRF2

@jos_mosa thanks, I'll close this thread.