Very strange behavior, CoreXY with external drivers

Capricorn

Hello all together,
I have a big Problem, that i can't solve by myself. My Board is a duet2 ethernet and I connected 3 external drivers to the breakout - board
Drive 5-7. Redirected x to 5, y to 6 and z to 7.
Disabled the onboard xyz drivers. All ext. Drivers and Motors are working and running in the right direction.
Homing x works, also y. But!!! The x-motor is bonded to the z-motor. Moving the x Motor also moves the z Motor and vice versa. As the x Motor needs 88 steps/mm and the z Motor 1300 steps/mm leads to a crash in x, when moving the z-axis more than 40mm, as the x-motor is then also driven with 1300 steps/mm. I don't know, what causes this behavior.
I really hope, a Genius out there, can help me.
Thx and greetings from germany.

Phaedrux

Can you post your config file?

Capricorn

Good Morning,
shure, i can... (try to)
; Configuration file for Duet WiFi (firmware version 1.21)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v2 on Sat May 04 2019 10:06:41 GMT+0200 (Mitteleuropäische Sommerzeit)

; General preferences
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves

M669 K1 ; Select CoreXY mode

; Network
M550 P"Excalibur" ; Set machine name
; M551 P"3dprinter" ; Set password
M552 P192.168.2.151 S1 ; Enable network and set IP address
M553 P255.255.255.0 ; Set netmask
M554 P192.168.2.1 ; Set gateway
M586 P0 S1 ; Enable HTTP
M586 P1 S0 ; Disable FTP
M586 P2 S0 ; Disable Telnet

; Drives
M569 P0 S1 R-1 ; Drive 0 goes forwards
M569 P1 S1 R-1 ; Drive 1 goes forwards
M569 P2 S1 R-1 ; Drive 2 goes forwards
M569 P3 S1 ; Drive 3 goes forwards
M569 P4 S0 ; Drive 4 goes reverse
M569 P5 S0 R0 T2.5:2.5:6:0 ; Drive 5 goes reverse
M569 P6 S0 R0 T2.5:2.5:6:0 ; Drive 6 goes reverse
M569 P7 S1 R0 T2.5:2.5:6:0 ; Drive 7 goes forwards
M584 X5 Y6 Z7 E0:1:2:3:4 ; Apply custom drive mapping
M350 E16:16 I1 ; Configure microstepping with interpolation
M92 X88.89 Y88.89 Z1303 E415.00:415.00 ; Set steps per mm
M566 X900.00 Y900.00 Z120.00 E120.00:120.00 ; Set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z600.00 E1200.00:1200.00 ; Set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z100.00 E250.00:250.00 ; Set accelerations (mm/s^2)
M906 E800.00:800.00 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z0 S1 ; Set axis minima
M208 X420 Y500 Z410 S0 ; Set axis maxima

; Endstops
M574 X2 Y2 S0 ; Set active low and disabled endstops
M591 D0 P1 C3 S1 ; Filamentmonitor E0
M591 D1 P1 C4 S1 ; Filamentmonitor E1

; Z-Probe
M574 Z1 S2 ; Set endstops controlled by probe
M307 H7 A-1 C-1 D-1 ; Disable heater on PWM channel for BLTouch
M558 P9 H5 F100 T2000 ; Set Z probe type to bltouch and the dive height + speeds
G31 P25 X10 Y-20.0 Z2.5 ; Set Z probe trigger value, offset and trigger height
M556 S100 X0 Y0 Z0 ; Set orthogonal axis compensation parameters
M557 X20:380 Y120:480 S40 ; Define mesh grid

; Heaters
M141 H6 ; Assign chamber heater to heater 0
M307 H6 B0 S1.0 ; Enable bang-bang mode for the bed heater and set PWM limit
M305 P0 T100000 B4138 R4700 ; Set thermistor + ADC parameters for heater 0
M143 H0 S130 ; Set temperature limit for heater 0 to 130C
M305 P1 X200 ; Configure PT100 for heater 1
M143 H1 S320 ; Set temperature limit for heater 1 to 320C
M305 P2 X201 ; Configure PT100 for heater 2
M143 H2 S320 ; Set temperature limit for heater 2 to 320C
M305 P6 T100000 B4138 R4700 ; Set thermistor + ADC parameters for heater 6
M143 H6 S70 ; Set temperature limit for heater 6 to 70C

; Fans
M106 P0 S255 I0 F500 H1:2 T45 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned on
M106 P1 S0 I0 F500 H-1 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P2 S0 I0 F500 H-1 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned off

