Feature request: rapid and feed override.

tecno wrote: Is this fool-proof in the trajectory planner to issue FRO in running G-code?

Not sure what you mean. Feed Override is _for_ adjustments to running gcode.
The planer will not violate speed and acceleration limits on override adjustments if correctly set up.

Chris M

OK, you all convinced me. I will change max-velocity slider to be rapid-override.

As gmoccapy 2.0 is comming closer, I will indroduce the change with the new version and leave all gmoccapy 1.XX versions unchanged.

Something more you would like to change?
If it was only me, I would change some hal pin names to collegt them in groups, all jog hal pin in a jog group etc, but I am affraid to destroy to much configs with such a change.

Norbert

Hmm, let me think...

- When I try to jog when MDI mode is selected but the machine is idle, I get the EMC_BLABLA error 'cannot do that'. Quite irritating; when positioning I use both MDI to go to known coordinates (e.g. G0 X0Y0 to position the mill in the XY plane) and jogging (to find the Z height for touchoff when I cannot use the probe, for example).

- In settings 'Apearance' is written wrong.

- Clicking on the DRO to change to absolute/DTG mode is irritating; I never do that on purpose, only by accident. Gmoccapy already shows the absolute and DTG numbers. I would like to have a setting to only have one of the relative/absolute/DTG modes displayed, plus homed/not homed.

- Editing the tool table needs some getting used to. You need to check the box in front of the tool you want to edit, click on the field, enter a value, and then you HAVE to press enter otherwise it is not remembered. And then there is the 'apply' button; if you forget to press that one and go to another screen (to see the DRO for example) and back the changes are lost.

- This is more a LinuxCNC than a gmoccapy issue and certainly not something you can solve alone: people visit my place and see a kitted out LinuxCNC installation with probe_screen, features, etc. They see me entering some numbers, mount a block of material, a lot of noise and a few minutes later, presto, bracket is ready.
Now they think 'Wow, great!', they download and install the Wheezy ISO, and are stuck with a very basic Stepconf generated AXIS setup that can only load a file and play it. Every single user has to scrape the components together and integrate them to have a more useful CNC control.
Maybe it is time to integrate a few of these externals. You more or less did that with tool measurement too. Probe-screen is a good candidate, as well as features or ngcgui. That allows people to actually do something with the software after installing. If someone doesn't need it then that tab simply isn't used.

- When I try to jog when MDI mode is selected but the machine is idle, I get the EMC_BLABLA error 'cannot do that'. Quite irritating; when positioning I use both MDI to go to known coordinates (e.g. G0 X0Y0 to position the mill in the XY plane) and jogging (to find the Z height for touchoff when I cannot use the probe, for example).

I hate this behavior from linuxcnc too!, but it is not gmoccapy related. I am a little surprised that you get an error. Do you use the gmoccapy hal pin?

- In settings 'Apearance' is written wrong.

Will correct that and make it "Ausssehen" :whistle:

- Clicking on the DRO to change to absolute/DTG mode is irritating; I never do that on purpose, only by accident. Gmoccapy already shows the absolute and DTG numbers. I would like to have a setting to only have one of the relative/absolute/DTG modes displayed, plus homed/not homed.

Took that to my to do list, to check if I can realize that with a settings switch.

- Editing the tool table needs some getting used to. You need to check the box in front of the tool you want to edit, click on the field, enter a value, and then you HAVE to press enter otherwise it is not remembered. And then there is the 'apply' button; if you forget to press that one and go to another screen (to see the DRO for example) and back the changes are lost.

I do agree 100 % with you, the tool table and tool editing is a mess! I would like to integrate a new "tool editing with moving through the cells with TAB, and add also wear offsets and some more stuff, like small images. Unfortunately, that is some coding work and due to gtk2 it is not as easy as I imagined, Just let me some new stuff for gmoccapy 3.0

Maybe it is time to integrate a few of these externals. You more or less did that with tool measurement too. Probe-screen is a good candidate, as well as features or ngcgui. That allows people to actually do something with the software after installing. If someone doesn't need it then that tab simply isn't used.

Yes, it would be time and linuxcnc-features is on the best way to make it. But we are very far away from a point and Click configuration system. I do not think, that that will ever happen, as linuxcnc offers to much possibilities to include all of them.
So feel free to make a schedule or a little sketch, "How should a beginner linuxcnc config be? We may then make such a sample config as start point and add later a GUI to set more parameters. Begin with the hardware, then the GUI, that the options etc.

Such a detailed documentation would be very helpfull.


Norbert

newbynobi wrote: I hate this behavior from linuxcnc too!, but it is not gmoccapy related. I am a little surprised that you get an error. Do you use the gmoccapy hal pin?

Yes:

..
# MPG buttons to gmoccapy jog
net jog-x-plus xhc-hb04.button-macro3 => gmoccapy.jog-x-plus
net jog-x-minus xhc-hb04.button-macro1 => gmoccapy.jog-x-minus
..
..

It should not be too hard to rig a few HAL-components together that switches from MDI to manual mode when needed. I just did not do it yet.

and make it "Ausssehen" :whistle:

Fine with me!

Just let me some new stuff for gmoccapy 3.0

Do you want us to keep nagging you that long?

Yes, it would be time and linuxcnc-features is on the best way to make it. But we are very far away from a point and Click configuration system. I do not think, that that will ever happen, as linuxcnc offers to much possibilities to include all of them.

Maybe it is not a gmoccapy thing, but more a stepconf/pncconf thing. Once you do not need those anymore you are probably capable enough to spice up your configuration to your liking. The problem is the beginner that uses stepconf.

So feel free to make a schedule or a little sketch, "How should a beginner linuxcnc config be? We may then make such a sample config as start point and add later a GUI to set more parameters. Begin with the hardware, then the GUI, that the options etc.

Hmm. Hardware is easy; 'everybody' starts with stepconf or pncconf, so imho that part is covered.
But once stepconf is finished, you would like to actually do something with the software, and that is not really possible. You cannot mill a single hole or turn the outside of a piece of stock to diameter. Most other software has wizards for simple tasks.

So what would I prefer? Something like linuxcnc-features (or ngcgui; that's already in the distribution) and probe_screen integrated in a few tabs. There is no reason why 'user tabs' should be user tabs only, and if somebody does not use it they are not in the way either.

But the more I think about it, the more I think it is really a stepconf/pncconf issue.

I hate this behavior from linuxcnc too!, but it is not gmoccapy related. I am a little surprised that you get an error. Do you use the gmoccapy hal pin?

Yes:

..
# MPG buttons to gmoccapy jog
net jog-x-plus xhc-hb04.button-macro3 => gmoccapy.jog-x-plus
net jog-x-minus xhc-hb04.button-macro1 => gmoccapy.jog-x-minus
..
..

I got the bug, it is caused when releasing the button, I missed to check for Manual Mode, will correct that.
And I will try to allow Jogging in MDI Mode, but that could cause some deeper changes.

Norbert