Topics created by GBusy24

@droftarts Result of motor drive mapping with M584- X=0 Y=1 Z=2 E=3. Extruder does not move along with X and Z when attempting to extrude. Physically looking at the board everything looks perfect. No damage. I see nothing amiss under the board. It sits on a 3D printed mount. I will say that when attempting to test motor movement following the Duet 3D guide, I get no movement at all when sending , G1 H2 X10 F3000, but I do get movement out of X,Y when sending G1 H2 Y10 F3000 and it moves how the guide describes it should in the +x and -Y directions. Here are the things you asked me to share. Homeall.g1000008461.jpg 1000008463.jpg ![1000008464.jpg](/assets/uploads/files/1745450157161-1000008464-resized.jpg Thankful for your help.

EDIT 4/25/25:
AHA! The move X command, G1 H2 X10 F3000 is turning the extruder motor upon further testing, but why does moving X in DWC work normal as expected? Why doesn't the extruder motor turn instead of X in DWC?Now, my question to you and myself is,.....Did I plug X and E into the board swapped when changing out boards? I don't think so. That means the problem lies within config.g or motor mapping doesn't it? But motor mapping seems proper and so does config.g.

I just uploaded my current .json file to the RRF config tool and notice the motor mapping it displays is different from what I'm seeing in my config.g Here it is from the RRFC. Only P3 is changed from S0 in my config.g to S1 that I'm seeing in RRFC tool. I've tried changing it to that in my config.g,, but end up with a bad result.

M569 P0 S0 D2 ; driver 0 goes backwards (X axis)
M569 P1 S0 D2 ; driver 1 goes backwards (Y axis)
M569 P2 S0 D2 ; driver 2 goes backwards (Z axis)
M569 P3 S1 D2 ; driver 3 goes forwards (extruder 0)

EDIT 4/25/24: Solved
I did have the X and E swapped into wrong positions on the board.

@droftarts @Phaedrux , I think it was both the error with the quotatiion mark and also the I parameter I had in the 587. I'm jusy happy you guys help me solve it. Thanks again.

@Phaedrux Okay, thanks

@GBusy24 said in HOMING ERROR:

Found it.

Glad you got it!

@Phaedrux, that's what I was looking for. The reference to the '!'. I had forgotten about it. Thank you kindly.

@gbusy24 glad to hear it

@gbusy24
Too bad it didn't work with the ; before the command line.
But I still think this command line is unnecessary, but the moderator can tell you more about it, he is more familiar with it because it is his daily job and he knows the various configurations.
I don't have the line and I couldn't find it anywhere in the documentation.
mine looks like this...

; Endstops M574 X1 P"!xstop" ; configure unsupported switch-type endstop for low end on X via pin xstop M574 Y1 S1 P"ystop" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin ystop M574 Z1 P"!zstop+!e0stop" ; configure unsupported switch-type endstop for low end on Z via pin null

On the Z-axis (2 endstops) and on the Y-axis I have self-made endstops that work with a HAL-Sensor and a magnet that I can adjust.
I still have the original endstop microswitch on the Y-axis, but with an LED and three cables.

You should use the two outer pins on the microswitch, i.e. C and NC
C is the input and NC and NO are the outputs.
NO = Normally Open
NC = Normally closed

Google Translate
----- Original Text -----

Schade das es nicht funktioniert hat mit dem ; vor der Kommandozeile.
Ich glaube aber immer noch, diese Kommandozeile ist unnötig, aber dazu kann Dir der Moderator mehr sagen, der kennt sich damit besser aus weil es sein täglicher Job ist und er die verschiedensten Konfigurationen kennt.
Bei mir ist die Zeile nicht vorhanden und in der Dokumentation konnte ich sie auch nirgends finden.
Meine sieht so aus...

; Endstops M574 X1 P"!xstop" ; configure unsupported switch-type endstop for low end on X via pin xstop M574 Y1 S1 P"ystop" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin ystop M574 Z1 P"!zstop+!e0stop" ; configure unsupported switch-type endstop for low end on Z via pin null

An der Z-Achse (2 Endstops) und an der Y-Achse habe ich selbstgebaute Endstops die mit einem HAL-Sensor und einem Magneten funktionieren den ich justieren kann.
An der Y-Achse habe ich noch den Original Microschalter Endstop, aber mit LED und drei Kabeln.

An dem Microschalter solltest Du die beiden äußeren Pins nutze, also C und NC
C ist der Eingang und NC und NO sind die Ausgänge.
NO = Normal Offen
NC = Normal geschlossen

@tecno @GBusy24 you can also just copy or cut/paste images into your post.

@engikeneer I tried removing the ! And it didn't change anything. Yes I have my Y set up like that because my end stop is at the back of the bed. I will give all this a look over again to try and figure out what I'm doing wrong and get back with you. I appreciate your response.

@jay_s_uk Here's the Config.g from SD card.

; Configuration file for Duet WiFi (firmware version 3.3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Mon Jan 24 2022 20:50:56 GMT-0500 (Eastern Standard Time)

; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"CoreXY 1" ; set printer name
M669 K1 ; select CoreXY mode

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

; Drives
M569 P0 S0 ; physical drive 0 goes forwards
M569 P1 S0 ; physical drive 1 goes forwards
M569 P2 S0 ; physical drive 2 goes forwards
M569 P3 S0 ; physical drive 3 goes forwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E852 ; set steps per mm
M566 X900.00 Y900.00 Z60.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z900.00 E1200.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E1200 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 X320 Y185 Z300 S0 ; set axis maxima

; Endstops
M574 X1 S1 P"!xstop" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin xstop
M574 Y2 S1 P"!ystop" ; configure switch-type (e.g. microswitch) endstop for high end on Y via pin ystop
M574 X1 Y2 S1 ; X home to min. Y home to max. Normally Closed limit switches.
M574 Z1 S2 ; Define Z to use Probe. Home to Min

; Z-Probe
M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch
M558 P9 C"^zprobe.in" H5 F120 T6000
G31 P500 X-41.8 Y32.2 Z2.2
M557 X10:320 Y0:190 S50 ; define mesh grid

; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
M307 H0 R0.495 K0.404:0.000 D4.40 E1.35 S1.00 B0; 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"e0temp" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S280 ; set temperature limit for heater 1 to 280C

; Fans
M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on

; Tools
M563 P0 D0 H1 F0 ; 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

; Custom settings are not defined
M501

Everything works as should now. Thanks

@dc42 Hi, I just saw your message and ran the command. E-thing seems good to go. Here's the response: "M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
I've come to terms that this smaller stepper needs higher current than normal sized steppers. I'm okay with that. I've used this motor for years on my setup and haven't had any problems. I am going to show it a lil' love tho with a nice heatsink that arrives tomorrow

@diy-o-sphere A friend helped me find the problem. Thanks for your help.

@droftarts Fabulous! that did it. Thanks

@o_lampe Thanks for that info. Wasn't aware of all that. Time to get at it then.

@droftarts It works now thanks for the help!

@phaedrux That did I
it! Thank you