Z direction fixed

Extruder works fine and it's in the right direction   Tested to see that the hotend had to be hot for the extrusion to operate - it did

Regarding XY (CoreXY) motors, I'm going to try swapping the motor connectors.

Later... No difference.  Did notice that trying to move X gave a different buzz compared with Y for the same amount.

Wonder if I should update the firmware - currently 1.19.2.

Endstops work according to the LEDs on the board, including the Z probe (at 4mm above bed)

It won't let me test the Z homing until it has homed the X and Y.  It's not even satisfied that the X and Y axes have been homed manually so that the endstops are activated.  Seems that I have to sort out the XY motors before I can do any more testing.   Impasse!!

I've updated the main firmware to 1.20.  That was pretty painless

XY motors still not working   Here's my config.g :-

; Configuration file for Duet WiFi (firmware version 1.20 or newer)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool on Mon Jan 15 2018 15:49:12 GMT+0000 (GMT)

; General preferences
M111 S0                           ; Debugging off
G21                               ; Work in millimetres
G90                               ; Send absolute coordinates...
M83                               ; ...but relative extruder moves
M555 P2                           ; Set firmware compatibility to look like Marlin
; Automatic saving after power loss is not enabled
M208 X0 Y0 Z0 S1                  ; Set axis minima
M208 X200 Y200 Z200 S0            ; Set axis maxima

; Endstops
M574 X1 Y1 S1                     ; Set active high endstops
M574 Z1 S2                        ; Set endstops controlled by probe
M558 P4 H5 F120 T6000             ; Set Z probe type to unmodulated and the dive height + speeds
G31 P500 X24 Y0 Z2.5              ; Set Z probe trigger value, offset and trigger height
M557 X15:185 Y15:185 S20          ; Define mesh grid

; Drives
M569 P0 S1                        ; Drive 0 goes forwards
M569 P1 S1                        ; Drive 1 goes forwards
M569 P2 S1                        ; Drive 2 goes forwards
M569 P3 S0                        ; Drive 3 goes backwards
M350 X16 Y16 Z16 E16 I1           ; Configure microstepping with interpolation
M92 X62.45 Y62.45 Z401.02 E783.53 ; Set steps per mm
M566 X900 Y900 Z12 E120           ; Set maximum instantaneous speed changes (mm/min)
M203 X6000 Y6000 Z180 E1200       ; Set maximum speeds (mm/min)
M201 X500 Y20 Z250 E250           ; Set accelerations (mm/s^2)
M906 X1000 Y1000 Z1000 E800 I30   ; Set motor currents (mA) and motor idle factor in per cent
M84 S30                           ; Set idle timeout

; Heaters
M305 P0 T100000 B4138 C0 R4700    ; Set thermistor + ADC parameters for heater 0
M143 H0 S150                      ; Set temperature limit for heater 0 to 150C
M305 P1 T100000 B4138 C0 R4700    ; Set thermistor + ADC parameters for heater 1
M143 H1 S300                      ; Set temperature limit for heater 1 to 300C

; Tools
M563 P0 D0 H1                     ; Define tool 0
G10 P0 X0 Y0 Z0                   ; Set tool 0 axis offsets
G10 P0 R0 S0                      ; Set initial tool 0 active and standby temperatures to 0C

; Network
M550 P"GinaRep Mini"              ; Set machine name
M552 S1                           ; Enable network
;*** Access point is configured manually via M587
M586 P0 S1                        ; Enable HTTP
M586 P1 S0                        ; Disable FTP
M586 P2 S0                        ; Disable Telnet

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

; Custom settings are not configured

I can't see where it's set to CoreXY.

Found this :-

Quote

Main configuration file

Movement section

To switch the firmware to CoreXY mode, add this command to the movement section:

M667 S1                   ; switch to CoreXY mode

Use S1 for CoreXY, S2 for CoreXZ, and S3 for CoreYZ.

 

So I've added "M667 S1  ; switch to CoreXY mode" before the drive motor directions.

Hmm... that's had no effect!  X gives a fast, short "burp" and Y a slower, longer one.  Both motors do this together.

Also checked that the motors are right way round :-

Quote

For a CoreXY or H-Bot machine, RepRapFirmware assumes that the motor connected to the X motor output moves the head in the +X and +Y directions when it runs forwards, and that the Y motor moves the head in +X and -Y directions when it runs forwards.

Which they are now but no difference as I expected.  That would only make the Y direction wrong.

I think that's as far as I can go ATM.  The motors are wired correctly and I would expect an error or fault to affect just one motor not both.  From the amount of sound coming from the motors I would think there's plenty of drive current (I set it to 1A with a motor rating of 1.5A).  And the other two motors are fine (Extruder and Z axis).

There is another "funny".  If I try homing X or Y the Z motor runs in addition to noise from the XY motors.

