Gmoccapy - A new screen for linuxcnc

sliptonic wrote: The Ctrl+space trick is a good workaround but doesn't help running a touchscreen.

Pull up matchbox-keyboard? I just installed it last night specifically for this kind of thing. It's not perfect, but it seems perfectly useful to me.

@sliptonic

OK I do know now, that you run linuxcnc 2.6.2 on Debian Wheezy on a 15 " Touch Screen, correct?

What resolution do you run?

The cutting off of the Gcode and the programm name, could be caused because you use to big font size in the standard settings of XFCE, could you check the settings please.

I do not know why the error message should appear, the messages you show, should only be displayed if you push the corresponding test button on the settings page.

And the should never be shortend or compressed like on your screen.I just tested with 25 messages and did not get the behavior you showed.

According to onboard, I allready took contakt to the development board and got some advices. At the moment you will be forced to build it from source. Chris uses the same keyboard with gscreen, so he proposed making a linuxcnc paket for it. Lets see how the others think about it.

May be some of you do like to check xvkbd, I hope it is a good replacement.



Norbert

Correct. This is a Triview 15" touchscreen at 1024x768. The Wheezy install is stock except but I bumped down the default font from 11 to 10 point and it looks better. The clipped lines are fixed.

I pushed the test button to create those messages for the screenshot but they appear the same way on other errors. At this point, I can live with it. I'll try the other keyboard alternatives though.

Thanks everyone.

In regards to the error messages, how do you configure your own messages? When running Gscreen, I was able to configure 20 or so error messages in the INI file, that would pop up in a dialog box center screen and depending on the type of message I could stop motion, estop the machine, etc but when I switched to gmoccapy I don't see any way to configure these. It is very handy to have these, and operators got used to them,

Thanks

Rick

sliptonic wrote: At this point, I can live with it.

Maybe I can't. I'm testing more thoroughly now and getting strange behavior related to tool change. When I switch to the tool table, select a tool and click the button to change to the selected tool (not the M61 button) it returns to manual mode with all the jog and mode buttons greyed out. Clicking the machine off and on returns control. I never get the dialog box to change the tool.

If I run a program, it just hangs at a line like T3 M06 G43. Again, no dialog.

Thoughts?

sliptonic wrote: If I run a program, it just hangs at a line like T3 M06 G43. Again, no dialog.

Thoughts?

Aren't you missing something on that line?

Zahnrad Kopf wrote:

sliptonic wrote: If I run a program, it just hangs at a line like T3 M06 G43. Again, no dialog.

Thoughts?

Aren't you missing something on that line?

No, that's fine. G43 defaults to the current tool.

My guess is that the system is waiting for the tool change. How is your tool-changer set up? It may be that you have none at all (not even the manual toolchange routine configured)

Sorry. I should have been more clear on that point. This is manual tool change.

Per the gmoccapy wiki I have these three lines in the gmoccapy_postgui.hal file

net tool-change gmoccapy.toolchange-change <= iocontrol.0.tool-change
net tool-changed gmoccapy.toolchange-changed <= iocontrol.0.tool-changed
net tool-prep-number gmoccapy.toolchange-number <= iocontrol.0.tool-prep-number

@Rick,
Let me see if i can implement that, as it isn't at the moment.
But only if you do the documentation on the WIKI:-)

@sliptonic,
Could you please post your config files?
Does the sim config gmoccapy.ini work like expected?

Norbert

sliptonic wrote: If I run a program, it just hangs at a line like T3 M06 G43. Again, no dialog.
Thoughts?

Yes, I had that too. Snippet from my (postgui) HAL file:

# Use gmoccapy toolchanger..
net tool-change gmoccapy.toolchange-change <= iocontrol.0.tool-change
net tool-changed gmoccapy.toolchange-changed <= iocontrol.0.tool-changed
net tool-prep-number gmoccapy.toolchange-number <= iocontrol.0.tool-prep-number
net tool-prepare-loopback iocontrol.0.tool-prepare => iocontrol.0.tool-prepared

The last line is what I added; LinuxCNC is indeed waiting until the tool is prepared but without above line (or more complex logic) that will never happen. This is not gmoccapy specific.