You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/emc/usr_intf/pncconf/ADDING_A_MESA_CARD.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,10 +44,12 @@ The remainder of the data structure consists of list entries specifying the indi
44
44
45
45
Allocation of the order of I/O pins to connectors is done at the Mesa hardware level and in our case the Mesa manual for the `7i93` specifies `CONECTOR P2 I/O 0..23` and `CONNECTOR P1 I/O 24..47`.
46
46
47
-
If logical number < 100 => GPIO can be changed to GPIOO or GPIOD at the start of linuxcnc, load time if you prefer (run time)
47
+
If logical number < 100 => GPIO can be changed to GPIOO or GPIOD at the start of linuxcnc, load time if you prefer (or run time)
48
48
If logical number > 100 => GPIO can NOT be changed to GPIOO or GPIOD at the start of linuxcnc, load time (always input or always output)
49
49
Value of number or number-100 corresponds with HAL Pin of Hostmot2 component
50
-
The number 0 or 100 can be repeated only for GPIO and the numbering is done automatically.
50
+
The number 0 or 100 currentky only has meaning for GPIO, SSR, INM and OUTM components.
51
+
With GPIO the numbering uses the position in the firmware, starting with the first found GPIO as 0.
52
+
SSR encodes the logical number within the 1xx number. ie 100 = zero component, 101 the #1 component etc.
51
53
52
54
The data structure from the code is replicated below. Using the data above, you should be able to decode this information:
0 commit comments