Posts made by martinv

I thought I'd post an update on the enclosure heater design. While I still don't have an enclosure for the Duet3D delta printers I've built, I have an enclosure on a Prusa i3 that I do heat, using the same heater controller design.

Splash screen:

The unit measures temperature, current flow through the heater element fan and RPM of the 'mixer' fan. I have only briefly hooked up the serial port and it wasn't working, so something to investigate there. So it's all manual for now.

Driving the mains powered heater element is handled by a separate box using a relay.

@droftarts the parts arrived in due course and here is the made up adapter cable. I'm happy with it.

Note to all, this cable carries mains voltage and should be tucked out of the way and safely covered where you cannot touch it. This photo is with the cover removed for photo purposes.

This is not specific to a Duet powered printer, but I thought I'd write about it here anyway.

TL;DR Stop your delta printer effector crashing into the bed at power off using this small part.

For a while I've been tinkering with a Tevo Little Monster that I "repowered" with a Duet Mini 5+ board. The printer uses a BL Touch for sensing bed height. What I have found is that when the printer was powered off, the effector and arms would sometimes start to slide down and hit the print surface with a thunk. This wasn't the end of the world, but when powering the printer back on the BL Touch performs a self test, and with the effector firmly on the print surface this self test fails. The upshot is having to turn the printer off again, raise the effector off the bed by hand, and, while holding it off the bed, reach up and power on the printer.

More recently I modded another Little Monster with another Duet Mini 5+ board, and gave it 1.5m rails instead of the 1m rails on the original. This printer has the same problem when the power is turned off, except now it's even harder to reach the power switch on the top of the machine without raising the effector a long way up. A hassle more than anything. Anyway I wondered about how I could fix this issue and here is my solution.

It's a flexible bracket that has enough resistance to stop the arms falling at power off, but not so much resistance as to stop the arms moving while under power. I position it a couple of mm below the rear carriage while the effector is in the parked position.

As these printers use 80x40mm C-beams the bracket I designed works with those only, however I think the idea could be applied to any other design. It's possible others have come up with something similar, but I didn't find anything in my searching. As is often the case the biggest problem may be figuring out what it's called!

Anyway, here are some photos. I use two screws with T-nuts to hold it on the rail.

Here is a photo of the two monsters, showing the bracket in place.

@droftarts

As alternatives, and for which I'll use to make an adapter cable, I found these:

https://www.aliexpress.com/item/1005004265820177.html

They are described as 63080 with 6.3mm pitch. This seems, maybe to be something like a Molex Minifit. Maybe. Who knows with Ali Express. I'll have a close look at it when it arrives. I suspect it will be OK for voltage (230V here) and current (surely at most 2A for the TLM heater).

I would have ordered something nice from Digikey, but in the past I have spent a lot of time and almost lost my sanity trying to find housings, both male and female, and terminals to suit the wire gauge, all which fit together properly and for which I have a crimp tool. The Ali Express store RiccoDi seem to have lots of "sets" including male, female, and terminals which really helps with the headache.

This is the last piece of the puzzle for the printer conversion to 1.5m rails. I really hope it works and produces some at least half way decent prints.

@martinv

Ahh rats, I think I found it on Digikey. 6.2mm pitch apparently. Unfortunately it seems to be obsolete.

Molex part 351-43-0201

@droftarts

I measured the pitch again today and get 6.1mm, so maybe it's actually a 6mm pitch. A bit unusual. Notice also the half rounded housing keying. After much searching I've found that the rounded keying is unusual; most keyed connectors seem to use 45 degree angles.

Here's another photo; having real trouble taking a nice shot alas. I'll have a look on Digikey for 6mm pitch housings...

Another thing I could do is instead of making a complete new cable, or splicing the old one with some nasty solder joint would be to use the cable I have to make a short adapter to a new (and importantly, obtainable) connector. Kind of like...

heat bed--->X X<---->known male/known female<------- ... 2m to power supply end.

Hi everyone,

