Posts made by ddxdesign

@phaedrux Oh I would assume the warranty would be for the whole machine from the machine's maker, I didn't expect the board to have its own. Interesting. I have no idea if the Duet they put in this machine is off the shelf or modded or added onto in any way.

@phaedrux Just revisited my records and I bought this machine brand new, receiving it on Jan 20, 2021 - so not even 13 months ago it turns out. Really, THAT is out of warranty?? What?

@phaedrux Right, that's what I was thinking. I would have to dismantle the top of the machine to get a look at the board itself. I didn't buy the Duet standalone, I bought a complete machine - SeeMeCNC Artemis 300 - about a year and a half ago. It's been the best machine ever in terms of use and print quality so this is a real downer.

@phaedrux And here is the result of those commands when connected to terminal by usb. Somehow starting wifi worked, but on screen I still have no SD card content showing and the part-fans are running full tilt.

m552
WiFi module is disabled<LF>ok<LF>
m552 s0
ok<LF>WiFi module started<LF>
m552 s1
ok<LF>WiFi module is connected to access point MOTO3E2E, IP address 192.168.0.206<LF>
m122 p104 s10
Error: Failed to create folder 0:/gcodes in path 0:/gcodes/test.tst<LF>Error: M122: Failed to create file<LF>ok<LF>
m997 s1
Error: M997: File DuetWiFiServer.bin not found<LF>ok<LF>

@phaedrux well for now I grabbed the tree screenshot from the WWW folder sitting on my desktop (which I copied over into the SD card)

@phaedrux Well, I found the files for my FW (3.2.2) and loaded the new card in the machine and.... nothing. the macros don't show up, the gcodes don't show up, it doesn't have anything showing in console, nothing.

@dc42 OK so I do need to find them and get them back in there. Thanks.

@phaedrux OK this took entirely too long to get back to, but I did find that a couple of the big .GZ files in the www folder were unable to be copied out from the old card. I'm trying to find the files elsewhere in my computer, ideally just the entire www folder. what could happen if those GZip files aren't there? I can't imagine the printer itself has the utilities to unzip and use the contents thereof, right?

@phaedrux I finally got a chance to try to do the DWC connection while plugged into the USB and got the same file read error. So I suppose my next item is to buy a new sd card.

@phaedrux I will at least look up the specs from the manufacturer and email them if that doesn't yield anything. If I have to disassemble the head of the machine then so be it, I guess (I don't build these things, I just use them).

EDIT I looked it up and it's apparently a Meanwell 350W 12V supply. I assume I should ask the company if it should be adjusted, just in case. I don't know if they overvolt something on purpose in there.

But, that said, for a machine that has given me no issues for 2 years or so, outside of 2 network/wifi based problems (this being the second one), is there a reason to suspect a voltage misadjustment now?

@phaedrux Oh I see. How would I find out the PSU voltage?

