Best posts made by ddxdesign

@jay_s_uk OK let me see if I can remember how to use Yat...

@jay_s_uk Well, did that, but now when I paste in the true full output, I can't post it - forum gives me a Flagged As Spam error...

I did just discover some new-firmware instructions from seemecnc; I will have to allocate a big chunk of time to trying this I think. EDIT: Sigh, have to go buy an SD-to-USB thing.

@jay_s_uk Alrighty, from YAT the full M122 output is:

=== Diagnostics ===<LF>RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet WiFi 1.02 or later<LF>Board ID: 08DLM-996RU-N85S4-7JKF4-3SN6P-TU97R<LF>Used output buffers: 1 of 20 (13 max)<LF>=== RTOS ===<LF>Static ram: 25524<LF>Dynamic ram: 98864 of which 0 recycled<LF>Exception stack ram used: 432<LF>Never used ram: 6252<LF>Tasks: NETWORK(ready,544) HEAT(blocked,1232) MAIN(running,3636) IDLE(ready,200)<LF>Owned mutexes:<LF>=== Platform ===<LF>Last reset 69:35:24 ago, cause: power up<LF>Last software reset at 2021-08-22 09:46, reason: User, spinning module GCodes, available RAM 6212 bytes (slot 3)<LF>Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d<LF>Error status: 8<LF>Free file entries: 10<LF>SD card 0 detected, interface speed: 20.0MBytes/sec<LF>SD card longest block write time: 0.0ms, max retries 0<LF>MCU temperature: min 40.4, current 40.6, max 41.6<LF>Supply voltage: min 13.0, current 13.1, max 13.1, under voltage events: 0, over voltage events: 0, p[Warning: Maximal number of bytes per line exceeded! Check the EOL (end-of-line) settings or increase the limit in the advanced terminal settings.]

@siam Hmm; where my printer is, I would have to use my laptop on battery to get to anyways, so maybe this isn't a concern?

@jay_s_uk No USB, it's all through the panel due. SeeMe says they do not recommend connecting to this machine through USB - to do everything from the panel. Running 2.02 FW (12/24/18). That's odd because I got the machine brand new 8 mos ago, but then again maybe their machines use older FW on purpose (assuming there have been new FWs in the ensuing time)

@jay_s_uk M588 still not working "Failed to reset to factory" - M587 not working "Failed to add network" - M122 shows, lets see.... aside from the version IDs and things it says:

Use output buffers 1 of 20 (12 max) === RTOS === Static ram 25524 Dynamic ram 98864 of which 0 recycled Exception stack ram used 432 Ne (it just cuts off there)

@dc42 @jay_s_uk OK, firmware seemed to work but everything else once again no dice. If I can't load up customers' orders to print, this $1600 machine has just become a sculpture. UGH.

@jay_s_uk Aha, ok, that did work to redo the firmware it looks like. now to try all the setup stuff again.

@dc42 Update: I did try it and it says "Warning: M996 command is not supported."

Beyond trying to fix it right now, I have to ask: How does something like this go from working every day for months to, after a 3 day period of being powered off, suddenly just deciding not to work anymore?

@dc42 Thank you for the suggestion; I'll try it. Is there a way to check from the panel itself whether the firmware is in there?

Repost from SeeMeCNC forum where they suggested I post here instead:

Went to print this morning after some 3 days of downtime in which my Artemis was turned off, but today it's just constantly repeating that there are no networks and wifi is idle.

M552 S-1 stops the module OK, M552 S0 starts it ok. M587 alone yields no known networks even though it's been running fine on my network for months and I just turned it off a few days ago to save power.

The factory reset command M588 yields a failure, and I can't remember which command but might be the M587, sometimes says 'bad reply format version'.

Needless to say, the normal M552/M587 combo with ssid and password doesn't do anything but toss it back into the wifi error wifi idle message, which repeats every second endlessly unless I stop the module.

Emergency reset and even off/on doesn't change the situation either.

Hope you guys can help. Thanks. NOTE: I don't know anything about the assembly and electronics portion of the program here - I don't build my machines, I just use them.

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

@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.

@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.