Posts made by elvisprestley

@elvisprestley Alright - with the correct size SD card, I'm back in business! Thanks all.

@phaedrux yeah - OK, I'm not brave enough to try partitioning this "too big card" just to see what happens. I've got a new card on order, I'll save the twiddling until it arrives...

@jay_s_uk thank you. I understand now, and see it in the help files, and forum posts now that I know what to look for. A new card is on order...

@elvisprestley and I'm on a mac - so if I need to be formatting this card into two partitions, I need some pointers

@elvisprestley Here's a screenshot of the contents of the SD card

@elvisprestley it's a SanDisk formatted as a ExFAT 255.8 GB it does click in when it's seated fully. OK I tried it all again, manually started the Wifi and HTTP using the USB connection, and got a better diag this time:

=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2.2 running on Duet WiFi 1.02 or later
Board ID: 0JD0M-9P6B2-NJ4S8-6J9D6-3SD6J-1U7YL
Used output buffers: 1 of 24 (12 max)
=== RTOS ===
Static ram: 23460
Dynamic ram: 71744 of which 0 recycled
Never used RAM 16876, free system stack 177 words
Tasks: NETWORK(ready,364) HEAT(blocked,366) MAIN(running,409) IDLE(ready,20)
Owned mutexes: WiFi(NETWORK) USB(MAIN)
=== Platform ===
Last reset 00:05:46 ago, cause: power up
Last software reset at 2022-05-28 16:03, reason: User, GCodes spinning, available RAM 16876, slot 2
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
MCU temperature: min 29.9, current 30.4, max 30.9
Supply voltage: min 12.8, current 12.9, max 13.1, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: position 0, standstill, SG min/max not available
Driver 1: position 0, standstill, SG min/max not available
Driver 2: position 0, standstill, SG min/max not available
Driver 3: position 0, standstill, SG min/max not available
Driver 4: position 0, standstill, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 1970-01-01 00:00:00
Cache data hit count 413585918
Slowest loop: 0.44ms; fastest: 0.21ms
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: 30.0MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 200.40ms; fastest: 0.10ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 0 of 8

• WiFi -
  Network state is active
  WiFi module is connected to access point
  Failed messages: pending 0, notready 0, noresp 1
  WiFi firmware version 1.25
  WiFi MAC address 48:3f:da:a6:e3:25
  WiFi Vcc 3.35, reset reason Power up
  WiFi flash size 2097152, free heap 26856
  WiFi IP address 192.168.164.234
  WiFi signal strength -63dBm, mode 802.11n, reconnections 0, sleep mode modem
  Clock register 00002002
  Socket states: 0 0 0 0 0 0 0 0

1. Still no DWC connection even after I (2) manually start and connect the Wifi Module
2. still getting the error that Duet rejects the HTTP request: page not found
3. when I try running M997 S0 to upgrade the firmware I'm still getting the error Error: M997: Firmware binary "Duet2CombinedFirmware.bin" not found even when that file is copied into every folder on the SD card and root...

What's the next step to determining if the SD card is good or being read at all?

@jay_s_uk Yes the SD card works normally in a PC.

I've got a Rostock V3.2 with a Duet Wifi. She's been sitting idle so long that she won't talk to me anymore. I need some hand-holding to get her updated. I've been working on this for 4 hours, reading all the help manuals and instructions and I've no idea what the issue really is.

1. I have no DWC connection

• Every time I power cycle the main power, the Wifi module comes up as disabled. 25/25 times see below:

=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2.2 running on Duet WiFi 1.02 or later
Board ID: 0JD0M-9P6B2-NJ4S8-6J9D6-3SD6J-1U7YL
Used output buffers: 1 of 24 (11 max)
=== RTOS ===
Static ram: 23460
Dynamic ram: 71744 of which 0 recycled
Never used RAM 16876, free system stack 177 words
Tasks: NETWORK(ready,519) HEAT(blocked,366) MAIN(running,398) IDLE(ready,20)
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:27:06 ago, cause: power up
Last software reset at 2022-05-28 16:03, reason: User, GCodes spinning, available RAM 16876, slot 2
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
MCU temperature: min 24.4, current 27.1, max 27.5
Supply voltage: min 0.5, current 0.5, max 13.0, under voltage events: 2, over voltage events: 0, power good: no
Driver 0: position 0, standstill, SG min/max not available
Driver 1: position 0, standstill, SG min/max not available
Driver 2: position 0, standstill, SG min/max not available
Driver 3: position 0, standstill, SG min/max not available
Driver 4: position 0, standstill, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 1970-01-01 00:00:00
Cache data hit count 2324298341
Slowest loop: 300.31ms; fastest: 0.14ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 20.0MBytes/sec
SD card longest read time 0.4ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 0.33ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 0 of 8

