Gmoccapy - A new screen for linuxcnc

DaBit,

The button is located on the edit button list.

Go to auto mode, then press edit, now you should see the reload button, as only here it make sence.

Norbert

newbynobi wrote: DaBit,
The button is located on the edit button list.
Go to auto mode, then press edit, now you should see the reload button, as only here it make sence.

Hi Norbert,

The one wirh description 'Save, reload and run' I assume? That one is quite useless imho; after changing things I prefer to inspect the preview first before hitting the big blue play button and often the changes are not made from within gmoccapy. I might have run a CAM program again because actual stock available is a bit different from what I chose initially, for example.

I'll see if I can replace the 'machine optional blocks' button with a VCP Action Reload myself.

Another thing: I am seeing gmoccapy change back from G59 used in a program to G54 when that program is finished. Costed me a center drill yesterday. Is that expected behaviour?
(I did not compare to AXIS)

DaBit wrote: Another thing: I am seeing gmoccapy change back from G59 used in a program to G54 when that program is finished. Costed me a center drill yesterday. Is that expected behaviour?
(I did not compare to AXIS)

I concur. It would seem that gmoccapy does not keep the the fixture that was selected either during a program or manually. If you select say G55 and do your touchoff and cut an MDI sequence, it will return to G54 every time. Now you want to repeat the sequence then the offsets are incorrect as the controller is now in G54 resulting in a destroyed tool

I have not used my lathe since I finished it due to the fact that the tool changer is not done yet so the problem was not reported. I also scanned the code at the time and I did see a place where to fix it but that was a while ago and I cannot remember.

What happens if you end your program with just a % instead of an M2 or M30?

@DaBit,

Not the save and run button, there should be a reload button on the left, or you use an old release.
If you change a program outside of gmoccapy, you should use the open file button and just load it again.

The only reason to reload a program is, if you did changes and before saving it you feel the change you did was wrong. There is no other reason i see. If a file has been changed, just do open it again!

G54/G55
If you do read the doumentation of M2 M30 etc. You will see, that this commands do reset the coordinate system to default G54. Axis should react exactly as gmoccapy do. A good coded program should begin with a call to the used system, so there should not be a problem. If you want to mantain the cloordinate system, you should begin and finish with '%‘.

If you use MDI commands, the selected system should not change after a move.
But if you do use macros, they should not end with M2, as thid are normal g code.

Marius, please give an example to test.

Norbert

Amazing GUI, thank you for all of the hard work. I am not a programmer by any means, but I'm learning bits here and there. I made my own glade tab, and got it into Gmoccapy by adding the 3 lines to my INI file, my question is, how to I access the signals any widgets (buttons, LED, etc) I might add to my glade file? For instance, I have a custom HALoutput pin for PSI on my application, and I would like to display that in my custom tab, how would I go about doing so? Thanks for any help.