CRAMPS BBB Seg fault: USRMOT: ERROR: command timeout , emcMotionInit: ini_hal_init fail

[Michael Brown]

I have been unable to run my updated package(wheezy) configuration since yesterday.
I updated the config files to the latest inst component reference examples online.

The errors I receive are lots of:
USRMOT: ERROR: command timeout
USRMOT: ERROR: command timeout
USRMOT: ERROR: command timeout
USRMOT: ERROR: command timeout
emcMotionInit: ini_hal_init fail

linuxcnc.log says something about an seg fault:

May 30 18:59:00 bbbx msgd:0: rtapi_app:2060:user pid=2060 flavor=xenomai gcc=4.6.3 git=git not installed at configure time
May 30 18:59:00 bbbx msgd:0: ulapi:2089:user hal_xinit:239 HAL: hal_lib2089 initialization complete
May 30 18:59:00 bbbx msgd:0: hal_lib:2089:user hal_xinit:246 HAL: legacy component 'halcmd2089' id=1876 initialized
May 30 18:59:00 bbbx msgd:0: hal_lib:2089:user hal_start_threads:291 HAL: starting threads
May 30 18:59:00 bbbx msgd:0: rtapi_app:2060:user signal 11 - 'Segmentation fault' received, dumping core (current dir=/home/machinekit/CRAMPS2/configs/ARM/Beaglebone/MibRapX)

 

May 30 18:59:00 bbbx msgd:0: rtapi_app:2060:user (backtrace not available - libbacktrace not found during build)
May 30 18:59:00 bbbx msgd:0: hal_lib:2089:user hal_exit:258 HAL: removing component 1876
May 30 18:59:00 bbbx msgd:0: hal_lib:2089:user hal_exit:258 HAL: removing component 1875
May 30 18:59:00 bbbx msgd:0: hal_lib:2089:user ULAPI:0 git not installed at configure time exit

Do I need to change the linuxcnc launch in run.py ?

I also do not understand the git not installed messages ? (git is installed on my BBB)


Links to Console output, linuxcnc.log and cramps  configuration Attached:

Console output

linuxcnc.log

https://github.com/the-snowwhite/CRAMPS2/tree/master/configs/ARM/Beaglebone/MibRapX

Best wishes
Thanks

[Michael Brown]

Updated packages again today, still no change
Then
Thought I would try running linuxcnc standard axis config  instead
This however also failed with following messages:

__________________

machinekit@bbbx:~$ linuxcnc
MACHINEKIT - 0.1
Machine configuration directory is '/home/machinekit/machinekit/configs/ARM.BeagleBone.CRAMPS'
Machine configuration file is 'CRAMPS.ini'
Starting Machinekit...
io started
halcmd loadusr io started
cape-universal overlay found
cape-bone-iio overlay found
task pid=4291
emcTaskInit: using builtin interpreter
X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  155 (GLX)
  Minor opcode of failed request:  3 (X_GLXCreateContext)
  Value in failed request:  0x0
  Serial number of failed request:  742
  Current serial number in output stream:  743
Shutting down and cleaning up Machinekit...
exiting HAL component Therm
Cleanup done
machinekit@bbbx:~$ cat /var/log/linuxcnc.log
 
