Duet3 Expansion Board 3HC - No CAN-Connection

A Former User

@CR3D said in Duet3 Expansion Board 3HC - No CAN-Connection:

So far the same problem

post the config for that when you do, copy past the text and use the formatting function here makes it much easier to read. (on the toolbar with bold, italics, its the fifth from the left to format as code which makes it nice and readable)

CR3D

@JoergS5

Okay, thanks for the hint.

but it worked fine on the X-axis ...

CR3D

I have now connected the endstops of the Y-Axis and those of the U-Axis on the 3HC ... unfortunately without success ...

Here is the config...

Main:

; Configuration file for Duet 3 (firmware version 3)


; General preferences
G90            ; send absolute coordinates...
M82            ; and absolute extruder moves
M550 P"I444-S" ; set printer name

; Network
M552 S1        ; enable network 
M586 P0 S1     ; enable HTTP
M586 P1 S0     ; disable FTP
M586 P2 S0     ; disable Telnet

; Drives

M569 P0.0 S1   ; physical drive 0.0 goes forwards Z0
M569 P0.1 S1   ; physical drive 0.1 goes forwards Z1
M569 P0.2 S1   ; physical drive 0.2 goes forwards Z2
M569 P0.3 S1   ; physical drive 0.3 goes forwards X0
M569 P0.4 S1   ; physical drive 0.4 goes forwards E0
M569 P0.5 S1   ; physical drive 0.5 goes forwards E1

M569 P1.0 S1   ; physical drive 1.0 goes forwards X1 (U)
M569 P1.1 S1   ; physical drive 1.0 goes forwards Y0
M569 P1.2 S1   ; physical drive 1.0 goes forwards Y2


M584 X0.3 Y1.1:1.2 U1.0 Z0.0:0.1:0.2 E0.4:0.5  ; set drive mapping
M350 X16 Y16:16 Z16:16:16 E16:16 I1  ; configure microstepping 
M92 X80.00 Y35.56:35.56 Z4000:4000:4000 E415:415 ;set steps per mm
M566 X900 Y900:900 Z12:12:12 E120:120   ;set maximum instantaneous speed changes (mm/min)
M203 X30000 Y30000:30000 Z300:300:300 E9000:9000      ;set maximum speeds (mm/min)
M201 X1000 Y1000:1000 Z20:20:20 E1000:1000            ;set accelerations (mm/s^2)
M906 X1400 Y4200:4200 Z1200:1200:1200 E1000:1000 I30  ;set motor currents (mA)
M84 S30               ; Set idle timeout

; Axis Limits
M208 X0 Y0 U0 Z0 S1   ; set axis minima
M208 X500 Y450 U600 Z420 S0         ; set axis maxima

; Endstops
M574 X1 S1 P"!io0.in" ; active-high endstop for low end on X via pin io0.in
M574 U2 S1 P"!1.io1.in" ; active-high endstop for high end on U via pin io1.in
M574 Y2 S1 P"!1.io2.in" ; active-high endstop for high end on Y via pin io2.in



; Z-Probe (Piezo)
M558 P5 I1 C"io3.in" R0.5 H5 F400 6000 ; Z probe type -> Piezo

M557 X120:400 Y20:400 P04:04      ; define mesh grid

; Heaters
M308 S0 P"temp0" Y"thermistor" T100000 B4092          ; 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 B0 S1.00                                      ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0                                               ; map heated bed to heater 0
M143 H0 S120                                          ; set temperature limit for heater 0 to 120C

M308 S1 P"temp1" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin temp1
M950 H1 C"out1" T1                                    ; create nozzle heater output on out1 and map it to sensor 1
M307 H1 B0 S1.00                                      ; disable bang-bang mode for heater  and set PWM limit

M308 S2 P"temp2" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 2 as thermistor on pin temp2
M950 H2 C"out2" T2                                    ; create nozzle heater output on out2 and map it to sensor 2
M307 H2 B0 S1.00                                      ; disable bang-bang mode for heater  and set PWM limit

