search

gaged / moccagui

Automatically exported from code.google.com/p/moccagui
0 stars 1 forks source link

Mocca auf Ubuntu 10.04 mit EMC 2.5.1 #49

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Hi,

ich habe mocca installiert und in der ini-Datei eingetragen, aber beim Start 
vom EMC erhalte ich folgenden Fehler:

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.5.1
Machine configuration directory is '/home/ralph/linuxcnc/configs/XYUV'
Machine configuration file is 'hotwinch.ini'
INIFILE=/home/ralph/linuxcnc/configs/XYUV/hotwinch.ini
PARAMETER_FILE=emc.var
TASK=milltask
HALUI=halui
DISPLAY=mocca
Starting LinuxCNC...
Starting LinuxCNC server program: linuxcncsvr
Loading Real Time OS, RTAPI, and HAL_LIB modules
Starting LinuxCNC IO program: io
emc/iotask/ioControl.cc 751: can't load tool table.
Starting HAL User Interface program: halui
Starting TASK program: milltask
Starting DISPLAY program: mocca
Shutting down and cleaning up LinuxCNC...
Killing task linuxcncsvr, PID=2596
Killing task milltask, PID=2670
Removing HAL_LIB, RTAPI, and Real Time OS modules
Removing NML shared memory segments
Cleanup done

Debug file information:
Can not find -sec MOT -var MOT -num 1 
Can not find -sec IO -var IO -num 1 
Can not find -sec LINUXCNC -var NML_FILE -num 1 
Can not find -sec EMC -var NML_FILE -num 1 
mocca: error while loading shared libraries: libemcini.so.0: cannot open shared 
object file: No such file or directory
2596
  PID TTY      STAT   TIME COMMAND
2670
  PID TTY      STAT   TIME COMMAND
Stopping realtime threads
Unloading hal components

Kernel message information:
[ 4058.455743] I-pipe: Domain RTAI registered.
[ 4058.455756] RTAI[hal]: <3.8.1> mounted over IPIPE-NOTHREADS 2.6-03.
[ 4058.455761] RTAI[hal]: compiled with gcc version 4.4.3 (Ubuntu 
4.4.3-4ubuntu5) .
[ 4058.455827] RTAI[hal]: mounted (IPIPE-NOTHREADS, IMMEDIATE (INTERNAL IRQs 
DISPATCHED), ISOL_CPUS_MASK: 0).
[ 4058.455833] PIPELINE layers:
[ 4058.455839] f9f33e20 9ac15d93 RTAI 200
[ 4058.455845] c085cb20 0 Linux 100
[ 4058.482131] RTAI[malloc]: global heap size = 2097152 bytes, <BSD>.
[ 4058.482374] RTAI[sched]: IMMEDIATE, MP, USER/KERNEL SPACE: <with RTAI OWN 
KTASKs>, kstacks pool size = 524288 bytes.
[ 4058.482382] RTAI[sched]: hard timer type/freq = APIC/12502108(Hz); default 
timing: periodic; linear timed lists.
[ 4058.482388] RTAI[sched]: Linux timer freq = 250 (Hz), TimeBase freq = 
3000454000 hz.
[ 4058.482391] RTAI[sched]: timer setup = 999 ns, resched latency = 2943 ns.
[ 4058.482611] RTAI[usi]: enabled.
[ 4058.559263] RTAI[math]: loaded.
[ 4058.668169] config string '0x378'
[ 4059.294323] RTAI[math]: unloaded.
[ 4059.340521] SCHED releases registered named ALIEN RTGLBH
[ 4059.372365] RTAI[malloc]: unloaded.
[ 4059.472020] RTAI[sched]: unloaded (forced hard/soft/hard transitions: traps 
0, syscalls 0).
[ 4059.476195] I-pipe: Domain RTAI unregistered.
[ 4059.476275] RTAI[hal]: unmounted.

ch hab mich sofort auf die Suche nach der libemcini.so.0 gemacht, alles was ich 
finden konnte war jedoch die libemcini.so und die libemchal.so beide 
Verknüpfungen waren fehlerhaft die libemchal.so ließ sich auf die 
liblinuxcnchal.so verknüpfen, bei der libemcini.so bin ich ebenso verfahren.
Leider hat es nix genützt, nachem ich mit meinen bescheidenen Linuxkenntnissen 
jetzt am Ende bin, suche ich hier malHilfe.

Viele Grüße
Ralph

ubuntu version: 10.04
mocca version: (binary/source)
emc2 vesion:    2.5.1
widget kit: gtk, gtk2, qt

Sonstiges:
Other:

Original issue reported on code.google.com by ralph.ei...@googlemail.com on 18 Oct 2012 at 9:54

GoogleCodeExporter commented 9 years ago

Original comment by benjamin...@gmx.de on 6 Dec 2012 at 10:00

GoogleCodeExporter commented 9 years ago 
Spätestens mit der Version 0.2.4 müsste das Problem jetzt behoben sein.

------

With versions 0.2.4 or newer, this problem should not occur any more

Original comment by benjamin...@gmx.de on 17 Feb 2013 at 10:11