@phaedrux A couple points before I go dig out the SD card again (it's a PITA as the spring loaded slot is inset from the surface and I have to stick little tools in there to get it to pop out) regarding your questions:

1. It wasn't immediately after a print, but I had printed things earlier in the day. Printing is totally unhindered, just connecting from wifi is.

2. PSU... VIN? No idea what that means; pretty sure it's not Vehicle Identification Number.

3. Yes, I tried to do it over the DWC page with the USB plugged in as well but no dice. But what good is using DWC if you'd have to be plugged into the machine anyway? SeeMe instructs everyone to NOT "run the machine live" via Terminal, though, so DWC and the front panel are The Way.

4. My firmware is as upgraded as I was told to take it (here in this forum) when I had a previous issue back in September. How much further does it have to be?

5. OK, I will have to go find somewhere to buy a new SD card. Just dupe the old one onto it? or does it have to be formatted a certain way first?

@phaedrux
OK, sorry for delay, been super busy. here is the M122 before it drops:
m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2.2 running on Duet WiFi 1.02 or later
Board ID: 08DLM-996RU-N85S4-7JKF4-3SN6P-TU97R
Used output buffers: 1 of 24 (3 max)
=== RTOS ===
Static ram: 23460
Dynamic ram: 72960 of which 80 recycled
Never used RAM 15492, free system stack 105 words
Tasks: NETWORK(ready,364) HEAT(blocked,308) MAIN(running,463) IDLE(ready,20)
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 142:08:42 ago, cause: software
Last software reset time unknown, reason: User, GCodes spinning, available RAM 15492, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 37.8, current 39.3, max 46.0
Supply voltage: min 12.8, current 13.1, max 13.3, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: position 169577, standstill, SG min/max 0/430
Driver 1: position 169488, standstill, SG min/max 0/432
Driver 2: position 169639, standstill, SG min/max 0/413
Driver 3: position 0, standstill, SG min/max not available
Driver 4: position 0, standstill, SG min/max 0/1023
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 4294967295
Slowest loop: 31.40ms; 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: 20.0MBytes/sec
SD card longest read time 8.5ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 84, maxWait 270260ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 154990, completed moves 154990, hiccups 770, 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.1
Heater 1 is on, I-accum = 0.6
=== 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: 16.46ms; 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.25
  WiFi MAC address f4:cf:a2:66:97:85
  WiFi Vcc 3.38, reset reason Turned on by main processor
  WiFi flash size 4194304, free heap 24696
  WiFi IP address 192.168.0.206
  WiFi signal strength -56dBm, mode 802.11n, reconnections 0, sleep mode modem
  Clock register 00002002
  Socket states: 0 0 0 0 0 0 0 0
  ok

and now i'll try to connect over wifi and do it again...
m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2.2 running on Duet WiFi 1.02 or later
Board ID: 08DLM-996RU-N85S4-7JKF4-3SN6P-TU97R
Used output buffers: 2 of 24 (13 max)
=== RTOS ===
Static ram: 23460
Dynamic ram: 72960 of which 80 recycled
Never used RAM 15492, free system stack 105 words
Tasks: NETWORK(blocked,217) HEAT(blocked,308) MAIN(running,407) IDLE(ready,20)
Owned mutexes: WiFi(NETWORK) USB(MAIN)
=== Platform ===
Last reset 142:14:13 ago, cause: software
Last software reset time unknown, reason: User, GCodes spinning, available RAM 15492, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 38.9, current 39.5, max 39.8
Supply voltage: min 13.0, current 13.1, max 13.3, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: position 169577, standstill, SG min/max not available
Driver 1: position 169488, standstill, SG min/max not available
Driver 2: position 169639, 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: 2022-01-15 10:07:47
Cache data hit count 4294967295
Slowest loop: 600.61ms; fastest: 0.24ms
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 52.6ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 84, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 154990, completed moves 154990, 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.1
Heater 1 is on, I-accum = 0.6
=== 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: 699.67ms; fastest: 0.10ms
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 1
  WiFi firmware version 1.25
  WiFi MAC address f4:cf:a2:66:97:85
  WiFi Vcc 3.38, reset reason Turned on by main processor
  WiFi flash size 4194304, free heap 23120
  WiFi IP address 192.168.0.206
  WiFi signal strength -54dBm, mode 802.11n, reconnections 0, sleep mode modem
  Clock register 00002002
  Socket states: 0 0 0 0 0 0 0 0
  ok

Most interesting part? When I just tried to connect over wifi with my phone WHILE the usb was plugged in for terminal, it responded fine on the phone, but as soon as I disconnected the usb and tried it on the laptop, it threw the card read error. On the front panel and on the phone screen it now says "Error: cannot read file, error code 1". So then I plugged back in to get the second m122 result.

@dc42 I would have to find and buy one and figure out what format it needs to be and all that, so I was saving that idea for after the troubleshooting is done. What could possibly make the card suddenly fail only when accessing it via the wifi connection, but otherwise still be working fine from the front panel?

@phaedrux Yes, will try to get that tonight. Thanks.

@flyeyes @terbospaghetti
This kind of thing happened to me and part of my resolution dance, along with a big chain of FW upgrades to current, was in discovering that my modem/router had smashed the 2.4ghz and 5ghz networks into one automode SSID. And the Duet doesn't like 5ghz I think. I had to dig into my router config and force the two networks to separate SSIDs, after which the Duet was much better about seeing the 2.4ghz network even after a restart or a few days switched off. Not perfect, but much better.

Maybe looking into that could help.

Crossposted from the SeeMeCNC forums - regarding my Artemis 300 printer.

OK - SO - after recent troubles I upgraded my Artemis's firmware (thanks to help here from you guys on the Duet forum) and it was like having a brand new machine all over again. Flawless leveling, amazing prints, even faster and cleaner than before.

But then a few days ago, I went to upload a new model to it over the Duet Wifi, and got this 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

Went upstairs to the printer and checked the console, did the off/on dance, even simulated a print, no problems.

Came back downstairs, reloaded the wifi interface page, and the error came back.

Back upstairs, did the whole thing again of checking whatever I could. No problems after a restart, again.

Then, though, I decided to check the wifi page right from my phone while still in the room, where I could watch the machine's front panel. And... THAT is what triggers a misread on the card, apparently - trying to connect to it over wifi. Instantly: Card Read Error 2. And, back to the same symptoms.

So, I have since had to walk the sd card back and forth to load models, and control prints from the front panel. Naturally, I have to upload new models to print for customers - this never happens when I just want to print things for myself, eh?

What do I even do here?

Thanks!

@jay_s_uk Well, I just spent an hour sweating in my printer room going through EVERYTHING - it's all up at 3.2.2 now, wifi is up at 1.25....

And no dice. Exact same thing again. It just fails to get on the network: every M552 S1 yields an endless stream of "no known networks found, wifi module is idle." I even tried the thing I had to do once where I had to escape all the lowercase letters in the password with a single ' before each.

EDIT I GOT IT. I saw something in the docs about the Duet only working on 2.4ghz. Now, it's been working for 5 months since I moved here on my router where both bands were on the same SSID. I forcibly split the bands to have their own names, logged specifically into the 2.4ghz one, et voila.

UGH that was a heck of a dance.

@jay_s_uk Doh, I just realized it would likely be the same instructions as you sent for 1.23 - heh.

@jay_s_uk OK, I will get a card reader this afternoon - so, are there instructions for the 1.25 wifi FW? And should I do that after I take the RRFW up to 322?