Gmoccapy - A new screen for linuxcnc

balestrino
Offline
New Member

12 years 7 months ago #44294 by balestrino

Replied by balestrino on topic Gmoccapy - A new screen for linuxcnc

thank you Norbert, your work is great!

i'm testing the 1.0 release but i cant jog around any more

Please Log in to join the conversation.

newbynobi
Offline
Platinum Member

12 years 7 months ago #44295 by newbynobi

Replied by newbynobi on topic Gmoccapy - A new screen for linuxcnc

Do you use the jog keys, or the keyboard? If keyboard, check settings page.

Norbert

Please Log in to join the conversation.

balestrino
Offline
New Member

12 years 7 months ago #44298 by balestrino

Replied by balestrino on topic Gmoccapy - A new screen for linuxcnc

keyboard shortcuts are ok but jogging button do nothing

Please Log in to join the conversation.

newbynobi
Offline
Platinum Member

12 years 7 months ago #44299 by newbynobi

Replied by newbynobi on topic Gmoccapy - A new screen for linuxcnc

I am just installing a new machine, so I will be able to test in a few minutes, stay tuned ;-)

Shit, I can reproduce that error.

Norbert

Please Log in to join the conversation.

newbynobi
Offline
Platinum Member

12 years 7 months ago #44300 by newbynobi

Replied by newbynobi on topic Gmoccapy - A new screen for linuxcnc

I found the error, will fix within the next three hours.

Norbert

Please Log in to join the conversation.

newbynobi
Offline
Platinum Member

12 years 7 months ago #44302 by newbynobi

Replied by newbynobi on topic Gmoccapy - A new screen for linuxcnc

Halo balestrino,

solved and pushed!

Please do not forget to do a make after the pull, it is needed now, because we are stand alone, so the changed files must be copied from src/usr_intf/gmoccapy to /bin or lib/gmoccapy or share/gmoccapy and that is what make does.

Norbert

Please Log in to join the conversation.

cmorley
Topic Author
Offline
Platinum Member

12 years 7 months ago #44305 by cmorley

Replied by cmorley on topic Gmoccapy - A new screen for linuxcnc

newbynobi wrote: gmoccapy 1.0 !!

I made it, gmoccapy reached stable state!

The main difference from previous versions is that gmoccapy is now stand alone, completely separated from gscreen.
This has two main reasons:

1. gmoccapy has become so complex, that it is not any more a typical gscreen skin, it is an own application.
2. I got a speed advantage because I do not need as much timers as before.

But take care!
Due to the change, all hal pin has changed their names from gscreen. to gmoccapy. and also the tooloffset pin changed their names.
I did update the WIKI according to the changes, so please read it!

I hope to get now a more easy product for support, because there will be less influence from other code parts and I can put more effort in new features.

I would like to express, that this decision has nothing to do with gscreen and its very good code and features and that this decision is completely conform to Chris opinion. Chris I thank you for gscreen and I will also in the feature have an eye on that, because without gscreen I would never have begone to code gmoccapy.

THANKS CHRIS!

Hope you will support me also in feature!

Norbert

Congrats to you Norbert for Gmoccapy 1.0 - alot of hard work you have put in.

I have enjoyed our work together - you have made Gscreen better and given more choices to the people.
Thanks for the shout out - I am happy I could help you.

Gmoccapy is an excellent screen. - Another step up for linuxcnc.
I am happy you are another official developer of linuxcnc too

Of course I will support you in the future.
Feel free to send idea/opinion my way - we don't have to always agree but ideas thrown about helps create better products.

Chris M

Please Log in to join the conversation.

hobride
Offline
New Member

12 years 7 months ago #44311 by hobride

Replied by hobride on topic Gmoccapy - A new screen for linuxcnc

Hello all,

i have installed the last update from buildbot today.
after that i have trouble with gmoccapy screen.
My ini file contained:

Code:

DISPLAY = gscreen -c gmoccapy -d

this worked for me until the last update.

now, after the update linuxcnc starts with the gscreen and does not show me the gmoccapy screen.

also:

Code:

DISPLAY = gmoccapy

does not works for me:

Code:

