Topics created by ampex_fhm

My intention was to implement standstill current reduction in firmware, but I haven't done that yet.

I will correct the docstrings in the source files at the next commit.

@Phaedrux my idea was to keep the orignal functionality of S3 if no timeout is specified, and allow to the dialogue to time out on its own if a non-zero timeout is passed via the gcode. That way we could avoid having an extra type.

@dc42 I was not aware of these complications. If this is too tricky to implement you can safely ignore this request of course.

I had hoped the drivers would reset to some default state that was usable, but your reply confirmed that this is most likely not the case. Thanks for your reply!

true, but wouldn't that also require a separate M584 call everytime I want to jog a different axis?

right now I'm using a workflow like

M584 ... (set up all four pairs with overlapping drive assignments) G0 FRONT_PAIR G0 RIGHT_PAIR G0 REAR_PAIR M584 ... (restore drive mapping for normal operation) <normal operation>

If I understand correctly, your suggestion would require to change this to:

M584 ... (set up mapping for FRONT_PAIR movement) G0 FRONT_PAIR M584 ... (set up mapping for RIGHT_PAIR movement) G0 RIGHT_PAIR M584 ... (set up mapping for REAR_PAIR movement) G0 REAR_PAIR M584 ... (restore drive mapping for normal operation) <normal operation>

@djdemond that's how I'm doing it now. I just wanted to confirm that I am not running into some other issue

@dc42 thanks for clearing that up. I hope others with the same question as mine will find this explanation as well.