; Fans
M950 F0 C"out7" Q500                                  ; create fan 0 on pin out7 and set its frequency
M106 P0 S0 H1 T50                                     ; set fan 0 value. Thermostatic control is turned on
M950 F1 C"out8" Q500                                  ; create fan 1 on pin out8 and set its frequency
M106 P1 S1 H2 T50                                     ; set fan 1 value. Thermostatic control is turned on
M950 F2 C"out4" Q500                                  ; create fan 2 on pin out4 and set its frequency
M106 P2 S1 H-1                                        ; set fan 2 value. Thermostatic control is turned off
M950 F3 C"out5" Q500                                  ; create fan 3 on pin out5 and set its frequency
M106 P3 S1 H-1                                        ; set fan 3 value. Thermostatic control is turned off

; Tools
M563 P0 S"Links" D0 H1 F0:2  ; define tool 0
G10 P0 X0 Y0 Z0 S0 R0        ; set tool 0 axis offsets
G10 P0 R0 S0                 ; active and standby temperatures 
M563 P1 S"Rechts" D1 H2 X3 F0:3   ; define tool 1
G10 P1 Y0 U0 Z0 S0 R0        ; set tool 1 axis offsets
G10 P1 R0 S0                 ; active and standby temperatures 



; Custom settings are not defined

; Open Door Switch
M581 T0 C"1.io3.in"  S0 C0		;trigger #2 (calls trigger2.g)


; LED
M950 F3 C"out3" Q500  ; create fan 3 on pin out5 and set its frequency
M106 P3 S1     ;set fan 3 value. Thermostatic control is turned off






; Miscellaneous






M501          ; load saved parameters from non-volatile memory

T0            ; select first tool

M572 D0 S0.03

The X-Homing is working:

; homex.g
; called to home the X axis
;
; generated by RepRapFirmware Configuration Tool v3.1.3 on Fri Jun 19 2020 21:08:48 GMT+0200 (Mitteleuropäische Sommerzeit)
G91               ; relative positioning
G1 H2 Z5 F6000    ; lift Z relative to current position
G1 H1 X-505 F1800 ; move quickly to X axis endstop and stop there (first pass)
G1 H2 X5 F6000    ; go back a few mm
G1 H1 X-505 F360  ; move slowly to X axis endstop once more (second pass)
G1 H2 Z-5 F6000   ; lower Z again
G90               ; absolute positioning

The Y Homing is not working for example:

; homey.g
; called to home the Y axis
;
; generated by RepRapFirmware Configuration Tool v3.1.3 on Fri Jun 19 2020 21:08:48 GMT+0200 (Mitteleuropäische Sommerzeit)
G91              ; relative positioning
G1 H2 Z5 F6000   ; lift Z relative to current position
G1 H1 Y455 F1800 ; move quickly to Y axis endstop and stop there (first pass)
G1 H2 Y-5 F6000  ; go back a few mm
G1 H1 Y455 F360  ; move slowly to Y axis endstop once more (second pass)
G1 H2 Z-5 F6000  ; lower Z again
G90              ; absolute positioning

The U-Axis also...

and I think the motors have hardly any power ... so those that are connected to the 3HC ..

CR3D

the limit switches are displayed correctly ...

JoergS5

@CR3D but now this could be valid? "Endstop switches connected to the main board cannot control motors on an expansion board. This is planned to be fixed in release 3.2.0." from https://duet3d.dozuki.com/Wiki/Duet_3_firmware_configuration_limitations

Endstops are on the main board, the steppers for U and Y on the expansion board. X is both on main board. Would explain X working, U and Y not.

CR3D

Yes that´s right! But i tested the endstops on the Expansion board too! see the config i posted above...

JoergS5

@CR3D I lost the overview, ~~which config you mean. But maybe this was when you still used the S0 parameter? 000~~ sorry, now I saw it...

yes, that's strange!

A Former User

@CR3D said in Duet3 Expansion Board 3HC - No CAN-Connection:

But i tested the endstops on the Expansion board too!

and they change state if you manipulate them by hand?

CR3D

@bearer

Yes!

CR3D

If I set the Y-Axis to zero with G92 Y0, then i can move it...

A Former User

call a the doctor, an exorcist, or "just" dc42 methinks.

