trying to see why when i home x and y they only go half way.

frnknstn518

@frnknstn518 that was it. but i do get this now

Error: M913: Board 1 received unknown msg type 47
Board 1 received unknown msg type 47

frnknstn518

@frnknstn518 my x and y are on board 1

Phaedrux

Can you send M122 and M122 B# where # is the canbus address of your additional boards? I suspect your expansion board firmware doesn't match your mainboard.

frnknstn518

M122 B1

m122 B1
Diagnostics for board 1:
Duet EXP3HC firmware version 3.3 (2021-06-15 16:12:41)
Bootloader ID: SAME5x bootloader version 2.3 (2021-01-26b1)
Never used RAM 159104, free system stack 4387 words
Tasks: Move(notifyWait,0.0%,125) HEAT(delaying,0.0%,104) CanAsync(notifyWait,0.0%,69) CanRecv(notifyWait,0.0%,80) CanClock(notifyWait,0.0%,71) TMC(notifyWait,7.4%,29) MAIN(running,91.3%,396) IDLE(ready,0.0%,39) AIN(delaying,1.3%,263), total 100.0%
Last reset 00:34:54 ago, cause: software
Last software reset data not available
Driver 0: position 0, 160.0 steps/mm,  standstill, reads 30248, writes 27 timeouts 0, SG min/max 0/116, steps req 228800 done 99199
Driver 1: position 225600, 160.0 steps/mm,  standstill, reads 30249, writes 27 timeouts 0, SG min/max 0/113, steps req 228800 done 99199
Driver 2: position 0, 80.0 steps/mm,  standstill, reads 30266, writes 11 timeouts 0, SG min/max 0/0, steps req 0 done 0
Moves scheduled 6, completed 6, in progress 0, hiccups 0, step errors 0, maxPrep 43, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
Peak sync jitter -7/6, peak Rx sync delay 180, resyncs 0/0, no step interrupt scheduled
VIN: 24.1V, V12: 12.3V
MCU temperature: min 37.7C, current 40.4C, max 40.7C
Ticks since heat task active 228, ADC conversions started 2095141, completed 2095141, timed out 0, errs 0
Last sensors broadcast 0x00000000 found 0 233 ticks ago, loop time 0
CAN messages queued 45, send timeouts 0, received 27202, lost 0, free buffers 37, min 37, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 411, adv 36840/37068

frnknstn518

@frnknstn518 M122

m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.5 (2022-11-30 19:35:23) running on Duet 3 MB6HC v1.01 (SBC mode)
Board ID: 08DJM-9P63L-DJMSS-6JKD0-3S46M-9UFZ8
Used output buffers: 1 of 40 (12 max)
=== RTOS ===
Static ram: 152760
Dynamic ram: 67108 of which 240 recycled
Never used RAM 130492, free system stack 154 words
Tasks: SBC(ready,0.6%,436) HEAT(notifyWait,0.0%,322) Move(notifyWait,0.0%,256) CanReceiv(notifyWait,0.0%,774) CanSender(notifyWait,0.0%,336) CanClock(delaying,0.0%,339) TMC(notifyWait,7.9%,57) MAIN(running,91.4%,923) IDLE(ready,0.1%,30), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:33:06 ago, cause: software
Last software reset at 2023-05-19 12:45, reason: User, GCodes spinning, available RAM 130564, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 134
MCU temperature: min 44.1, current 46.3, max 46.4
Supply voltage: min 23.9, current 23.9, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.0, max 12.1, 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 0, mspos 8, reads 1214, writes 11 timeouts 0
Driver 1: standstill, SG min 0, mspos 520, reads 1206, writes 19 timeouts 0
Driver 2: standstill, SG min 0, mspos 520, reads 1206, writes 19 timeouts 0
Driver 3: standstill, SG min 0, mspos 520, reads 1206, writes 19 timeouts 0
Driver 4: standstill, SG min 0, mspos 520, reads 1206, writes 19 timeouts 0
Driver 5: standstill, SG min 0, mspos 8, reads 1215, writes 11 timeouts 0
Date/time: 2023-05-19 13:18:41
Slowest loop: 29.38ms; 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 3, maxWait 33535ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 10, completed 10, 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
Heater 1 is on, I-accum = 0.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 17892, received 39656, lost 0, boc 0
Longest wait 3ms for reply type 6053, peak Tx sync delay 267, free buffers 50 (min 47), ts 9931/9930/0
Tx timeouts 0,0,0,0,0,0
=== SBC interface ===
Transfer state: 5, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 13506/13506
SPI underruns 0, overruns 0
State: 5, disconnects: 0, timeouts: 0 total, 0 by SBC, IAP RAM available 0x2ad48
Buffer RX/TX: 0/0-0, open files: 0
=== Duet Control Server ===
Duet Control Server v3.4.5
Code buffer space: 4096
Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0
Full transfers per second: 39.86, max time between full transfers: 129.3ms, max pin wait times: 67.0ms/23.9ms
Codes per second: 0.04
Maximum length of RX/TX data transfers: 3072/724

frnknstn518

@frnknstn518 how do i update the EXP3HC
looks like it is 3.3
and the main is 3.4.5

frnknstn518

@frnknstn518 sweet. i updated it and no more warnings. you guys are life savers
now i have to get the klicky right

Phaedrux

Since it appears you are using the SBC, the way to update is to use the Pi terminal and send sudo apt update && sudo apt upgrade

Then check the firmware versions again. If it still hasn't updated, you can manually force an update by sending M997 B1 in the Duet gcode console.

Do you also have a toolboard a can address 121? You should check that one as well.

frnknstn518

@Phaedrux i ran them but now my nozzle temp went to 2000 and is offline and my graph has lines going straight up

frnknstn518

@frnknstn518 nevermind i reset and it went back to normal

Phaedrux

Which did you run? You may need to reboot after updating the pi.

Did you check the firmware was updated?

frnknstn518

@Phaedrux i updated both the boards. then i rebooted. all went to normal thank you

dc42

@frnknstn518 thanks, I'll mark this as solved then.