How do PnCConf's Mesa Card 0 I/O tabs' pin numbers correspond to stepconf's?

More
4 years 1 month ago #251104 by PCW
A couple notes:

1. Mesa hal files only use GPIO numbers, _never_ pin numbers.

2. Pins with secondary input function are still available
as inputs even if the secondary function is enabled
(so you could still use GPIO 14,15,16 as inputs with
the encoder enabled)

Please Log in or Create an account to join the conversation.

More
4 years 1 month ago #251163 by clunc

A couple notes:

1. Mesa hal files only use GPIO numbers, _never_ pin numbers.
Okay, but that means I still don't grasp how to get DB25/P3 pin numbers out of the hal file.

2. Pins with secondary input function are still available
as inputs even if the secondary function is enabled
(so you could still use GPIO 14,15,16 as inputs with
the encoder enabled)

I am not able to imagine a setup that would need this--BUT I think I've documented that I am not imaginative.

Please Log in or Create an account to join the conversation.

More
4 years 1 month ago - 4 years 1 month ago #251164 by clunc
(Slowing down, taking a breath... reading what I wrote.)

...I still don't grasp how to get DB25/P3 pin numbers out of the hal file.

Not true.

The .pin file (and output of mesaflash --readhmid --device 5i25) show the correlation between DB25 pin# and GPIO#; I just mis-edited the .hal file assuming that I was changing DB25 pin#s when I was really changing GPIO#.

So, I need to edit the .hal again to correct my misunderstanding.

Now, I have it!

[EDIT: I've gone back to edit my summary post to include Peter's correction.]
[EDIT: I've edited this post to complain about the forum-software's pernicious "auto-formatting 'feature'" that arbirtrarily corrupts existing format when Edit Post is selecting, requiring considerable effort to put-it-back-the-way-it-was.]
Last edit: 4 years 1 month ago by clunc.

Please Log in or Create an account to join the conversation.

More
4 years 1 month ago #251274 by clunc
When linuxcnc is run from a console terminal, the pinouts of the Mesa card appear in the listing; for example in my case:
--clip--
hm2/hm2_5i25.0: IO Pin 000 (P3-01): PWMGen #0, pin Out0 (PWM or Up) (Output)
hm2/hm2_5i25.0: IO Pin 001 (P3-14): IOPort
hm2/hm2_5i25.0: IO Pin 002 (P3-02): StepGen #0, pin Step (Output)
hm2/hm2_5i25.0: IO Pin 003 (P3-15): IOPort
hm2/hm2_5i25.0: IO Pin 004 (P3-03): StepGen #0, pin Direction (Output)
hm2/hm2_5i25.0: IO Pin 005 (P3-16): IOPort
hm2/hm2_5i25.0: IO Pin 006 (P3-04): StepGen #1, pin Step (Output)
hm2/hm2_5i25.0: IO Pin 007 (P3-17): IOPort
hm2/hm2_5i25.0: IO Pin 008 (P3-05): StepGen #1, pin Direction (Output)
hm2/hm2_5i25.0: IO Pin 009 (P3-06): StepGen #2, pin Step (Output)
hm2/hm2_5i25.0: IO Pin 010 (P3-07): StepGen #2, pin Direction (Output)
hm2/hm2_5i25.0: IO Pin 011 (P3-08): StepGen #3, pin Step (Output)
hm2/hm2_5i25.0: IO Pin 012 (P3-09): StepGen #3, pin Direction (Output)
hm2/hm2_5i25.0: IO Pin 013 (P3-10): IOPort
hm2/hm2_5i25.0: IO Pin 014 (P3-11): IOPort
hm2/hm2_5i25.0: IO Pin 015 (P3-12): IOPort
hm2/hm2_5i25.0: IO Pin 016 (P3-13): IOPort
--/clip--

Please Log in or Create an account to join the conversation.

Moderators: cmorley
Time to create page: 0.328 seconds
Powered by Kunena Forum