My Google-Fu is failing me. Does anyone have an idea of what connector this is in the photo? My measurement of the pitch is 5.9mm (difficult to measure exactly as it's only 2-way).

For the whole story, I have a Tevo Little Monster delta where I have lengthened the rails. So now I have to lengthen all the cables. For the (mains powered) bed I'd rather build a complete new power cable rather than splice the old one. I could change to a different connector and be done with it, but Ideally I'll keep the original as I have a number of these printers and I'd like the possibility of easily swapping the beds.

@dc42 Thanks for the reply. I took a look at the link, but decided that's quite a departure from the Arduino and would be quite a lot of work to re-implement everything for a new development environment that's otherwise low on my radar. I'll hopefully set up a quick test in the coming days to have a look at the M118 command in more depth.

@droftarts Ahh! I think I might have found something useful - M118.

Eg. M118 P2 S"SET_TEMP 60"

This looks to send the string "SET_TEMP 60" to serial port 2 of the Duet, which I could pick up using the Arduino. Not sure yet how I could send info in the other direction though; like chamber presently at 53C. Or how I could get the Duet to wait until the temperature hits 60.

@droftarts Hmm, having had a look at those two projects as well as generally reading up on PanelDue it looks to me like the Duet sends status information (bed, hotend temperatures etc.) to the PanelDue and the PanelDue sends control information like axis movements to the Duet. So if you're wanting to get in the middle of that, it's all good. I'm not presently seeing how I might use this for a chamber heater interface however. The communication looks to be in the wrong direction, as in the Duet might tell the PanelDue the chamber temperature, not the other way round. Am I missing something?

What I kind of need is a way to see the G-code "as it goes by" to the printer so that I can control the chamber heater. Then somehow to report the chamber temperature back to the Duet. Hmm...

@droftarts the serial port sounds like a good idea to me. As you say there is the opportunity for feedback. Thanks for the idea!

Hi everyone. I have been experimenting with an Arduino controlled active chamber heater for a Prusa i3. This has been successful and so my next step is to build a chamber heater for my Duet 3 Mini 5+ delta machine. This got me thinking as to how I might control the chamber heater. Presently the Arduino
does everything, so brings the chamber up to temperature and then I start the printer printing. Then later when I see the print is done I can slowly cool the part down. All very manual.

For the Duet I'm thinking there is possibly a better way to do this. So I took a look in the Duet instructions and I see info on how to connect a simple chamber heater with thermistor and heating element. The thing is my chamber heater is more elaborate (Eg. multiple independently controlled fans) and so it would be better if the Duet could somehow tell the Arduino the desired temperature and the Arduino could report back the current temperature. Or something like that. I'm wondering if there is a meaningful way to do this and how. My brief searches suggest that canbus is used by a number of external boards, but if I went down this path would this require changes to the Duet firmware?

On one hand I have experience building and writing code for canbus devices for my day job. On the other hand, I don't want to embark on a massive mission.

@KenW interesting. Well it's been about a month now and I haven't had the controller WiFi issue at all since then, so it seems that avoiding allocating Wi-Fi channel 1 on the access point has indeed turned out to be a successful workaround. I mention this for anyone else having issues.

I decided that this was good enough and have ordered another Duet 3 Mini 5+ WiFi for my next Tevo Little Monster upgrade/conversion.

I haven't tried changing the firmware to the latest beta yet, but I have tried changing the configuration on the access point nearest the controller. I've changed it so that while it still assigns the WiFi channel automatically, it now avoids channel 1. See https://docs.duet3d.com/en/User_manual/Troubleshooting/WiFi_troubleshooting

It has been going a couple of days now without getting irretrievably stuck. This is longer than it usually lasts, so I'm hopeful. The log still shows lost connections, but it seems to be recovering each time:

WiFi module is connected to access point gadget67, IP address 192.168.2.207
Error: WiFi module reported: Lost connection, auto reconnecting
Error: WiFi module reported: Timed out while trying to connect to gadget67
WiFi module is connected to access point gadget67, IP address 192.168.2.207
Error: WiFi module reported: Lost connection, auto reconnecting
Error: WiFi module reported: Timed out while trying to connect to gadget67
WiFi module is connected to access point gadget67, IP address 192.168.2.207
Error: WiFi module reported: Lost connection, auto reconnecting
Error: WiFi module reported: Timed out while trying to connect to gadget67
WiFi module is connected to access point gadget67, IP address 192.168.2.207
Error: WiFi module reported: Lost connection, auto reconnecting
Error: WiFi module reported: Timed out while trying to connect to gadget67
WiFi module is connected to access point gadget67, IP address 192.168.2.207
Error: WiFi module reported: Lost connection, auto reconnecting
Error: WiFi module reported: Timed out while trying to connect to gadget67
WiFi module is connected to access point gadget67, IP address 192.168.2.207
Error: WiFi module reported: Lost connection, auto reconnecting
Error: WiFi module reported: Timed out while trying to connect to gadget67
WiFi module is connected to access point gadget67, IP address 192.168.2.207
Error: WiFi module reported: Lost connection, auto reconnecting
Error: WiFi module reported: Timed out while trying to connect to gadget67
WiFi module is connected to access point gadget67, IP address 192.168.2.207
Error: WiFi module reported: Lost connection, auto reconnecting

If this works then that's great, but it would also be lame that it crashes if trying to operate on Wifi channel 1 (for whatever reason).

@danzaywer OK the problem resurfaced and I tried M552 S0 then M552 S1 and that brought it back to life. So it looks like either M552 S-1 or M552 S0 followed by M552 S1 works for me at least.

I'm running WiFi firmware version 1.27. I hope to try the very latest some time today.

@danzaywer The M552 S-1 is what I'm using. I saw this mentioned elsewhere in the forums when people had WiFi problems. Looking in the reference [https://docs.duet3d.com/User_manual/Reference/Gcodes#m552-set-ip-address-enabledisable-network-interface](link url) I see:

Snnn 0 = disable networking, 1 = enable networking as a client, 2 = enable networking as an access point , -1 = disable WiFi module

So there is a difference between disabling the networking and disabling the WiFi module, but the specific differences are not clear to me. If M552 S0 is working for you... Maybe I'll try it next time my controller gets stuck.

Looks like the new microSD card didn't help - the controller has done the same thing again:

WiFi module is idle
Error: WiFi module reported: network scan failed
WiFi module is idle
Error: failed to retrieve WiFi status message: SPI timeout
WiFi module is idle
Error: failed to change WiFi mode: SPI timeout
m122
...
= WiFi =
Interface state: disabled
Module is disabled
Failed messages: pending 0, notready 0, noresp 4
Socket states: 0 0 0 0 0 0 0 0
ok

Looks like I'll be trying the very latest firmware next...

@droftarts interesting. I took a look at all that and have decided to try another microSD card first. Let's see how that goes.

@danzaywer It's curious that both you and I posted messages at almost the same time. I'm also seeing the message "Error: failed to retrieve WiFi status message: SPI timeout" appearing in the serial output from the controller (I'm connecting via USB; I don't have a display), with the WiFi interface state turning to "disabled" after that and so no response to pings etc. For me power cycling fixes it, as does sending:

m552 s-1
m552 s1

I wonder if there is a firmware bug where the recovery from an SPI timeout is not being handled properly. I think first I'll look at trying the latest firmware, and if it's still doing it I guess have a look at the code if that's available. I'm new to Duet so not sure if the code's available but I guess I'll find out.

One thing I'm wondering, how many WiFi access points do you have on the same SSID? Is it just one, or do you have multiple?

My post FWIW [https://forum.duet3d.com/topic/34030/duet-3-mini-5-wifi-losing-network-connection-never-to-return](link url)

Hi everyone,

I have been experiencing an issue with the Duet controller in the printer I recently converted to use a Mini 5+ WiFi.

[https://forum.duet3d.com/topic/33758/duet-3-mini-5-tevo-little-monster-conversion](link url)

The issue concerns the Wi-Fi connection. After running for a day or even a few hours it will disappear from my network and I can no longer ping it. The green light on the Mini 5+ is not lit when this happens. To get it back I power cycle and all is well, until the next time.

I have tried pinging the controller from a PC in an attempt to 'keep it alive', and that works very well. I set up a ping and left that running for it must have been more than a week, and no problems. Then once I stop the ping, a few hours later I check and no more ping responses. So I could keep pinging but that's a bit lame. I also want to buy another Duet controller for another printer but I'm hesitant to buy the WiFi one again if it's going to behave like this, yet I want WiFi if at all possible rather than the Ethernet version.

So I hooked up a PC to monitor the USB interface, recording m122 output before and after the issue. Here is the log. Maybe someone can help identify a way to fix this problem.

FWIW I have other brand WiFi connected printers and am not seeing network issues with them.

The M596, M593 and M915 commands in there you can ignore - I was reading the G-code documentation and trying out commands. Then after that I printed a calibration cube, but it failed (filament break), so I restarted it. The cube printed to completion. Nothing happened after that until the issue where the first Error: line seems to be the WiFi module losing connection. Then it times out, then no known networks, then it gets stuck in a loop where the network scan fails. When I found it the next day I ran m122 and found indeed no WiFi. Then I tried M552 S-1 and M552 S1 to restart WiFi and that brought everything back to life.

Any help appreciated.

-Martin

m122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.4.6 (2023-07-21 14:09:13) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: 8BVJM-P196U-D65J0-40KMN-2H03Z-ZVMP8
Used output buffers: 1 of 40 (16 max)
=== RTOS ===
Static ram: 103712
Dynamic ram: 109796 of which 76 recycled
Never used RAM 28032, free system stack 148 words
Tasks: NETWORK(ready,15.1%,221) HEAT(notifyWait,0.0%,358) Move(notifyWait,0.2%,276) CanReceiv(notifyWait,0.0%,941) CanSender(notifyWait,0.0%,335) CanClock(delaying,0.0%,342) TMC(notifyWait,0.7%,80) MAIN(running,82.9%,400) IDLE(ready,0.3%,30) AIN(delaying,0.8%,265), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 06:29:00 ago, cause: power up
Last software reset at 2023-10-19 17:09, reason: User, GCodes spinning, available RAM 28128, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
MCU revision 3, ADC conversions started 23340129, completed 23340128, timed out 0, errs 0
Step timer max interval 1490
MCU temperature: min 22.8, current 23.3, max 23.9
Supply voltage: min 24.2, current 24.4, max 24.4, 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, read errors 0, write errors 0, ifcnt 12, reads 23413, writes 3, timeouts 0, DMA errors 0, CC errors 0
Driver 1: standstill, SG min 0, read errors 0, write errors 0, ifcnt 12, reads 23414, writes 3, timeouts 0, DMA errors 0, CC errors 0
Driver 2: standstill, SG min 0, read errors 0, write errors 0, ifcnt 12, reads 23414, writes 3, timeouts 0, DMA errors 0, CC errors 0
Driver 3: standstill, SG min 0, read errors 0, write errors 0, ifcnt 9, reads 23417, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 4: standstill, SG min 0, read errors 0, write errors 0, ifcnt 9, reads 23416, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 5: not present
Driver 6: not present
Date/time: 2023-10-31 17:21:56
Cache data hit count 4294967295
Slowest loop: 271.85ms; fastest: 0.08ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 6.4ms, write time 6.6ms, max retries 0
=== Move ===
DMs created 83, segments created 4, maxWait 20428569ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 45283, completed 45283, 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
Heater 1 is on, I-accum = 0.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 ready with "m122" 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
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== CAN ===
Messages queued 26419, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 18 (min 18), ts 14677/0/0
Tx timeouts 0,0,14677,0,0,11742 last cancelled message type 30 dest 127
=== Network ===
Slowest loop: 286.90ms; fastest: 0.06ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
= WiFi =
Interface state: active
Module is connected to access point 
Failed messages: pending 0, notready 0, noresp 14
WiFi firmware version 1.27
WiFi MAC address d8:bf:c0:14:e6:01
WiFi Vcc 3.38, reset reason Power up
WiFi flash size 2097152, free heap 25968
WiFi IP address 192.168.2.207
WiFi signal strength -50dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

m586
CORS disabled
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
m593
Input shaping is disabled
m915
Driver 0.0: stall threshold 1, steps/sec 200, coolstep 0, action on stall: none
Driver 0.1: stall threshold 1, steps/sec 200, coolstep 0, action on stall: none
Driver 0.2: stall threshold 1, steps/sec 200, coolstep 0, action on stall: none
Driver 0.3: stall threshold 1, steps/sec 200, coolstep 0, action on stall: none
Driver 0.4: stall threshold 1, steps/sec 200, coolstep 0, action on stall: none
Driver 0.5: stall threshold 1, steps/sec 200, coolstep 0, action on stall: none
Driver 0.6: stall threshold 1, steps/sec 200, coolstep 0, action on stall: none
m915
Driver 0.0: stall threshold 3, steps/sec 200, coolstep 0, action on stall: raise event
Driver 0.1: stall threshold 3, steps/sec 200, coolstep 0, action on stall: raise event
Driver 0.2: stall threshold 3, steps/sec 200, coolstep 0, action on stall: raise event
Driver 0.3: stall threshold 1, steps/sec 200, coolstep 0, action on stall: none
Driver 0.4: stall threshold 1, steps/sec 200, coolstep 0, action on stall: none
Driver 0.5: stall threshold 1, steps/sec 200, coolstep 0, action on stall: none
Driver 0.6: stall threshold 1, steps/sec 200, coolstep 0, action on stall: none
Calibrated 6 factors using 13 points, (mean, deviation) before (0.115, 0.088) after (-0.000, 0.021)
Resume state saved
Cancelled printing file 0:/gcodes/xyzCalibration_cube.gcode, print time was 0h 6m
Calibrated 6 factors using 13 points, (mean, deviation) before (-0.023, 0.029) after (-0.000, 0.027)
Finished printing file 0:/gcodes/xyzCalibration_cube.gcode, print time was 0h 50m
Error: WiFi module reported: Lost connection, auto reconnecting
Error: WiFi module reported: Timed out while trying to connect to gadget67
Error: WiFi module reported: no known networks found
WiFi module is idle
Error: WiFi module reported: network scan failed
WiFi module is idle
Error: WiFi module reported: network scan failed
WiFi module is idle
Error: WiFi module reported: network scan failed

[deleted 146000 repeated lines...]

WiFi module is idle
Error: WiFi module reported: network scan failed
WiFi module is idle
Error: failed to retrieve WiFi status message: SPI timeout
WiFi module is idle
Error: failed to change WiFi mode: SPI timeout
m122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.4.6 (2023-07-21 14:09:13) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: 8BVJM-P196U-D65J0-40KMN-2H03Z-ZVMP8
Used output buffers: 1 of 40 (25 max)
=== RTOS ===
Static ram: 103712
Dynamic ram: 109796 of which 76 recycled
Never used RAM 27504, free system stack 118 words
Tasks: NETWORK(ready,11.6%,201) HEAT(notifyWait,0.6%,326) Move(notifyWait,3.5%,265) CanReceiv(notifyWait,0.0%,941) CanSender(notifyWait,0.0%,334) CanClock(delaying,0.3%,342) TMC(notifyWait,15.0%,72) MAIN(running,50.4%,87) IDLE(ready,0.8%,30) AIN(delaying,18.0%,263), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 21:29:32 ago, cause: power up
Last software reset at 2023-10-19 17:09, reason: User, GCodes spinning, available RAM 28128, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
MCU revision 3, ADC conversions started 77372389, completed 77372388, timed out 0, errs 0
Step timer max interval 1491
MCU temperature: min 20.1, current 20.2, max 29.9
Supply voltage: min 23.3, current 24.4, max 24.4, 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, read errors 0, write errors 0, ifcnt 23, reads 25516, writes 11, timeouts 0, DMA errors 0, CC errors 0
Driver 1: standstill, SG min 0, read errors 0, write errors 0, ifcnt 23, reads 25515, writes 11, timeouts 1, DMA errors 0, CC errors 0, failedOp 0x71
Driver 2: standstill, SG min 0, read errors 0, write errors 0, ifcnt 23, reads 25515, writes 11, timeouts 0, DMA errors 0, CC errors 0
Driver 3: standstill, SG min 0, read errors 0, write errors 0, ifcnt 22, reads 25513, writes 13, timeouts 0, DMA errors 0, CC errors 0
Driver 4: standstill, SG min 0, read errors 0, write errors 0, ifcnt 9, reads 25527, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 5: not present
Driver 6: not present
Date/time: 2023-11-01 08:22:29
Cache data hit count 4294967295
Slowest loop: 264.87ms; fastest: 0.11ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 7.0ms, write time 132.7ms, max retries 0
=== Move ===
DMs created 83, segments created 26, maxWait 4494566ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 82601, completed 82601, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 8], 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 ready with "m122" 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
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== CAN ===
Messages queued 486290, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 18 (min 18), ts 270161/0/0
Tx timeouts 0,0,270161,0,0,216129 last cancelled message type 30 dest 127
=== Network ===
Slowest loop: 542.08ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 0 of 8
= WiFi =
Interface state: disabled
Module is disabled
Failed messages: pending 0, notready 0, noresp 18
Socket states: 0 0 0 0 0 0 0 0

M552 S-1

M552 S1

WiFi module started
WiFi module is connected to access point gadget67, IP address 192.168.2.207

m122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.4.6 (2023-07-21 14:09:13) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: 8BVJM-P196U-D65J0-40KMN-2H03Z-ZVMP8
Used output buffers: 1 of 40 (25 max)
=== RTOS ===
Static ram: 103712
Dynamic ram: 109796 of which 76 recycled
Never used RAM 27504, free system stack 118 words
Tasks: NETWORK(ready,112.6%,201) HEAT(notifyWait,1.1%,326) Move(notifyWait,0.1%,265) CanReceiv(notifyWait,0.0%,941) CanSender(notifyWait,0.0%,334) CanClock(delaying,0.7%,342) TMC(notifyWait,32.0%,72) MAIN(running,198.8%,87) IDLE(ready,0.0%,30) AIN(delaying,37.9%,263), total 383.2%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 47:30:08 ago, cause: power up
Last software reset at 2023-10-19 17:09, reason: User, GCodes spinning, available RAM 28128, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
MCU revision 3, ADC conversions started 171008513, completed 171008512, timed out 0, errs 0
Step timer max interval 728
MCU temperature: min 20.1, current 25.5, max 27.9
Supply voltage: min 24.3, current 24.3, max 24.4, 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, read errors 0, write errors 0, ifcnt 23, reads 11415, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 1: standstill, SG min 2, read errors 0, write errors 0, ifcnt 23, reads 11415, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 2: standstill, SG min 2, read errors 0, write errors 0, ifcnt 23, reads 11415, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 3: standstill, SG min 0, read errors 0, write errors 0, ifcnt 22, reads 11415, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 4: standstill, SG min 0, read errors 0, write errors 0, ifcnt 9, reads 11415, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 5: not present
Driver 6: not present
Date/time: 2023-11-02 10:23:05
Cache data hit count 4294967295
Slowest loop: 99.98ms; fastest: 0.13ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 3.3ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 26, maxWait 0ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 82601, completed 82601, 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 ready with "m122" 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
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== CAN ===
Messages queued 842452, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 18 (min 18), ts 468029/0/0
Tx timeouts 0,0,468029,0,0,374423 last cancelled message type 4514 dest 127
=== Network ===
Slowest loop: 12.27ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 0 of 8
= WiFi =
Interface state: active
Module is connected to access point 
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.27
WiFi MAC address d8:bf:c0:14:e6:01
WiFi Vcc 3.38, reset reason Power up
WiFi flash size 2097152, free heap 26048
WiFi IP address 192.168.2.207
WiFi signal strength -52dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0