Gmoccapy - A new screen for linuxcnc

Hallo Marius,

please describe in Detail, how I can reproduce that.

Norbert

Hi Norbert

What I do is to start with I home the X axis of my machine. The Z has no home switch. Then I do a tool offset edit. It would seem to happen after I tired to edit a tool. The editor jumps out of edit mode once you press return. After that the if I select MDI, the button comes on but the jogging controls remain in place as if the machine is still in manual mode.

Hi Norbert,
In Gmoccapy, large g-code program is dynamically loaded into the window and scroll slider is impossible to estimate how much has already been done.
Is it possible to make indicator of the accomplished part of large g-code programm?

Hallo Marius,

Hi Norbert

What I do is to start with I home the X axis of my machine. The Z has no home switch. Then I do a tool offset edit. It would seem to happen after I tired to edit a tool. The editor jumps out of edit mode once you press return. After that the if I select MDI, the button comes on but the jogging controls remain in place as if the machine is still in manual mode.

I am not able to reproduce that!

I switch on the machine, Estop reste, machine on
I go to home
I do home only X
I go back to manual page clicking the back arrow,
I push the tool button
I click in the tool table and edit a x value,

All is OK!

What are you doing?

Norbert

Norbert
I am not too sure about how it happens. Maybe the use of pyngcgui has something to do with that. I have a feeling that if a subroutine is interrupted before finishing that there might be some codes still active or the MDI mode cannot be entered. The PYNGCGUI stuff puts the system into auto mode in order to load the gcode that was generated. Maybe something there.

I have not used PYNGCGUI for a while as I am trying to setup tool tables and offsets for now. The tool editor and offset editor is a huge pain when it does not stay in the editor.

Leave it for now and once I have the lathe running properly I will investigate to see how to reproduce the error again. It happened many times during my testing of the PYNGCGUI stuff.

I have Andy's LatheMacro and PYNGCGUI running very well in the Gscreen setup. So now I have a reference to work from to get Gmoccapy going.

I have to add a proper jog wheel and a selector plus the spindle encoder. After that is done I will test again.

I have to add a proper jog wheel and a selector plus the spindle encoder. After that is done I will test again.

Please do not forget the Z home Switch

Norbert

Ha ha, yes but I have done that already

I am going to take a break for a number of days to do some resting and some fly fishing and when I get back the lathe must get finished as I have some work for it.

Next after that is the tool changer.

Hello.

I am check last pre4. Ferror no more.

Gmoccapy - it same 1.5.3.


But now it work perfecly without error.

verser wrote:

Hi Norbert,
In Gmoccapy, large g-code program is dynamically loaded into the window and scroll slider is impossible to estimate how much has already been done.
Is it possible to make indicator of the accomplished part of large g-code programm?

Meanwhile made ​​such an indicator as an addendum to Gmoccapy


replace txt with rar
Unrar to ~/linuxcnc-dev/configs/sim/gmoccapy/
Add to [Display] section of ~/linuxcnc-dev/configs/sim/gmoccapy/gmoccapy-your-machine.iniget here is

had to use one timer, although it can be excluded, but then you have to make changes in gmoccapy.py ,
maybe Norbert will do it