inconsistent behavior - duet wifi on latest beta

Phaedrux

Can you grab a M122 diagnostic the next time it happens? Might shed some light.

Danal

@mentaluproar said in inconsistent behavior - duet wifi on latest beta:

Before I transferred the board I did wipe the card with the SD formatter tool and completely redid it.

After you rebuilt the card and put it in a Duet... did you issue the M commands to update firmware in both the Duet and the WiFi module? Or equivalent?

Shot in the dark here... but I'm wondering if there is somehow an incompatibility between what is running in flash on the controllers vs. something on the card. Maybe.

Mentaluproar

No. I thought the firmware did little more than load what was in the card to memory. What are those M codes?

Danal

M997 S0:1U date firmware modules 0 and 1. This should be what you want for a Duet Wifi

S0 - main firmware

Older releases filename was sys/RepRapFirmware.bin (Duet) or sys/DuetWiFiFirmware (Duet WiFi).
Latest releases, filename is /sys/Duet2CombinedFirmware.bin
File sys/iap.bin (Duet) or sys/iap4e.bin (Duet WiFi) must also be present.

1 - web server firmware

Filename sys/DuetWiFiServer.bin (Duet WiFi only)

Latest released binary files Here: https://github.com/dc42/RepRapFirmware/releases I do recommend the very latest releases, I'm running them on a couple of different Detlas, no issues.

.

AFTER you do those upgrades, you may also want to refresh DWC (Duet Web Control), just to be sure. Upload the whole zip file (don't unzip) through the Settings>General>Upload web stuff. https://github.com/chrishamm/DuetWebControl/releases

Mentaluproar

@danal said in inconsistent behavior - duet wifi on latest beta:

M997 S0:1

Error: M997: File DuetWiFiServer.bin not found

interesting....

Mentaluproar

reinstalled firmware. probing still crashes into tower. config.g has not disappeared yet so far.

dc42

Sometimes, the delta homing flys off the plate and into a pillar, sometimes it probes normally

I assume you mean probing, not homing. If you have old deployprobe.g and retractprobe.g files in /sys on the SD card, delete them.

Mentaluproar

no probing files. I must have configured something wrong. delta tries to probe larger than the bed.

Mentaluproar

I'm dumb. I made a typo in the M665 line.

Mentaluproar

config.g disappeared again. Twice. I can undelete it every time without a problem. Given how FAT32 works, I'm thinking something in the firmware is telling it to delete the file.

dc42

@mentaluproar said in inconsistent behavior - duet wifi on latest beta:

config.g disappeared again. Twice. I can undelete it every time without a problem. Given how FAT32 works, I'm thinking something in the firmware is telling it to delete the file.

Which firmware and DWC versions are you using?

I don't think the current firmware and DWC versions ever delete config.g. When you edit it in DWC and save it, I think it first deletes config.bak if it exists, then renames config.g to config.bak, then uploads the new config.g. Or chrishamm may have implemented it another way, such as uploading to config.new first and then doing a double rename. Either way, if the process fails you should still have the old config.g renamed to config.bak.

Mentaluproar

config.bak is generally there. I think it has vanished before too but I can't remember.

kungfueinstein

its just disappeared for me too. this is not the first time. Also having problems opening the DMS file to restore the bak.

dc42

@kungfueinstein said in inconsistent behavior - duet wifi on latest beta:

its just disappeared for me too. this is not the first time. Also having problems opening the DMS file to restore the bak.

When it disappeared, were you editing it and trying to save it? Or was it after you uploaded a new file to /gcodes?

How many files do you have in the /sys folder? There is a limit to how many files in a folder the firmware can return to DWC. Although this normally affects only the /gcodes folder, it could affect /sys if you have a lot of files in it.

Mentaluproar

I've only had the files necessary for operation in the sys folder. I only ever notice config.g isn't there when I go to edit it. Sometimes I'll realize I forgot to do something after it goes to reboot the board, so I'll wait, then go back to system editor and see the file is gone.

I don't know if this is relevant, but if I reload the page (like if it's on a tab and my mac has to reload the tab because I was doing lots of other things) the board will repeat the last few instructions sent to it. Even if it is printing, it will interrupt the print to home and calibrate. This happens every time on safari, and a little less frequently on firefox.

Basically, once it's all dialed in, the board works great, but interacting with it in any way leads to unpredictable results. Still nowhere near as bad as octoprint though.