Wiring Multiple Endstops in Parallel or Series with Duet 6XD

developeralgo222

@droftarts
when i test it manually according to the right-hand cartesian coordinates . My X-Axis moves Backwards from Home(Right to Left) instead of the Normal Forward ( Left to Right ) , that's why i was using Negative infront of that otherwise it crashes the X-Axis. If you look at the Endpoints and motor placements diagram above , you will see the description

droftarts

@developeralgo222 In that case, change the direction of the motor with the S parameter in M569, eg:

M569 P0.0 S0 T5:5:10:10

Then update the M208 command, and check it goes the right direction.

Ian

developeralgo222

@droftarts said in Wiring Multiple Endstops in Parallel or Series with Duet 6XD:

@developeralgo222 In that case, change the direction of the motor with the S parameter in M569, eg:
M569 P0.0 S0 T5:5:10:10
Then update the M208 command, and check it goes the right direction.

Ian

yes updated config.g and that fixed X-axis negative max issue

droftarts

@developeralgo222 Okay. Does it still crash when you send M98 P"config.g"?

Ian

droftarts

@developeralgo222 Another snag on homing; I checked with @dc42 if the trigger is ignored on homing moves. He said:

No, you have to deactivate the trigger.
..because after the homing move you need to move away form the endst9p to release it, to avoid triggering

So in your homing macros, rather than disabling the trigger pin and enabling the endstop, you need to disable the trigger itself, while homing. So now the homing macros will look like this:

M581 T1 P-1 ; disable trigger
 
[normal homing routine for X and Y axis in here]
 
M581 T1 X Y S1 R0 ; re enable trigger

Ian

developeralgo222

@droftarts Going to test that now. i was just testing if its able to Home X and Y-axis and it seems its able . Anything i need to modify on homex.g and homey.g files in relation to config.g

homex.g

; homex.g
; called to home the X axis
 
M581 T1 P-1 ; disable trigger

;	Home X-Axis 
G91                   ; relative positioning
G1 H2 X0              ; move X-axis Minimum Homing endstop and stop there (first pass)
G1 H2 X1575 F5000     ; move quickly to X-axis Maximum endstop and stop there (first pass)
G1 H2 X-1575 F5000      ; go back to X0 Minimum Homing endstop 
G1 H2 X1575 F5000     ; move quickly to X-axis Maximum endstop and stop there (second pass)
G1 H2 X-1575 F5000       ; go back quickly to X0 Minimum Homing endstop once more (second pass)
G1 H2 X0              ; Mark it as the X-axis Minimum Homing endstop and stop there (second pass)
G92 X0
G90                   ; absolute positioning

 
M581 T1 X Y S1 R0 ; re enable trigger

Homey.g

; homey.g
; called to home the Y axis

M581 T1 P-1 ; disable trigger
 
;	Home Y-Axis 
G91                   ; relative positioning
G1 H2 Y0              ; move Y-axis Minimum Homing endstop and stop there (first pass)
G1 H2 Y2135 F5000      ; move quickly to Y-axis Maximum endstop and stop there (first pass)
G1 H2 Y-2135 F5000     ; go back to Y0 Minimum Homing endstop 
G1 H2 Y2135 F5000      ; move quickly to Y-axis Maximum endstop and stop there (second pass)
G1 H2 Y-2135 F5000     ; go back quickly to Y0 Minimum Homing endstop once more (second pass)
G1 H2 Y0              ; Mark it as the Y-axis Minimum Homing endstop and stop there (second pass)
G92 Y0
G90                   ; absolute positioning
 
 M581 T1 X Y S1 R0 ; re enable trigger

droftarts

@developeralgo222 See my reply before yours. You will need to edit your homing files.

Edit:
Using M950 J1 and J2 in your homing files to refer to limit switches will be messing with these in config.g:

; SMC NPN Vacuum Sensors -ZSE30A-01-N-L (Not Z-Probe)
M950 J1 C"!2.io3.in"   ; Duet 3 3HC CAN_ID 2 Port 4- Vacuum Sensor Nozzle 1
M950 J2 C"!2.io4.in"   ; Duet 3 3HC CAN_ID 2 Port 5- Vacuum Sensor Nozzle 2

