Gmoccapy - A new screen for linuxcnc

However sometimes i need to temporarily limit the max velocity (without editing the ini file): for example when my mill runs for a long time, one axis tends to get blocked at high speeds. I know that it means that i really need to fix the mill and i'm working on it, but in the meantime i'm simply using the max velocity slider to keep it from reaching too high speeds.

It is possible to split again the max velocity and the feed, but I realy do not know if that makes sense? It would be possible to reduce the max vel to 1000 mm/min and have a feed of 1500 mm/min. So this is not logic in my opinion. Why not using the gmoccapy.max-velocity.direct-value hal pin?

5.2. Velocities and overrides

All sliders from gmoccapy can be connected to hardware encoders or potmeters.

To connect hardware encoderas the following hal pins are exported:

gmoccapy.max-vel-counts (Maximal Velocity of the machine)
gmoccapy.jog-speed-counts (Jog velocity)
gmoccapy.spindle-override-counts (spindle override)
gmoccapy.feed-override-counts (feed override)
gmoccapy.reset-feed-override (reset the feed override to 100 %)
gmoccapy.reset-spindle-override (reset the spindle override to 100 %)

If you prefer potmeters to control the sliders you will need to connect to the following pin

gmoccapy.analog-enable HAL.BIT (must be True to activate the analog inputs)
gmoccapy.spindle-override-value HAL.FLOAT
gmoccapy.max-vel-value HAL.FLOAT
gmoccapy.jog-speed-value HAL.FLOAT
gmoccapy.feed-override-value HAL.FLOAT

all four taking a float input as percentage, meaning a value from 0.0 to 1.0, setting the corresponding sliders directly to the given value.

i.e. spindle override slider has min of 30 % and max 150 % and you set gmoccapy.spindle-override-value to 0.25 the slider will jump to 60 % , as the result of min + (max-min) * pin.value

if gmoccapy.analog.enable = True, the counts are handled as well, so please be careful if you connect to both pin types
It is strongly recommended not to mix both types for the same slider!

Would that be a solution for your personal problem?

Norbert

@ssalrin,

I do have plans to include such a probing page, but because of leak of time I did not begin yet.
The image from Mach3 does IMHO contain to much information. I would prefer a page with the probing button on the left side and some input pages on the right, only showing the relevant information, may be even with a small image.

If you want to do the first steps, please make the corresponding button Icon and send them with a GPL license.
Make a first design of how it should look, a small basic documentation. And we do need the corresponding ngc-code.

I will check how difficult it would be to integrate linuxcnc-features in gmoccapy. I do thing linuxcnc-features should be a part of linuxcnc and should standard for 2.7 release.

I will ask Mick about his opinion.

Norbert

I will check how difficult it would be to integrate linuxcnc-features in gmoccapy. I do thing linuxcnc-features should be a part of linuxcnc and should standard for 2.7 release.

I will ask Mick about his opinion.

Norbert
If we can get the linuxcnc-features into Gmoccapy then maybe it is all we need for now. I saw today on the Russian forum that someone has built it into Gmoccapy but I cannot see how as my Russian is non-existent


I agree the Mach screen has to much info but the probing functions is what we need to look at. I just posted that to show some example.

ssalrin wrote: Sounds like a probing tab that incorporates in to any of the interfaces would be the perfect platform to indulge your "scalable button" distraction :whistle: Mariusl said he'd help.

Rather than pollute this (huge) thread:

www.linuxcnc.org/index.php/english/forum...ic-probing-tab#57327

newbynobi wrote: @ssalrin,

I do have plans to include such a probing page, but because of leak of time I did not begin yet.
The image from Mach3 does IMHO contain to much information. I would prefer a page with the probing button on the left side and some input pages on the right, only showing the relevant information, may be even with a small image.

If you want to do the first steps, please make the corresponding button Icon and send them with a GPL license.
Make a first design of how it should look, a small basic documentation. And we do need the corresponding ngc-code.

I will check how difficult it would be to integrate linuxcnc-features in gmoccapy. I do thing linuxcnc-features should be a part of linuxcnc and should standard for 2.7 release.

I will ask Mick about his opinion.

Norbert

Norbert,

With what little I can comprehend of linuxcnc-features thus far, I agree, it would be a compliment to an already outstanding interface you have created. I do not even have my machine yet, and was dreading getting back into linux after many years. Then I found your work, and all the wonderful supportive people, a community if you will. Now I find myself looking forward to becoming a contributing member. Thank you for being a part of that.
I'm afraid I know very little, but I do have a smattering of a graphic background. I'll be glad to see what I can do about buttons, if you really think I'd be of help. I'll do what I'll I can.

Scott

@Scott,

just make the ICOn and a very basic layout, I will try to do the rest

Norbert