Posts made by dirtybirdnj

@droftarts YOU ARE THE MAN!

Thank you SO MUCH to everyone in this thread, but you get the gold star for being the one to suggest the antenna.

It worked IMMEDIATELY upon connecting it. I connected over USB and saw the "successfully connected / heres the IP" terminal message I expected. I disconnected USB and powered up via the 24v power supply directly... and it still works!

@Phaedrux thank you for clarifying that I don't need the single quotes anymore due to the macro / no effect by input method

It looks like I can get back to my task of being clueless about how to configure my board... but at least it works! Next steps X/Y config... and then getting a servo to do up down (z 1/0) and I am getting closer to drawing pictures with this heap of metal, motors and pcbs.

I am THRILLED. Happy Monday thank you everyone.

No real progress but I've been diligently testing / trying everything that has been suggested.

I prepared two macros, one with the "force it lowercase" single quotes, and one without.

I also made sure that every line was terminated with a semicolon, and removed any extra whitespace.

WifiAdd.g

; Add default wifi network

M552 S0;		; Disable network module
G4 S5;			; wait 5 seconds
M587 S"'s'l'o't'h'n'e't" P"'d'e'a'l'w'i't'h'i't";
G4 S5;			; wait 5 seconds
M552 S1;		; reenable wifi module

WifiAdd2.g

; Add default wifi network

M552 S0;		; Disable network module
G4 S5;			; wait 5 seconds
M587 S"slothnet" P"dealwithit";
G4 S5;			; wait 5 seconds
M552 S1;		; reenable wifi module

WifiClear.g

; Clear all wifi networks

M552 S0			; Disable network module
G4 S5			  ; wait 5 seconds
M588 S"*"		; Clear all saved wifi networls

M291 R"WIFI networks forgotten." P"You must add a new WIFI network."

Here's the log of me running both of these commands, they both result in the same "failed to connect" over and over again.

M115
FIRMWARE_NAME: RepRapFirmware for Duet 3 Mini 5+ FIRMWARE_VERSION: 3.4.6 ELECTRONICS: Duet 3 Mini5plus WiFi FIRMWARE_DATE: 2023-07-21 14:09:13
ok
M98 P"WifiAdd2.g";
M98 P"WifiAdd2.g";
ok
Error: WiFi module reported: no known networks found
WiFi module is idle
Error: WiFi module reported: no known networks found
WiFi module is idle
Error: WiFi module reported: no known networks found
WiFi module is idle
Error: WiFi module reported: no known networks found
WiFi module is idle
Error: WiFi module reported: Failed while trying to connect to slothnet
WiFi module is idle
Error: WiFi module reported: Failed while trying to connect to slothnet
WiFi module is idle
Error: WiFi module reported: Failed while trying to connect to slothnet
WiFi module is idle
Error: WiFi module reported: Failed while trying to connect to slothnet
WiFi module is idle
M552 S0
ok
M552 S0
ok
Error: WiFi module reported: Failed while trying to connect to slothnet
WiFi module is idle
M552 S0;
ok
M98 P"WifiClear.g";
- WIFI networks forgotten. -
You must add a new WIFI network.
ok
M587;
M587;
Remembered networks: none
ok
M98 P"WifiAdd.g";
ok
Error: WiFi module reported: Failed while trying to connect to slothnet
WiFi module is idle
Error: WiFi module reported: Failed while trying to connect to slothnet
WiFi module is idle
Error: WiFi module reported: Failed while trying to connect to slothnet
WiFi module is idle
Error: WiFi module reported: Failed while trying to connect to slothnet
WiFi module is idle