Ian

developeralgo222

@droftarts said in Wiring Multiple Endstops in Parallel or Series with Duet 6XD:

Edit:
Using M950 J1 and J2 in your homing files to refer to limit switches will be messing with these in config.g:
; SMC NPN Vacuum Sensors -ZSE30A-01-N-L (Not Z-Probe)
M950 J1 C"!2.io3.in"   ; Duet 3 3HC CAN_ID 2 Port 4- Vacuum Sensor Nozzle 1
M950 J2 C"!2.io4.in"   ; Duet 3 3HC CAN_ID 2 Port 5- Vacuum Sensor Nozzle 2
Ian

Not sure i understand what you mean by this ?

developeralgo222

@developeralgo222

i sent

 M98 P"config.g"

command and it disconnected again same issue. I don't know what is in the config.g that makes Duet 6XD crash ?

droftarts

@developeralgo222 never mind, you updated your homing files and have fixed it now. You can always check how pins are defined by sending, M950 J1 for example.

Ian

developeralgo222

@droftarts ok got it

Getting response timeout errors on SMC Vacuum Pressure Sensors when i try to send manually M950 Jx as below

12/18/2023, 1:28:42 PM	M950 J6
Error: M950: Response timeout: CAN addr 3, req type 6037, RID=65
12/18/2023, 1:28:37 PM	M950 J5
Error: M950: Response timeout: CAN addr 3, req type 6037, RID=64
12/18/2023, 1:28:33 PM	M950 J4
Error: M950: Response timeout: CAN addr 3, req type 6037, RID=63
12/18/2023, 1:28:26 PM	M950 J3
Error: M950: Response timeout: CAN addr 2, req type 6037, RID=62
12/18/2023, 1:28:22 PM	M950 J2
Error: M950: Response timeout: CAN addr 2, req type 6037, RID=61
12/18/2023, 1:28:12 PM	M950 J1
Error: M950: Response timeout: CAN addr 2, req type 6037, RID=60

But i get the following for Integrated Solenoid valve (Pump & Vacuum) when i send M950 Px which seems to be fine

12/18/2023, 1:32:17 PM	M950 P6
GPIO/servo port 6 pin !io8.in frequency 500Hz
12/18/2023, 1:32:15 PM	M950 P5
GPIO/servo port 5 pin !io7.in frequency 500Hz
12/18/2023, 1:32:12 PM	M950 P4
GPIO/servo port 4 pin !io6.in frequency 500Hz
12/18/2023, 1:32:09 PM	M950 P3
GPIO/servo port 3 pin !io5.in frequency 500Hz
12/18/2023, 1:32:05 PM	M950 P2
GPIO/servo port 2 pin !io4.in frequency 500Hz
12/18/2023, 1:31:57 PM	M950 P1
GPIO/servo port 1 pin !io3.in frequency 500Hz

After Updating to RRF 3.5.0.-rc.2 and rebooting i attempted to test the input pins for the SMC NPN sensors but getting an error

12/18/2023, 5:34:40 PM	M950 J6
Error: M950: Board 3 does not have input handle 2180
12/18/2023, 5:34:37 PM	M950 J5
Error: M950: Board 3 does not have input handle 2140
12/18/2023, 5:34:33 PM	M950 J4
Error: M950: Board 3 does not have input handle 2100
12/18/2023, 5:34:30 PM	M950 J3
Error: M950: Board 2 does not have input handle 20c0
12/18/2023, 5:34:15 PM	M950 J2
Error: M950: Board 2 does not have input handle 2080
12/18/2023, 5:34:08 PM	M950 J1
Error: M950: Board 2 does not have input handle 2040

developeralgo222

@developeralgo222

Also trying to get all the endstops on all Axis working. On the Z-Axes, i have 3 x Nema 17 Motors that are directly connected to 3HC board CAN ID = 1 , Drive 0,1 & 2. This are CAM Driven Axes

