Topics created by ajdtreyd

@dc42
All connections between the accelerometer and duet were mapped correctly when I checked this morning. However, after re-seating at both ends everything is working as expected. Perhaps one of the wires is intermittently breaking. I used a solid core Cat6 cable and should probably remake with silicon jacketed, braided wire given all the movement.

I assumed that the issue was software because I had tested the accelerometer just before the update and the failure occurred just after. A good example of "correlation doesn't equal causation"!

Thanks for the help and pointing out the obvious thing I should have checked!

😬

@ajdtreyd thanks for pointing this out. I confirm that the behaviour is not as intended. This will be fixed in the next 3.4 beta release.

@ppaukstelis unfortunately there are some commands that must be executed or remembered even when skipping an object, such as tool changes and fan speed settings. Also, I don't think it is guaranteed that after the slicer signals the start of a new object, the first move will be a travel move. Therefore RRF interprets many of the skipped commands and tracks the head position through those commands.

If it was guaranteed that the slicer always started a new object with a travel move, then RRF would not need to track the head position, which would make skipping moves faster.

Alternatively, if the pause while skipping an object is not of itself a problem, but nozzle oozing during the pause is, then we could execute a macro when switching from a printing to a cancelled object, and another when switching back to a printing object. In those macros you cold move the print head to the edge of the build plate, and clean/re-prime the nozzle.