Print file information:
RUN_IN_PLACE=no
LINUXCNC_DIR=
LINUXCNC_BIN_DIR=/usr/bin
LINUXCNC_TCL_DIR=/usr/lib/tcltk/linuxcnc
LINUXCNC_SCRIPT_DIR=
LINUXCNC_RTLIB_DIR=/usr/realtime-2.6.32-122-rtai/modules/linuxcnc
LINUXCNC_CONFIG_DIR=
LINUXCNC_LANG_DIR=/usr/share/linuxcnc/tcl/msgs
INIVAR=inivar
HALCMD=halcmd
LINUXCNC_EMCSH=/usr/bin/wish8.5
LINUXCNC - 2.6.0-pre0-5251-g1fda8e6
Machine configuration directory is '/home/cnc/linuxcnc/configs/lcf1'
Machine configuration file is 'lcf1.ini'
INIFILE=/home/cnc/linuxcnc/configs/lcf1/lcf1.ini
PARAMETER_FILE=linuxcnc.var
TASK=milltask
HALUI=halui
DISPLAY=gmoccapy
Starting LinuxCNC...
Starting LinuxCNC server program: linuxcncsvr
Loading Real Time OS, RTAPI, and HAL_LIB modules
Starting LinuxCNC IO program: io
io started
halcmd loadusr io started
Starting HAL User Interface program: halui
Starting TASK program: milltask
task pid=7252
Starting DISPLAY program: gmoccapy
Can't execute DISPLAY program gmoccapy  
Shutting down and cleaning up LinuxCNC...
emcTaskInit: using builtin interpreter
Killing task linuxcncsvr, PID=7198
Killing task milltask, PID=7252
Removing HAL_LIB, RTAPI, and Real Time OS modules
Removing NML shared memory segments
Cleanup done

Debug file information:
7198
  PID TTY      STAT   TIME COMMAND
7252
  PID TTY      STAT   TIME COMMAND
Stopping realtime threads
Unloading hal components

Kernel message information:
[ 2001.034423] I-pipe: Domain RTAI registered.
[ 2001.034429] RTAI[hal]: <3.8.1> mounted over IPIPE-NOTHREADS 2.6-03.
[ 2001.034431] RTAI[hal]: compiled with gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) .
[ 2001.034474] RTAI[hal]: mounted (IPIPE-NOTHREADS, IMMEDIATE (INTERNAL IRQs DISPATCHED), ISOL_CPUS_MASK: 0).
[ 2001.034476] PIPELINE layers:
[ 2001.034478] fbb76e20 9ac15d93 RTAI 200
[ 2001.034480] c085cb20 0 Linux 100
[ 2001.050152] RTAI[malloc]: global heap size = 2097152 bytes, <BSD>.
[ 2001.050290] RTAI[sched]: IMMEDIATE, MP, USER/KERNEL SPACE: <with RTAI OWN KTASKs>, kstacks pool size = 524288 bytes.
[ 2001.050294] RTAI[sched]: hard timer type/freq = APIC/12500368(Hz); default timing: periodic; linear timed lists.
[ 2001.050297] RTAI[sched]: Linux timer freq = 250 (Hz), TimeBase freq = 2700162000 hz.
[ 2001.050299] RTAI[sched]: timer setup = 999 ns, resched latency = 2943 ns.
[ 2001.050369] RTAI[usi]: enabled.
[ 2001.080465] RTAI[math]: loaded.
[ 2001.141751] config string '0xE800 out  '
[ 2003.541097] RTAI[math]: unloaded.
[ 2003.562558] SCHED releases registered named ALIEN RTGLBH
[ 2003.592207] RTAI[malloc]: unloaded.
[ 2003.692016] RTAI[sched]: unloaded (forced hard/soft/hard transitions: traps 0, syscalls 0).
[ 2003.694054] I-pipe: Domain RTAI unregistered.
[ 2003.694105] RTAI[hal]: unmounted.

Please Log in to join the conversation.

mariusl
Offline
Platinum Member

12 years 7 months ago #44312 by mariusl

Replied by mariusl on topic Gmoccapy - A new screen for linuxcnc

The entry for the display should read

DISPLAY = gmoccapy

just change the current line by deleting the gscreen and the -d stuff. Also have a look at the Wiki page for more instructions

If that does not work make sure that you have run ./autogen.sh and ./configure from the /src directory before you do the make..

Regards
Marius

www.bluearccnc.com

Please Log in to join the conversation.

hobride
Offline
New Member

12 years 7 months ago #44317 by hobride

Replied by hobride on topic Gmoccapy - A new screen for linuxcnc

until now I've never compiled linuxcnc or gmoccapy self.
is that now necessary?

Please Log in to join the conversation.

Time to create page: 0.167 seconds