; Tools
M563 P0 S"Links" D0 H1 ; Define tool 0
G10 P0 X-10 Y0 Z0 ; Set tool 0 axis offsets
G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C
M563 P1 S"Rechts" D1 H2 ; Define tool 1
G10 P1 X10 Y0 Z0 ; Set tool 1 axis offsets
G10 P1 R0 S0 ; Set initial tool 1 active and standby temperatures to 0C

; Automatic power saving
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; Set voltage thresholds and actions to run on power loss

; Custom settings are not configured

; Miscellaneous
T0 ; Select first tool

dc42

My best guess is that the printer is running in CoreXZ mode instead of CoreXY mode. Which firmware version are you using? If you send M669 without parameters, what does it report?

Try replacing the M669 K1 command in config.g by M667 S1.

Veti

@capricorn

M305 P6 T100000 B4138 R4700 ; Set thermistor + ADC parameters for heater 6
M305 P0 T100000 B4138 R4700 ; Set thermistor + ADC parameters for heater 0

The beta value 4138 is the default in the configurator. double check that this is correct for your thermistors.

Capricorn

@dc42

thx for reply.

M667 S1 i had bevor i changed it to M669 K1. Same behavior....
Firmware is the newest you posted lately. (2.03RC5), but also with 2.02 is this problem.

Capricorn

@veti

thx for reply.

i have the thermistors from E3D for bed and chamber. this values seem to work.
As i am in the building process for may printer, i first had to get the motors runnig correctly.....

Veti

@capricorn said in Very strange behavior, CoreXY with external drivers:

i have the thermistors from E3D

e3d uses semitech thermistors

https://e3d-online.com/100k-ohm-ntc-thermistor-semitec

the correct values for that are
β: 4725 K
C : 7.060000e-8

dc42

@capricorn said in Very strange behavior, CoreXY with external drivers:

@dc42

thx for reply.

M667 S1 i had bevor i changed it to M669 K1. Same behavior....
Firmware is the newest you posted lately. (2.03RC5), but also with 2.02 is this problem.

Please send M669 without parameters, also M584 without parameters, and report the responses.

The other possibility is a short-circuit between the E2_STEP (driver 5) and E4_STEP (driver 7) signals, however this seems unlikely because those signals are not adjacent on the Duet microcontroller (pins 131 and 1), or on the expansion connector (pins 5 and 15). If you have a multimeter, you could use it to check for a short circuit between those pins on the expansion connector of the Duet or the breakout board.

Capricorn

@dc42

M669 without parameters reports:

Kinematics is CoreXY, matrix:
1.00 1.00 0
1.00 -1.00 0
0 0 1.00

dc42

@capricorn said in Very strange behavior, CoreXY with external drivers:

@dc42

M669 without parameters reports:

Kinematics is CoreXY, matrix:
1.00 1.00 0
1.00 -1.00 0
0 0 1.00

That matrix looks correct for CoreXY. What about M584?

Capricorn

@dc42

M584
Driver assignments: X5 Y6 Z7 E0:1:2:3:4, 3 axes visible

dc42

That looks OK too. So I think it's either very obscure firmware error or a short-circuit between those two signals (see my earlier message).

Capricorn

@dc42

to clarify how my extern drivers are connected:
all Step+/Dir+ from the ext. drivers go to +5V.
all Step-/Dir- from the ext. drivers go to the corresponding pins on the breakout board

dc42

@capricorn said in Very strange behavior, CoreXY with external drivers:

@dc42

to clarify how my extern drivers are connected:
all Step+/Dir+ from the ext. drivers go to +5V.
all Step-/Dir- from the ext. drivers go to the corresponding pins on the breakout board

That sounds good.

Are you using G1 S2 moves (after sending G91 to select relative axis coordinates) to test the motors individually?

Capricorn

@dc42

yes, i did, x and z go together and i can´t find a shortcut...
i also tried to redirect z to drive 8 or 9. Same behavior...

dc42

Do any other motors move when you command the Y motor?
Please check that you really do have +5V on the common 5V feed to the + inputs of the stepper drivers.

Capricorn

@dc42

no other motors affected by moving Y.
the Voltage at the + inputs of the drivers is 4.56 V

Capricorn

@dc42

meanwhile i tested another driver for z-motor (have more of them as spare) and also testet to set the
config to cartesian kinematiks. No luck, always x/z move together.... I´m frustrated....

Capricorn

@veti

thank you, for your help, i´m just about cabling the printer. i can test it, when everything else is running.