Configuration Error - Waiting for S.Axes

More
11 Apr 2014 05:19 - 11 Apr 2014 05:25 #45824 by Fweek
Hello,

I recently setup my mill with linxucnc and after a couple of reboots started getting a configuration error when trying to start up the AXIS interface. I can get to the LinuxCNC Configuration Selector (see image) but after making my choice it craps out. I'm not sure what causing it because I haven't modified anything since I initially set it up. What can I do? Thanks



Here is the terminal output after running linuxcnc &:
LINUXCNC - 2.6.0~pre
Machine configuration directory is '/home/linuxcnc/linuxcnc/configs/ARM/BeagleBone/PBX-BB'
Machine configuration file is 'PRU-Driven-INCH.ini'
Starting LinuxCNC...
io started
halcmd loadusr io started
BBB-LCNC-PBX overlay found
memmapped gpio port 2 to 0xb6927000, oe: 0xb6927134, set: 0xb6927194, clr: 0xb6927190
pin 8 maps to pin 2-3, mode 85
memmapped gpio port 0 to 0xb6924000, oe: 0xb6924134, set: 0xb6924194, clr: 0xb6924190
pin 14 maps to pin 0-26, mode 85
memmapped gpio port 1 to 0xb6922000, oe: 0xb6922134, set: 0xb6922194, clr: 0xb6922190
pin 15 maps to pin 1-15, mode 85
pin 17 maps to pin 0-27, mode 85
pin 18 maps to pin 2-1, mode 85
pin 26 maps to pin 1-29, mode 85
pin 11 maps to pin 0-30, mode 85
pin 12 maps to pin 1-28, mode 85
pin 14 maps to pin 1-18, mode 85
pin 15 maps to pin 1-16, mode 85
pin 16 maps to pin 1-19, mode 85
pin 22 maps to pin 0-2, mode 85
pin 24 maps to pin 0-15, mode 85
pin 26 maps to pin 0-14, mode 85
prussdrv_init
prussdrv_open
prussdrv_pruintc_init
prussdrv_map_prumem
PRU data ram mapped
num_pwmgens : 3
num_stepgens: 5
task pid=4069
waiting for s.axes
waiting for s.axes
waiting for s.axes
waiting for s.axes
waiting for s.axes
waiting for s.axes
waiting for s.axes
waiting for s.axes
waiting for s.axes
A configuration error is preventing LinuxCNC from starting.
More information may be available when running from a terminal.
Shutting down and cleaning up LinuxCNC...
emc/task/emctaskmain.cc 2962: can't initialize motion
/home/linuxcnc/linuxcnc/bin/milltask exiting
/home/linuxcnc/linuxcnc/scripts/linuxcnc: line 449: 4069 Segmentation fault $EMCTASK -ini "$INIFILE"
Cleanup done
LinuxCNC terminated with an error. You can find more information in the log:
/home/linuxcnc/linuxcnc_debug.txt
and
/home/linuxcnc/linuxcnc_print.txt
as well as in the output of the shell command 'dmesg' and in the terminal




Here is the linuxcnc_print.txt:
RUN_IN_PLACE=yes
LINUXCNC_DIR=
LINUXCNC_BIN_DIR=/home/linuxcnc/linuxcnc/bin
LINUXCNC_TCL_DIR=/home/linuxcnc/linuxcnc/tcl
LINUXCNC_SCRIPT_DIR=
LINUXCNC_RTLIB_DIR=/home/linuxcnc/linuxcnc/rtlib
LINUXCNC_CONFIG_DIR=
LINUXCNC_LANG_DIR=/home/linuxcnc/linuxcnc/src/objects
INIVAR=inivar
HALCMD=halcmd
LINUXCNC_EMCSH=/usr/bin/wish8.5
INIFILE=/home/linuxcnc/linuxcnc/configs/ARM/BeagleBone/PBX-BB/PRU-Driven-INCH.ini
PARAMETER_FILE=pru-stepper.var
TASK=milltask
HALUI=
DISPLAY=axis
Starting LinuxCNC server program: linuxcncsvr
Loading Real Time OS, RTAPI, and HAL_LIB modules
Starting LinuxCNC IO program: io
Starting TASK program: milltask
Starting DISPLAY program: axis
Killing task linuxcncsvr, PID=4037
Removing HAL_LIB, RTAPI, and Real Time OS modules
Removing NML shared memory segments




Here is the linuxcnc_debug.txt
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
4037
PID TTY STAT TIME COMMAND
Stopping realtime threads
Unloading hal components


Here is the dmesg:
pastebin.ca/2694098
Attachments:
Last edit: 11 Apr 2014 05:25 by Fweek.

Please Log in or Create an account to join the conversation.

More
11 Apr 2014 10:14 #45836 by jmelson
I think this one comes from having a line in your .ini file
like this :
NML_FILE = emc.nml

At least, I think having this line will cause that S.Axes error.

The line should be removed from the .ini file.

Jon

Please Log in or Create an account to join the conversation.

More
12 Apr 2014 00:05 - 12 Apr 2014 01:27 #45859 by Fweek
Ok let me try that.
Last edit: 12 Apr 2014 01:27 by Fweek.

Please Log in or Create an account to join the conversation.

More
12 Apr 2014 01:26 #45860 by Fweek

I think this one comes from having a line in your .ini file
like this :
NML_FILE = emc.nml

At least, I think having this line will cause that S.Axes error.

The line should be removed from the .ini file.

Jon



Thanks for the reply but I don't have that line in my ini file.

This is what I have in my PRU-Driven-INCH.ini unless you're referring to some other ini file.
www.pastebin.ca/2694455

Please Log in or Create an account to join the conversation.

More
12 Apr 2014 03:04 #45865 by cncbasher
please post your hal config also

Please Log in or Create an account to join the conversation.

More
12 Apr 2014 03:39 - 12 Apr 2014 03:47 #45867 by Fweek
This is the hal file I found in the same directory as the ini file. Hope that's the right one.

PBX-BB.hal

pastebin.ca/2694576
Last edit: 12 Apr 2014 03:47 by Fweek.

Please Log in or Create an account to join the conversation.

More
12 Apr 2014 08:25 #45873 by jmelson



Thanks for the reply but I don't have that line in my ini file.


/home/linuxcnc/linuxcnc/scripts/linuxcnc: line 449: 4069 Segmentation fault $EMCTASK -ini "$INIFILE"

Probably anything that causes emctask to bomb out will cause that error.

Jon

Please Log in or Create an account to join the conversation.

More
13 Apr 2014 05:59 #45896 by Fweek
How do I figure out what's causing emctask to die?

Please Log in or Create an account to join the conversation.

More
13 Apr 2014 21:26 #45909 by cncbasher
it would be helpful to know which linuxcnc image you have uploaded and if you built from source
the command line switches

have you made any changes etc

Please Log in or Create an account to join the conversation.

More
15 Apr 2014 03:18 #45950 by Fweek

it would be helpful to know which linuxcnc image you have uploaded and if you built from source
the command line switches

have you made any changes etc


Ah ok so the linuxcnc image I'm using is a custom one provided by Probotix which I got here www.probotix.com/wiki/index.php/PBX-BB

In regards to changes, no I haven't made any. After I finish writing a fresh image, I would boot it up and get to the AXIS interface window where I would manually step a couple of motors just to test. Then I would shut it down and later when I boot it up I get that error where I can't load the AXIS interface anymore. Haven't made any changes. This has happened twice with two different SD cards.

Please Log in or Create an account to join the conversation.

Time to create page: 0.199 seconds
Powered by Kunena Forum