Help straighten me out on pin naming

kb58

@peter247 So there's an internal association between, say, motor 1 and io_1, without explicitly having to say as much, yes?

peter247

@kb58 https://duet3d.dozuki.com/Wiki/Duet_3_Mainboard_6HC_Wiring_Diagram

not motor 0 can be anything so can io_0 , it can be a end stop filament out sensor or trigger , it is all on you to set how it works.

kb58

This post is deleted!

peter247

@kb58 it is not named that is on duet 2

Javajoeuk

no i dont think so you have to tell it which pin you want it to use

peter247

@javajoeuk Yes you tell it which pin to use , but it can be any pin to do any job.

kb58

@peter247 Okay, so I'm still not seeing it. If any pin can be anything, I'm back to asking the same question, that naming an end stop is only half the picture, that somewhere it has to get "pointed" to the physical connector that I'm plugging that switch into. Sorry for being dense, but I'm an engineer...

resam

@kb58 look here for a full list of pin names:
https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview#Section_Duet_3_MB6HC_pin_names

and the wiring an hardware overview:
https://duet3d.dozuki.com/Wiki/Duet_3_Mainboard_6HC_Wiring_Diagram#Section_Revision_1_0_and_1_Num_01

and the M574 for RRF3 help:
https://duet3d.dozuki.com/Wiki/Gcode#Section_M574_RepRapFirmware_Num_3

kb58

@resam I know about the pin names, but a name is just text, it's not hardwired to anything. If I have: M574 X1 S1 P"X_endstop", what connector is "X_endstop" looking at?

kb58

@resam Or, are you saying that I have to use M574 X1 S1 P"io1.in", and that I'm not free to rename them? That seems doubtful because io1.in is just a text string, no?

peter247

@kb58 This is my set up .

; Endstops
M574 X1 S1 P"!io0.in"                          ; configure active-high endstop for low end on X via pin xstop
M574 Y2 S1 P"!io1.in"                          ; configure active-high endstop for low end on Y via pin ystop
;M574 Z1 S2  

; Z-Probe
M558 P9 C"io2.in" H2 F100 T8000 A5		        ; set Z probe type to bltouch and the dive height + speeds
M950 S0 C"io2.out"							    ; create servo pin 0 for BLTouch
G31 P500 X 30 Y 55 Z 1.4                        ; set Z probe trigger value, offset and trigger height
M557 X60:240 Y60:240 S30

But I could have used io1.in for the X stop if I had configured it that way.

kb58

@peter247 Ah, okay, so only predefined pin names can be used.

resam

@kb58 Duet3 does not have a "X_endstop" pin, see https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview#Section_Duet_3_MB6HC_pin_names for the official pin names.

If you want to create an endstop for your X-axis, then use M574 with the X1 parameter for the X-axis, and e.g., P"io0.in" to use the IO0 input pin.

kb58

@resam Got it, finally, and thanks, everyone.