Software bundle 3.1.1 now available



  • @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.


Log in to reply