Re: [Machinekit] Re: Machinekit not starting after compilation

2017-05-25 Thread schoone...@btinternet.com
On 24/05/17 16:40, michelvanderbregge...@gmail.com wrote: Can anybody tell me against which version of libprotobuf-dev and libprotoc-dev I should build machinekit? libprotobuf > 2.4.0. libprotoc the same Jessie is currently

Re: [Machinekit] Re: Machinekit not starting after compilation

2017-05-24 Thread michelvanderbreggen21
Can anybody tell me against which version of libprotobuf-dev and libprotoc-dev I should build machinekit? Op woensdag 24 mei 2017 13:51:15 UTC+2 schreef michelvand...@gmail.com: > > Sorry, > I know this is getting a long thread. > > It seems as if the rtapi_app is unable to connect to shared

Re: [Machinekit] Re: Machinekit not starting after compilation

2017-05-24 Thread michelvanderbreggen21
Sorry, I know this is getting a long thread. It seems as if the rtapi_app is unable to connect to shared memory. When I start the app standalone, the following appears in the syslog *rtapi:0: rtapi_app:0 ERROR: cannot attach glocal segment key=0x154711 No such file or directory* Op

Re: [Machinekit] Re: Machinekit not starting after compilation

2017-05-24 Thread michelvanderbreggen21
How do I prevent the build-script from building a RIP version? It seems that it does this automaticly Op woensdag 24 mei 2017 13:12:33 UTC+2 schreef Schooner: > > > > On 24/05/17 11:36, michelvand...@gmail.com wrote: > > Strange thing is that the same config file works when I start it with the

Re: [Machinekit] Re: Machinekit not starting after compilation

2017-05-24 Thread michelvanderbreggen21
Strange thing is that the same config file works when I start it with the prebuild machinekit on the same machine. It looks like the rtapi_app fails, or is unresponsive for some reason Op woensdag 24 mei 2017 11:44:45 UTC+2 schreef Schooner: > > It is saying it cannot find the section

Re: [Machinekit] Re: Machinekit not starting after compilation

2017-05-24 Thread michelvanderbreggen21
Hello Bas, what I noticed when I looked in /var/log/linuxcnc.log is the following May 24 09:19:22 beaglebone msgd:0: startup pid=2533 flavor=xenomai rtlevel=1 usrlevel=1 halsize=524288 shm=Posix cc=gcc 4.9.2 version=unknown May 24 09:19:22 beaglebone msgd:0: ØMQ=4.0.5 czmq=3.0.2 protobuf=3.2.0

Re: [Machinekit] Re: Machinekit not starting after compilation

2017-05-24 Thread Bas de Bruijn
If you search this string on the google group a few similar threads show up. If you’re not running as root, then perhaps this link may help.

Re: [Machinekit] Re: Machinekit not starting after compilation

2017-05-24 Thread schooner30
It is saying it cannot find the section [DISPLAY] INTRO_GRAPHIC can't say further without your .ini file You should not need INTRO_GRAPHIC or INTRO_TIME, but if you do have them what they point to must be valid On 24/05/17 10:32, michelvanderbregge...@gmail.com wrote: Can not find -sec

[Machinekit] Re: Machinekit not starting after compilation

2017-05-24 Thread michelvanderbreggen21
I also found the following information in the print and debug files *machinekit@beaglebone:~$ cat /tmp/linuxcnc.debug* Can not find -sec DISPLAY -var INTRO_GRAPHIC -num 1 2511 PID TTY STAT TIME COMMAND Stopping realtime threads Unloading hal components *machinekit@beaglebone:~$ cat