Firmware 2.0RC1 and 1.21.1RC1 released

dc42

@shadowx said in Firmware 2.0RC1 and 1.21.1RC1 released:

@dc42

My settings all have the Thermostatic control turned off.
Edit: It seems like you already confirmed that its a bug.

I updated the firmware using the "upload file" function on the DWC, however, it still shows up as 1.21 after the "update". I uploaded with the older revision of DWC and also the RC1 version and it would not update the firmware. I don't know if others have the same issues with upgrading the firmware. I have the DuetWifi version 1.01 board and tried upgrade using the "Duet2CombinedFirmware.bin" file.

Is there a different process to upload the RC1 file?

If you are already running main firmware 1.21 and DWC 1.21 or later, then you should just be able to upload the new Duet2CombinedFirmware.bin file through the Settings/General page of DWC. DWC should then offer to install it.

Printtome3d

@bmmal said in Firmware 2.0RC1 and 1.21.1RC1 released:

DWC

Hello i have two Duet 3D WiFi and one after Install the new firmware the DWC have crash and reboot when i try to Connect to the board. Can you Help me.

dc42

I'm sorry to here you are unable to run the new firmware. Suggestions:

If you have a PanelDue connected, disconnect it and see if the Duet will start up.
Remove the SD card, then power up the Duet and see if you can connect via USB.
If either #1 or #2 lets you start the Duet, run M122 immediately and post the software reset data here.

Printtome3d

ok i am going to do this and send to you the result of M112

Printtome3d

this is the error when i try to Connect to the board with the DWC.

SyntaxError: JSON Parse error: Unexpected identifier "nan"

Printtome3d

This is the result of M122 send on USB

< 20:00:39: ResponseBusy
< 20:00:39: Bad recv status size
< 20:00:39: WiFi: avail: 10
< 20:00:39: WiFi: used: 0
< 20:00:39: === Diagnostics ===