Motor 1 ---- On Drive 0 --- Rotates Clockwise or Anticlockwise to move CAM driven dual nozzles down and up on Z & U axis on CAN ID = 1 - Duet 3HC Drive 1.0 i.e Z & U-axes share a single motor 1

Motor 2 ---- On Drive 1 --- Rotates Clockwise or Anticlockwise to move CAM driven dual nozzles down and up on V & W axis on CAN ID = 1 - Duet 3HC Drive 1.1 i.e V & W-axes share a single motor 2

Motor 3 ---- On Drive 3 --- Rotates Clockwise or Anticlockwise to move CAM driven dual nozzles down and up on A & B axis on CAN ID = 1 - Duet 3HC Drive 1.2 i.e A & B-axes share a single motor 3

Trying to define them correctly in the config before updating the homing files. Here is a sample picture courtesy of @wayneosdias of where roughly the endstops for Z, U, V,W,A,B are located.

Two nozzles are at either end of the of the cam and at the center a stepper motor. At rest/homed both nozzles are at the Z max height and suspended this way by springs supporting against gravity. Once the stepper is activated, CCW the 1st nozzle is pushed down and the 2nd nozzle is suspended by the spring. Conversely when the stepper is activated CC the 2nd nozzle is driven down and the 1st nozzle is suspended at max z by the spring.

How do i get endstops for Z, U, V,W,A,B configured correctly ? Here is the snapshot of those Z-axes with drives and Endstops. I am not even sure that the Drives are configured correctly as per @dc42

; Drives
;Physical Drives CAN ID = 0
M569 P0.0 S0 T5:5:10:10           ; X-Axis physical drive 0.0 goes backwards on CAN ID = 0 - Duet 6XD Drive 0.0 with 2.5us timings between pulses
M569 P0.1 S0 T5:5:10:10           ; Y-Axis physical drive 0.1 goes forwards on CAN ID = 0 - Duet 6XD Drive 0.1 with 2.5us timings between pulses
;Physical Drives CAN ID = 1
M569 P1.0 S1                ; Z & U Axis physical drive 1.0 Rotates Clockwise or Anticlockwise to move CAM driven dual nozzles down and up on Z & U axis on CAN ID = 1 - Duet 3HC Drive 1.0
M569 P1.1 S1                ; V & W Axis physical drive 1.1 Rotates Clockwise or Anticlockwise to move CAM driven dual nozzles down and up on V & W axis on CAN ID = 1 - Duet 3HC Drive 1.1
M569 P1.2 S1                ; A & B Axis physical drive 1.2 Rotates Clockwise or Anticlockwise to move CAM driven dual nozzles down and up on A & B axis on CAN ID = 1 - Duet 3HC Drive 1.2
;Physical Drives CAN ID = 2
M569 P2.0 S1                ; C-Axis physical drive 2.0 goes Rotates forwards and backwards (+180 and -180 ) on CAN ID = 2 - Duet 3HC Drive 2.0
M569 P2.1 S1                ; D-Axis physical drive 2.1 goes Rotates forwards and backwards (+180 and -180 ) on CAN ID = 2 - Duet 3HC Drive 2.1
M569 P2.2 S1                ; 'A-Axis physical drive 2.2 goes Rotates forwards and backwards (+180 and -180 ) on CAN ID = 2 - Duet 3HC Drive 2.2
;Physical Drives CAN ID = 3
M569 P3.0 S1                ; 'B-Axis physical drive 3.0 goes Rotates forwards and backwards (+180 and -180 ) on CAN ID = 3 - Duet 3HC Drive 3.0
M569 P3.1 S1                ; 'C-Axis physical drive 3.1 goes Rotates forwards and backwards (+180 and -180 ) on CAN ID = 3 - Duet 3HC Drive 3.1
M569 P3.2 S1                ; 'D-Axis physical drive 3.2 goes Rotates forwards and backwards (+180 and -180 ) on CAN ID = 3 - Duet 3HC Drive 3.2


