Pausing mid print and elsewhere.
-
Just turned it on and printed the same model with the same configuration and the print is way past the same point where it failed before, so I dont believe this is a problem with the G code or machine configuration. Especially since it happens even during homing. Doesnt matter why its moving, it starts pausing and doesnt stop until I restart the Duet
-
@frank26080115 It literally stops for 3-4 seconds. I will get a video. Everywhere it stops leaves a blob of plastic. It just dawned on me that it pauses during homing too.
-
Heres my settings from Config.g
(Printing now without a problem)
M92 X200.00 Y200.00 Z1600.00 E2660 ; Set steps per mm
M566 X15 Y15 Z.5 E20 ; Set maximum instantaneous speed changes (mm/min)
M201 X1500.00 Y1500.00 Z100.00 E1500.00 ; Set accelerations (mm/s^2)
M203 X25000.00 Y25000.00 Z1200.00 E5000.00 ; Set maximum speeds (mm/min) -
@henrydara This sounds very much like the I2C errors that a few of us have experienced. See this thread https://forum.duet3d.com/topic/7269/duet-sometimes-really-slow-i2c-error-or
The next time it happens, run M122 and look for I2C errors. That will confirm if it is indeed the same problem or otherwise.
There are a number of suggestions to try in the thread I linked too. Suggest you try them all but I fitted the resistors that DC42 recommended, and thus far have had no recurrence of the problem.
-
@henrydara said in Pausing mid print and elsewhere.:
M566 X15 Y15 Z.5 E20 ; Set maximum instantaneous speed changes (mm/min)
I think you've set your jerk values as if they were in mm/s rather than mm/min. Try multiplying your values by 60 and try again. I think that would be what you actually want.
-
@phaedrux Thanks, you might be right.
-
@deckingman Thanks, that sounds like my problem. I have plenty to cleanup in my wiring, so now is as good a time as any.
-
Just happened again a few hours into a print. Ran M122 (see below) but I2C looks just fine as far as I can tell.
I fixed my jerk values, and it did run smoother, but not sure if its the culprit here.
Did the same thing as above (stopping and splotching on the print) so had to cancel the print.
Again, when the Duet board starts doing this, it happens even during the homing sequence, and it stop until I reboot the board. Its like the Duet board has a stroke until it gets restarted.
Oh, and I did get my wiring cleaned up, and everything grounded (have to just take my word)
Heres my config and rev info...
M92 X160.00 Y160.00 Z1600.00 E2660 ; Set steps per mm
M566 X600 Y600 Z.5 E20 ; Set maximum instantaneous speed changes (mm/min)
M201 X1500.00 Y1500.00 Z100.00 E1500.00 ; Set accelerations (mm/s^2)
M203 X25000.00 Y25000.00 Z1200.00 E5000.00 ; Set maximum speeds (mm/min)
M204 R1000 ; Set Retract acceleration (mm/s^2)Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
Firmware Electronics: Duet WiFi 1.02 or later + DueX5
Firmware Version: 2.03beta3 (2019-03-25b6)
WiFi Server Version: 1.21
Web Interface Version: 1.22.6=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.03beta3 running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DGM-917NK-F2MS4-7J9FG-3SJ6Q-9ZUNG
Used output buffers: 4 of 20 (20 max)
=== RTOS ===
Static ram: 25632
Dynamic ram: 94832 of which 0 recycled
Exception stack ram used: 596
Never used ram: 10012
Tasks: NETWORK(ready,524) HEAT(blocked,1236) MAIN(running,3776) IDLE(ready,196)
Owned mutexes:
=== Platform ===
Last reset 08:47:11 ago, cause: software
Last software reset at 2019-03-30 14:33, reason: User, spinning module GCodes, available RAM 3784 bytes (slot 1)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 28
Free file entries: 9
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 33.6, current 34.0, max 34.1
Supply voltage: min 23.7, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max 0/1023
Driver 4: standstill, SG min/max not available
Driver 5: standstill, SG min/max not available
Driver 6: standstill, SG min/max not available
Driver 7: standstill, SG min/max not available
Driver 8: standstill, SG min/max not available
Driver 9: standstill, SG min/max not available
Date/time: 2019-03-30 23:52:14
Cache data hit count 4294967295
Slowest loop: 63.05ms; fastest: 29.20ms
I2C nak errors 0, send timeouts 3035, receive timeouts 0, finishTimeouts 3035
=== Move ===
Hiccups: 0, FreeDm: 169, MinFreeDm: 155, MaxWait: 61ms
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== MainDDARing ===
Scheduled moves: 210148, completed moves: 210133, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
Heater 0 is on, I-accum = 0.1
Heater 1 is on, I-accum = 0.5
=== GCodes ===
Segments left: 0, aux move: no
Stack records: 2 allocated, 0 in use
Movement lock held by null
http is idle in state(s) 0
telnet is idle in state(s) 0
file is idle in state(s) 0
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 174.02ms; fastest: 0.08ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 3 of 8- WiFi -
Network state is running
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.21
WiFi MAC address b4:e6:2d:52:f2:f3
WiFi Vcc 3.49, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 15448
WiFi IP address 10.233.58.102
WiFi signal strength -60dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0
- WiFi -
-
@henrydara There are over 3000 I2C send timeouts. I'm pretty sure that is abnormal. Assuming that you have checked the Vin link wires are short and thick, and that the screws are good and tight, then I suggest you try the resistors that were mentioned in the thread I linked too.
Your description of the problem you are seeing is exactly the same as the problem that I have experienced and since installing those resistors, I have had no recurrence of the issue. -
@deckingman Thanks, I looked right past that one. Need to open my eyes.
-
Please note, on very recent production DueX boards we are already using different i2C pullup resistors, so additional ones should not be added (they might make things worse). The built-in resistors are labeled R52 and R52 and are close to the corner of the board with the 10-pin GPIO header. If they are marked 472 then adding extra resistors is recommended. If they are marked 1001 then do not add extra resistors.
-
Thanks Dave. Mine are marked 472.
I added 2K ohm resistors like the other post said (between 3.3v and TWC/TWD)
Double checked the "thick" wire Ground connection direct between Duet and Duex is good. (12awg, 130mm lead, tug checked)Just had another instance occur mid print.
I2C nak errors 1, send timeouts 33876, receive timeouts 1, finishTimeouts 33875The problem seems to occur when I look at the printer too hard while its printing.
Should I try a different resistor next?
Any other ideas?
-
@henrydara said in Pausing mid print and elsewhere.:
Should I try a different resistor next?
I suggest 1.2K or 1.3K.
Keep stepper motor wiring away from the ribbon cable.