< 20:00:39: RepRapFirmware for Duet 2 WiFi/Ethernet version 2.0(RTOS)RC1 running on Duet WiFi 1.02 or later
< 20:00:39: Board ID: 08DDM-9FAM2-LW4S4-6JKF0-3S86J-TLSBX
< 20:00:39: Used output buffers: 1 of 20 (11 max)
< 20:00:39: === RTOS ===
< 20:00:39: Static ram: 28484
< 20:00:39: Dynamic ram: 96036 of whiWiFi: max: 0
< 20:00:39: ch 0 recycled
< 20:00:39: Exception stack ram used: 408
< 20:00:39: Never used ram: 6144
< 20:00:39: Task NETWORK ready, free stack 340
< 20:00:39: Task HEAT blocked, free stack 1260
< 20:00:39: Task MAIN running, free stack 3800
< 20:00:39: === Platform ===
< 20:00:39: Last reset 20:29:50 ago, cause: power up
< 20:00:39: Last software reset at 2018-05-08 00:36, reason: User, spinning module GCodes, WiFi: err: 0
< 20:00:39: available RAM 3848 bytes (slot 2)
< 20:00:39: Software reset code 0x0003 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0041f000, BFAR 0xe000ed38, SP 0xffffffff
< 20:00:39: Error status: 0
< 20:00:39: Free file entries: 10
< 20:00:39: SD card 0 detected, inteWiFi:
< 20:00:39: rface speed: 20.0MBytes/sec
< 20:00:39: SD card longest block write time: 0.0ms
< 20:00:39: MCU temperature: min 34.1, WiFi: avail: 4
< 20:00:39: current 34.3, max 38.8
< 20:00:39: Supply voltage: min 0.2, current 0.4, max 12.9, under voltage events: 1, over voltage events: 0
< 20:00:39: Driver 0: standstill, SG min/max not availWiFi: used: 0
< 20:00:39: able
< 20:00:39: Driver 1: standstill, SG min/max not available
< 20:00:39: Driver 2: standstill, SG min/max not available
< 20:00:39: Driver 3: standstill, SG min/maWiFi: max: 0
< 20:00:39: x not available
< 20:00:39: Driver 4: standstill, SG min/max not available
< 20:00:39: Date/time: 2018-05-09 20:00:35
< 20:00:39: Slowest main loop (seconds): 0.0WiFi: err: 0
< 20:00:39: 12307; fastest: 0.000065
< 20:00:39: === Move ===
< 20:00:39: Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm 236, MaxWait: 2696479971ms, Underruns: 0, 0
< 20:00:39: Scheduled moves: 9, completed moves: 9
< 20:00:39: Bed compensation in use: none
< 20:00:39: Bed probe heights: 0.000 0.000 0.000 0.000 0.000
< 20:00:39: === Heat ===
< 20:00:39: Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
< 20:00:39: === GCodes ===
< 20:00:39: Segments left: 0
< 20:00:39: Stack records: 2 allocated, 0 in use
< 20:00:39: Movement lock held by null
< 20:00:39: http is idle in state(s) 0
< 20:00:39: telnet is idle in state(s) 0
< 20:00:39: file is idle in state(s) 0
< 20:00:39: serial is ready with "M122 " in state(s) 0
< 20:00:39: aux is idle in state(s) 0
< 20:00:39: daemon is idle in state(s) 0
< 20:00:39: queue is idle in state(s) 0
< 20:00:39: autopause is idle in state(s) 0
< 20:00:39: Code queue is empty.
< 20:00:39: === Network ===
< 20:00:39: Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
< 20:00:39: HTTP sessions: 0 of 8
< 20:00:39: - WiFi -
< 20:00:39: Network state is running
< 20:00:39: WiFi module is connected to access point
< 20:00:39: Failed messages: pending 0, notready 0, noresp 0
< 20:00:39: WiFi firmware version 1.21
< 20:00:39: WiFi MAC address 60:01:94:34:38:80
< 20:00:39: WiFi Vcc 3.32, reset reason Turned on by main processor
< 20:00:39: WiFi flash size 4194304, free heap 15912
< 20:00:39: WiFi IP address 192.168.1.76
< 20:00:39: WiFi signal strength -62dBm, reconnections 0, sleep mode modem
< 20:00:39: Socket states: 0 0 0 0 0 0 0 0
< 20:00:39: === Expansion ===

Printtome3d

ok i try test the DWC on Google Chrome and is Connect to the board but when i click on the settings the DWC disconnect and give me the error SyntaxError: Unexpected token a in JSON at position 216

AS-3D Druck

First print was successful 2. print in Progress.
The new Firmware works fine for.

dc42

@printtome3d said in Firmware 2.0RC1 and 1.21.1RC1 released:

this is the error when i try to Connect to the board with the DWC.

SyntaxError: JSON Parse error: Unexpected identifier "nan"

Thanks. Please send M408 S2 and then M408 S3 from USB, and post the responses here.

Printtome3d

Thanks i have put the old DWC and the board work fine, them i have update the DWC to the new 1.21.1 and now works very well this firmware is the better Version of all i have print with the two Duet WiFi and the result is very good. thank for all

ShadowX

@dc42 said in Firmware 2.0RC1 and 1.21.1RC1 released:

@shadowx said in Firmware 2.0RC1 and 1.21.1RC1 released:

@dc42

My settings all have the Thermostatic control turned off.
Edit: It seems like you already confirmed that its a bug.

I updated the firmware using the "upload file" function on the DWC, however, it still shows up as 1.21 after the "update". I uploaded with the older revision of DWC and also the RC1 version and it would not update the firmware. I don't know if others have the same issues with upgrading the firmware. I have the DuetWifi version 1.01 board and tried upgrade using the "Duet2CombinedFirmware.bin" file.

Is there a different process to upload the RC1 file?