; set visible drive mapping
; X-Axis , Y-Axis (2 x Nema 34 Closed Loop Motors) and Z-Axes (Z,U,V,W,A,B) mapping to 3 Stepper motors 
; directly connected to 3HC (CAN ID = 1) (which moves the nozzles up and down along Z-axis)
;M584 X0.0 Y0.1 R0 ;  LIN R0 = LINEAR, R1 = ROTATION
; Rotational Axes mapping (C, D, 'A, 'B, 'C, 'D ) to 6 motors directly connected to 3HC (CAN ID 2 and 3) (which rotates the nozzles +180 / -180 along Rotational axis)
;M584 Z1.0 U1.0 V1.1 W1.1 A1.2 B1.2 C2.0 D2.1 'A2.2 'B3.0 'C3.1 'D3.2 R1  ;    LIN R0 = LINEAR, R1 = ROTATION

M584 X0.0 Y0.1 Z1.0 U1.0 V1.1 W1.1 A1.2 B1.2 R0 ;  LIN R0 = LINEAR, R1 = ROTATION
M584 C2.0 D2.1 'A2.2 'B3.0 'C3.1 'D3.2 R1  ;    LIN R0 = LINEAR, R1 = ROTATION

M350 Z16 U16 V16 W16 A16 B16 C16 D16 'A16 'B16 'C16 'D16 I1                     ; configure microstepping with interpolation. This is irrelevant for external drives (X & Y )
M92 X64.00 Y64.00 Z8.888 U8.888 V8.888 W8.888 A8.888 B8.888  C8.888 D8.888 'A8.888 'B8.888 'C8.888 'D8.888          ; set steps per mm 50mm/rev
M566 X300.0 Y300.0 Z300.0 U300.0 V300.0 W300.0 A300.0 B300.0  C100.0 D100.0 'A100.0 'B100.0 'C100.0 'D100.0         ; set maximum instantaneous speed changes (mm/min)
M203 X5000.00 Y5000.00 Z5000.00 U5000.00 V5000.00 W5000.00 A5000.00 B5000.00  C5000.00 D5000.00 'A5000.00 'B5000.00 'C5000.00 'D5000.00     ; set maximum speeds (mm/min)
M201 X1000.00 Y1000.00 Z500.00 U500.00 V500.00 W500.00 A500.00 B500.00  C1000.00 D1000.00 'A1000.00 'B1000.00 'C1000.00 'D1000.00                         ; set accelerations (mm/s^2)
M906 Z600.0 U600.0 V600.0 W600.0 A600.0 B600.0  C500.0 D500.0 'A500.0 'B500.0 'C500.0 'D500.0 I30        ; set motor currents (mA) and motor idle factor in per cent. This is irrelevant for external drives (X & Y )
M84 S30      ; Set idle timeout
M564 H0		 ; Sets homing, H0 allows mvmnt wo homing

; Axis Limits
;M208 X0 Y0 Z-160 U-160 V-160 W-160 A-160 B-160  C0 D0 'A0 'B0 'C0 'D0 S1	; Set axis minima
;M208 X1600 Y2135 Z0 U0 V0 W0 A0 B0 C180 D180 'A180 'B180 'C180 'D180 S0	    ; Set axis maxima

M208 X0 Y0 Z-75 U-75 V-75 W-75 A-75 B-75  C0 D0 'A0 'B0 'C0 'D0 S1	; Set axis minima
M208 X1600 Y2135 Z75 U75 V75 W75 A75 B75 C180 D180 'A180 'B180 'C180 'D180 S0	    ; Set axis maxima


; Triggers -- Two triggers, one for X and one for Y, and set them to pause the machine

;M950 J1 C"!0.io0.in"  ; define input #1 pin IO_0
;M950 J2 C"!0.io1.in"  ; define input #2 pin IO_1
; Trigger number 0 causes an emergency stop as if M112 had been received. Trigger number 1 causes the print to be paused as if M25 had been received. Any trigger number # greater than 1 causes 
; the macro file sys/trigger#.g to be executed. Polling for further trigger conditions is suspended until the trigger macro file has been completed
M581 T1 X Y S1 R0 ; invoke trigger 1 (pause) when an inactive-to-active edge (correct for NO switches) is detected on input 1 or input 2 at any time

