Gmoccapy - A new screen for linuxcnc

Hi
Look in the INI file under the [TRAJ] section you will find and entry MAX_LINEAR_VELOCITY = xxx. Change that entry to MAX_VELOCITY = xxx

As for the messages, what config are you running?

norbert,

is it possible perhaps to seperate error messages to it's own frame or window , so closing the window would close all errors

just a thought

dave

Dave
CRTL + SPACE closes all messages.

P.S.
There are also some error handling hal pins in gmoccapy now. Not sure how it works but check the wiki for some info. Also some posts earlier on

mariusl wrote: Hi
Look in the INI file under the [TRAJ] section you will find and entry MAX_LINEAR_VELOCITY = xxx. Change that entry to MAX_VELOCITY = xxx

As for the messages, what config are you running?

Awesome. I'd commented out MAX_LINEAR_VELOCITY but not replaced it. I thought I'd recalled something about that error but couldn't find it in the thread. Maybe we need a troubleshooting or FAQ section on the wiki.

My config is based on the default sim config but modified quite a bit for my mill. I've been running it for 6 months and just upgraded linuxcnc and the machine it runs on. Now running debian so also affected by the lack of onboard.

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

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