M568 no longer needed?
-
@techbutterfly For the pi run: sudo apt update and then sudo apt upgrade in a termial like PuTTY.
-
@stephen6309 Thanks. I ran those but they didn't seem to do much and M122 still shows version 3.2.2. Can you tell what's going on here?
pi@duet3:~ $ sudo apt update Get:1 http://raspbian.raspberrypi.org/raspbian buster InRelease [15.0 kB] Hit:2 http://archive.raspberrypi.org/debian buster InRelease Hit:3 https://pkg.duet3d.com unstable InRelease Hit:4 https://pkg.duet3d.com stable InRelease Get:5 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages [13.0 MB] Fetched 13.0 MB in 25s (514 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done 6 packages can be upgraded. Run 'apt list --upgradable' to see them. pi@duet3:~ $ apt list --upgradable Listing... Done libpulse-mainloop-glib0/oldstable 12.2-4+deb10u1+rpi3 armhf [upgradable from: 12.2-4+deb10u1] libpulse0/oldstable 12.2-4+deb10u1+rpi3 armhf [upgradable from: 12.2-4+deb10u1] libpulsedsp/oldstable 12.2-4+deb10u1+rpi3 armhf [upgradable from: 12.2-4+deb10u1] pulseaudio-module-bluetooth/oldstable 12.2-4+deb10u1+rpi3 armhf [upgradable from: 12.2-4+deb10u1] pulseaudio-utils/oldstable 12.2-4+deb10u1+rpi3 armhf [upgradable from: 12.2-4+deb10u1] pulseaudio/oldstable 12.2-4+deb10u1+rpi3 armhf [upgradable from: 12.2-4+deb10u1] pi@duet3:~ $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: libxss1 rpi-eeprom-images Use 'sudo apt autoremove' to remove them. The following packages have been kept back: libpulse-mainloop-glib0 libpulse0 libpulsedsp pulseaudio pulseaudio-module-bluetooth pulseaudio-utils 0 upgraded, 0 newly installed, 0 to remove and 6 not upgraded. -
@techbutterfly Sometimes I have to run it at least twice. You might try a reboot of the pi, and run it again. For the unstable, it goes to 3.4.1.RC1 and stable is 3.4.0.
-
@stephen6309 Thanks. Is there a way to specify stable or unstable? If there is, which should I choose?
-
@techbutterfly See: https://docs.duet3d.com/en/User_manual/Machine_configuration/DSF_RPi
Unstable, if you want to try beta/rc firmware, but it may have bugs.
Stable is the released firmware.
-
@stephen6309 I would like to use the stable version. I followed the directions change to stable. But I'm still not getting any actual updates. I did run both update and upgrade multiple times and also rebooted the pi. What else can I try?
Here's what I'm getting in Putty:
pi@duet3:~ $ sudo apt update Hit:1 http://raspbian.raspberrypi.org/raspbian buster InRelease Hit:2 http://archive.raspberrypi.org/debian buster InRelease Hit:3 https://pkg.duet3d.com stable InRelease Reading package lists... Done Building dependency tree Reading state information... Done 6 packages can be upgraded. Run 'apt list --upgradable' to see them. pi@duet3:~ $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages have been kept back: libpulse-mainloop-glib0 libpulse0 libpulsedsp pulseaudio pulseaudio-module-bluetooth pulseaudio-utils 0 upgraded, 0 newly installed, 0 to remove and 6 not upgraded. pi@duet3:~ $ -
@techbutterfly When it didn't work the first time, running it again fixed it. Have you tried turning it off and on again.
-
@stephen6309 Thanks, but I have turned it off and on again - twice. And also run both update and upgrade multiple times. I don't know what else to do. I was so close to getting this fancy duet working.
-
@techbutterfly The only suggestion I have left is to redo the PI sd card with the image at https://docs.duet3d.com/en/User_manual/Machine_configuration/SBC_setup
Don't forget to save the sys files and macro files.
-
The firmware on the Duet seems not to have gotten updated during the sudo apt update, etc.
You can try updating the firmware manually in a couple of ways.
First, if you want to stay on the stable release branch, you can downgrade the pi software using these steps.
https://docs.duet3d.com/en/User_manual/Machine_configuration/DSF_RPi#switch-to-stable-packages
Then you can try and manually update the firmware by uploading the firmware bin file in DWC. It may prompt to install it. If not, you can send M997 to trigger an update.
Upload these files in this order.
https://github.com/Duet3D/RepRapFirmware/releases/download/3.4.0/Duet3_SDiap32_MB6HC.bin
https://github.com/Duet3D/RepRapFirmware/releases/download/3.4.0/Duet3Firmware_MB6HC.bin
That should get you to 3.4 all around. If not, and it's still stuck, you can use USB and bossa software to flash it with a PC as described here:
https://docs.duet3d.com/en/User_manual/RepRapFirmware/Updating_firmware#fallback-procedure-2
-
@phaedrux Thanks for those detailed instructions. I've completed them and now I'm able to start the heaters as expected. Here's the result of M122, just for a sanity check. Does everything look right now?
M122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.4.0 (2022-03-15 18:57:24) running on Duet 3 MB6HC v1.01 or later (SBC mode) Board ID: 08DJM-956BA-NA3TN-6J9F6-3SN6N-TB8UU Used output buffers: 1 of 40 (13 max) === RTOS === Static ram: 151000 Dynamic ram: 65728 of which 424 recycled Never used RAM 133520, free system stack 216 words Tasks: SBC(ready,0.6%,487) HEAT(notifyWait,0.0%,321) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,944) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,333) TMC(notifyWait,7.8%,92) MAIN(running,91.6%,923) IDLE(ready,0.0%,30), total 100.0% Owned mutexes: HTTP(MAIN) === Platform === Last reset 00:03:06 ago, cause: software Last software reset at 2022-05-14 14:47, reason: User, none spinning, available RAM 133520, slot 0 Software reset code 0x0012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a Error status: 0x00 Aux0 errors 0,0,0 Step timer max interval 131 MCU temperature: min 43.0, current 43.1, max 43.2 Supply voltage: min 23.8, current 23.9, max 23.9, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 12.0, current 12.0, max 12.0, under voltage events: 0 Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0 Events: 0 queued, 0 completed Driver 0: standstill, SG min n/a, mspos 8, reads 23991, writes 0 timeouts 0 Driver 1: standstill, SG min n/a, mspos 8, reads 23991, writes 0 timeouts 0 Driver 2: standstill, SG min n/a, mspos 8, reads 23991, writes 0 timeouts 0 Driver 3: standstill, SG min n/a, mspos 8, reads 23991, writes 0 timeouts 0 Driver 4: standstill, SG min n/a, mspos 8, reads 23991, writes 0 timeouts 0 Driver 5: standstill, SG min n/a, mspos 8, reads 23991, writes 0 timeouts 0 Date/time: 2022-05-14 14:50:30 Slowest loop: 1.05ms; fastest: 0.05ms === Storage === Free file entries: 10 SD card 0 not detected, interface speed: 37.5MBytes/sec SD card longest read time 0.0ms, write time 0.0ms, max retries 0 === Move === DMs created 125, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0 === GCodes === Segments left: 0 Movement lock held by null HTTP* is doing "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 idle 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 Aux2 is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty === CAN === Messages queued 39, received 0, lost 0, boc 0 Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 50 (min 50), ts 22/0/0 Tx timeouts 0,0,22,0,0,17 last cancelled message type 30 dest 127 === SBC interface === Transfer state: 4, failed transfers: 0, checksum errors: 0 RX/TX seq numbers: 7579/7579 SPI underruns 0, overruns 0 State: 5, disconnects: 0, timeouts: 0, IAP RAM available 0x2b880 Buffer RX/TX: 0/0-0, open files: 0 === Duet Control Server === Duet Control Server v3.4.0 Code buffer space: 4096 Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0 Full transfers per second: 39.59, max time between full transfers: 31.1ms, max pin wait times: 26.2ms/0.1ms Codes per second: 0.24 Maximum length of RX/TX data transfers: 3108/820 -
undefined TechButterfly has marked this topic as solved
-
Yes that looks good now. You're versions match.