Another observation is that after trying an X or Y movement the XY motors are in "hold" mode.  Trying to turn them caused them to buzz.

Add this to set corexy mode:

M667 S1                                   ; Select CoreXY mode

I've done that.  Here's the latest config.g :-

; Configuration file for Duet WiFi (firmware version 1.20 or newer)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool on Mon Jan 15 2018 15:49:12 GMT+0000 (GMT)

; General preferences
M111 S0                           ; Debugging off
G21                               ; Work in millimetres
G90                               ; Send absolute coordinates...
M83                               ; ...but relative extruder moves
M555 P2                           ; Set firmware compatibility to look like Marlin
; Automatic saving after power loss is not enabled
M208 X0 Y0 Z0 S1                  ; Set axis minima
M208 X200 Y200 Z200 S0            ; Set axis maxima

; Endstops
M574 X1 Y1 S0                     ; Set active low endstops       **********  Gina added
M574 Z1 S2                        ; Set endstops controlled by probe
M558 P4 H5 F120 T6000             ; Set Z probe type to unmodulated and the dive height + speeds
G31 P500 X24 Y0 Z2.5              ; Set Z probe trigger value, offset and trigger height
M557 X15:185 Y15:185 S20          ; Define mesh grid

; Drives
M667 S1                           ; switch to CoreXY mode *** Gina added
M569 P0 S1                        ; Drive 0 goes forwards
M569 P1 S1                        ; Drive 1 goes forwards
M569 P2 S1                        ; Drive 2 goes forwards
M569 P3 S0                        ; Drive 3 goes backwards
M350 X16 Y16 Z16 E16 I1           ; Configure microstepping with interpolation
M92 X62.45 Y62.45 Z401.02 E783.53 ; Set steps per mm
M566 X900 Y900 Z12 E120           ; Set maximum instantaneous speed changes (mm/min)
M203 X6000 Y6000 Z180 E1200       ; Set maximum speeds (mm/min)
M201 X500 Y20 Z250 E250           ; Set accelerations (mm/s^2)
M906 X1000 Y1000 Z1000 E800 I30   ; Set motor currents (mA) and motor idle factor in per cent
M84 S30                           ; Set idle timeout

; Heaters
M305 P0 T100000 B4138 C0 R4700    ; Set thermistor + ADC parameters for heater 0
M143 H0 S150                      ; Set temperature limit for heater 0 to 150C
M305 P1 T100000 B4138 C0 R4700    ; Set thermistor + ADC parameters for heater 1
M143 H1 S300                      ; Set temperature limit for heater 1 to 300C

; Tools
M563 P0 D0 H1                     ; Define tool 0
G10 P0 X0 Y0 Z0                   ; Set tool 0 axis offsets
G10 P0 R0 S0                      ; Set initial tool 0 active and standby temperatures to 0C

; Network
M550 P"GinaRep Mini"              ; Set machine name
M552 S1                           ; Enable network
;*** Access point is configured manually via M587
M586 P0 S1                        ; Enable HTTP
M586 P1 S0                        ; Disable FTP
M586 P2 S0                        ; Disable Telnet

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

; Custom settings are not configured

When you home the axes it runs the homex.g, homey.g, homez.g or homeall.g depending on what you clicked. Check the contents of those to make sure they are not doing something strange.

Found the post where you showed links to your config files Dave, and downloaded your config.g.  Saw you had the CoreXY setting in a different place so I tried putting mine there but it made no difference.

37 minutes ago, tekkydave said:

When you home the axes it runs the homex.g, homey.g, homez.g or homeall.g depending on what you clicked. Check the contents of those to make sure they are not doing something strange.

Ah yes - homex lifts the Z (or in this case lowers the bed).  That explains why homing X (or Y) moves the Z axis.

Still not solved the XY motor problem though.

Maybe if I swapped motors around it might shed some light.  It's only a matter of moving connectors.

Swapped motors and the extruder and Z axis work off the XY and vice versa.  Result - X or Y movement moves the extruder and Z motors.  Z movement makes the motor buzz but not move.  SO the fault is with the motors - BOTH of them!  I think.  To confirm I'm heating up the hotend ready to try the extruder which now operates one of the XY motors.

This is weird - both the XY motors growl if either Z or extruder motors are operated from the Duet.  Yet the power should only be applied to one of them.  This is magic!!

Tomorrow I shall take two brand new NEMA 17 motors (I have several) and connect them to the X and Y motor connectors.  I shall crack this!!!

