How to test duex.pwm5

dc42

@trobison said in How to test duex.pwm5:

Other interesting behaviour since upgrading to Version 3.4. Sending a M122 causes the network to drop out and then return. I didn’t get this Version 3.3. Is this new and normal?

No, that's not intentional. Does the M122 command return a full report?

Please verify that you are running the 3.4.0 final release. There was a bug with driving servos in some of the 3.4 beta and RC versions.

trobison

@dc42 Sorry, I though I had the output of M122. Here is the output from the console when I powered up the printer, then sent a M122 from the console. Midway down you can see the network drop out after M122 has been sent, then the results from M122. I believe it is running version 3.4.0.

07/04/2022, 22:31:37	=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.0 (2022-03-15 18:58:31) running on Duet Ethernet 1.02 or later + DueX5
Board ID: 0JD0M-9P6M2-NWNS0-7J9DJ-3SJ6S-K90RJ
Used output buffers: 2 of 24 (19 max)
=== RTOS ===
Static ram: 23868
Dynamic ram: 73160 of which 0 recycled
Never used RAM 14788, free system stack 118 words
Tasks: NETWORK(ready,23.8%,226) HEAT(notifyWait,0.1%,332) Move(notifyWait,0.0%,285) DUEX(notifyWait,0.0%,24) MAIN(running,75.1%,440) IDLE(ready,1.0%,30), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:01:13 ago, cause: power up
Last software reset at 2022-04-07 16:44, reason: User, GCodes spinning, available RAM 15260, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 17.5, current 22.2, max 22.4
Supply voltage: min 24.0, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0
Driver 1: standstill, SG min 0
Driver 2: standstill, SG min 0
Driver 3: standstill, SG min n/a
Driver 4: standstill, SG min n/a
Driver 5: standstill, SG min n/a
Driver 6: standstill, SG min n/a
Driver 7: standstill, SG min 0
Driver 8: standstill, SG min n/a
Driver 9: standstill, SG min n/a
Driver 10: 
Driver 11: 
Date/time: 2022-04-07 22:31:33
Cache data hit count 2629899681
Slowest loop: 6.55ms; fastest: 0.16ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 4.4ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 11, maxWait 44815ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 20, completed 20, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Segments left: 0
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
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== DueX ===
Read count 1, 0.82 reads/min
=== Network ===
Slowest loop: 23.75ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 2 of 8
Interface state active, link 100Mbps full duplex

07/04/2022, 22:31:36	Connection established
07/04/2022, 22:31:36	Connection interrupted, attempting to reconnect...
Operation failed (Reason: Service Unavailable)

07/04/2022, 22:31:34	M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.0 (2022-03-15 18:58:31) running on Duet Ethernet 1.02 or later + DueX5
Board ID: 0JD0M-9P6M2-NWNS0-7J9DJ-3SJ6S-K90RJ
Used output buffers: 2 of 24 (19 max)
=== RTOS ===
Static ram: 23868
Dynamic ram: 73160 of which 0 recycled
Never used RAM 14788, free system stack 118 words
Tasks: NETWORK(ready,23.8%,226) HEAT(notifyWait,0.1%,332) Move(notifyWait,0.0%,285) DUEX(notifyWait,0.0%,24) MAIN(running,75.1%,440) IDLE(ready,1.0%,30), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:01:13 ago, cause: power up
Last software reset at 2022-04-07 16:44, reason: User, GCodes spinning, available RAM 15260, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 17.5, current 22.2, max 22.4
Supply voltage: min 24.0, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0
Driver 1: standstill, SG min 0
Driver 2: standstill, SG min 0
Driver 3: standstill, SG min n/a
Driver 4: standstill, SG min n/a
Driver 5: standstill, SG min n/a
Driver 6: standstill, SG min n/a
Driver 7: standstill, SG min 0
Driver 8: standstill, SG min n/a
Driver 9: standstill, SG min n/a
Driver 10: 
Driver 11: 
Date/time: 2022-04-07 22:31:33
Cache data hit count 2629899681
Slowest loop: 6.55ms; fastest: 0.16ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 4.4ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 11, maxWait 44815ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 20, completed 20, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Segments left: 0
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
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== DueX ===
Read count 1, 0.82 reads/min
=== Network ===
Slowest loop: 23.75ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 2 of 8
Interface state active, link 100Mbps full duplex
07/04/2022, 22:30:54	Connected to 192.168.10.60

Phaedrux

I can't remember from your previous thread, but did you downgrade to 3.3 and see if it works correctly again?

trobison

@phaedrux Yes. The same issue. I was asked to send my details to the warranty team. Thank you for following up.
Regards,

dc42

@trobison we now have another report of a user not able to operate a BLTouch connected to duex.pwm5. So there may be a bug in firmware 3.4. I will test it on Monday.

Phaedrux

@dc42 said in How to test duex.pwm5:

@trobison we now have another report of a user not able to operate a BLTouch connected to duex.pwm5. So there may be a bug in firmware 3.4. I will test it on Monday.

In their case with the troodon board it is now working correctly, so seemingly not related.

dc42

@trobison I have now tested a BLTouch connected to duex.pwm5 and to duex.pwm4. In both cases it is working correctly, using commands M3280 P0 S10 and M280 P0 S90.

trobison

Cheers guys. I installed a replacement Duex5 board. All working nicely now. I have a question. Is there firmware I have to worry about on the extension board, or is it just that, an extension to the DUET 2 board and firmware is installed there.

dc42

@trobison there is no firmware on the DueX expansion board.

trobison

@dc42 Many thanks.