Error when trying to update- Duet3_SBCiap32_MB6HC.bin missing
-
; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M669 K1 ; select CoreXY mode; Drives
M569 P0.0 S0 ; physical drive 0.0 goes forwards
M569 P0.1 S0 ; physical drive 0.1 goes forwards
M569 P0.2 S0 ; physical drive 0.2 goes forwards
M569 P0.3 S0 ; physical drive 0.3 goes forwards
M569 P0.4 S0 ; physical drive 0.4 goes forwards
M569 P0.5 S0 ; physical drive 0.5 goes forwards
M569 P1.0 S1 ; physical drive 1.0 goes backwards
M569 P1.1 S0 ; physical drive 1.0 goes forwards
M569 P1.2 S0 ; physical drive 1.0 goes forwards
M584 X0.0 Y0.1 Z0.2:0.3:0.4:0.5 E1.0 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z1600.00 E415.00 ; set steps per mm
M566 X900.00 Y900.00 Z120.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z480.00 E1200.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E940 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout
M671 X33.2:33.2:355.5:355.5 Y447.5:-61:447.5:-61 S20 ; leadscrew definition; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X374 Y360 Z430 S0 ; set axis maxima; Endstops
M574 X1 S1 P"!io0.in" ; configure active-low endstop for low end on X via pin io0.in
M574 Y1 S1 P"!io1.in" ; configure active-low endstop for low end on Y via pin io1.in
M574 Z1 S2 ; configure Z-probe endstop for low end on Z; Z-Probe
M950 S0 C"io7.out" ; create servo pin 0 for BLTouch
M558 P9 C"^io7.in" H10 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X-48 Y15 Z2.291 ; set Z probe trigger value, offset and trigger height
M557 X15:360 Y15:345 S35 ; define mesh grid; Heaters
M308 S0 P"temp0" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin temp0
M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0
M307 H0 A232.9 C532.1 D1.7 V23.8 B0 ; heater definition as provided by auto tune
M140 H0 ; map heated bed to heater 0
M143 H0 S130 ; set temperature limit for heater 0 to 130C
M308 S1 P"1.temp0" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin 1.temp0
M950 H1 C"1.out0" T1 ; create nozzle heater output on 1.out0 and map it to sensor 1
M307 H1 B0 S1.00 ; default heater definition
;M307 H1 A570.8 C282.2 D 4.1 V23.8 B0 ; heater definition as provided by auto tune; Fans
M950 F0 C"1.out6" Q500 ; create fan 0 on pin 1.out6 and set its frequency
M106 P0 S0 H1 T45 ; set fan 0 value. Thermostatic control is turned on
M950 F1 C"1.out7" Q500 ; create fan 1 on pin 1.out7 and set its frequency
M106 P1 S0 H-1 ; set fan 1 value. Thermostatic control is turned off; Tools
M563 P0 D0 H1 F-1 ; define tool 0
G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C; Custom Settings
M564 H0 ; Allow movement before axes are homed -
I've been running with this config for a while now, when running the 3.2 update it just broke
-
It looks like any command that requires it to talk to the 3HC fails with a CAN timeout? The 3HC is blinking in sync with the 6HC though. The errors I'm getting all have a motor or heater defined on the 3HC, I have that set for the extruder motor, heater and thermistor.
1/15/2021, 12:51:26 PM Error: M307: Heater 1 not found
1/15/2021, 12:51:26 PM Warning: M950: Command is not supported
1/15/2021, 12:51:26 PM Warning: M308: Invalid Z probe index
1/15/2021, 12:51:26 PM Error: M906: Response timeout: CAN addr 1, req type 6043, RID=6
1/15/2021, 12:51:25 PM Warning: Discarded msg src=1 typ=4510 RID=4095 exp 6
1/15/2021, 12:51:25 PM Error: M92: Response timeout: CAN addr 1, req type 6042, RID=5
1/15/2021, 12:51:24 PM Warning: Discarded msg src=1 typ=4510 RID=4095 exp 5
1/15/2021, 12:51:24 PM Error: M350: Response timeout: CAN addr 1, req type 6042, RID=4
1/15/2021, 12:51:23 PM Error: M584: Response timeout: CAN addr 1, req type 6042, RID=3
1/15/2021, 12:51:23 PM Warning: Discarded msg src=1 typ=4510 RID=4095 exp 4 -
I would suggest trying a fresh download and re-image of DuetPi on your Pi SD card followed by a sudo apt update/upgrade. Seems like you may be using the image that came on the card with the Duet3?
-
Yes, I was. I've run the updates and upgrades since though. Is that something that should be done every so often? Reimage the SD card to the latest DuetPi?
-
@cdthomas9 No, but the image was updated since and re-imaging has solved problems for others in the past, so worth a shot.
-
I just ran M997 B1 to manually force the 3HC to update to 3.2, and it looks like that fixed it
-
Can I run a PID tuning on the heater attached to the 3HC now? I remember I couldn't before, wasn't sure if 3.2 fixed it
-
@cdthomas9 the heater tuning algorithm has been updated in 3.2, which paves the way for tuning on tool boards and expansions in 3.3 I believe.
@cdthomas9 said in Error when trying to update- Duet3_SBCiap32_MB6HC.bin missing:
I just ran M997 B1 to manually force the 3HC to update to 3.2, and it looks like that fixed it
From your first post with the M997 error message I thought you had already tried to manually update it.
-
I did, but I wasn't trying to run the expansion board directly or separately. I was letting it run through and update everything in bulk, at least I think I was...
-
I ran a M997 to update all firmware, thinking that the command would run through the main board and expansion boards
-
Ah ok. Well glad it's sorted out. Now that you're on a full release with all boards synced the sudo apt update should work going forward.
-
Thanks! What was the file it was looking for? the SBC iap file? I saw an SD iap file but not that one. I couldn't find that anywhere
-
The SBC IAP file would come from doing Sudo apt update/upgrade I believe
-
@cdthomas9 said in Error when trying to update- Duet3_SBCiap32_MB6HC.bin missing:
Thanks! What was the file it was looking for? the SBC iap file? I saw an SD iap file but not that one. I couldn't find that anywhere
The IAP files are needed when updating main board firmware versions. They are not needed to update the 3HC or other expansion or tool board firmware.
-
Thanks for all of your help! I appreciate your time and assistance getting me back up and running.