May 31 19:50:46 bbbx msgd:0: startup pid=3882 flavor=xenomai rtlevel=1 usrlevel=1 halsize=524288 shm=Posix gcc=4.6.3 version=git not installed at configure time
May 31 19:50:46 bbbx msgd:0: ØMQ=4.0.4 czmq=2.2.0 protobuf=2.4.1
May 31 19:50:46 bbbx msgd:0: configured: sha=git not installed or executable
May 31 19:50:46 bbbx msgd:0: built:      May 31 2015 12:38:35 sha=git not installed or executable
May 31 19:50:46 bbbx msgd:0: register_stuff: actual hostname as announced by avahi='bbbx.local'
May 31 19:50:46 bbbx msgd:0: zeroconf: registering: 'Log service on bbbx.local pid 3882'
May 31 19:50:46 bbbx msgd:0: rtapi_app:3887:user accepting commands at ipc:///tmp/0.rtapi.a42c8c6b-4025-4f83-ba28-dad21114744a
May 31 19:50:47 bbbx msgd:0: zeroconf: registered 'Log service on bbbx.local pid 3882' _machinekit._tcp 49152 TXT "uuid=a42c8c6b-4025-4f83-ba28-dad21114744a" "instance=9098ee82-07bd-11e5-b62a-544a16bfaedd" "service=log" "dsn=tcp://bbbx.local:49152"
May 31 19:50:52 bbbx msgd:0: hal_lib:3887:rt memmapped gpio port 2 to 0xb53c3000, oe: 0xb53c3134, set: 0xb53c3194, clr: 0xb53c3190
May 31 19:50:52 bbbx msgd:0: hal_lib:3887:rt pin 7 maps to pin 2-2, mode 85
May 31 19:50:52 bbbx msgd:0: hal_lib:3887:rt pin 8 maps to pin 2-3, mode 85
May 31 19:50:52 bbbx msgd:0: hal_lib:3887:rt pin 9 maps to pin 2-5, mode 85
May 31 19:50:52 bbbx msgd:0: hal_lib:3887:rt pin 10 maps to pin 2-4, mode 85
May 31 19:50:52 bbbx msgd:0: hal_lib:3887:rt memmapped gpio port 0 to 0xb53c1000, oe: 0xb53c1134, set: 0xb53c1194, clr: 0xb53c1190
May 31 19:50:52 bbbx msgd:0: hal_lib:3887:rt pin 17 maps to pin 0-27, mode 85
May 31 19:50:52 bbbx msgd:0: hal_lib:3887:rt pin 11 maps to pin 0-30, mode 85
May 31 19:50:52 bbbx msgd:0: hal_lib:3887:rt pin 13 maps to pin 0-31, mode 85
May 31 19:50:52 bbbx msgd:0: hal_lib:3887:rt memmapped gpio port 1 to 0xb53bf000, oe: 0xb53bf134, set: 0xb53bf194, clr: 0xb53bf190
May 31 19:50:52 bbbx msgd:0: hal_lib:3887:rt memmapped gpio port 3 to 0xb53bd000, oe: 0xb53bd134, set: 0xb53bd194, clr: 0xb53bd190
May 31 19:50:52 bbbx msgd:0: hal_lib:3887:rt prussdrv_init
May 31 19:50:52 bbbx msgd:0: hal_lib:3887:rt prussdrv_open
May 31 19:50:52 bbbx msgd:0: hal_lib:3887:rt prussdrv_pruintc_init
May 31 19:50:52 bbbx msgd:0: hal_lib:3887:rt prussdrv_map_prumem
May 31 19:50:52 bbbx msgd:0: hal_lib:3887:rt PRU data ram mapped
May 31 19:50:52 bbbx msgd:0: hal_lib:3887:rt num_pwmgens : 6
May 31 19:50:52 bbbx msgd:0: hal_lib:3887:rt num_stepgens: 4
May 31 19:50:52 bbbx msgd:0: hal_lib:3887:rt num_encoders: 0
May 31 19:50:52 bbbx msgd:0: hal_lib:3887:rt Init pwm
May 31 19:50:52 bbbx msgd:0: hal_lib:3887:rt hpg_pwm_init
May 31 19:50:52 bbbx msgd:0: hal_lib:3887:rt Init stepgen
May 31 19:50:52 bbbx msgd:0: hal_lib:3887:rt hpg_stepgen_init
May 31 19:51:06 bbbx rtapi:0: unload: 'trivkins' not loaded
May 31 19:51:06 bbbx rtapi:0: unload: 'tp' not loaded
May 31 19:51:06 bbbx rtapi:0: unload: 'motmod' not loaded
May 31 19:51:06 bbbx rtapi:0: unload: 'hal_bb_gpio' not loaded
May 31 19:51:06 bbbx rtapi:0: unload: 'hal_pru_generic' not loaded
May 31 19:51:06 bbbx rtapi:0: unload: 'pid' not loaded
May 31 19:51:06 bbbx rtapi:0: unload: 'limit1' not loaded
May 31 19:51:06 bbbx msgd:0: hal_lib:3887:rt Init encoder
May 31 19:51:06 bbbx msgd:0: rtapi_app exit detected - scheduled shutdown
May 31 19:51:08 bbbx msgd:0: msgd shutting down
May 31 19:51:08 bbbx msgd:0: zeroconf: unregistering 'Log service on bbbx.local pid 3882'
May 31 19:51:08 bbbx msgd:0: log buffer hwm: 0% (24 msgs, 1755 bytes out of 524288)
May 31 19:51:08 bbbx msgd:0: normal shutdown - global segment detached
 

[Alexander Rössler]