; Endstops 
; For X and Y Axis
M574 X1 S1 P"!0.io0.in"               ; configure active high endstop switch for low end on X via pin io0.in  
M574 Y1 S1 P"!0.io1.in"               ; configure active high endstop switch for low end on Y via pin io1.in
; For Z-Axis (Z,U,V,W,A,B) - Up/down)  -- CAM Driven Dual Nozzles ( 1 Motor rotates up/down to drive 2 Nozzles )
M574 Z1 S1 P"!1.io0.in"             ; configure active high endstop switch for low end on Z via pin 1.io0.in
M574 U1 S1 P"!1.io1.in"             ; configure active high endstop switch for low end on U via pin 1.io1.in
M574 V1 S1 P"!1.io2.in"             ; configure active high endstop switch for low end on V via pin 1.io2.in
M574 W1 S1 P"!1.io3.in"             ; configure active high endstop switch for low end on W via pin 1.io3.in
M574 A1 S1 P"!1.io4.in"             ; configure active high endstop switch for low end on A via pin 1.io4.in
M574 B1 S1 P"!1.io5.in"             ; configure active high endstop switch for low end on B via pin 1.io5.in
; For Rotational Axes only (C,D,'A,'B,'C,'D) +180 / - 180 )  
M574 C1 S1 P"!2.io0.in"            ; configure active high endstop switch for low end on C via pin 2.io0.in
M574 D1 S1 P"!2.io1.in"            ; configure active high endstop switch for low end on D via pin 2.io1.in
M574 'A1 S1 P"!2.io2.in"            ; configure active high endstop switch for low end on 'A via pin 2.io2.in
M574 'B1 S1 P"!3.io0.in"            ; configure active high endstop switch for low end on 'B via pin 3.io0.in
M574 'C1 S1 P"!3.io1.in"            ; configure active high endstop switch for low end on 'C via pin 3.io1.in
M574 'D1 S1 P"!3.io2.in"            ; configure active high endstop switch for low end on 'D via pin 3.io2.in

;***Inputs
; SMC NPN Vacuum Sensors -ZSE30A-01-N-L (Not Z-Probe)
M950 J1 C"!2.io3.in"   ; Duet 3 3HC CAN_ID 2 Port 4- Vacuum Sensor Nozzle 1
M950 J2 C"!2.io4.in"   ; Duet 3 3HC CAN_ID 2 Port 5- Vacuum Sensor Nozzle 2
M950 J3 C"!2.io5.in"   ; Duet 3 3HC CAN_ID 2 Port 6- Vacuum Sensor Nozzle 3
M950 J4 C"!3.io3.in"   ; Duet 3 3HC CAN_ID 2 Port 4- Vacuum Sensor Nozzle 4
M950 J5 C"!3.io4.in"   ; Duet 3 3HC CAN_ID 2 Port 5- Vacuum Sensor Nozzle 5
M950 J6 C"!3.io5.in"   ; Duet 3 3HC CAN_ID 2 Port 6- Vacuum Sensor Nozzle 6

;***Outputs
; (SMC) LINGERA CM85-10-A-6S Integrated Solenoid Valves (Pump and Vacuum) on the Duet 6XD
M950 P1 C"!0.io3.in"   ; Duet 3 6XD CAN_ID 0 Port 4- Pump and Vacuum Solenoid Valve for Nozzle 1
M950 P2 C"!0.io4.in"   ; Duet 3 6XD CAN_ID 0 Port 5- Pump and Vacuum Solenoid Valve for Nozzle 2
M950 P3 C"!0.io5.in"   ; Duet 3 6XD CAN_ID 0 Port 6- Pump and Vacuum Solenoid Valve for Nozzle 3
M950 P4 C"!0.io6.in"   ; Duet 3 6XD CAN_ID 0 Port 7- Pump and Vacuum Solenoid Valve for Nozzle 4
M950 P5 C"!0.io7.in"   ; Duet 3 6XD CAN_ID 0 Port 8- Pump and Vacuum Solenoid Valve for Nozzle 5
M950 P6 C"!0.io8.in"   ; Duet 3 6XD CAN_ID 0 Port 9- Pump and Vacuum Solenoid Valve for Nozzle 6