• WiFi -
  Network state is disabled
  WiFi module is disabled
  Failed messages: pending 2779096485, notready 2779096485, noresp 2779096485
  Socket states: 0 0 0 0 0 0 0 0

2. I can use USB to start the Wifi Module (and the HTTP module because it's also off by default) and I can get to a state where I'm connected to my access point. See below:

• WiFi -
  Network state is active
  WiFi module is connected to access point
  Failed messages: pending 0, notready 0, noresp 0
  WiFi firmware version 1.25
  WiFi MAC address 48:3f:da:a6:e3:25
  WiFi Vcc 3.35, reset reason Power up
  WiFi flash size 2097152, free heap 27016
  WiFi IP address 192.168.164.234
  WiFi signal strength -64dBm, mode 802.11n, reconnections 0, sleep mode modem
  Clock register 00002002
  Socket states: 0 0 0 0 0 0 0 0

3. When I go to the address http://192.168.164.234 I get the following error:

Your Duet rejected the HTTP request: page not found
Check that the SD card is mounted and has the correct files in its /www folder

4. My goal here is to upgrade from 3.2.2 to the latest release. When I try running M997 S0 I get the following error:

Error: M997: Firmware binary "Duet2CombinedFirmware.bin" not found

Since I'm running old FW I've tried moving files around within the file structure but can't get any other errors but this. So even when I put the "Duet2CombinedFirmware.bin" in every folder and in the root, it still says "not found".

5. I'm suspicious that my SD card may be bad ? It reads and writes just fine, but it's as if the Duet can't find it. ever. maybe I've broken the connector on the board? How can I figure this out.

Please, I need some hand-holding what to do next. I'm just flailing.

I'm running

• DWC version 3.3.0
• RipRapFW version 3.3
• Wifi version 1.26

I want to downgrade to RR v2.2 to resolve some issues I'm having with overheating and fan cooling controls.

I wipe the SD card and install the FW I want.
I connect via USB and hit M997 S0 to install it and I get the error:

 File 0:/firmware/DuetWiFiServer.bin not found

Which is because v2.2 doesn't have this file structure. So I looks like I might need to reset the Duet. I'm running a Duet 2 wifi, no reset button, but I see where the jumper is.

Anyone got any last words of advice for me before I brick this thing?

@bot Can you please tell me more about "fallback procedure #2" (IIRC) in the documentation. It is a set of instructions for erasing the firmware on your board with the erase jumper

where do I find these instructions?

@stough buyer beware
I upgraded my original Rostock V3 to the new RR V3.3 and I have never been able to downgrade again. They changed the folder structure that the Duet uses to look for files. Once you change, I can't figure out how to go back. I wipe and format the SD card, and still the older software "knows" that the file folder structure has changed and it goes looking for things in all the wrong places. Even if you try to fool the older version it doesn't fall for it.

I'd recommend sticking with V2.2 as supported by SeeMe CNC. Steve knows his stuff.
Running V3.3, I have unresolved heater fan issues, and am dead in the water as a result.

Good luck!

@phaedrux I am finally printing! I used the SeeMeCNC config files (which were almost identical to my own) and took apart the hotend again reassembling it very carefully.

I've got good power supply, good extrusion, and no heater faults.

• The Wifi is still failing to initialize about 10% of the time, annoying, but manageable with a quick USB plugin and resetting the system.

Things are going so well, I'm tempted to start rolling some of this software forward...

@phaedrux caught the wifi failing to initialize. Here's the M122 output:

=== Network ===
Slowest loop: 14.98ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 0 of 8

• WiFi -
  Network state is active
  WiFi module is connected to access point
  Failed messages: pending 0, notready 0, noresp 0
  WiFi firmware version 1.23
  WiFi MAC address 48:3f:da:a6:e3:25
  WiFi Vcc 3.35, reset reason Power up
  WiFi flash size 2097152, free heap 26936
  WiFi IP address 255.255.255.255
  WiFi signal strength 31dBm, mode none, reconnections 0, sleep mode modem
  Clock register ffffffff
  Socket states: 0 0 0 0 0 0 0 0
  ok

If I try to inquiry the state of the WiFi Module with a M552 S1 I get no response. But if I set it to S0 and then S1 it will kick back in and start working again.

So strange.

@phaedrux I was copying the files to the SD card, and connecting via terminal which is where I was seeing the file not found error.

I gave up, and tried it in the DWC, which happily rolled back the WiFi server and the DWC with no errors but when I try uploading the Duet2CombinedIAP.bin and the Duet2combinedFirmware.bin as a package - it silently fails to do the downgrade.

This leaves me here:

• DWC version 2.0.4
• RipRapFW version 3.3
• Wifi version 1.23

Like you said, I don't think any of this matters. Although I haven't had the Wifi fail to connect so the jury is still out.

@phaedrux hey there, thanks for helping me out with this.

It looks like because of the file structure changes between RipRap 3.2.2 -> 3.3 I am no longer able to downgrade. What happens is when I hit M997 S0:1 the system throws the error that the file 0:/firmware/DuetWifiServer.bin is not found. Which of course it isn't since I'm trying to downgrade. Oddly, even if I put the file there, it still is unable to find it. I still get the error that the file is not found.

OK so then it gets weird. M997 S1 does successfully install the old WiFiServer with no errors.
And doing M997 S0 says 0:/firmware/Duet2CombinedFirmware.bin is not found - even when the file is there. I've tried putting the old file there, and the new file there. I've even tried renaming the WifiServer.bin to see if I could spoof it. No joy. Long story short - I am unable to downgrade

@phaedrux I had a long conversation with Steve from SeeMeCNC and he suggested I roll back from RipRap version 3.3 to 3.2.2 and follow his service manual guide: https://docs.google.com/document/d/1IQf191FP7EgV8IRpa__jZviF_lfd1jcKVwHD2J7U9pw/edit

He said he's tested this instruction set on over 100 different brands (he might have been exaggerating a little). He cautioned me that there are a few redundant steps, flash the FW, make a change, and flash it again. He said doing that was important. So tomorrow, I'm going to go through his instructions and follow every step.

If/when I hit the issue where the Duet wifi server fails to initialize again, I'll send you the M122 output. With any luck rolling back might address that.

what am I supposed to do when my Duet's wifi card fails to initialize? This seems to happen about 10% of the time and it's ridiculously annoying to plug in the USB and re-initialize the wifi module all the time like this.

@droftarts this is brilliant, why is this not a step in the setup configuration?

@phaedrux So I got another power supply and am getting a good solid 14v. When I fire up the heaters this is what happens:

Error: Heater 1 fault: temperature excursion exceeded 15.0°C (target 195.0°C, actual 213.2°C)

Heater 1 is my hot end heater. Fortunately, I haven't blown this power supply (yet).

So, do I conclude that my brand-new hotend has a short? Or could there still be a problem on the Duet board? How do I diagnose where the issue is?

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.02 or later
Board ID: 0JD0M-9P6B2-NJ4S8-6J9D6-3SD6J-1U7YL
Used output buffers: 3 of 24 (14 max)
=== RTOS ===
Static ram: 23876
Dynamic ram: 74928 of which 0 recycled
Never used RAM 15612, free system stack 116 words
Tasks: NETWORK(ready,14.8%,237) HEAT(delaying,0.0%,208) Move(notifyWait,0.1%,303) MAIN(running,84.8%,153) IDLE(ready,0.3%,29), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:05:02 ago, cause: power up
Last software reset at 2022-02-20 15:31, reason: User, GCodes spinning, available RAM 12388, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Step timer max interval 0
MCU temperature: min 22.7, current 28.8, max 29.1
Supply voltage: min 14.4, current 14.7, max 15.1, 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
Driver 0: position 52028, standstill, SG min/max 0/602
Driver 1: position 52028, standstill, SG min/max 0/587
Driver 2: position 52028, standstill, SG min/max 0/580
Driver 3: position 0, standstill, SG min/max not available
Driver 4: position 0, standstill, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 2022-02-24 18:44:13
Cache data hit count 4294967295
Slowest loop: 6.34ms; fastest: 0.14ms
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 2.4ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 15909ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 59, completed moves 59, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 0 is on, I-accum = 0.3
=== 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.
=== Network ===
Slowest loop: 15.46ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8

• WiFi -
  Network state is active
  WiFi module is connected to access point
  Failed messages: pending 0, notready 0, noresp 0
  WiFi firmware version 1.26
  WiFi MAC address 48:3f:da:a6:e3:25
  WiFi Vcc 3.35, reset reason Power up
  WiFi flash size 2097152, free heap 26664
  WiFi IP address 192.168.164.234
  WiFi signal strength -63dBm, mode 802.11n, reconnections 0, sleep mode modem
  Clock register 00002002
  Socket states: 4 0 0 0 0 0 0 0

@phaedrux @mendenmh thank you. This power supply has been working great and this only just happened after switching out the hotend. Any chance the hot-end created a problem that I would not have noticed (meaning there was no smoke or flame event)?