Printer pausing between commands

deckingman

@dc42 I'm fairly sure that I am using end stops on the Duex5 but I'll confirm when I get back to the UK in a couple of days time.

gnydick

Nope, just motors and one fan

dc42

Thanks. Next time the problem occurs, please check whether when when you do a software reset of the printer (e.g. M999 or Emergency Stop), the DueX is recognised afterwards (send M115 and look at the Electronics string).

If the DueX is not recognised after a software reset (so you have to power the system down an up again for the DueX to be recognised), then I have a theory about what is causing the problem. If it is correct, then the following should help. Most users run the VIN ground wire from the PSU to the Duet, and then on to the DueX using a short thick wire. The fix would be to run the VIN ground wire from the PSU to the DueX first, and then on to the Duet using a short thick wire. The +Vin wire isn't critical, it can be routed in either order or using separate wires from the PSU to the Duet and DueX.

deckingman

@deckingman said in Printer pausing between commands:

@dc42 I'm fairly sure that I am using end stops on the Duex5 but I'll confirm when I get back to the UK in a couple of days time.

I can now confirm that I'm using 4 of the end stops. Also, 5 motors, 5 fans and 5 thermistors. Nothing connected to the GPIO other than the recommended resistors. Confused as to why a wiring change might be the solution when I had no problems from when I originally started using the board in December 2016 until July(ish) 2018. But when it misbehaves again, I'll do the tests and make the changes.

fulg

@dc42 said in Printer pausing between commands:

[...] Next time the problem occurs, please check whether when when you do a software reset of the printer (e.g. M999 or Emergency Stop), the DueX is recognised afterwards [...].

I can reproduce this problem easily, and every time soft-resetting the Duet via M999 was enough to get the printer back in operation. I did not issue M115 explicitly but my setup uses 4 Z motors on the Duex and it always worked fine after a soft reset (so the Duex was recognized).

My wiring is as per the documentation, VIN/GND to the Duet then short wires to the Duex. I can flip that around if needed.

dc42

@fulg said in Printer pausing between commands:

I can reproduce this problem easily, and every time soft-resetting the Duet via M999 was enough to get the printer back in operation. I did not issue M115 explicitly but my setup uses 4 Z motors on the Duex and it always worked fine after a soft reset (so the Duex was recognized).

If that's the case then there is hope that recovery from the i2C communication breakdown may be possible. But please check with M115 next time you have this issue and do a soft reset.

My wiring is as per the documentation, VIN/GND to the Duet then short wires to the Duex. I can flip that around if needed.

gnydick

@dc42 I found that a loose connection on my main board caused my problem. I don't remember if it was a sensor, a fan, or a thermistor, but I found it, reproduced, snugged it up, and it's been fine.

deckingman

OK, this happened again for me. Sequence as follows. Turn on printer. Home all. Then I changed a roll of filament simply by cutting the existing filament, heating the hot end to 190 deg C and feeding a few mm of the new filament by rotating the extruder gears by hand until the hobbed bolts gripped it. Then I lowered the bed by 100mm using DWC and extruded 300mm of filament through DWC to purge out the old filament. Then I ran homeall.g again and it was during this second homing that I started getting 5 to 10 second pauses between moves. Ran M122 and sure enough noticed I2C errors as follows:

I2C nak errors 0, send timeouts 4917, receive timeouts 0, finishTimeouts 4917

Ran M999 to reset. Then ran M115 which reported the following :

FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.03beta2 ELECTRONICS: Duet Ethernet 1.0 or 1.01 + DueX5 FIRMWARE_DATE: 2019-02-16b1

So the software reset fixed the issue and the Duex5 was immediately recognised again.

At least I know I can run M199 and don't have to cycle the power but..........