Issues upgrading to 3.1.1 on Duet3+SBC



  • Hi All,

    I'm running a Duet3 + SBC (Raspberry 3) on my large delta (since I fried my old Duet).

    I'm running into a number of issues

    • Extruder not working (extrusion control remains grayed out)
      • G1 E100 F60 does not work either
      • Tool T0 is active
    • Thermostatic fan not working (manual control works fine)

    so I decided to check if I'm running the latest and greatest firmware.
    M122 reports : RepRapFirmware for Duet 3 MB6HC version 3.01-RC9 running on Duet 3 MB6HC v1.01 or later which isn't what I expected since I did an apt-get update and apt-get upgrade on the Raspberry PI...

    pi@duet3:~ $ sudo apt-get update
    Hit:1 http://archive.raspberrypi.org/debian buster InRelease
    Get:2 http://raspbian.raspberrypi.org/raspbian buster InRelease [15.0 kB]
    Hit:3 https://pkg.duet3d.com stable InRelease
    Get:4 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages [13.0 MB]
    Fetched 13.0 MB in 23s (574 kB/s)
    Reading package lists... Done
    pi@duet3:~ $ sudo apt-get upgrade
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    Calculating upgrade... Done
    0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
    

    I'm very confused...

    full M122 output

    M122
    === Diagnostics ===
    RepRapFirmware for Duet 3 MB6HC version 3.01-RC9 running on Duet 3 MB6HC v1.01 or later
    Board ID: 08DJM-956L2-G43S8-6JKDL-3S86R-183QFUsed output buffers: 1 of 40 (10 max)
    === RTOS ===
    Static ram: 154572
    Dynamic ram: 161068 of which 116 recycled
    Exception stack ram used: 408
    Never used ram: 77052
    Tasks: NETWORK(ready,2084) HEAT(blocked,1184) CanReceiv(suspended,3824) CanSender(suspended,1436) CanClock(blocked,1432) TMC(blocked,80) MAIN(running,4700) IDLE(ready,80)
    Owned mutexes:
    === Platform ===
    Last reset 00:06:28 ago, cause: software
    Last software reset at 2020-11-01 21:42, reason: User, spinning module LinuxInterface, available RAM 76756 bytes (slot 1)
    Software reset code 0x0010 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task 0x4e49414d
    Error status: 0
    Free file entries: 10
    SD card 0 not detected, interface speed: 37.5MBytes/sec
    SD card longest block write time: 0.0ms, max retries 0
    MCU temperature: min 29.8, current 30.3, max 30.4
    Supply voltage: min 24.0, current 24.2, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
    12V rail voltage: min 12.1, current 12.1, max 12.2, under voltage events: 0
    Driver 0: standstill, reads 5526, writes 19 timeouts 0, SG min/max 0/182
    Driver 1: standstill, reads 5527, writes 19 timeouts 0, SG min/max 0/177
    Driver 2: standstill, reads 5527, writes 19 timeouts 0, SG min/max 0/208
    Driver 3: standstill, reads 5533, writes 14 timeouts 0, SG min/max 0/0
    Driver 4: standstill, reads 5536, writes 11 timeouts 0, SG min/max 0/0
    Driver 5: standstill, reads 5537, writes 11 timeouts 0, SG min/max 0/0
    Date/time: 2020-11-01 21:48:57
    Slowest loop: 4.72ms; fastest: 0.15ms
    === Move ===
    Hiccups: 0(0), FreeDm: 375, MinFreeDm: 369, MaxWait: 51301ms
    Bed compensation in use: none, comp offset 0.000
    === MainDDARing ===
    Scheduled moves: 5, completed moves: 5, 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 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
    Heater 0 is on, I-accum = 0.0
    Heater 1 is on, I-accum = 0.6
    === GCodes ===
    Segments left: 0
    Movement lock held by null
    HTTP* is ready with "M122" 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 assembling a command in state(s) 0
    Trigger* is idle in state(s) 0
    Queue is idle in state(s) 0
    LCD is idle in state(s) 0
    SBC 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: 0.68ms; fastest: 0.01ms
    Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
    HTTP sessions: 0 of 8
    - Ethernet -
    State: disabled
    Error counts: 0 0 0 0 0
    Socket states: 0 0 0 0 0 0 0 0
    === CAN ===
    Messages sent 1517, longest wait 0ms for type 0
    === Linux interface ===
    State: 0, failed transfers: 0
    Last transfer: 20ms ago
    RX/TX seq numbers: 12218/12220
    SPI underruns 0, overruns 0
    Number of disconnects: 1
    Buffer RX/TX: 0/0-0
    === Duet Control Server ===
    Duet Control Server v3.1.1
    Trigger:
    Finishing macro config.g, started by system
    > Next stack level
    Code buffer space: 4096
    Configured SPI speed: 8000000 Hz
    Full transfers per second: 32.05
    

  • Moderator

    It may be worth redoing your Pi SD card with a fresh image of DuetPi if you're using one of the original images.

    https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_DuetPi

    You can also try this method of updating the firmware via DWC to get things back in sync.

    https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_Updating_Duet_3_from_RRF3_0_Beta_12_to_3_0_Final_via_DWC



  • @Phaedrux that did the trick, thanks!
    Resolution that worked for me

    • Update the firmware
    • Start with a fresh SD

Log in to reply