Software bundle 3.1.1 now available


  • administrators

    On behalf of the entire Duet3D team I am pleased to announce the releases of

    Starting from this release, we will maintain uniform version numbers for our software products in hope to simplify the upgrade process and compatibility overview. Before you go ahead and install the new versions, please read the upgrade notes for RepRapFirmware. Additional notes for DuetWebControl and DuetSoftwareFramework are available, too, but they are not as important as for RepRapFirmware. If you are upgrading from older firmware versions and ignore this, some things will NOT work! Besides, all our software and hardware files are now available on the same GitHub account.

    Users of Duet 3 + Raspberry Pi may upgrade from the stable or unstable package feeds using sudo apt-get update and sudo apt get upgrade from a command-line terminal (via SSH or on the Pi itself). All other Duet users can get the required components from the links at the top (see also here). Apart from that, new DuetPi versions with v3.1.0 are now available (see here).

    The new versions provide many bug fixes, various improvements, and conditional G-code. Now that the new object model has been declared stable, we will start documenting it as well. Until then, a preliminary auto-generated documentation can be found here.

    If you have any questions or encounter problems, please look for a post in the forum categories for

    and if you could not find one, please create it there and not here.



  • @dc42 @chrishamm It was a lot of work and a long haul I know. Congratulations!



  • Upgraded. Pi+6HC+2x3HC+1HC. No issues.

    Fantastic to have everything match. Conditional, etc.

    Thank You.



  • Sorry if I'm being thick but I'm still on a very early beta (pre - RC) firmware and it has been many months since I last installed an update. I'm not sure what the RepRap firmware zip file contains - maybe I missed something somewhere.

    I've made the following assumptions which I'd like to be confirmed please. Note, I'm still running stand alone - non RPi

    1. The "Duet2and3Firmware-3.1.0.zip is just the firmware. I still need to separately download and instal "DuetwebControl 3.1.0." Yes or no?

    2. The "Duet2and3Firmware-3.1.0.zip" is just for the main board. I still need to separately download and instal "Duet3Firmware_EXP3HC.bin" for the expansion boards. Yes or no?

    Also, what is the procedure for updating expansion board firmware these days? Do I still need to send M997 Bn after uploading it or just run M98 P"config.g"?

    Thanks


  • Moderator

    @deckingman said in Software bundle 3.1.0 now available:

    Duet2and3Firmware-3.1.0.zip

    Looks like the zip file contains everything needed for the board firmware, expansion tool board firmwares and the DWC files.

    I don't know what version you're running specifically, but it may be best to update to 3.0 with it's zip file, and then 3.01 with it's zip file



  • @Phaedrux said in Software bundle 3.1.0 now available:

    Looks like the zip file contains everything needed for the board firmware, expansion tool board firmwares and the DWC files.

    I don't know what version you're running specifically, but it may be best to update to 3.0 with it's zip file, and then 3.01 with it's zip file

    1. ref Zip file - Cool.
    2. ref 3.0 - Good point. I'd have to check but methinks it'll be something like MB6HC291919 for the main board and EXPHC28b4 for the expansion boards. I guess it'll do no harm to update to 3.0 first in any case.

    Do you happen to know if it's still necessary to send M997 Bn after uploading expansion board firmware?


  • administrators

    @deckingman said in Software bundle 3.1.0 now available:

    Do you happen to know if it's still necessary to send M997 Bn after uploading expansion board firmware?

    It should install it automatically. Use M115 B# (# = CAN address of each expansion board) to check that it worked.



  • @dc42 said in Software bundle 3.1.0 now available:

    @deckingman said in Software bundle 3.1.0 now available:

    Do you happen to know if it's still necessary to send M997 Bn after uploading expansion board firmware?

    It should install it automatically. Use M115 B# (# = CAN address of each expansion board) to check that it worked.

    Well... then... report:

    In a Pi + 6HC + 2 x 3HC + 1HC system, the 6HC was firmware upgraded during the "sudo apt upgrade". The expansions and tool were not. I M997 each manually, and that went fine.

    sudo journalctl -u duetcontrolserver (snipped to startup of 3.1 server)
    
    May 15 13:29:36 duet3 systemd[1]: Started Duet Control Server.
    May 15 13:29:36 duet3 DuetControlServer[3530]: Duet Control Server v3.1.0
    May 15 13:29:36 duet3 DuetControlServer[3530]: Written by Christian Hammacher for Duet3D
    May 15 13:29:36 duet3 DuetControlServer[3530]: Licensed under the terms of the GNU Public License Version 3
    May 15 13:29:36 duet3 DuetControlServer[3530]: [info] Settings loaded
    May 15 13:29:37 duet3 DuetControlServer[3530]: [info] Environment initialized
    May 15 13:29:37 duet3 DuetControlServer[3530]: [info] Connection to Duet established
    May 15 13:29:37 duet3 DuetControlServer[3530]: [info] IPC socket created at /var/run/dsf/dcs.sock
    May 15 13:29:37 duet3 systemd[1]: /lib/systemd/system/duetcontrolserver.service:9: CPU scheduling priority is out of range, ignoring: 20
    May 15 13:29:39 duet3 systemd[1]: /lib/systemd/system/duetcontrolserver.service:9: CPU scheduling priority is out of range, ignoring: 20
    May 15 13:29:40 duet3 systemd[1]: /lib/systemd/system/duetcontrolserver.service:9: CPU scheduling priority is out of range, ignoring: 20
    May 15 13:29:44 duet3 DuetControlServer[3530]: [info] Flashing IAP binary
    May 15 13:29:44 duet3 DuetControlServer[3530]: [info] Flashing RepRapFirmware
    May 15 13:29:51 duet3 DuetControlServer[3530]: [info] Verifying checksum
    May 15 13:29:54 duet3 DuetControlServer[3530]: [info] Firmware update successful
    May 15 13:29:54 duet3 DuetControlServer[3530]: [info] Starting macro file config.g on channel Trigger
    May 15 13:29:54 duet3 DuetControlServer[3530]: [info] FTP is enabled on port 21
    May 15 13:29:54 duet3 DuetControlServer[3530]: [info] TELNET is enabled on port 23
    May 15 13:29:55 duet3 DuetControlServer[3530]: [info] Starting macro file yLimitPark.g on channel Trigger
    May 15 13:29:55 duet3 DuetControlServer[3530]: [info] Finished macro file yLimitPark.g
    May 15 13:29:55 duet3 DuetControlServer[3530]: [warn] M307: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C
    May 15 13:29:55 duet3 DuetControlServer[3530]: [info] Starting macro file /sys/Toffsets.g on channel Trigger
    May 15 13:29:56 duet3 DuetControlServer[3530]: [info] Finished macro file /sys/Toffsets.g
    May 15 13:29:56 duet3 DuetControlServer[3530]: [info] Finished macro file config.g
    pi@duet3:~ $
    

  • administrators

    @Danal We decided to upgrade only the main firmware via the 3.1.0 package but that may change in 3.2.0. You do have to run M997 B>=1 in SBC mode to update the expansion boards.



  • @Phaedrux said in Software bundle 3.1.0 now available:

    Looks like the zip file contains everything needed for the board firmware, expansion tool board firmwares and the DWC files.

    I don't know what version you're running specifically, but it may be best to update to 3.0 with it's zip file, and then 3.01 with it's zip file

    Sorry - I'm still big thick. I've downloaded both RRF 3.0 and 3.1 zip files and extracted the contents into separate folders. I'm not seeing any DWC files that you indicated would be included, so I guess I still need to download the DWC zip separately yes? Or have I done something wrong?

    Also, I see "DuetFirmware_TOOL1LC.bin" which I'm guessing is for tool boards. So as I only have expansion boards, I don't need that yes?

    Finally, I see "Duet3_SDiap_MB6HC.bin. I think I already have that but I'm guessing this might be a later version so I ought to instal it yes?

    Cheers



  • @deckingman said in Software bundle 3.1.0 now available:

    I've downloaded both RRF 3.0 and 3.1 zip files and extracted the contents into separate folders

    upload straight to dwc, no extraction first?



  • @bearer said in Software bundle 3.1.0 now available:

    @deckingman said in Software bundle 3.1.0 now available:

    I've downloaded both RRF 3.0 and 3.1 zip files and extracted the contents into separate folders

    upload straight to dwc, no extraction first?

    Oh really? Cool👍

    Edit - things have moved on since December ☺



  • @deckingman might be a feature of dwc2, however from my point of view its always been like that even in RRF2. Then again I'm (relatively) new to the game



  • @bearer said in Software bundle 3.1.0 now available:

    @deckingman might be a feature of dwc2, however from my point of view its always been like that even in RRF2. Then again I'm (relatively) new to the game

    Yes DWC has been updated by installing from a zip file for a very long time. But last time I updated the main board and expansion boards firmware back in December it was still done by uploading the individual firmware files. So updating everything, including all the boards firmwares as well as DWC from a single zip is new to me.



  • @deckingman said in Software bundle 3.1.0 now available:

    So updating everything, including all the boards firmwares as well as DWC from a single zip is new to me.

    Didn't know it can be done like that?

    I always upload the two bin's and the DWC ask if I want to flash the updated firmware file. The "big" zip file has too much stuff, never tried uploading that one 🙂


  • administrators

    So far we are investigating two bug reports for the 3.1.0 release:

    1. One user has reported that he is getting occasional resets. The M122 report shows the reason is stack overflow from the Network task (NETW in the M122 report). If you encounter this issue, please see this thread https://forum.duet3d.com/topic/16390/3-1-0-firmware-reboots-periodically for what to do.

    2. Duet 3 with attached SBC fails to write the height map file after running G29. We are investigating this. Further information will be posted in this thread https://forum.duet3d.com/topic/16388/g29-not-writing-a-heightmap-csv.



  • @arhi Glad I'm not the only one who didn't know that (but I haven't tried it yet).



  • @dc42 Ahhh. Well in that case I'll hold off updating for now....



  • @chrishamm said in Software bundle 3.1.0 now available:

    @Danal We decided to upgrade only the main firmware via the 3.1.0 package but that may change in 3.2.0. You do have to run M997 B>=1 in SBC mode to update the expansion boards.

    Thanks. That's actually what I thought... I just read something into a post that wasn't there. 🙂



  • This post is deleted!


  • the update to 3.10 worked well, unfortunately my PanelDue 7 "no longer wants to connect to my duet2maestro
    there are already solutions for this Problem?
    thank you





  • 8.5h print - done, flawless (few small ones done before it)

    5/16/2020, 8:30:07 PM 	M122
    === Diagnostics ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.0 running on Duet Ethernet 1.02 or later
    Board ID: 08DGM-9T6BU-FG3S4-6J9FD-3SD6Q-KVRBF
    Used output buffers: 3 of 24 (14 max)
    === RTOS ===
    Static ram: 28180
    Dynamic ram: 93784 of which 32 recycled
    Exception stack ram used: 568
    Never used ram: 8508
    Tasks: NETWORK(ready,76) HEAT(blocked,1168) MAIN(running,1880) IDLE(ready,80)
    Owned mutexes:
    === Platform ===
    Last reset 21:14:17 ago, cause: power up
    Last software reset at 2020-05-15 22:30, reason: User, spinning module GCodes, available RAM 9356 bytes (slot 3)
    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN
    Error status: 10
    MCU temperature: min 28.5, current 35.4, max 37.0
    Supply voltage: min 23.0, current 24.0, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
    Driver 0: ok, SG min/max 0/367
    Driver 1: ok, SG min/max 0/411
    Driver 2: standstill, SG min/max 0/435
    Driver 3: ok, SG min/max 0/1023
    Driver 4: standstill, SG min/max not available
    Date/time: 2020-05-16 20:30:07
    Cache data hit count 4294967295
    Slowest loop: 604.84ms; fastest: 0.13ms
    I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
    === Storage ===
    Free file entries: 9
    SD card 0 detected, interface speed: 20.0MBytes/sec
    SD card longest read time 5.3ms, write time 617.0ms, max retries 0
    === Move ===
    Hiccups: 0(0), FreeDm: 157, MinFreeDm: 104, MaxWait: 44825051ms
    Bed compensation in use: mesh, comp offset 0.000
    === MainDDARing ===
    Scheduled moves: 1381801, completed moves: 1381761, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: 3
    === AuxDDARing ===
    Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
    === Heat ===
    Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
    Heater 0 is on, I-accum = 0.0
    Heater 1 is on, I-accum = 0.8
    === GCodes ===
    Segments left: 1
    Movement lock held by null
    HTTP is idle in state(s) 0
    Telnet is idle in state(s) 0
    File is doing "G1 E0.1000 F3000" in state(s) 0
    USB is idle in state(s) 0
    Aux is idle in state(s) 0
    Trigger is idle in state(s) 0
    Queue is idle in state(s) 0
    Daemon is idle in state(s) 0
    Autopause is idle in state(s) 0
    Code queue is empty.
    === Network ===
    Slowest loop: 617.56ms; fastest: 0.02ms
    Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
    HTTP sessions: 1 of 8
    Interface state active, link 100Mbps full duplex
    === Filament sensors ===
    Extruder 0 sensor: no data received
    5/16/2020, 9:12:44 PM 	Finished printing file 0:/gcodes/Body_high_detail.gcode, print time was 8h 28m
    5/17/2020, 1:10:04 AM 	M122
    === Diagnostics ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.0 running on Duet Ethernet 1.02 or later
    Board ID: 08DGM-9T6BU-FG3S4-6J9FD-3SD6Q-KVRBF
    Used output buffers: 1 of 24 (19 max)
    === RTOS ===
    Static ram: 28180
    Dynamic ram: 93784 of which 32 recycled
    Exception stack ram used: 568
    Never used ram: 8508
    Tasks: NETWORK(ready,76) HEAT(blocked,1168) MAIN(running,1880) IDLE(ready,80)
    Owned mutexes:
    === Platform ===
    Last reset 25:54:14 ago, cause: power up
    Last software reset at 2020-05-15 22:30, reason: User, spinning module GCodes, available RAM 9356 bytes (slot 3)
    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN
    Error status: 10
    MCU temperature: min 31.6, current 35.1, max 35.7
    Supply voltage: min 23.4, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
    Driver 0: standstill, SG min/max 0/315
    Driver 1: standstill, SG min/max 0/383
    Driver 2: standstill, SG min/max 0/405
    Driver 3: standstill, SG min/max 0/1023
    Driver 4: standstill, SG min/max not available
    Date/time: 2020-05-17 01:10:04
    Cache data hit count 4294967295
    Slowest loop: 79.29ms; fastest: 0.14ms
    I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
    === Storage ===
    Free file entries: 10
    SD card 0 detected, interface speed: 20.0MBytes/sec
    SD card longest read time 2.0ms, write time 0.0ms, max retries 0
    === Move ===
    Hiccups: 0(0), FreeDm: 169, MinFreeDm: 109, MaxWait: 14ms
    Bed compensation in use: mesh, comp offset 0.000
    === MainDDARing ===
    Scheduled moves: 1498329, completed moves: 1498329, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
    === AuxDDARing ===
    Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
    === Heat ===
    Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
    Heater 0 is on, I-accum = 0.0
    Heater 1 is on, I-accum = 0.7
    === GCodes ===
    Segments left: 0
    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
    USB is idle in state(s) 0
    Aux is idle in state(s) 0
    Trigger is idle in state(s) 0
    Queue is idle in state(s) 0
    Daemon is idle in state(s) 0
    Autopause is idle in state(s) 0
    Code queue is empty.
    === Network ===
    Slowest loop: 7.02ms; fastest: 0.06ms
    Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
    HTTP sessions: 1 of 8
    Interface state active, link 100Mbps full duplex
    === Filament sensors ===
    Extruder 0 sensor: no data received
    

  • administrators

    We have just published a bug fix release following the initial 3.1.0 release so the first post has been updated. This will fix potential network problems on the Duet 2 series and inconsistent code execution on the Duet 3 series in SBC mode. Apart from that, a few bugs problems have been fixed in DWC2. See the release notes in the main post for further details.



  • Hi,

    if your using Duet Wifi v1.04, which firmware package do i use?

    Duet2and3Firmware-3.1.1.zip

    OR

    Duet2CombinedFirmware.bin

    regards,

    Tony.


Log in to reply