New firmware 1.19 beta 2
-
Sounds like the kind of crashes I had before but I upgraded to beta4 this morning and it's been printing now for 7-8hours without a crash yet. Seems like the bug I was experiencing is fixed now. I got a old-school cartesian setup tho so no corexy here.
-
Hi guys. After updating the firmware, the machine becomes unresponsive. After turning it off and back on, it seems to revert to the last firmware. I had either Beta 2 or 3 on there. Bed leveling doesn't work. After resetting it still has the same Mac address, I believe that should have changed with beta 4. This is what displays after trying to update there firmware. I have done it with the web interface and the USB gcode method. Both produce the same results. THANKS!
Firmware Electronics: Duet Ethernet 1.0
Firmware Version: 1.19-b6 (2017-05-19)
Web Interface Version: 1.16 -
celebrated t o early
Crashed now after trying to start a print. It became unresponsive and I had to reboot it by powercycle to get it back on. Just stopped mid-print like the other times. I'm rolling back to the version where the web interface is on own chip again to check if that removes these problems so I can see if it could be hardware related. -
Thanks for the reports. I had a 0x5001 software reset earlier today too using beta4 on a Duet WiFi. I'm looking into it.
-
I can't seem to figure out what it is that causes it. This time to was the first time today where I used 2x baby steps upwards. Can't remember if I did that before so could be just a coinsidense ^^ Back on 1.18 now printing fine. Will try printing 10-15hours just to see that it works before I can confirm that it's nothing hardware/network related here. I know I don't have the best wifi signals at -73dB but it's no problem to use and the speed is decent. It's also has not been a problem before.
-
Is there any reasonable way to complete the upgrade without USB or a PanelDue (specifically getting reconnected to wifi)? Hooking up a USB cable to my printer is a gigantic pain.
-
I know in general terms why these resets are happening, and I expect to fix it in a new beta today.
@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.
-
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.
-
Beta 5 does the same thing for me. While flashing the firmware becomes unresponsive. After power down and up, it is running the old firmware.
I'm excited for this firmware to become stable. I want to buy a couple more
-
Beta 5 does the same thing for me. While flashing the firmware becomes unresponsive. After power down and up, it is running the old firmware.
I'm excited for this firmware to become stable. I want to buy a couple more
You mean it's still reporting in DWC that beta 4 is running? You may need to update file iap4e.bin to latest version first - just up!oad it through the Settings/General page as you do the firmware.
-
Where do I find the most up to date iap4e.bin? The one in my sys directory currently is 60.0 KiB 4/7/2017, 1:24:13 PM.
I noticed I am on the CK fork. Could that be my problem? I believe at the time you had not released the most up to date Duet Ethernet firmware. I was trying to get bed mesh to work so I was trying anything I could think of.
Thank you for the quick responses as always.
-
I used SAM-BA to flash beta 5. That appears to have worked. As I was pressing the erase button I realized the reset button MAY have been pressed by a wire.
-
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.