M552 S0
ok
M552 S0;
ok
Error: WiFi module reported: Failed while trying to connect to slothnet
WiFi module is idle
M115;
FIRMWARE_NAME: RepRapFirmware for Duet 3 Mini 5+ FIRMWARE_VERSION: 3.4.6 ELECTRONICS: Duet 3 Mini5plus WiFi FIRMWARE_DATE: 2023-07-21 14:09:13
ok
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: S4AX7-H296U-D65J0-40KMU-2X03Z-78MGP
Used output buffers: 1 of 40 (1 max)
=== RTOS ===
Static ram: 103712
Dynamic ram: 109156 of which 156 recycled
Never used RAM 28688, free system stack 144 words
Tasks: NETWORK(ready,7.9%,370) HEAT(notifyWait,0.0%,374) Move(notifyWait,0.0%,363) CanReceiv(notifyWait,0.0%,941) CanSender(notifyWait,0.0%,335) CanClock(delaying,0.0%,342) TMC(notifyWait,0.0%,124) MAIN(running,91.2%,463) IDLE(ready,0.1%,30) AIN(delaying,0.8%,272), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:04:31 ago, cause: power up
Last software reset time unknown, reason: StuckInSpinLoop, GCodes spinning, available RAM 15772, slot 0
Software reset code 0x0083 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0000080f BFAR 0xe000ed38 SP 0x20003f88 Task NETW Freestk 4294953423 ok
Stack: 00000000 20003038 10000000 e000e000 20019290 0009fad1 0009f1aa 610d0000 0009f193 203b736d ffffffff 00000000 00067fa3 0a736d30 2002c1a4 ffffffff 200117d0 00000009 0009f247 20004030 2002c1a0 200114c8 0009c48f 2002c1a0 0002d9df 2002c1a4 2000420c
Error status: 0x00
MCU revision 3, ADC conversions started 271236, completed 271236, timed out 0, errs 0
Step timer max interval 742
MCU temperature: min 22.8, current 28.0, max 28.0
Supply voltage: min 0.3, current 0.9, max 1.0, under voltage events: 0, over voltage events: 0, power good: no
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: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 1: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 2: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 3: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 4: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 5: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 6: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Date/time: 1970-01-01 00:00:00
Cache data hit count 572132509
Slowest loop: 3.49ms; fastest: 0.12ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 5.4ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, 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 -1 -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 1356, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 18 (min 18), ts 1356/0/0
Tx timeouts 0,0,1355,0,0,0 last cancelled message type 30 dest 127
=== Network ===
Slowest loop: 1.30ms; 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 idle
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.26
WiFi MAC address f0:08:d1:03:d4:d7
WiFi Vcc 3.40, reset reason Power up
WiFi flash size 2097152, free heap 30216
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
ok

After this I was determined to try to find SOMETHING to report on to try to figure out next steps. I used M929 to turn on event logging and it was... not useful. It just repeated the "can't connect" error but didn't explain why.

I had the idea then of turning on the Wifi with M522 S1 and waiting for it to be active, maybe then the output of M122 Will show something else?

Full M122 output below but wifi info shows reset reason Exception:

