Gmoccapy 3.5.1

pippin88 wrote:

Suggestion / request:
Overrides
When starting a program running (cycle start): user is prompted that an override (rapid, feed, or spindle) and asked whether they want to continue with override, or want to reset to 100%

I could imagine make an optional warn dialog with a settable limit. For all overrides? Feed, rapid and spindle?

I start the program with an external button.

Well, yes but what hal pin do you use to start the program?
I presume 'halui.program.run'

Aciera wrote:

I start the program with an external button.


Well, yes but what hal pin do you use to start the program?
I presume 'halui.program.run'

Probably. At least I could reproduce it this way.

Probably. At least I could reproduce it this way.

The issue here is that using 'halui' in parallel to a gui is not really a very good idea at all. Many do it, myself included, to connect panel buttons. Gmoccapy is designed to use button rows aligned with the gui buttons but that is not always practical.

I wonder if it would make sense to have gmoccapy create its own dedicated pins like 'halui' so we would have more control over them.

Control panel connections :

net matrix_r2c2 matrix_kb.0.key.r2c2 => halui.spindle.0.stop
net matrix_r2c1 matrix_kb.0.key.r2c1 => halui.spindle.0.forward
net matrix_r2c3 matrix_kb.0.key.r2c3 => halui.spindle.0.reverse

pippin88 wrote:

Suggestion / request:
Overrides
When starting a program running (cycle start): user is prompted that an override (rapid, feed, or spindle) and asked whether they want to continue with override, or want to reset to 100%

HansU wrote:

I could imagine make an optional warn dialog with a settable limit. For all overrides? Feed, rapid and spindle?

Yes, something like attached.



Warning pop up if any override is on.

"Reset to 100%" would not work if you are using analog signals for the overrides.
So it will be only options for proceed and abort.

Overrides are just set via physical up and down buttons, or via GUI in my setup.

New machine will sue encoders to have physical knob.

If easiest, a pop up warning that overrides are set, and buttons to cancel program, or proceed, would be very useful.

Firstly, I have already implemented a solution for checking the tool table . If this seems useful for others, we could consider integrating this function directly into Gmoccapy.


I would also find it useful if there were an additional option available for each tool in the tool table—for example, a checkbox or drop-down menu for the direction of rotation (CW or CCW).  This would make it easy to determine the required direction of rotation for each tool and eliminate errors caused by incorrect rotation.    

besriworld wrote:

Control panel connections :

net matrix_r2c2 matrix_kb.0.key.r2c2 => halui.spindle.0.stop
net matrix_r2c1 matrix_kb.0.key.r2c1 => halui.spindle.0.forward
net matrix_r2c3 matrix_kb.0.key.r2c3 => halui.spindle.0.reverse

Why do you use the halui pin?
you could use  linuxcnc.org/docs/html/gui/gmoccapy.html..._bottom_button_lists

Norbert