Made a mistake while upgrading, my system from 3.4.2 to 3.4.6
-
Hi,
Made mistake upgrading, my system from 3.4.2 to 3.4.6 on my Duet 3 MB6HC v1.01 (SBC mode).
I can not do ssh so I hooked up a screen, keyboard and mouse. And made the upgrade.
Then I went to my wifi connected notebook and wanted to check what had happened. To see if I could down load the config.g
Made a M122 to see how far the installation had proceeded and by mistake I hit a M112.There was not a immediate shutdown so the upgrade proceeded but the firmware on the 1XD board and the MB6HC did not get installed. The installation stoped at 98%.
I can't remember if I restarted the 1XD that could not have a firmware upgrade. But the installation ended.
I made manual upgrade to 1XD
M997 S0 to upgrade the main boardPart of the M122 say that the 3.4.6 is installed
M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.6 (2023-07-21 14:11:38) running on Duet 3 MB6HC v1.01 (SBC mode)
Board ID: 08DJM-9P63L-DJ3T0-6J9FJ-3S86S-T80Z8
Used output buffers: 1 of 40 (13 max)The printer runs. But I can't get the {state.time} to get updated. It is the same everytime my daemon.g echos it to the control.
Is that enough? Or do I have to check other things to be upgraded?
-
@Schickfus Can you confirm that you upgraded DSF as well? I cannot reproduce your problem on my setup with 3.4.6:
Note that the 1-hour discrepancy is because I haven't updated the timezone on my SBC yet.
-
-
Post the full output of M122.. The DSF version is near the end.
-
M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.6 (2023-07-21 14:11:38) running on Duet 3 MB6HC v1.01 (SBC mode)
Board ID: 08DJM-9P63L-DJ3T0-6J9FJ-3S86S-T80Z8
Used output buffers: 1 of 40 (13 max)
=== RTOS ===
Static ram: 153252
Dynamic ram: 66352 of which 0 recycled
Never used RAM 128068, free system stack 130 words
Tasks: SBC(ready,2014.0%,466) HEAT(notifyWait,9.4%,371) Move(notifyWait,1255.3%,214) CanReceiv(notifyWait,140.5%,773) CanSender(notifyWait,8.0%,327) CanClock(delaying,17.1%,344) TMC(notifyWait,23115.4%,90) MAIN(running,3453.6%,1231) IDLE(ready,29.3%,30), total 30042.6%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 15:54:45 ago, cause: power up
Last software reset at 2023-08-22 12:21, reason: User, GCodes spinning, available RAM 128036, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
Error status: 0x00
Step timer max interval 136
MCU temperature: min 33.3, current 39.0, max 53.9
Supply voltage: min 12.0, current 12.1, max 12.1, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 11.2, current 11.3, max 11.4, under voltage events: 0
Heap OK, handles allocated/used 99/1, heap memory allocated/used/recyclable 2048/870/854, gc cycles 2607
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0, mspos 8, reads 50647, writes 11 timeouts 0
Driver 1: standstill, SG min 0, mspos 8, reads 50647, writes 11 timeouts 0
Driver 2: standstill, SG min 0, mspos 8, reads 50647, writes 11 timeouts 0
Driver 3: standstill, SG min 0, mspos 8, reads 50647, writes 11 timeouts 0
Driver 4: standstill, SG min 0, mspos 8, reads 50647, writes 11 timeouts 0
Driver 5: standstill, SG min 0, mspos 8, reads 50647, writes 11 timeouts 0
Date/time: 2023-08-24 01:20:35
Slowest loop: 61.41ms; fastest: 0.03ms
=== 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 6, maxWait 1702072ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 4102, completed 4102, hiccups 0, stepErrors 0, LaErrors 0, Underruns [675, 0, 130], 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 -1 -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 428291, received 2749746, lost 0, boc 0
Longest wait 2ms for reply type 6023, peak Tx sync delay 30891, free buffers 50 (min 45), ts 286427/286417/0
Tx timeouts 0,0,9,0,0,0 last cancelled message type 30 dest 127
=== SBC interface ===
Transfer state: 5, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 63174/63174
SPI underruns 0, overruns 0
State: 5, disconnects: 0, timeouts: 0 total, 0 by SBC, IAP RAM available 0x2ab5c
Buffer RX/TX: 0/0-0, open files: 0
=== Duet Control Server ===
Duet Control Server v3.4.6
Code buffer space: 4096
Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0
Full transfers per second: 38.50, max time between full transfers: 109.5ms, max pin wait times: 63.2ms/5.9ms
Codes per second: 0.80
Maximum length of RX/TX data transfers: 3676/1720 -
@Schickfus That looks OK. Please share your
daemon.gfile as well and I'll try to reproduce your problem.
