DuetWIFI migration
-
I see that you posted a 1.11b-dc42 so I tried it and the same thing happens and I also do not see the monospace font in the Configuration File panel so that is odd. Something is going on that doesn't make sense.
For what it's worth…
I tried to play with the DuetWiFi a bit today and loaded up the new firmware bundle from dc42's beta release earlier today. I don't have a PanelDue and didn't want to use the USB interface, so I did it from the WiFi interface. The main firmware loaded fine and I power cycled after it came back up. Version 1.15beta3 showed up on the web interface settings screen. Then, I uploaded both the webserver and WiFi chip firmware via the web interface. Ran M997 S1 and let it do it's thing for about 90 seconds and then did M997 S2. The blue light on the WiFi antenna lit up (which I never had noticed before), but it never went out. The web interface settings page never showed the newer web server firmware update version. I then power cycled the Duet and tried M997 S1:2 and waited about 5 minutes. After that, I did another power cycle and everything seems to be as it should be. The latest versions showed up on the web interface.
-
It takes a few minutes to update DuetWebControl. I am going to use the diagnostic LED to indicate firmware update in progress, but in the mean time the blue LED on the wifi module is a good indicator that the update is still in progress.
Updating DuetWiFiServer sometimes happens fast enough for DuetWebControl to reconnect after the green firmware updating bar has run its course, and sometimes not.
DuetWebControl doesn't yet understand what M997 S1 or S2 do, so it won't automatically refresh the web interface after M997 S2.
-
Well, I've had no luck recovering. Here's how I got to this point:
installed and commissioned the stock beta Duet WiFi
made 1 print
updated PanelDue firmware to the latest
made 1 print
made my monospace font hack and rebuilt the DuetWebControl.bin
uploaded via the web interface (via iap4e.bin that was stock to the Duet WiFi)
web interface would not stay connected very long
thought maybe a problem with my build of DuetWebControl.bin
reverted to DuetWebControl.bin from David's GIT (pre v. 1.11b-dc42) via web interface
same problem, web interface drops connection
reverted to DuetWebControl.bin from the CF card that came with the Duet WiFi via web interface
same problem, web interface drops connection
reverted to DuetWebControl.bin v. 1.11b-dc42 via web interfaceAnd Ive rebooted the Duet WiFi several times in the process, it just won't stay connected and I'm at a loss at what to do.
-
Interesting, I just rebooted (power off and on) and when it came up and was able to connect for 30ish seconds, I looked at the Settings->General page and see:
Firmware Name: n/a
Firmware Version: n/a
Web Interface Version: HTML: 1.11, JS: 1.11a-dc42And this should have been the 1.11b-dc42
So something is amiss, I am going to reinstall the firmware and all other components via bossac over USB.
-
Ok, this is a bummer. When I erase/reset DuetWiFI I do not see the device show up in /dev on OS X. I've done this hundreds of times on other Duets and was able to do it on this board. I seem to be in a funky state. So without a serial port, I can't reinstall the firmware. I am going to try to do this from a Windows 10 laptop.
-
Why does this seem like deja vu all over again!?
Now on a Windows 10 laptop. I've used bossac from this machine successfully.
I hook up USB, press erase for a few seconds and then reset. I hear the Windows device "bee bop" sound. I see COM3 show up in Device Manager->Ports (COM & LPT). I run:
bossac –port=COM3 -U true -e -w -v -b DuetWiFiFirmware.bin -R
(at the same level where the firmware is located) and get:
no device found on COM3
And now I have no firmware installed so it did actually erase.
-
Michael, please see the firmware upload instructions at https://duet3d.com/wiki/Updating_main_firmware. You can't use bossac because it doesn't support the SAM4 processor used on the Duet WiFi.
-
ok! That would make sense then! I'll do that now, sorry for not reading!
-
It might have assigned another com port to the duet. You can see if it found the new port and get its number…
I don't know windows 10 very well but in windows 7, it's under device manager then scroll down the list to COM/LPT ports and it hopefully shows up.Or you could just try COM 4 in the bossac command. I bet that's it.
-
I had to go to Backup procedure #2 but get this:
Connecting…
[ERROR] Could not connect to /dev/tty.usbmodem14431 at baudrate 57600:
Serial error: could not open port /dev/tty.usbmodem14431: [Errno 2] No such file or directory: '/dev/tty.usbmodem14431'So on to Emergency proceedure?
-
Toddimus, thanks but you probably didn't read David's reply, can't do it with bossac on the Duet WiFi!
-
EDITED, stay tuned
-
Ok, I am able to install firmware with SAM-BA from Windows 10. I can now connect from Pronterface on Windows or Mac.
I then did Backup procedure #1 with the original .bin files that were installed on the CF when I got it.
I reenabled WIFI by sending M552 S1 from Pronterface. And connected from a web browser and got this 3 seconds later:
Communication Error
An AJAX error has been reported, so the current session has been terminated.
Please check if your printer is still on and try to connect again.
Error reason: timeout
Note that I had placed all 3 .bin files (including DuetWebControl.bin) on the CF card for Backup procedure #1. Does M997 S0 also install it? Or do I need to do this manually with the web interface?
-
Forgot to mention, after doing the above the Settings->General panel shows:
firmware version 1.13 (2016-06-13)
Web interface: 1.11 JS: 1.11a=dc42Is this the as-sent stock configuration?
-
David, are you sure that the reported version # for the DuetWebControl.bin you uploaded yesterday is 1.11b-dc42?
I've attempted to upload this version 3 times now to verify that I can upload and I get the 1.11a-dc42 version even after a hard reboot.
At this point I am not able to stay connected to the web interface for very long at all. Interestingly, if I am quick and get an upload started, it seems to complete that successfully and then drops the connection a few seconds later. Perhaps it isn't actually uploading the new web control. Is there another way to install the web control?
-
David, here's another odd thing. I set the MAC address in my config.g file to avoid conflicts. However, when I scan my network and find the Duet WiFi, it has a completely different MAC address than what I assigned.
I assign: M540 P0xBE:0xEF:0xDE:0xAD:0xFE:0xED
it shows up as: 18:fe:34
98:c7This address doesn't conflict with anything either but I find that odd.
-
I set the MAC address in my config.g file to avoid conflicts.
https://duet3d.com/wiki/Changes_to_config_gcodes_and_firmware_behaviour
The M540 command (set MAC address) has no effect.
-
David, are you sure that the reported version # for the DuetWebControl.bin you uploaded yesterday is 1.11b-dc42?
I've attempted to upload this version 3 times now to verify that I can upload and I get the 1.11a-dc42 version even after a hard reboot.
At this point I am not able to stay connected to the web interface for very long at all. Interestingly, if I am quick and get an upload started, it seems to complete that successfully and then drops the connection a few seconds later. Perhaps it isn't actually uploading the new web control. Is there another way to install the web control?
I noticed a similar thing, but after the second try of re-uploading both the DuetWebControl.bin and DuetWiFiServer.bin and then running the M997 S1:2 and waiting for like 10 minutes (went to do something else and came back to it), it worked. I did a hard reboot of the Duet after the wait and then the web interface showed 1.11b-dc42.
-
Toddimus, thanks but you probably didn't read David's reply, can't do it with bossac on the Duet WiFi!
I think I was typing my post right as David was typing his. I hadn't seen his until after. I haven't ever used bossac because I'm new to the Duet world and haven't needed it yet.
-
I set the MAC address in my config.g file to avoid conflicts.
https://duet3d.com/wiki/Changes_to_config_gcodes_and_firmware_behaviour
The M540 command (set MAC address) has no effect.
Thanks.