If you are already running main firmware 1.21 and DWC 1.21 or later, then you should just be able to upload the new Duet2CombinedFirmware.bin file through the Settings/General page of DWC. DWC should then offer to install it.

I am running 1.21 and using Duet Wifi 1.0 or 1.01. I upload the Duet2CombinedFirmware.bin through the DWC Settings/General/Upload files. It would upload the file and ask me if "You have just uploaded a firmware file. Would you like to update your Duet now?" I press "Yes" to proceed with the update. It goes through the process with the green bar till completion. However, the version stay the same as shown below. I performed this upgrade with the released 1.21 DWC and also the RC1 version shown below with the same results.

I think this may affect the people still using the original or 1.01 hardware but not the later versions. It would be great if someone else with the same hardware can confirm if this is a bug.

Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
Firmware Electronics: Duet WiFi 1.0 or 1.01
Firmware Version: 1.21 (2018-03-21)
WiFi Server Version: 1.21
Web Interface Version: 1.21.1-RC1

Edit: I retried the process by renaming the file as "DuetWifiFirmware.bin" and it worked. It would not work when it was named as "Duet2CombinedFirmware.bin" when I uploaded it. The file in the system editor is now named "Duet2CombinedFirmware.bin". It looks like the DWC or the firmware was looking for that original file name and rejected the update if its not the right filename. The system now shows 2.0(RTOS)RC1 on the software information page.

Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
Firmware Electronics: Duet WiFi 1.0 or 1.01
Firmware Version: 2.0(RTOS)RC1 (2018-05-02b1)
WiFi Server Version: 1.21
Web Interface Version: 1.21.1-RC1

rmriggin

Just updated to the latest 2.0 RC and had a print just stop with no error or message 6 hours into a print. Print looked excellent and came back to it and it was just stopped with print head still over the print like it just stopped in the middle of a layer. The bed and nozzle were not at temp still either. I'll have to lookup the and to pull log and see if it shines any light on what happened.

dc42

@shadowx said in Firmware 2.0RC1 and 1.21.1RC1 released:

...
Edit: I retried the process by renaming the file as "DuetWifiFirmware.bin" and it worked. It would not work when it was named as "Duet2CombinedFirmware.bin" when I uploaded it. The file in the system editor is now named "Duet2CombinedFirmware.bin". It looks like the DWC or the firmware was looking for that original file name and rejected the update if its not the right filename. The system now shows 2.0(RTOS)RC1 on the software information page.

It might just mean that you have a very old version of iap4e.bin on the SD card. Try uploading the latest one through DWC.

dc42

@rmriggin said in Firmware 2.0RC1 and 1.21.1RC1 released:

Just updated to the latest 2.0 RC and had a print just stop with no error or message 6 hours into a print. Print looked excellent and came back to it and it was just stopped with print head still over the print like it just stopped in the middle of a layer. The bed and nozzle were not at temp still either. I'll have to lookup the and to pull log and see if it shines any light on what happened.

I'm sorry to hear that you had a crash. It's possible that you hit the bug reported by @BMMal in the second post in this thread. Please can you run M122 and post the software reset data from that report.

ShadowX

@dc42 said in Firmware 2.0RC1 and 1.21.1RC1 released:

iap4e.bin

I still had the original iap4e.bin file from 6/11/2016. I didn't realize I had to update that until I looked at the bottom of the 1.21 which mentions the iap4e.bin should be revised also. Thanks.

dc42

@shadowx said in Firmware 2.0RC1 and 1.21.1RC1 released:

@dc42 said in Firmware 2.0RC1 and 1.21.1RC1 released:

iap4e.bin

I still had the original iap4e.bin file from 6/11/2016. I didn't realize I had to update that until I looked at the bottom of the 1.21 which mentions the iap4e.bin should be revised also. Thanks.

Thanks for confirming. The original iap4e.bin file had the firmware filename hard coded as "DuetWiFiFirmware.bin". Later versions use the filename passed to them by the firmware that is being replaced.