Thought I would do another check on the motor connections for the XY motors and guess what - wrong!!   The left-hand motor came off a RepRap printer yet the connections were wrong - could have been the Velleman Kit with the original Velleman control board I guess - maybe that was non-standard.  It was my mistake on connecting the other one though and I thought I had checked - twice.  Anyway, I've put the connections right and the XY motors are now working   Now it's just a case of getting all the movement directions right.  I've got the X and Y right and those axes home alright.  The Z axis moves in the right direction but the homing is wrong.  I guess the homez.g needs looking at.  Moving the axes individually from the control panel is whisper quiet

Now fixed the Z homing   Found this in the Z Probe section of the wiki :-

Quote

In firmware 1.16 and later, use I1 in the M558 command to select active low, otherwise it defaults to active high.

This system is more sensible than the Marlin in that it goes to the first bed probe point rather than going to the middle before Z homing.  I've always thought it was daft for the Z homing to be in the middle the to move nearly half a diagonal for auto-bed-levelling.

ATM Z homing is very slow so I'll increase the speed later.  There's several other things to adjust first.

Been adjusting various things including increasing the Z maximum speed to 900mm/min from 180mm/min which was very slow.  Have found a problem with the Y endstop - it clashes with a bed support so I've had to alter that.  Fine now   Bed levelling setup is next...  Or maybe tidy up the wiring.

Done some wiring tidying up.  Been trying to get the Mesh Grid Compensation working but having problems.  It only seems to want to probe 6 points out of 9.  I've tried various things but it insists on probing fewer than the 9 points set up in a 3x3 matrix.  This is the Mesh Grid setup line :-

M557 X15:175 Y15:175 S80          ; Define mesh grid

And here's the whole config.g :-

; Configuration file for Duet WiFi (firmware version 1.20 or newer)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool on Mon Jan 15 2018 15:49:12 GMT+0000 (GMT)

; General preferences
M111 S0                           ; Debugging off
G21                               ; Work in millimetres
G90                               ; Send absolute coordinates...
M83                               ; ...but relative extruder moves
M555 P2                           ; Set firmware compatibility to look like Marlin
; Automatic saving after power loss is not enabled
M667 S1                           ; switch to CoreXY mode *** Gina added
M208 X0 Y0 Z0 S1                  ; Set axis minima
M208 X190 Y190 Z240 S0            ; Set axis maxima

; Endstops
M574 X1 Y1 S0                     ; Set active low endstops       **********  Gina added
M574 Z1 S2                        ; Set endstops controlled by probe
M558 P4 H7 F600 T6000 I1          ; Set Z probe type to unmodulated and the dive height + speeds  *** I1 added  speed 600mm/min
G31 P500 X24 Y0 Z2.5              ; Set Z probe trigger value, offset and trigger height
M557 X15:175 Y15:175 S80          ; Define mesh grid

; Drives
M667 S1                           ; switch to CoreXY mode *** Gina added
M569 P0 S0                        ; Drive 0 goes forwards
M569 P1 S0                        ; Drive 1 goes backwards
M569 P2 S1                        ; Drive 2 goes forwards
M569 P3 S0                        ; Drive 3 goes backwards
M350 X16 Y16 Z16 E16 I1           ; Configure microstepping with interpolation
M92 X62.45 Y62.45 Z401.02 E783.53 ; Set steps per mm
M566 X900 Y900 Z12 E120           ; Set maximum instantaneous speed changes (mm/min)
M203 X6000 Y6000 Z900 E1200       ; Set maximum speeds (mm/min)
M201 X500 Y20 Z250 E250           ; Set accelerations (mm/s^2)
M906 X1000 Y1000 Z1000 E800 I30   ; Set motor currents (mA) and motor idle factor in per cent
M84 S30                           ; Set idle timeout

; Heaters
M305 P0 T100000 B4138 C0 R4700    ; Set thermistor + ADC parameters for heater 0
M143 H0 S150                      ; Set temperature limit for heater 0 to 150C
M305 P1 T100000 B4138 C0 R4700    ; Set thermistor + ADC parameters for heater 1
M143 H1 S300                      ; Set temperature limit for heater 1 to 300C

; Tools
M563 P0 D0 H1                     ; Define tool 0
G10 P0 X0 Y0 Z0                   ; Set tool 0 axis offsets
G10 P0 R0 S0                      ; Set initial tool 0 active and standby temperatures to 0C

; Network
M550 P"GinaRep Mini"              ; Set machine name
M552 S1                           ; Enable network
;*** Access point is configured manually via M587
M586 P0 S1                        ; Enable HTTP
M586 P1 S0                        ; Disable FTP
M586 P2 S0                        ; Disable Telnet

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

; Custom settings are not configured

The M557 parameters in config.g get used when you execute G29. Try running G29 from the gcode console (after homing the axes of course).

If you run the Mesh Grid Compensation from the button on the control page it seems to want to run bed.g if present. Otherwise it runs G32 using the M557 parameters. I think. Still a bit confused myself.

See M557 and G32 for some clarity. Maybe