Topics created by stevenim

@bearer said in M950 GPIO Bug:

mixing inputs and outputs here

you're right, thanks for explaining.

@dc42 When they compete with motion system... That explain my problem about this. My macro trigger the use of an extra stepper motor, which is connected to a driver on an expansion board. So depending on the printing speed, Im detecting strange "pauses" either on the gcode printing or in the time the extra motor moves..
Now I understand why, the re is a competition for the motion system even when this extra motor is not really part of the motion of the printer, it is just vor moving a heavy filament spool, but I guess since it is using a stepper driver, it is considered part of the motion system?

PS - I suspect the issue is that the Duet web server can respond to a maximum of 4 HTTP requests concurrently.

There used to be a good bit of info in the DWC readmed on github, but seems to have been relocated.

You might find this enlightening https://forum.duet3d.com/topic/12677/boilerplate-http-connection-code-for-python-based-ui

Well I think that runs into the same limitation of USB commands being sequential in general.

M917 takes advantage of features of the drivers on the Maestro and Duet 3 board to allow current reduction for slower moves or briefly pausing, but not yet idle.

https://duet3d.dozuki.com/Wiki/Gcode?revisionid=HEAD#Section_M917_Set_motor_standstill_current_reduction

@stevenim said in Asynchronous Stop w/o using emergency stop and ack message:

Does anyone think the M25 command can make the motor stop while it's running?

Currently, M25 always waits until at least the end of the current move before movement stops. I have it on my work list to allow it to gracefully terminate long moves before then.