ShadowX

@dc42 said in Firmware 2.0RC1 and 1.21.1RC1 released:

@shadowx said in Firmware 2.0RC1 and 1.21.1RC1 released:

@dc42 said in Firmware 2.0RC1 and 1.21.1RC1 released:

iap4e.bin

I still had the original iap4e.bin file from 6/11/2016. I didn't realize I had to update that until I looked at the bottom of the 1.21 which mentions the iap4e.bin should be revised also. Thanks.

Thanks for confirming. The original iap4e.bin file had the firmware filename hard coded as "DuetWiFiFirmware.bin". Later versions use the filename passed to them by the firmware that is being replaced.

I just did a quick test with the old iap4e.bin and it won't take the 2.0RC1 update. As soon as I updated the file to the latest one from 1.21, the update worked perfectly. Thanks for all your help. Hopefully, this will help someone else if they have not updated that file.

rmriggin

@dc42 misread the command and did a M112 which cleared log so I guess I won't know what caused that print failure.

ayudtee

@dc42, I am pleased that you have created another release for the SAM3XA boards. I have a duet 0.8.5 on an Ormerod 2, and I installed 1.21.1. Unfortunately it noticeably slowed down the printer. I only ran a few prints on 1.21.1RC1 before I downgraded back to 1.21. I read in your post that released 2.0RC2 that you had not received any feedback on 1.21.1RC1 and apologize for not responding days ago. I also read that you have upgraded your Ormerod to a Maestro. If you would like any further followup feedback or testing on 1.2.1RC1 or anything else, my Ormerod 2 and I are at your disposal Sir.

rmriggin

@dc42 said in Firmware 2.0RC1 and 1.21.1RC1 released:

@rmriggin said in Firmware 2.0RC1 and 1.21.1RC1 released:

Just updated to the latest 2.0 RC and had a print just stop with no error or message 6 hours into a print. Print looked excellent and came back to it and it was just stopped with print head still over the print like it just stopped in the middle of a layer. The bed and nozzle were not at temp still either. I'll have to lookup the and to pull log and see if it shines any light on what happened.

I'm sorry to hear that you had a crash. It's possible that you hit the bug reported by @BMMal in the second post in this thread. Please can you run M122 and post the software reset data from that report.

@dc42 it happened again at the same height into a print (25mm)

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.0(RTOS)RC1 running on Duet Ethernet 1.02 or later
Board ID: 08DDM-9FAMU-JW4S4-6JKD4-3SJ6R-92YRV
Used output buffers: 3 of 20 (9 max)
=== RTOS ===
Static ram: 28484
Dynamic ram: 95388 of which 16 recycled
Exception stack ram used: 324
Never used ram: 6860
Task NETWORK ready, free stack 448
Task HEAT blocked, free stack 1260
Task MAIN running, free stack 3800
=== Platform ===
Last reset 07:41:11 ago, cause: software
Last software reset at 2018-05-11 01:00, reason: Hard fault, spinning module GCodes, available RAM 6516 bytes (slot 3)
Software reset code 0x4033 HFSR 0x40000000, CFSR 0x00010000, ICSR 0x0441f803, BFAR 0xe000ed38, SP 0x200049dc
Stack: 00444d4f 00424f82 61000000 0042afda 21000000 0000000a 20000180 200001e0 00000000 000000f8 00000000 00000000 2000b3c8 2000a480 00000000 000000f8 20004cf4 a5a5a5a5 a5a5a5a5 a5a5a5a5 00424fc3 2000b3c8 0042afe1 00000000
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 46.2, current 46.7, max 54.8
Supply voltage: min 24.1, current 24.2, max 24.4, under voltage events: 0, over voltage events: 0
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 2018-05-11 08:41:38
Slowest main loop (seconds): 0.006040; fastest: 0.000069
=== Move ===
Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm 240, 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
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
=== 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
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8
Interface state: 5
=== Expansion ===