MVO to RO

More
10 months 1 week ago #340251 by gravedigger
MVO to RO was created by gravedigger
I've spent several hours trying to get rapid override working. I happened to read about the change in the designation from MVO to RO. The Mesa Config program doesn't recognize this yet.
Then I noticed that the manual has the wrong name.
Instead of rapid.rapid-override, it should be rapid-override.
I have now entered the following manually and it finally seems to be working.

# ---max Geschwindigkeit Neufestsetzungs-Signale an Mesa Encoder - mpg (rapid override signals to mesa encoder - mpg)---

net ro-count     <=  [HMOT](CARD0).7i73.0.0.enc3.count

# verbinde max Geschwindigkeit Neufestetzung Inkrement - MPG (connect rapid override increments - MPG)

    setp halui.rapid-override.direct-value false
    setp halui.rapid-override.scale 0.01
    setp halui.rapid-override.count-enable true
net ro-count            =>  halui.rapid-override.counts

Please Log in to join the conversation.

More
10 months 1 week ago #340252 by gravedigger
Replied by gravedigger on topic MVO to RO
I was very close to replacing the Linux CNC with a different system.
The small inaccuracies make it very difficult for a newcomer.

Please Log in to join the conversation.

More
10 months 1 week ago #340258 by tommylight
Replied by tommylight on topic MVO to RO
What inaccuracies? In the documentation?

Please Log in to join the conversation.

More
10 months 1 week ago #340264 by PCW
Replied by PCW on topic MVO to RO
Instead of rapid.rapid-override, it should be rapid-override.

What manual is this in and what LinuxCNC verison?

(the current halui man page does not have this error)

Please Log in to join the conversation.

More
10 months 1 week ago #340265 by rodw
Replied by rodw on topic MVO to RO
Its really important to read the instructions for the version of LInuxcnc you are using. Often a Google search will display dated info

Please Log in to join the conversation.

More
10 months 1 week ago #340266 by gravedigger

Please Log in to join the conversation.

More
10 months 1 week ago #340267 by gravedigger
Replied by gravedigger on topic MVO to RO
To connect encoders, the following pins are exported:

gmoccapy.jog.jog-velocity.counts (s32 IN) - Jog velocity

gmoccapy.jog.jog-velocity.count-enable (bit IN) - Must be True, to enable counts

gmoccapy.feed.feed-override.counts (s32 IN) - feed override

gmoccapy.feed.feed-override.count-enable (bit IN) - Must be True, to enable counts

gmoccapy.feed.reset-feed-override (bit IN) - reset the feed override to *0%

gmoccapy.spindle.spindle-override.counts (s32 IN) - spindle override

gmoccapy.spindle.spindle-override.count-enable (bit IN) - Must be True, to enable counts

gmoccapy.spindle.reset-spindle-override (bit IN) - reset the spindle override to *0%

gmoccapy.rapid.rapid-override.counts (s32 IN) - Maximal Velocity of the *chine

gmoccapy.rapid.rapid-override.count-enable (bit IN) - Must be True, to enable counts

Please Log in to join the conversation.

More
10 months 1 week ago #340272 by Aciera
Replied by Aciera on topic MVO to RO
Seems you are looking at 'gmoccapy' documentation for using 'halui' pins.

Halui documentation is here:
linuxcnc.org/docs/html/man/man1/halui.1.html#Rapid%20Override

However you should really be using the pins provided by gmoccapy for this purpose.
If unsure comment all lines in your hal files that give errors and use the 'Halshow' tool on the Settings page of Gmoccpy.
Using 2.9.7 I get this (which seems to agree with the documentation for Gmoccapy):
 

Attachment not found

Please Log in to join the conversation.

More
10 months 1 week ago #340273 by rodw

Please Log in to join the conversation.

Time to create page: 0.100 seconds
Powered by Kunena Forum