Can you try another user interface (replace DISPLAY = axis in
ini). Looks like axis is failing to start.

--
Alexander Rössler

[Michael Brown]

Mnnn Sorry for the late reply
I'm facing multiple problems getting my machineface / 2,4 gantry / vel-ext config up and running.
however I found the first culprit:

I'm only able to load 1 gantry with the newinst command, and loadrt can't load the latching gantry any more.

(I don't know other Ui's than axis for non mkwrapper use
What do you suggest i replace  = axis
with ?)

It all started with this error message:

 from err1.txt

stat: No such file or directory
MibRapX.hal:33: insmod failed, returned -1:
do_load_cmd: dlopen: gantry_latching.so: cannot open shared object file: No such file or directory

I then changed my config as following :
#loadrt gantry_latching names=gantry.y,gantry.z personality=2,4
newinst lgantry gantry.y pincount=2
newinst lgantry gantry.z pincount=4

and maybe over reacted by changing all used components I saw now available in the machinekit...icomponents folder to use newinst
cluttering my problem.

At last I tried reverting all my recent icomp changes and removing 1 gantry component and then my config loads without complaining.
like so:
#loadrt gantry_latching names=gantry.y,gantry.z personality=2,4
#newinst lgantry gantry.y pincount=2
newinst lgantry gantry.z pincount=4

trying to load more than 1 gantry instance gives the

USRMOT: ERROR: command timeout
emcMotionInit: ini_hal_init fail

failure
________

I then also experimented with
loadrt pid names=pid.e0-temp,pid.hbp-temp

newinst pid pid.hbp-temp
newinst pid.e0-temp

workes

newinst pid pid.hbp-temp pid.e0-temp

dosn't  as it only loads the first instance

I also have to use:
addf   pid.e0-temp.do-pid-calcs             servo-thread

instead of
addf   pid.e0-temp                          servo-thread

hmmm ?
______________________

The Second show stopper I'm facing is that I'm unable to get the newest (linux_64) version of Machinekit-client to detect the newest Machineface rev t
Using the older(+ 4 axis Lgantry modded) version of Machineface (before removal of qtknobs 5 may) that has been working for me so far makes the config crash
when executing run.py
Attached (err2.txt)

[Daren Schwenke]

loadrt pid count=2

works instead now.

newinst seems to be for when there is only one.

https://groups.google.com/d/msg/machinekit/13CyJvWyN90/Ef5J8SbA_IsJ 

I also have to use:
addf   pid.e0-temp.do-pid-calcs             servo-thread

instead of
addf   pid.e0-temp                          servo-thread

 addf   pid.0.do-pid-calcs             servo-thread

 addf   pid.1.do-pid-calcs             servo-thread

[schoo...@btinternet.com]

Hi

gantry-latched had to be replaced with lgantry, because the 41 char pin name restriction clobbered it

I will be circulating a guide in a couple of hours that hopefully covers all the changes and how to load the
components by different methods.

Both loadrt and newinst will work, it just depends if you need to set the number of joints as to which one you use

Bear with me for a short while please

regards

--
website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit
---
You received this message because you are subscribed to the Google Groups "Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to machinekit+...@googlegroups.com.
Visit this group at http://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.

[Alexander Rössler]

the latching gantry is now maned lgantry, personality is now pincount

e.g.
newinst lgantry <whatver-name> pincount=2

--
Alexander

[Michael Brown]

I tried running linuxcnc with
DISPLAY = tklinuxcnc
And it started fine instead of axis.

On Sunday, May 31, 2015 at 9:16:59 PM UTC+2, Alexander Rössler wrote:

[Michael Brown]

On Monday, June 1, 2015 at 8:43:33 AM UTC+2, Schooner wrote:

Hi

gantry-latched had to be replaced with lgantry, because the 41 char pin name restriction clobbered it

I will be circulating a guide in a couple of hours that hopefully covers all the changes and how to load the
components by different methods.

Both loadrt and newinst will work, it just depends if you need to set the number of joints as to which one you use

Bear with me for a short while please

regards

OK
I have started a new thread as I seem to have already followed your recommendations and the problem persists...
loading 2 instances of the new lgantry(former latching-gantry) component fails


 

[Kent A. Reed]

Michael:

Just to clear up a side-bar issue of yours: "...I also do not understand

the git not installed messages ? (git is installed on my BBB)"

See https://github.com/machinekit/machinekit/issues/236

Regards,
Kent