How to check CAN
-
@arnold_r_clark
Thks Arnold
2022-06-01 16:25:00 Error: M115: Response timeout: CAN addr 123, req type 6024, RID=36
2022-06-01 16:24:59 m115 b123
Warning: Discarded std reply src=122 RID=35 exp 36 "Duet EXP1XD firmware version 3.4.1rc2 (2022-05-25 13:48:15)"
2022-06-01 16:24:45 m115 b122
Duet EXP1XD firmware version 3.4.1rc2 (2022-05-25 13:48:15)
2022-06-01 16:24:36 m115 b121
Error: M115: Response timeout: CAN addr 121, req type 6024, RID=34 -
This post is deleted! -
@arnold_r_clark
Continuity check = OK
V_in = 24V
-
2022-06-01 16:50:13 Error: M115: Response timeout: CAN addr 123, req type 6024, RID=32
2022-06-01 16:50:12 M115 B123
Warning: Discarded std reply src=122 RID=31 exp 32 "Duet EXP1XD firmware version 3.4.1rc2 (2022-05-25 13:48:15)"
2022-06-01 16:49:58 M115 B122
Duet EXP1XD firmware version 3.4.1rc2 (2022-05-25 13:48:15)
2022-06-01 16:49:47 M115 B121
Error: M115: Response timeout: CAN addr 121, req type 6024, RID=30What puzzles me is that B122 in the middle of the CAN signal way is OK and start / end is not OK.
-
@tecno Did you configure the CAN addresses for the other two 1XDs as described here? https://docs.duet3d.com/en/Duet3D_hardware/Duet_3_family/Duet_3_Expansion_1XD#set-the-can-address The CAN address of each extra board must be set for things to work. Also make sure the CAN bus is only terminated by the last board in the chain.
-
Is this done 1 by 1, what about termination? Is it just to open cable loop?
-
All new
2022-06-01 17:34:12 M122 B42
Diagnostics for board 42:
Duet EXP1XD firmware version 3.4.1rc2 (2022-05-25 13:48:15)
Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1)
All averaging filters OK
Never used RAM 5524, free system stack 88 words
Tasks: Move(notifyWait,0.0%,153) HEAT(notifyWait,0.1%,115) CanAsync(notifyWait,0.0%,64) CanRecv(notifyWait,0.0%,77) CanClock(notifyWait,0.0%,64) MAIN(running,96.5%,448) IDLE(ready,0.0%,40) AIN(delaying,3.4%,142), total 100.0%
Last reset 00:06:33 ago, cause: software
Last software reset data not available
Driver 0: pos 0, 80.0 steps/mm, steps req 0 done 0
Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
Peak sync jitter -4/10, peak Rx sync delay 200, resyncs 0/0, no step interrupt scheduled
VIN voltage: min 24.5, current 24.6, max 24.6
MCU temperature: min 29.9C, current 30.0C, max 30.4C
Last sensors broadcast 0x00000000 found 0 243 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 3175, send timeouts 0, received 3500, lost 0, free buffers 37, min 37, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
2022-06-01 17:33:57 M122 B41
Diagnostics for board 41:
Duet EXP1XD firmware version 3.4.1rc2 (2022-05-25 13:48:15)
Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1)
All averaging filters OK
Never used RAM 5524, free system stack 88 words
Tasks: Move(notifyWait,0.0%,153) HEAT(notifyWait,0.1%,115) CanAsync(notifyWait,0.0%,64) CanRecv(notifyWait,0.0%,77) CanClock(notifyWait,0.0%,64) MAIN(running,96.5%,448) IDLE(ready,0.0%,40) AIN(delaying,3.4%,142), total 100.0%
Last reset 00:06:18 ago, cause: software
Last software reset data not available
Driver 0: pos 0, 80.0 steps/mm, steps req 0 done 0
Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
Peak sync jitter -4/9, peak Rx sync delay 198, resyncs 0/0, no step interrupt scheduled
VIN voltage: min 24.5, current 24.5, max 24.5
MCU temperature: min 31.0C, current 31.2C, max 31.3C
Last sensors broadcast 0x00000000 found 0 89 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 3057, send timeouts 0, received 3365, lost 0, free buffers 37, min 37, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
2022-06-01 17:33:24 M122 B40
Diagnostics for board 40:
Duet EXP1XD firmware version 3.4.1rc2 (2022-05-25 13:48:15)
Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1)
All averaging filters OK
Never used RAM 5524, free system stack 88 words
Tasks: Move(notifyWait,0.0%,153) HEAT(notifyWait,0.1%,115) CanAsync(notifyWait,0.0%,64) CanRecv(notifyWait,0.0%,77) CanClock(notifyWait,0.0%,64) MAIN(running,96.5%,448) IDLE(ready,0.0%,40) AIN(delaying,3.4%,142), total 100.0%
Last reset 00:05:44 ago, cause: software
Last software reset data not available
Driver 0: pos 0, 80.0 steps/mm, steps req 0 done 0
Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
Peak sync jitter -4/9, peak Rx sync delay 198, resyncs 0/0, no step interrupt scheduled
VIN voltage: min 24.6, current 24.6, max 24.6
MCU temperature: min 27.8C, current 28.0C, max 28.1C
Last sensors broadcast 0x00000000 found 0 40 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 2785, send timeouts 0, received 3059, lost 0, free buffers 37, min 37, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0 -
@tecno Yes, power only one 1XD board at first, set an arbitrary CAN address as described in the link, and then move on to the next board. Repeat this step for each board.
The termination is set by the two jumpers behind the CAN_IN connector. Remove them unless it is the last board in the chain (i.e. no cable going out from CAN_OUT).
-
M119 reports no active endstop Hi or Lo
-
Have you configured any endstops?
-
@phaedrux
; Endstops
M574 X2 S1 P"!40.io1.in" ; configure switch-type (e.g. microswitch) endstop for high end on X via pin io0.in
M950 P0 C"40.out0" ; config output
M42 P0 S1 ; set pwm 100%
M574 Y2 S1 P"!41.io1.in" ; configure switch-type (e.g. microswitch) endstop for high end on Y via pin io1.in
M950 P1 C"41.out0" ; config output
M42 P1 S1 ; set pwm 100%
M574 Z2 S1 P"!42.io1.in" ; configure switch-type (e.g. microswitch) endstop for high end on Z via pin io2.in
M950 P2 C"42.out0" ; config output
M42 P2 S1 ; set pwm 100%But no point to go further if https://forum.duet3d.com/topic/28717/the-tower-motors can be solved now!