= WiFi =
Interface state: changingMode
Module is trying to connect
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.26
WiFi MAC address f0:08:d1:03:d4:d7
WiFi Vcc 3.40, reset reason Exception
WiFi flash size 2097152, free heap 29824
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
ok
MError: WiFi module reported: Failed while trying to connect to slothnet`

Does the exception indicate something is wrong with the wifi? Or is that just the natural state of "failed to connect to network"? Is there some way to update the wifi firmware? What else can I do at this point?

Error: WiFi module reported: Failed while trying to connect to slothnet
WiFi module is idle
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: S4AX7-H296U-D65J0-40KMU-2X03Z-78MGP
Used output buffers: 1 of 40 (17 max)
=== RTOS ===
Static ram: 103712
Dynamic ram: 109156 of which 156 recycled
Never used RAM 28688, free system stack 144 words
Tasks: NETWORK(ready,8.7%,361) HEAT(notifyWait,0.0%,374) Move(notifyWait,0.0%,363) CanReceiv(notifyWait,0.0%,941) CanSender(notifyWait,0.0%,335) CanClock(delaying,0.0%,342) TMC(notifyWait,0.0%,124) MAIN(running,90.5%,383) IDLE(ready,0.0%,30) AIN(delaying,0.8%,272), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:06:41 ago, cause: power up
Last software reset time unknown, reason: StuckInSpinLoop, GCodes spinning, available RAM 15772, slot 0
Software reset code 0x0083 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0000080f BFAR 0xe000ed38 SP 0x20003f88 Task NETW Freestk 4294953423 ok
Stack: 00000000 20003038 10000000 e000e000 20019290 0009fad1 0009f1aa 610d0000 0009f193 203b736d ffffffff 00000000 00067fa3 0a736d30 2002c1a4 ffffffff 200117d0 00000009 0009f247 20004030 2002c1a0 200114c8 0009c48f 2002c1a0 0002d9df 2002c1a4 2000420c
Error status: 0x00
MCU revision 3, ADC conversions started 401510, completed 401508, timed out 0, errs 0
Step timer max interval 743
MCU temperature: min 27.8, current 28.2, max 28.4
Supply voltage: min 0.9, current 0.9, max 1.0, under voltage events: 0, over voltage events: 0, power good: no
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: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 1: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 2: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 3: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 4: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 5: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 6: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Date/time: 1970-01-01 00:00:00
Cache data hit count 849290131
Slowest loop: 3.15ms; fastest: 0.12ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 2.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, 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 -1 -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 159, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 18 (min 18), ts 159/0/0
Tx timeouts 0,0,159,0,0,0 last cancelled message type 30 dest 127
=== Network ===
Slowest loop: 2.00ms; 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: changingMode
Module is trying to connect
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.26
WiFi MAC address f0:08:d1:03:d4:d7
WiFi Vcc 3.40, reset reason Exception
WiFi flash size 2097152, free heap 29824
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
ok
MError: WiFi module reported: Failed while trying to connect to slothnet
WiFi module is idle
5M552 S0

I tried both the single quote delimited version, as well as the plaintext all lowercase versions.

I did this via both the M587 and the M98 P"AddWifi.g" ways and I am still running into the same brick wall

Here is the output of M122 while the wifi module is active (M522 S1)

FIRMWARE_NAME: RepRapFirmware for Duet 3 Mini 5+ FIRMWARE_VERSION: 3.4.6 ELECTRONICS: Duet 3 Mini5plus WiFi FIRMWARE_DATE: 2023-07-21 14:09:13
ok
M98 P"WifiAdd.g"
MError: WiFi module reported: Failed while trying to connect to slothnet
WiFi module is idle
M122
Error: M98: control character in string
Error: Bad command: M
=== 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: S4AX7-H296U-D65J0-40KMU-2X03Z-78MGP
Used output buffers: 1 of 40 (1 max)
=== RTOS ===
Static ram: 103712
Dynamic ram: 109156 of which 360 recycled
Never used RAM 28484, free system stack 145 words
Tasks: NETWORK(ready,8.0%,378) HEAT(notifyWait,0.0%,374) Move(notifyWait,0.0%,363) CanReceiv(notifyWait,0.0%,941) CanSender(notifyWait,0.0%,335) CanClock(delaying,0.0%,342) TMC(notifyWait,0.0%,124) MAIN(running,90.9%,448) IDLE(ready,0.2%,30) AIN(delaying,0.8%,272), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:01:30 ago, cause: power up
Last software reset time unknown, reason: StuckInSpinLoop, GCodes spinning, available RAM 15772, slot 0
Software reset code 0x0083 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0000080f BFAR 0xe000ed38 SP 0x20003f88 Task NETW Freestk 4294953423 ok
Stack: 00000000 20003038 10000000 e000e000 20019290 0009fad1 0009f1aa 610d0000 0009f193 203b736d ffffffff 00000000 00067fa3 0a736d30 2002c1a4 ffffffff 200117d0 00000009 0009f247 20004030 2002c1a0 200114c8 0009c48f 2002c1a0 0002d9df 2002c1a4 2000420c
Error status: 0x00
MCU revision 3, ADC conversions started 90559, completed 90557, timed out 0, errs 0
Step timer max interval 744
MCU temperature: min 24.5, current 29.1, max 29.1
Supply voltage: min 0.3, current 0.9, max 1.0, under voltage events: 0, over voltage events: 0, power good: no
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: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 1: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 2: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 3: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 4: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 5: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 6: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Date/time: 1970-01-01 00:00:00
Cache data hit count 190840772
Slowest loop: 33.70ms; fastest: 0.12ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 5.4ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, 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 -1 -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 453, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 18 (min 18), ts 453/0/0
Tx timeouts 0,0,452,0,0,0 last cancelled message type 30 dest 127
=== Network ===
Slowest loop: 1.25ms; 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: changingMode
Module is trying to connect
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.26
WiFi MAC address f0:08:d1:03:d4:d7
WiFi Vcc 3.40, reset reason Power up
WiFi flash size 2097152, free heap 30056
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
ok
Error: WiFi module reported: Failed while trying to connect to slothnet
WiFi module is idle
M552 S0
ok
Error: WiFi module reported: Didn't find access point while trying to connect to slothnet
WiFi module is idle

@dc42 you are correct that there's an extra trailing single quote, but that's not the issue

@Phaedrux I created the WifiAdd.g and ClearWifi.g macros

I added them to /macros and I got an error saying that the files / macros did not exist.

I added the files to /sys to see if that would work.

While I was doing this I visually observed that SerialTools was CHANGING MY QUOTES after I was typing them. This was an "am I going crazy" moment but it absolutely is happening.

Here is a thread about what I think is the issue, a MacOS setting that helpfully changes quotes for you. I do web development for a living and I've NEVER had an issue with quotes like this before it's completely dumbfounding.

https://apple.stackexchange.com/questions/136402/how-to-disable-smart-quotes

I updated the setting on my machine to NOT do the helpful thing. Just to illustrate here's a block of text I've been using for testing. I can confirm that SerialTools does not change my quotes before I have a chance to hit enter.

M587 S"'s'l'o't'h'n'e't" P"'d'e'a'l'w'i't'h'i't"

M587 S"slothnet" P"dealwithit"

M587 S”slothnet” P"dealwithit”

M587 S”’s’l’o’t’h’n’e’t” P”’d’e’a’l’w’i’t’h’i’t”

'’

‘’

After I changed the quote setting, I reconnected and as before, I cannot run any GCODE command that includes quotes. M98 just doesn't work for me... just like M587.

I want to find something other than SerialTools to use I am glad I didn't pay for it.

M115
Error: M98: control character in string
ok
M115
FIRMWARE_NAME: RepRapFirmware for Duet 3 Mini 5+ FIRMWARE_VERSION: 3.4.6 ELECTRONICS: Duet 3 Mini5plus WiFi FIRMWARE_DATE: 2023-07-21 14:09:13
ok
M98 P"WifiAdd.g"
M98 P"WifiAdd.g"


M115
M115
FIRMWARE_NAME: RepRapFirmware for Duet 3 Mini 5+ FIRMWARE_VERSION: 3.4.6 ELECTRONICS: Duet 3 Mini5plus WiFi FIRMWARE_DATE: 2023-07-21 14:09:13
ok
M587 S"slothnet" P"dealwithit"
M587 S"slothnet" P"dealwithit"
M587
Remembered networks: none
ok
M587
Remembered networks: none
ok

I am trying to get wifi configured for my Duet 3 Mini 1.01

I haven't worked on this project in a few months and I'm trying to dust it off and get it moving again so please forgive me if there's something obvious and dumb in my config / logs

3.5.0-rc.3.txt
3.4.6.txt <-- has M122 output
config.g

I previously kept running into a brick wall getting wifi configured, it would just fail to connect no matter what I did.

I downloaded SerialTools and it worked a lot better than Pronterface did last time I tried.

I used M587 to set the wifi password and IT DID WORK for a few glorious minutes. I saw the new web interface, it's awesome! I was modifying the config and restarting the machine (at least 2-3 times) trying to get it all set up. Then the wifi just... stopped cooperating forever.

I tried doing the M587 / M588 / M522 dance a few times but what I thought I did that fixed it apparently... didn't? My only troubleshooting idea left was upgrading firmware. I did this via the "hold down the power button / usb mass storage" process. I see the new version as expected in M115 output once it restarts.

I upgraded to 3.5.0, didn't realize it was an RC. This did not fix my wifi issue.

I downgraded to 3.4.6 I still cannot for the life of me get the thing to accept a password that works with my wifi.

It seems like it refuses to parse double quote strings that contain single quotes? I never get back an ok response when sending M587 using the lowercase syntax as explained in the docs .

M587 S"slothnet" P"dealwithit"

M587 S"'s'l'o't'h'n'e't" P"'d'e'a'l'w'i't'h'i't'"

I have attached logs from my two sessions using SerialTools on my mac, labeled by firmware version.

The 3.4.6 file includes the output of M122.

I have also attached my config.g

For reference the machine (a plotter) has two motors on one axis, and one on the other.

Hello,

I have a Duet 2 Wifi that's powering a Printrbot Simple Metal.

I currently use the web control UI 100% to control the printer.

I would like to have a few momentary push-button switches that I can use to make the printer run specific GCODE scripts. Here's the ones I want to set up so far:

1. Home All
2. Warm Hotend & Bed to standby temps
3. Pause
4. Resume
5. Firmware Reset / Emergency Stop
6. Start printing "newest" gcode file on SD card

I know it's possible to use some of the GPIO pins on the Duet for control of lights / LEDs and stuff but what I'm hoping to do is wire all these buttons to a raspberry pi, and have it send commands to control the Duet.

Any suggestions on taking advantage of the PanelDue pins vs sending commands over wifi and impersonating the duet web interface?

https://github.com/patrickkuo/PanelPi
https://duet3d.dozuki.com/Wiki/PanelDue

I found an interesting repo where someone seems to have done what I wanted by spoofing the web interface, but their project focus appears to be running a web UI and actuating controls based on that. I want to run a raspi in a headless / command line mode and read GPIO input, and then send commands to the Duet.

Eventually I would also like to use a multi-segment LED matrix to display the layer #, hotend temp, etc. I'd also like to be able to execute arbitrary post commands to send myself slack / sms updates (print is done, printer paused for material change etc) I basically need two things:

1. Get printer info every 60s
2. Send string with GCODE / Macro to run

Thanks!

Hello,

Yesterday I had a print lift off the bed and get stuck to my hotend. I caught it in time to remove the giant blob but while I was doing this the machine experienced some kind of fault and now the Hotend & Bed both read 2000C. I have tried turning the machine on / off with the bed / hotend sensors disconnected and it doesn't make a difference.... web UI still shows 2000C for both.

Additionally I tried searching how to reset heater faults... I found another thread that suggested M562 P1 and M562 P2
https://duet3d.dozuki.com/Wiki/Gcode#M562:_Reset_temperature_fault

This clears the "fault" display in the web UI, but when I power off / on again the fault returns.

Hello! I recently started having issues where my printer would brown out only when using the heated bed. I had been using the bed for many months happily but since a recent firmware update, it just wasn't cooperating. Most of the things I found googling this issue suggested replacing the wiring or PSU, so I figured now is the time for 24v.

I spent $20 on a 240W 10A 24v power supply and it totally fixed my browning out issues. Previously I would get "voltage low" errors until the brownout occurred, but it's now printing like a champ sticking around 24v.

Swapping out was pretty painless, the board accepts 12/24v readily, I had a small little circuit I made to make my bed sensor play nice with the duet and I put a small box I got off amazon that steps 24v down to 12v so I can keep printing now and fix this "less than perfect" thing later.

If you are still on 12v with your duet... upgrade! it's awesome! Heated bed reaches temp SO MUCH FASTER now... fans are louder which leads me to believe they were previously starved for power/voltage.

Hello,

I am working on making a drawbot style machine with an OpenBuilds XY kit and a duet 2. The kit I'm using uses standard NEMA 17s for the X and Y axis, but because it's designed for lasers and other minimal z-axis usage it has nothing to move the pen up and down.

Here's a pic of the kit for reference:

I do have a spare NEMA kicking around I could mount to the carriage, but one of the goals of this machine is to write as fast as possible. I'd prefer to just use a servo since I just need to move a small carriage up / down to control drawing and that would keep the weight of the stuff on the gantry down.

I'm planning on using this awesome design for a 1 axis pen holder, my thought is whether I use a servo or stepper it should be pretty easy to get one of these to "push down" the pen and have the rubber band in the design keep it up off the page while traveling.

I found a threads on here with suggestions and info:

• https://forum.duet3d.com/topic/4853/servos-as-axes - No servo Z-Axis support
• https://forum.duet3d.com/topic/132/servo-support-eventually/5 - Use a servo control board

The most promising one was suggesting using a sparkfun stepper controller board. This should let me move the servo to two distinct positions by turning a GPIO Pin on the duet on/off. Just wanted to get a second opinion that this sounds like a reasonable plan... I assume this means I'll have to have some custom "slicing" that uses different commands instead of G1 Z1, G1 Z1.0 etc. I have worked on some code that turns SVGs into GCODE so it shouldn't be too difficult as long as I understand the GCODE I'm replacing.

Please let me know if you have any suggestions or have done anything like this.

If you want to know what I'm drawing with the robot check out www.robotdrawsyou.com

@phaedrux said in DuetWifi 1.01 Updated to 1.24 - No Z Axis after update:

@dirtybirdnj said in DuetWifi 1.01 Updated to 1.24 - No Z Axis after update:

I just commented out their contents

What did they contain?

I copied the contents of the files over to a scratch pad before I commented them out, here they are. I don't recall setting these up so it seems like something that was on the SD card that the previous firmware didn't run / care about? Not sure... either way I am elated that I had two successful prints tonight!

// deployprobe.g
; Probe deployment routine for Mini Kossel
M564 S0					; don't apply limits
G1 X25 Y93 Z40 F10000	; put probe arm next to belt
G1 X-5 F500				; move probe arm across belt
G1 X12 F1000			; move probe back
G1 X0 Y0 F10000			; move to somewhere sensible
M564 S1					; apply limits again


//retractprobe.g
; Probe retraction routine for Mini Kossel
M564 S0					; don't apply limits
G1 Z40 F10000			; raise head
G1 X-59 Y66 Z35			; move over the post
G1 Z7 F500				; push probe down on post
G1 Z35 F10000			; raise head again
G1 X0 Y0				; move to somewhere sensible
M564 S1					; apply limits again

After taking a look at these I can clearly see it's setting M564 S1 at the end of each which is prob what was causing the "axes not homed" errors! I commented out the M654 H0 in my config.g and it homes the Z with no problem now. These files also account for the "random" x+y movements that were happening with the homing process as well... mysteries solved and case closed.

This thread can be marked solved! Thanks again to @dc42 @Phaedrux for your help!

@phaedrux

Can you try deleting the deployprobe.g and retractprobe.g files?

THIS WORKED The "random movements" issue has been solved! I didn't delete the files I just commented out their contents, but I'll prob remove them soon for good measure.

Still need to run M564 H0 before z-axis is unlocked, but I feel way more confidant about doing some test prints now that the machine is homing correctly and behaving as expected again.

@dc42

Do you mean you always need to run M564 H0 to home the Z axis; or only if you try to home the Z axis before X and Y have been homed?

Yes, this is exactly the case. Please see the screenshot above, I posted a log from the g-code console to document this.

Did you add the S2 parameter to the following command in homez.g as @Phaedrux said?

I did and the S2 allows for upward movement before the probe, but it still refuses to execute the G30 that does Z-probing unless I run M564 H0 first.

@phaedrux

First off thank you so much for your help with this!

Your G31 needs to define the X and Y offset between the probe and the nozzle.

!!!! wow lol seems like a critical thing to be missing... measuring this now and figuring out the distance

@phaedrux said in DuetWifi 1.01 Updated to 1.24 - No Z Axis after update:

I just occured to me now that it looks like you have a duet wifi but are running 1.24? I think you're eligible to upgrade further to 2.03 if you wished.

This was one part of the update that was super confusing, I wasn't sure if the Duet2 and the DuetWifi I have are directly compatible with the firmware offered.

The file I sent during firmware writing using BOSSA was Duet2CombinedFirmware.bin from what appears to be the latest release.

https://github.com/dc42/RepRapFirmware/releases/tag/2.03

@phaedrux

M558 is definiltey responding to the extra settings, but I still have to run M564 H0 to home the z-axis.

Additionally when it does run G30 it does one probe and then rises and dives again moving in x+y+z. In doing so it pushes up past the end-stops making bad noises even though it's already homed the x and y axes.

It seems like it's doing something after the probing, but none of the actions defined in any of the home_.g match what it's doing. What exactly happens when G30 runs and is it dictated by any of these files? Running G29 also causes the machine to push beyond its axes after x and y homing as well.

Here's the latest version of my config:

; Communication and general
M111 S1                            	; Debug off
M550 OldYeller				; Machine name and Netbios name (can be anything you like)
M551 Preprap                        	; Machine password (used for FTP)
;*** If you have more than one Duet on your network, they must all have different MAC addresses, so change the last digits
M540 P0xBE:0xEF:0xDE:0xAD:0xFE:0xED 	; MAC Address
;*** Wifi Networking
M552 S1					; Enable WiFi. Disabled for setup and testing. Enable once set up on your network.

M555 P2                           	; Set output to look like Marlin
M575 P1 B57600 S1			; Comms parameters for PanelDue

G21                                 	; Work in millimetres
G90                                	; Send absolute coordinates...
M83                                 	; ...but relative extruder moves

; Axis and motor configuration
M569 P0 S0                          ; Drive 0 (x motor) goes reverse
M569 P1 S0                          ; Drive 1 (y motor) goes reverse
M569 P2 S0                          ; Drive 2 (z motor) goes reverse
M569 P3 S0                          ; Drive 3 (ext motor) goes reverse
;M569 P4 S1                         ; Drive 4 goes forwards

M350 X16 Y16 Z16 E16 I1             ; set 16x microstepping with interpolation
M574 X1 Y1 Z0 S1		    ; set homing switch configuration (x and y switches, at low end, active high)
M906 X800 Y800 Z800 E800            ; Set motor currents (mA)
M201 X1000 Y1000 Z1000 E100         ; Accelerations (mm/s^2)
M203 X3000 Y3000 Z3000 E600         ; Maximum speeds (mm/min)
M566 X1000 Y1000 Z1000 E50          ; Maximum jerk speeds mm/minute
M208 X200 Y200 Z240                 ; set axis max and high homing switch positions (adjust to suit your machine)
M208 X-0 Y0 Z0 S1                   ; set axis min and low homing switch positions (adjust to make X=0 and Y=0 the edges of the bed)
M92 X80 Y80 Z400 E95                ; set axis steps/mm
G21                                 ; Work in millimetres
G90                                 ; Send absolute coordinates...
M83                                 ; ...but relative extruder moves

; Thermistors
M305 P0 T100000 B3950 R4700 H30 L0	; Put your own H and/or L values here to set the bed thermistor ADC correction
M305 P1 T100000 B3974 R4700 H30 L0	; Put your own H and/or L values here to set the first nozzle thermistor ADC correction
M305 P2 T100000 B3974 R4700 H30 L0	; Put your own H and/or L values here to set the second nozzle thermistor ADC correction
M570 S180				; Hot end may be a little slow to heat up so allow it 180 seconds

; Fans
;M106 P1 H-1 				; disable thermostatic mode for fan 1

; Tool definitions
M563 P0 D0 H1 F0:1                      ; Define tool 0 - Heater 1, Fan 0 (extruder) and Fan 1 (bed fan)
G10 P0 S0 R0                        	; Set tool 0 operating and standby temperatures
M92 E663:663                       	; Set extruder steps per mm

; Z probe and compensation definition
;*** If you have a switch instead of an IR probe, change P1 to P4 in the following M558 command
M558 P5 X0 Y0 Z1 F100 T5000 H2	        ; Z probe is an inductive probe and is used for homing
G31 P1000 Z2			        ; Set the zprobe height and threshold (put your own values here)

;*** If you are using axis compensation, put the figures in the following command
;M556 S78 X0 Y0 Z0                   	; Axis compensation here
M208 S1 Z-0			        ; set minimum Z
;
T0					; select first hot end


;Enable pronterface?
M555 P2

;Enable Z-Axis because of dumb firmware
;M564 H0

@dirtybirdnj said in DuetWifi 1.01 Updated to 1.24 - No Z Axis after update:

I'm using an inductive bed sensor on a Printrbot Simple Metal. I don't have a z-axis endstop, I have the inductive sensor wired to the Z-probe inputs. Not sure if this is relevant but the inductive bed sensor outputs its signal at 12v so I had to make a voltage divider to step it down to 3.3v. (see board diagram)

Here is an image for reference:

I believe the sensor itself is open by default and closed when activated. There is a little red LED on top of the unit and when a metal object is present under it the LED turns on.

I've added my homing files below, one thing of note is that I rarely ever used the homez.g functionality, I'd usually just run homeall.g. I see some G1 move commands there that based on the info so far in this thread thats not going to work.

Before I submitted this post I did a test, after manually setting M564 H0 I ran the homeall.g and noticed that when I put a metal object under the sensor it detected it as expected and set the zero height! After that I adjusted the nuts on the inductive sensor and ran it again letting it detect the bed by itself, and the machine finally completed a homeall.

So right now I think the main goal is to figure out what I have to change with the M558 so that I don't have to add the M564 H0 to my config or run it manually every time.

homex.g

G91                ; relative mode
G1 X-200 S1        ; move up to 200mm in the -X direction, stopping if the homing switch is triggered
G1 X100            ; move back to center
G90                ; back to absolute mode

homey.g

G91                ; relative mode
G1 Y-200 S1        ; move up to 200mm in the Y direction, stopping if the homing switch is triggered
G1 Y100
G90                ; back to absolute mode

homez.g

G91                ; relative mode
G1 Z1 F200         ; raise head 1mm to ensure it is above the Z probe trigger height
G90                ; back to absolute mode
G30                ; lower head, stop when probe triggered and set Z to trigger height
G1 Z1 F200         ; raise head 2mm after probe trigger 

homeall.g

G91                 ; set relative positioning

G1 X-200 S1         ; move up to 200mm in the -X direction, stopping if the homing switch is triggered
G1 Y-200 S1         ; move up to 200mm in the -Y direction, stopping if the homing switch is triggered
G1 X100 Y100 F3500

; Inductive Bed Sensor
G30                  ; lower head, stop when probe triggered and set Z to trigger height
G1 Z20 F1000         ; raise head 1

@phaedrux said in DuetWifi 1.01 Updated to 1.24 - No Z Axis after update:

M564 H0

Thank you for this!

Sending M564 H0 did indeed unlock my Z axis and allowed me to run a homing routine.

Before running M564 Both G28 and G30 commands return the same insufficient axes homed error... which makes no sense to me. Is there a different command to home the Z-axis now? I'm using an inductive bed sensor on a Printrbot Simple Metal. I don't have a z-axis endstop, I have the inductive sensor wired to the Z-probe inputs. Not sure if this is relevant but the inductive bed sensor outputs its signal at 12v so I had to make a voltage divider to step it down to 3.3v. (see board diagram)

The command I have in my config that defines Z homing is

M558 P5 X0 Y0 Z1 ; Z probe is an inductive probe and is used for homing

Is there something else I need to change in the config relative to the new firmware? The fact that neither G28 or G30 work by default leads me to believe there is something wrong with my M558. I tried adding S1 and S2 to both G28/30 commands as described in the FAQ and neither of them allowed me to home Z.

Or is the solution to simply add M564 H0 to my config.g? I like the fact that the machine won't move unless homed so it seems like an unnecessarily brute force way to solve this problem.

Hello,

I recently updated my DuetWifi 1.01 to the 1.24 firmware version. (edit: I believe it was 1.17 or 1.18 before update, so BIG jump in version)

I haven't made any changes to my wiring at all, but now my z-axis isn't working. I can't home it or move it. X, Y and EXT motors all function fine as does the heater control and bed temp control.

G28 works for X and Y axes. When I send the command to home the Z axis I get this error:

G28 Z Error: G0/G1: insufficient axes homed

Here is my config.g

M111 S0                                 ; Debug off
M550 OldYeller                ; Machine name and Netbios name (can be anything you like)
M551 Preprap                            ; Machine password (used for FTP)
;*** If you have more than one Duet on your network, they must all have different MAC addresses, so change the last digits
M540 P0xBE:0xEF:0xDE:0xAD:0xFE:0xED     ; MAC Address
;*** Wifi Networking
M552 S1                    ; Enable WiFi. Disabled for setup and testing. Enable once set up on your network.

M555 P2                               ; Set output to look like Marlin
M575 P1 B57600 S1            ; Comms parameters for PanelDue

G21                                     ; Work in millimetres
G90                                    ; Send absolute coordinates...
M83                                     ; ...but relative extruder moves

; Axis and motor configuration
M569 P0 S0                          ; Drive 0 (x motor) goes reverse
M569 P1 S0                          ; Drive 1 (y motor) goes reverse
M569 P2 S0                          ; Drive 2 (z motor) goes reverse
M569 P3 S0                          ; Drive 3 (ext motor) goes reverse

M350 X16 Y16 Z16 E16 I1             ; set 16x microstepping with interpolation
M574 X1 Y1 Z0 S1                    ; set homing switch configuration (x and y switches, at low end, active high)
M906 X800 Y800 Z800 E800            ; Set motor currents (mA)
M201 X1000 Y1000 Z1000 E100         ; Accelerations (mm/s^2)
M203 X3000 Y3000 Z3000 E600         ; Maximum speeds (mm/min)
M566 X1000 Y1000 Z1000 E50          ; Maximum jerk speeds mm/minute
M208 X203 Y203 Z240                 ; set axis max and high homing switch positions (adjust to suit your machine)
M208 X-0 Y0 Z0 S1                   ; set axis min and low homing switch positions (adjust to make X=0 and Y=0 the edges of the bed)
M92 X80 Y80 Z400 E95                ; set axis steps/mm
G21                                 ; Work in millimetres
G90                                 ; Send absolute coordinates...
M83                                 ; ...but relative extruder moves

; Thermistors
M305 P0 T100000 B3950 R4700 H30 L0    ; Put your own H and/or L values here to set the bed thermistor ADC correction
M305 P1 T100000 B3974 R4700 H30 L0    ; Put your own H and/or L values here to set the first nozzle thermistor ADC correction
M305 P2 T100000 B3974 R4700 H30 L0    ; Put your own H and/or L values here to set the second nozzle thermistor ADC correction
M570 S180                ; Hot end may be a little slow to heat up so allow it 180 seconds

; Fans
;M106 P1 H-1                 ; disable thermostatic mode for fan 1

; Tool definitions
M563 P0 D0 H1 F0:1                      ; Define tool 0 - Heater 1, Fan 0 (extruder) and Fan 1 (bed fan)
G10 P0 S0 R0                            ; Set tool 0 operating and standby temperatures
M92 E663:663                           ; Set extruder steps per mm

; Z probe and compensation definition
;*** If you have a switch instead of an IR probe, change P1 to P4 in the following M558 command
M558 P5 X0 Y0 Z1            ; Z probe is an inductive probe and is used for homing
G31 X25 Y0 Z0 P500            ; Set the zprobe height and threshold (put your own values here)

;*** If you are using axis compensation, put the figures in the following command
M556 S78 X0 Y0 Z0                       ; Axis compensation here

M208 S1 Z-0            ; set minimum Z
;
T0                    ; select first hot end


;Enable pronterface?
M555 P2```

@kingfisher:

Think its these

http://uk.rs-online.com/web/p/pcb-terminal-blocks/8030633/

I've just had the same issue (But it was all my fault - I didn't use Furrules in a temporary setup)
I'm going to try a repair this week.

Ah thank you so much! This is exactly what happened to me. The link you gave me provided the manufacturers part number… with that I was able to find it on digikey!

https://www.digikey.com/product-detail/en/phoenix-contact/1714955/277-1269-ND/260637

@number40fan:

Usually it is just from a loose connection. Are you using any kind of solder on the tip of the wire that goes into the Duet? Or is it just bare wires? Or do you have the supplied end crimped onto the wire and connected that way?

This is exactly what happened! I had ferrules to use for the hotend wiring into the screw terminals, but my wires for the heated bed were going directly into the screw terminal ports. There was no solder or anything. Definitely going to find those ferrules before I fire up the bed again!