Problems configuring 7i92TH with pncconf
- richcolvin
- Topic Author
- Offline
- New Member
Less
More
- Posts: 4
- Thank you received: 0
17 Jan 2025 17:56 #319197
by richcolvin
Problems configuring 7i92TH with pncconf was created by richcolvin
I am new to LinuxCNC, so please forgive me if this has already been answered. I searched and could not find it anywhere so am asking here. (I always hate on other forums when people just jump in with questions before searching.)
I have a 7i92TH connected to a Raspberry Pi 5. The use case for it is for rose engine lathes, and we need to drive a spindle + 7 axes.
The break-out board we are using for both 26-pin outputs from the 7i92TH was developed using the input from Peter. Fundamentally, we will have
mesaflash --device 7i92t --addr 192.168.1.121 --readhmid
the output matches the .pin file supplied by Peter, telling me that the mesaflash --write command worked to load the .bin file supplied by Peter.
When running pncconf:
ISSUE for which I'm seeking help: I can't figure out how the Num items (pin numbers?) match up to the .pin file. What am I missing?
I have a 7i92TH connected to a Raspberry Pi 5. The use case for it is for rose engine lathes, and we need to drive a spindle + 7 axes.
The break-out board we are using for both 26-pin outputs from the 7i92TH was developed using the input from Peter. Fundamentally, we will have
- 8 outputs to drivers, all with Step, Direction, & Enable
- 7+ inputs for limit switches
mesaflash --device 7i92t --addr 192.168.1.121 --readhmid
the output matches the .pin file supplied by Peter, telling me that the mesaflash --write command worked to load the .bin file supplied by Peter.
When running pncconf:
- I've tried with copying the contents of the .pin file into the Input tab on the Help screen, and not doing this.
- I was able to successfully discover the 7i92TH board, and it populated the Output tab on the Help screen (I didn't check word-for-word, but it seems to be duplicate of the output from mesaflash --readhmid).
ISSUE for which I'm seeking help: I can't figure out how the Num items (pin numbers?) match up to the .pin file. What am I missing?
Please Log in or Create an account to join the conversation.
- PCW
- Away
- Moderator
Less
More
- Posts: 17982
- Thank you received: 4832
17 Jan 2025 18:40 #319204
by PCW
Replied by PCW on topic Problems configuring 7i92TH with pncconf
The num items in pncconf are the channel numbers for things like stepgens,
pwmgens, and logical pin number for things like inms, outms. This is how
the actual hardware is addressed in the hal file.
For example, your configuration has 8 stepgens, 4 on each connector
and numbered 0..7. The actual pin assignments are listed in the pinout file
for each of these 8 stepgens.
One exception is GPIO pins which are listed by GPIO number in pncconf.
It probably would be helpful if pncconf added a physical pin column, but note
that physical pin numbers are not used at all in hal files for LinuxCNC configuration
with Mesa cards.
Configuration pin-out:
IO Connections for P2
DB25 pin# I/O Pri. func Sec. func Chan Sec. Pin func Sec. Pin Dir
1 0 IOPort StepGen 0 Step/Table1 (Out)
14 1 IOPort StepGen 0 Dir/Table2 (Out)
2 2 IOPort InM 0 Input0_EncA0 (In)
15 3 IOPort OutM 0 Output0 (Out)
pwmgens, and logical pin number for things like inms, outms. This is how
the actual hardware is addressed in the hal file.
For example, your configuration has 8 stepgens, 4 on each connector
and numbered 0..7. The actual pin assignments are listed in the pinout file
for each of these 8 stepgens.
One exception is GPIO pins which are listed by GPIO number in pncconf.
It probably would be helpful if pncconf added a physical pin column, but note
that physical pin numbers are not used at all in hal files for LinuxCNC configuration
with Mesa cards.
Configuration pin-out:
IO Connections for P2
DB25 pin# I/O Pri. func Sec. func Chan Sec. Pin func Sec. Pin Dir
1 0 IOPort StepGen 0 Step/Table1 (Out)
14 1 IOPort StepGen 0 Dir/Table2 (Out)
2 2 IOPort InM 0 Input0_EncA0 (In)
15 3 IOPort OutM 0 Output0 (Out)
Please Log in or Create an account to join the conversation.
Moderators: cmorley
Time to create page: 0.050 seconds