DuetWIFI migration

dc42 · 9 Jul 2016, 07:59

Getting connected to WIFI was MUCH EASIER than using the TP-Link WR702-N that I use on my other Duets!
One thing I noticed, I had done a little hack to the Duet Web Control code that I thought got included in the source to use a fixed width font for the Configuration File display. Since the web stuff seems to be rewritten as a bin, I can't make that change now. Is there a simple way to change this in DuetWebControl.bin or does it require recompiling?

The DuetWebControl we are using is chrishamm's version 1.11 with a small number of changes. If you can provide me with your changes, I can include them in the next version. If you want to make any changes yourself, you can find Duet Web Control for the Duet WiFi here https://github.com/dc42/DuetWebControl. The 'scripts' folder contains a Windows batch file for generating DuetWebControl.bin from source files.

mhackney · 9 Jul 2016, 13:41

David, it's a simple change. In defaults.css simply find #text_config and add the font-family line to it.

#text_config {
font-family: monospace;
background-color: inherit;
border: 0px;
margin-bottom: 15px;
min-height: 200px;
resize: none;
width: 100%;
}

I'll also make my own local .bin version for now to test and use.

thanks,
Michael

mhackney · 9 Jul 2016, 14:23

David, I'm attempting to generate the DuetWebControl.bin on a clean Windows 10 system. I run the batch file as administrator from the scripts directory and get:

C:\Users\XYZ\Desktop\DuetWebControl-master\scripts>dwcspiffs.bat
Root directory doesn't contain reprap.htm

What's the correct way to execute the batch file?

Cheers,
Michael

mhackney · 9 Jul 2016, 14:44

Ok, looking at the bat file I see it needs to be run above the scripts/ directory. I can do that now and it does everything up to the "zip" stuff. This is a clean Windows 10 system so zip is probably not available. Which zip should I use? I'm really a Mac guy and really haven't had to zip stuff on Windows.

dc42 · 9 Jul 2016, 15:05

Thanks, I've implemented that and it's working. Just a few tests do to before I release a new beta.

mhackney · 9 Jul 2016, 16:20

David, I ended up writing a shell script to create the DuetWebControl.bin file that works on OS X and Linux. I have it building and I unpacked your .bin and mine and compared and they are the same layout, files, etc. I need to upload and test it first though as the concat stuff might have a bug. However, I did find several places in your dcwspiff.bat file that I believe have incorrect file paths:

src\js\jquery-2.2.1.min.js+src\js\jquery.textarea_autosize.min.js+src\js\jquery.flot.min.js+src\js*jquery.resize.min.js*+src\js\jquery.flot.navigate.min.js+src\js\bootstrap.min.js+src\js\bootstrap-notify.min.js+src\js\bootstrap-slider.min.js+src\js*jzip.min.js*+src\js\model.js+src\js\viewmodel.js build\js\all.js

should be jquery.flot.resize.min.js
should be jszip.min.js

I think I got that right!

Once I have tested my .bin I'll send you the shell script and special instructions for linux and OS X (nothing special, just where to get mkspiffs, etc).
cheers,
Michael

dc42 · 9 Jul 2016, 16:46

Thanks Michael, I'll incorporate those corrections in my new release. If you send me a pull request or just a copy of your MacOS script, I'll add it to github.

mhackney · 10 Jul 2016, 03:06

David, this is very perplexing. I built DuetWebControl on OS X and verified that it has all the correct files packaged properly. after uploading and restarting, DWC won't stay connected. So I reverted to the .bin from your GIT but the same problem is occurring. I then reverted to the .bin that was on the CF card with the beta Duet WiFi and it's still happening. Once this happens with this message:

Error

Could not establish a connection to the Duet firmware! Please check your settings and try again.

not only can I not reconnect from the same browser, I attempted to connect with Firefox and Safari and they both report server not found. I was attending a wedding all day so haven't had time to investigate further but will do so tomorrow.

mhackney · 10 Jul 2016, 03:14

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.

Toddimus · 10 Jul 2016, 03:34

@mhackney:

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.

dc42 · 10 Jul 2016, 06:25

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.

mhackney · 10 Jul 2016, 15:41

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 interface

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

mhackney · 10 Jul 2016, 15:45

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-dc42

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

mhackney · 10 Jul 2016, 16:09

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.

mhackney · 7 Oct 2016, 16:46

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.

dc42 · 10 Jul 2016, 16:46

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.

mhackney · 10 Jul 2016, 16:47

ok! That would make sense then! I'll do that now, sorry for not reading!

Toddimus · 10 Jul 2016, 16:48

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.

mhackney · 10 Jul 2016, 16:52

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?

mhackney · 10 Jul 2016, 16:54

Toddimus, thanks but you probably didn't read David's reply, can't do it with bossac on the Duet WiFi!