The ports of FluidNC can all be freely defined and allocated through the Yaml file, so there is no fixed PinMap.
Our current definition is based on the test Yaml we use.
When applying it to your machine, you will need to define the pins yourself.
If you find the following section challenging, don't worry. You can complete the checklist steps first and then come back - it will make much more sense.
:pu configuration in YAML file.:low parameter.NO (Normally Open) or NC (Normally Closed) contacts as control signals.M3 S24000), if the output voltage does not reach 10V.GPIO.26.IO.12 or IO.4 by switching GND connection to complete the circuit.IO.12-MOS-GND and IO.4-MOS-GND ports serve as GND.24V input is strongly recommended.50V withstand voltage rating.>12V to generate proper signals.24V is recommended. Ensure correct polarity to avoid damage.3.3V when using SPI-type stepper motors.5V for external drivers requiring 5V logic signals.3.3V. Choose according to your specific driver requirements.GPIO.26 function selection jumper.I2SO output to control pin levels.MS0/MS1/MS2 - set according to actual pin functions.I2SO numbers.CS) signal.I2SO ports can also be used as CS signals for corresponding SPI drivers.EN, DIR, CLK, and GND signals.I2SO signals to the green TBX terminals.1-4 for onboard drivers, slots 5,6 for external relay output).I2SO signals for relays to TBX terminals.I2SO.3 as the Chip Select (CS) signal.USB 5V into the circuit for testing purposes.GPIO.25 and GPIO.27 ports.VCC and GND, as some OLED modules have different pin arrangements.GPIO.25 and GPIO.27 ports.