Python pendant logic problems

More
1 year 1 month ago #335152 by unknown
I'm probably missing the point, but how are the signals connecting to the internal Linuxcnc signals ?


Look this is an example of a MPG setup using the parallel port but it illustrates some basic routing of hal signals.

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

More
1 year 1 month ago #335338 by rodw
Replied by rodw on topic Python pendant logic problems
When AI reports info from a post of mine on the forum, you know it at best is only superficial.
There is an example in the docs on a mpg using an encoder. It is easy to convert to a Mesa MPG encoder input but I think on the 7i96s you need extra firmware from mesa web site and forgo some I/O pins.

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

More
1 year 1 month ago - 1 year 1 month ago #335344 by PCW
Replied by PCW on topic Python pendant logic problems
On the 7I96S there are 4 MPG channels built in with any standard firmware
These use the isolated inputs 0..7 but do not interfere with normal input use.

The count pins on the isolated I/O are:

hm2_7i96s.0.inm.00.enc0-count
hm2_7i96s.0.inm.00.enc1-count
hm2_7i96s.0.inm.00.enc2-count
hm2_7i96s.0.inm.00.enc3-count

There is also 7I96S firmware that puts MPG encoders on P1:

7i96sd_mpgp1.bin

Its MPG encoder count pins on P1 are:

hm2_7i96s.0.inm.01.enc0-count
hm2_7i96s.0.inm.01.enc1-count
hm2_7i96s.0.inm.01.enc2-count
hm2_7i96s.0.inm.01.enc3-count

These are additional to the MPG inputs available on the isolated I/O

If you are using buttons/MPG on P1, theĀ  7i96sd_mpgp1.bin
is probably the best as it also uses the INM module so has built-in
debounce on all inputs.
Last edit: 1 year 1 month ago by PCW.
The following user(s) said Thank You: unknown

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

More
1 year 1 month ago - 1 year 1 month ago #335509 by andypugh
As a first step, get the encoder counting so that you can see a "counts" pin incrementing when you turn the encoder.
There are a few ways to do this mentioned above, and there is always the possibility of using the software encoder counter too, connected to GPIO pins,

Once you have the counts HAL pin working, that then needs connecting to all the axis (and joint) jog-counts pins. You then wire the switches to set the jog-enable pins of the axes/joints as required,

For the actual pin names see:
linuxcnc.org/docs/stable/html/man/man9/m...n.9.html#AXIS%20PINS

linuxcnc.org/docs/stable/html/man/man9/m....9.html#JOINT%20PINS

And possibly linuxcnc.org/docs/stable/html/man/man1/h...html#Joint%20jogging

But prefer the pins in "motion" to those in "halui" as the former run in realtime and so are more dependable.
Last edit: 1 year 1 month ago by andypugh.

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

Time to create page: 0.068 seconds
Powered by Kunena Forum