New firmware 1.19 beta 2
-
I have withdrawn beta 4 and released beta 5, which fixes the known issue that was causing software resets. Those of you who were affected by this, please accept my apologies for the inconvenience caused. The WiFi module code has not changed, so you can install beta 5 over beta 4 using the standard firmware upgrade procedure.
The Duet06/085 build is still at beta 4 because it was not affected by this issue.
Nothing to apologise for! I'm using the beta releases to try to help test and locate the bugs. If I needed is to be stable all the time I'd be on the stable release
Glad to see that you got it sorted.You are doing great work btw!
-
@kelchm, you don't need USB or PanelDue to complete the upgrade. See https://duet3d.com/wiki/DuetWiFiFirmware_1.19_alpha#Getting_ready_to_upgrade. But I recommend you wait until I have released beta 5.
Just reviewing the steps again it seems step 2 under 'Doing the upgrade' requires a PanelDue or USB:
"When the Duet has restarted after the firmware upgrade, execute the SetNetwork macro on PanelDue or via USB (if using USB then the command is M98 P/macros/SetNetwork)." -
I see.
You could temporarily put that M98 command at the end of config.g.EDIT: I just realised that won't work, because the network won't be enabled at that point.
In a later beta I will add the facility to set up the connection by temporarily running the Duet as an access point, as before.
-
I'll give another try to 1.19 soon.. with the 1yr old twins, time is missing
-
I just updated my test machine to beta 5. Still the same problem where it won't connect to my network. After [c]M552 S1[/c], nothing happens for a while, until it finally says "Wifi module is idle".
-
In theory that means that you didn't send it a M587 command with the correct SSID and password, or that it can't see the wifi network. You can send M587 with no parameters to check that it has remembered the SSID correctly.
-
Hmm. I added another network (M587 reports both), and it did successfully join that one. Unfortunately, that's not the network I ideally want to use. Countless other devices in my home connect to my regular network without any problems. Strange.
-
I've just noticed a bug. If the password contains a semicolon then the M587 command will not be parsed correctly. So passwords containing semicolons won't work. I'll fix this in the next beta.
There may be other characters that won't work in wifi passwords - unfortunately the SDK for the WiFi module is not open source, so I can't check. But they should be the same characters that didn't work before, or a subset of them.
-
Just updated to 1.19 Beta 5, working well overall. noticed two small issues
-
when using Gcode console, if i try to add a new wifi network using
M587 S"Wifi Name" P"MyPassword" it will convert it all to Capitals. even if i need it to be Case sensitive. -
during a print, I paused it, and then went to control on Panel Due and wanted to extrude extra filament as i was changing rolls.. i set to to extrude 50mm at 5mms/sec and it ignores the speed setting and tried to extrude all within 1 second.. which was way too fast and caused the extruder to skip, dont recall if this was an issue on previous firmware
-
-
Just updated to 1.19 Beta 5, working well overall. noticed two small issues
-
when using Gcode console, if i try to add a new wifi network using
M587 S"Wifi Name" P"MyPassword" it will convert it all to Capitals. even if i need it to be Case sensitive. -
during a print, I paused it, and then went to control on Panel Due and wanted to extrude extra filament as i was changing rolls.. i set to to extrude 50mm at 5mms/sec and it ignores the speed setting and tried to extrude all within 1 second.. which was way too fast and caused the extruder to skip, dont recall if this was an issue on previous firmware
For number 1 you can turn off "Always Convert G-Codes to Upper-Case" in "Settings > User Interface", probably DWC need a check to see if it is a M587 gcode or simply leave the case of quoted parameters.
-
-
Hoping a Tab can be added to webcontrol to add/remove wifi networks. Enable ADhoc
-
I've just released 1.19beta6. Those of you already running a 1.19beta version can just install it over the network. See https://github.com/dc42/RepRapFirmware/blob/dev/WHATS_NEW.md for the change list.
-
I've just released this at https://github.com/dc42/RepRapFirmware/tree/dev/Release (look in the Edge folder for your board). See https://github.com/dc42/RepRapFirmware/blob/dev/WHATS_NEW.md for the full change information and important upgrade notes.
Hello,
what means this :"DuetWiFiServer-1.19beta1.bin Restored DuetWiFiServer-1.19beta1.bin"
Thank you
Dommy -
I accidentally removed that file from the Duet-WiF/Edge folder when I committed release 1.19beta6 of RepRapFirmware. So I put it back again.
-
1.19 beta 6 does not connect
I tried 1.19 beta6 but is unable to get the printer to connect to my wifi.
After updating, and running the SetNetwork macro, I connect through USB and M552 returns "Wifi module is idle"
Sending "M552 S1" and I get "Wifi module is changing state" for 1-2 minutes, then "Wifi module is idle" again.Ideas?
-
Meh, M552 S2 responds:
11:24:24.849 : WiFi reported error: invalid access point configuration -
M588 * does not work. Nothing is deleted
-
So I try to get the machine into AP mode:
11:45:44.303 : serial: N45 M589 S"DuetWifi" P"Silverspoon" I192.168.1.1*28
And then M552 S2
I get:
11:46:03.063 : WiFi reported error: invalid access point configuration -
I don't think AP mode is implemented yet, is it?
But yeah, I have the same problem joining my network. It just sits there doing nothing, like it can't find the network at all. Signal strength should be fine, and no other devices have any problems joining at all.
-
I got it to work by deleting all known networks one at a time and re-add my main wifi.