; Enable All the drives 
M17  ; Enable All the drives

droftarts

@developeralgo222 For the timeout errors, are you seeing all your boards in DWC, and are they all on the same firmware? Go to Settings > Machine-Specific, should look something like this:

If it doesn't show there, send M122 to check mainboard firmware version, and M122 B1, M122 B2 and M122 B3 to check status of each expansion board.

The expansion boards must be on the same firmware version as the mainboard.

Ian

developeralgo222

@droftarts

Only seeing B0 = 6XD, B1 = 3HC (CAN ID= 1) but not seeing B2 or B3 .A few days ago i could see all of them.They can connected fine. I did update all of them 2 weeks ago with same Firmware RRF 3.4.6

.

After updating to 3.5.0-rc.2 i can see all of them but i keep getting an error every minute about " Error: Expansion board 2 stopped sending status"

Error: Expansion board 2 stopped sending status

Screenshot 2023-12-18 163245.png

i will check the CAN cables and then reboot everything to see if it continues . After reboot , after a few minutes i started receiving the error again. Then i tried M122 B2 and i get

M122 B2
CAN response timeout: board 2, req type 6024, RID 91

developeralgo222

@developeralgo222
Able to see them all after update and reboot

M122 B3

Diagnostics for board 3:
Duet EXP3HC rev 1.02 or later firmware version 3.5.0-rc.2 (2023-12-14 08:56:47)
Bootloader ID: SAME5x bootloader version 2.4 (2021-12-10)
All averaging filters OK
Never used RAM 156976, free system stack 202 words
Tasks: Move(3,nWait,0.0%,182) HEAT(2,nWait,0.0%,122) CanAsync(5,nWait,0.0%,67) CanRecv(3,nWait,0.0%,80) CanClock(5,nWait,0.0%,70) TMC(2,nWait,5.7%,103) MAIN(1,running,93.1%,389) IDLE(0,ready,0.0%,39) AIN(2,delaying,1.1%,263), total 100.0%
Last reset 00:01:03 ago, cause: power up
Last software reset data not available
Driver 0: pos 0, 80.0 steps/mm, standstill, SG min 0, mspos 8, reads 52249, writes 11 timeouts 0, steps req 0 done 0
Driver 1: pos 0, 80.0 steps/mm, standstill, SG min 0, mspos 8, reads 52250, writes 11 timeouts 0, steps req 0 done 0
Driver 2: pos 0, 80.0 steps/mm, standstill, SG min 0, mspos 8, reads 52251, writes 11 timeouts 0, steps req 0 done 0
Moves scheduled 0, completed 0, in progress 0, hiccups 0, segs 0, step errors 0, maxLate 0 maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0, ebfmin 0.00 max 0.00
Peak sync jitter -3/6, peak Rx sync delay 179, resyncs 0/0, no timer interrupt scheduled
VIN voltage: min 24.5, current 24.5, max 24.6
V12 voltage: min 12.3, current 12.3, max 12.4
MCU temperature: min 24.2C, current 27.2C, max 27.2C
Last sensors broadcast 0x00000000 found 0 85 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 534, send timeouts 0, received 328, lost 0, errs 0, boc 0, free buffers 38, min 38, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0


M122 B2