CR3D

@dc42 perhabs you can help me ....

I have some other phenomenons too... for example i can not control Fan P3 for example...

deckingman

Just stumbled across this thread and I haven't read every post so might have missed something. However, I did notice quite a few things that are wrong with the config.g.

Firstly, the commands M350, M92, M566 M203, M201 and M906 are per axis, not per motor so all those colon separators need to be removed. (But keep the colons between the extruders because extruders are treated like individual axes).

Secondly, you have created an additional "U" axis but you have not set any of those above parameter for that U axis. So all those M350 through to M906 commands need to have U values as well as XYZ, and E.

dc42

Are you definitely running firmware 3.1.1 on the main board, and 3.1.0 on the expansion board? Use M115 to check.

CR3D

@deckingman said in Duet3 Expansion Board 3HC - No CAN-Connection:

Just stumbled across this thread and I haven't read every post so might have missed something. However, I did notice quite a few things that are wrong with the config.g.
Firstly, the commands M350, M92, M566 M203, M201 and M906 are per axis, not per motor so all those colon separators need to be removed. (But keep the colons between the extruders because extruders are treated like individual axes).
Secondly, you have created an additional "U" axis but you have not set any of those above parameter for that U axis. So all those M350 through to M906 commands need to have U values as well as XYZ, and E.

Ok... you are absolutely rigth! Shame on me!

I changed this now....

@dc42
You are also right... there is an older firmware ... now I want to Upload with Bossa but there is no connection... The board is erased now...

A Former User

@CR3D said in Duet3 Expansion Board 3HC - No CAN-Connection:

now I want to Upload with Bossa

thats usually a recovery option, and a few people have struggled due to bad usb cables and/or ports, as well as there seems to be a bug in Bossa affecting some users, but not all. M997 and/or DuetWebControl is the preferred option.

have you tried other cables/ports? can you try a different computer (/operating system)? some have found it helps using a USB hub.

I've generally found it works well from Raspberry Pi's, but others have also had encounters with the aforementioned bug there.

CR3D

@bearer

Yes i tested a new USB Cable and it worked!

@dc42 Now the Main Board and the Expansion Board hast the newest firmware.... Thank you!

The Homing of the X-Axis and U-Axis works well now, but the Y-Axis doesn´t...

the y-motors turn but do not yet react to the end stop. The Y axis works with 2 motors and an end stop (connected to 1.io2.in). the endstop is read out correctly, I have already checked that if I unplug it, of course it does not react, so it is properly connected. where do I still have the error here?

.

CR3D

Any ideas here?

I can not find a mistake till now....

dc42

Does DWC display the correct triggered/not triggered status for the Y endstop, or not?

CR3D

@dc42

Yes... if i manually move the axis the signal is shown right...

The sensor is correctly connected and also correctly mapped to the Y axis.

The sensor is correctly connected and also correctly connected to the Y axis.

If I actuate the limit switch of the Y axis before homing (i.e. put the axis in home position), the Y axis reacts and sets the axis as referenced.

If the limit switch is not actuated when homing, so the axis should move in the direction of the limit switch, the message "Homing failed" appears. I configured it so that my bed moves down a distance first. If homing failed occurs, the bed moves back to the starting position but the Y motors continue to rotate and do not react to the limit switch.

If I reference the axis manually with G92 Y0, I can also move the axis correctly.

Everything seems to be correct, but the normal homing of the Y axis does not work.

The config was created with the configuration tool. The homing of the other axes also works perfectly.

; homey.g
; called to home the Y axis
;
; generated by RepRapFirmware Configuration Tool v3.1.3 on Fri Jun 19 2020 21:08:48 GMT+0200 (Mitteleuropäische Sommerzeit)
G91              ; relative positioning
G1 H2 Z5 F6000   ; lift Z relative to current position
G1 H1 Y455 F1800 ; move quickly to Y axis endstop and stop there (first pass)
G1 H2 Y-5 F6000  ; go back a few mm
G1 H1 Y455 F360  ; move slowly to Y axis endstop once more (second pass)
G1 H2 Z-5 F6000  ; lower Z again
G90              ; absolute positioning