New firmware 1.19 beta 2
-
I upgraded to 1.19beta3. Now it does not connect over a web connection. In fact it does not advertise its web service at all.
(I'm an IT guy…)
Do I need to revert to the 1.18 i was running or is there a way to correct this? How would I roll it back to the previous firmwares? -
You need to set up access to your router different!y. There is a link to the instructions in the upgrade notes, but here it is for your convenience: https://duet3d.com/wiki/DuetWiFiFirmware_1.19_alpha.
-
you live in a country with high humidity, then this problem might be caused by condensation, and I may be able to suggest a modification you could try.
I'm not having any problems ('over the moon' is best description of my new DuetWifi experience!) - but I do live in such a country. Interested in any suggestions for ensuring the long term health of the system in such an environment?
-
Hi dc42, i actually live in Scotland so humidity isn't really an issue. The ajax errors have always been there but its the number of times that i need to re-flash the firmware that is starting to really frustrate. I can do a print and everything is perfect then go to do another and have no access to the web interface.
-
Please ask your supplier to replace the board. I think the microcontroller chip is faulty, it doesn't seem to be holding the state of the "Boot from flash" flag.
-
Hi dc42 thanks for that, the board actually came direct from yourselves.
-
Please send us an email and we will sort it!
-
Hi Tony just emailed you.
-
Well. Just tried the new beta4. Still no joy. Won't connect. Really looking forward to an ethernet module.
-
Have anyone that had crashes with alpa and beta1/2 tested the most recent ones? Any crashes?
-
David,
I've flashed beta 4 yesterday on my corexy and the board is resetting by itself without any known reason.
Yesterday the printer reseted during a print that was running for less than 5 minutes and this morning I was running my bed compensation macro and it crashed again.this is the m122 output.
M122
=== Diagnostics ===
Used output buffers: 3 of 32 (5 max)
=== Platform ===
RepRapFirmware for Duet WiFi version 1.19beta4 running on Duet WiFi 1.0
Board ID: 08DAM-999TL-NL5T8-6J1DA-3SJ6P-T55BJ
Static ram used: 20356
Dynamic ram used: 95876
Recycled dynamic ram: 2552
Stack ram used: 1304 current, 3804 maximum
Never used ram: 8484
Last reset 00:00:13 ago, cause: software
Last software reset reason: User, spinning module Network, available RAM 8484 bytes (slot 4)
Software reset code 0x5001, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0040080f, BFAR 0xe000ed38, SP 0xffffffff
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min -270.2, current 16.4, max 16.7
Supply voltage: min 11.2, current 11.4, max 11.7, under voltage events: 0, over voltage events: 0
Driver 0: stalled standstill
Driver 1: stalled standstill
Driver 2: stalled standstill
Driver 3: stalled standstill
Driver 4: standstill
Date/time: 2017-06-03 09:17:31
Slowest main loop (seconds): 0.004786; fastest: 0.000030
=== Move ===
MaxReps: 0, StepErrors: 0, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 0, completed moves: 0
Bed compensation in use: mesh
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
Probe change coordinates:
=== Heat ===
Bed heater = 0, chamber heater = -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Stack records: 1 allocated, 0 in use
Movement lock held by null
http is idle in state(s) 0
telnet is idle in state(s) 0
file is idle in state(s) 0
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
Code queue is empty.
Network state is running
WiFi module is connected to access point
WiFi firmware version 1.19-beta1
WiFi MAC address 5c:cf:7f:1b:3c:b8
WiFi Vcc 3.11, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 39864
WiFi IP address 192.168.1.101
WiFi signal strength -63db
HTTP sessions: 1 of 8
Socket states: 2 0 0 0 0 0 0 0
Responder states: HTTP(1) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) -
I ran the macro again and this time it failed just after its completion.
M122
=== Diagnostics ===
Used output buffers: 3 of 32 (6 max)
=== Platform ===
RepRapFirmware for Duet WiFi version 1.19beta4 running on Duet WiFi 1.0
Board ID: 08DAM-999TL-NL5T8-6J1DA-3SJ6P-T55BJ
Static ram used: 20356
Dynamic ram used: 95876
Recycled dynamic ram: 2552
Stack ram used: 1304 current, 3804 maximum
Never used ram: 8484
Last reset 00:00:13 ago, cause: software
Last software reset reason: User, spinning module Network, available RAM 7824 bytes (slot 0)
Software reset code 0x5001, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0440f80f, BFAR 0xe000ed38, SP 0xffffffff
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min -270.2, current 16.6, max 17.1
Supply voltage: min 11.2, current 11.6, max 11.7, under voltage events: 0, over voltage events: 0
Driver 0: stalled standstill
Driver 1: stalled standstill
Driver 2: stalled standstill
Driver 3: stalled standstill
Driver 4: standstill
Date/time: 2017-06-03 09:31:52
Slowest main loop (seconds): 0.004088; fastest: 0.000030
=== Move ===
MaxReps: 0, StepErrors: 0, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 0, completed moves: 0
Bed compensation in use: mesh
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
Probe change coordinates:
=== Heat ===
Bed heater = 0, chamber heater = -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Stack records: 1 allocated, 0 in use
Movement lock held by null
http is idle in state(s) 0
telnet is idle in state(s) 0
file is idle in state(s) 0
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
Code queue is empty.
Network state is running
WiFi module is connected to access point
WiFi firmware version 1.19-beta1
WiFi MAC address 5c:cf:7f:1b:3c:b8
WiFi Vcc 3.10, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 39736
WiFi IP address 192.168.1.101
WiFi signal strength -63db
HTTP sessions: 1 of 8
Socket states: 2 0 0 0 0 0 0 0
Responder states: HTTP(1) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) -
David,, I just downgraded back to 1.18.1 and everything is fine, no more unexpected reset
-
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.