Diagnostics for board 2:
Duet EXP3HC rev 1.02 or later firmware version 3.5.0-rc.2 (2023-12-14 08:56:47)
Bootloader ID: SAME5x bootloader version 2.4 (2021-12-10)
All averaging filters OK
Never used RAM 156976, free system stack 202 words
Tasks: Move(3,nWait,0.0%,182) HEAT(2,nWait,0.0%,122) CanAsync(5,nWait,0.0%,67) CanRecv(3,nWait,0.0%,80) CanClock(5,nWait,0.0%,70) TMC(2,nWait,5.7%,103) MAIN(1,running,93.1%,429) IDLE(0,ready,0.0%,39) AIN(2,delaying,1.1%,263), total 100.0%
Last reset 00:00:59 ago, cause: power up
Last software reset data not available
Driver 0: pos 0, 80.0 steps/mm, standstill, SG min 0, mspos 8, reads 35905, writes 11 timeouts 0, steps req 0 done 0
Driver 1: pos 0, 80.0 steps/mm, standstill, SG min 0, mspos 8, reads 35906, writes 11 timeouts 0, steps req 0 done 0
Driver 2: pos 0, 80.0 steps/mm, standstill, SG min 0, mspos 8, reads 35907, writes 11 timeouts 0, steps req 0 done 0
Moves scheduled 0, completed 0, in progress 0, hiccups 0, segs 0, step errors 0, maxLate 0 maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0, ebfmin 0.00 max 0.00
Peak sync jitter -4/4, peak Rx sync delay 178, resyncs 0/0, no timer interrupt scheduled
VIN voltage: min 24.5, current 24.5, max 24.5
V12 voltage: min 12.3, current 12.3, max 12.4
MCU temperature: min 24.1C, current 27.3C, max 27.3C
Last sensors broadcast 0x00000000 found 0 146 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 500, send timeouts 0, received 308, lost 0, errs 0, boc 0, free buffers 38, min 38, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0


M122 B1
	
Diagnostics for board 1:
Duet EXP3HC rev 1.02 or later firmware version 3.5.0-rc.2 (2023-12-14 08:56:47)
Bootloader ID: SAME5x bootloader version 2.4 (2021-12-10)
All averaging filters OK
Never used RAM 156976, free system stack 202 words
Tasks: Move(3,nWait,0.0%,182) HEAT(2,nWait,0.0%,122) CanAsync(5,nWait,0.0%,67) CanRecv(3,nWait,0.0%,80) CanClock(5,nWait,0.0%,70) TMC(2,nWait,5.7%,103) MAIN(1,running,93.1%,395) IDLE(0,ready,0.0%,39) AIN(2,delaying,1.1%,263), total 100.0%
Last reset 00:00:53 ago, cause: power up
Last software reset data not available
Driver 0: pos 0, 80.0 steps/mm, standstill, SG min 0, mspos 8, reads 12894, writes 11 timeouts 0, steps req 0 done 0
Driver 1: pos 0, 80.0 steps/mm, standstill, SG min 0, mspos 8, reads 12895, writes 11 timeouts 0, steps req 0 done 0
Driver 2: pos 0, 80.0 steps/mm, standstill, SG min 0, mspos 8, reads 12895, writes 11 timeouts 0, steps req 0 done 0
Moves scheduled 0, completed 0, in progress 0, hiccups 0, segs 0, step errors 0, maxLate 0 maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0, ebfmin 0.00 max 0.00
Peak sync jitter -4/6, peak Rx sync delay 178, resyncs 0/0, no timer interrupt scheduled
VIN voltage: min 24.4, current 24.4, max 24.4
V12 voltage: min 12.4, current 12.4, max 12.4
MCU temperature: min 20.9C, current 23.9C, max 23.9C
Last sensors broadcast 0x00000000 found 0 245 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 452, send timeouts 0, received 277, lost 0, errs 0, boc 0, free buffers 38, min 38, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0

droftarts

@developeralgo222 Have you checked the CAN termination on them? Only the last 3HC board should have the jumpers on the pins just behind the CAN ports.

Ian

developeralgo222

@droftarts jumper ? i see 2 jumpers behind the CAN Ports. Do you mean the CAN Bus termination jumpers ? Do i need to remove those 2 for Board 1 and board 2 and leave those for board 3

droftarts

@developeralgo222 CAN termination jumper:

Only have jumpers on the pins of the last 3HC in the chain. See https://docs.duet3d.com/Duet3D_hardware/Duet_3_family/Duet_3_Expansion_3HC#can

Termination

Just behind the RJ11 connectors is a 4-pin terminal block. On the last board in the CAN chain only (the one with a cable in only one of the RJ11 connectors), two jumpers must be fitted in that block to terminate the CAN bus. Jumpers must not be fitted in expansion boards that are not at the end of the CAN bus.

Ian

developeralgo222

@droftarts , yes just was reading that as you posted it . got it. done. No more timeout errors but still having issue with sending M950 Jx tests (J1 to J6 )