USRMOT: ERROR: command timeout
- bottleworks
- Offline
- Senior Member
-
Less
More
- Posts: 73
- Thank you received: 0
03 Aug 2015 12:33 #61136
by bottleworks
USRMOT: ERROR: command timeout was created by bottleworks
Hello.
I'm trying to figure out what's failing on a LinuxCNC setup. What error is "USRMOT: ERROR: command timeout"?
I'm trying to figure out what's failing on a LinuxCNC setup. What error is "USRMOT: ERROR: command timeout"?
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.0
Machine configuration directory is '/home/bradley/linuxcnc/configs/SuperMax'
Machine configuration file is 'SuperMax.ini'
INIFILE=/home/bradley/linuxcnc/configs/SuperMax/SuperMax.ini
PARAMETER_FILE=linuxcnc.var
TASK=milltask
HALUI=halui
DISPLAY=axis
Starting LinuxCNC...
Starting LinuxCNC server program: linuxcncsvr
Loading Real Time OS, RTAPI, and HAL_LIB modules
Starting LinuxCNC IO program: io
Starting HAL User Interface program: halui
INFO CLASSICLADDER- No ladder GUI requested-Realtime runs till HAL closes.
Starting TASK program: milltask
Starting DISPLAY program: axis
USRMOT: ERROR: command timeout
USRMOT: ERROR: command timeout
USRMOT: ERROR: command timeout
USRMOT: ERROR: command timeout
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
Shutting down and cleaning up LinuxCNC...
Running HAL shutdown script
Killing task linuxcncsvr, PID=1628
USRMOT: ERROR: command timeout
Killing task milltask, PID=1688
USRMOT: ERROR: command timeout
USRMOT: ERROR: command timeout
Timeout, trying kill -9
waiting for XHC-HB04 device
found XHC-HB04 device
connection lost, cleaning up
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
A configuration error is preventing LinuxCNC from starting.
More information may be available when running from a terminal.
1628
PID TTY STAT TIME COMMAND
1688
PID TTY STAT TIME COMMAND
1688 ? S 0:00 milltask -ini /home/bradley/linuxcnc/configs/SuperMax/SuperMax.ini
PID TTY STAT TIME COMMAND
1688 ? S 0:00 milltask -ini /home/bradley/linuxcnc/configs/SuperMax/SuperMax.ini
PID TTY STAT TIME COMMAND
1688 ? S 0:00 milltask -ini /home/bradley/linuxcnc/configs/SuperMax/SuperMax.ini
PID TTY STAT TIME COMMAND
1688 ? S 0:00 milltask -ini /home/bradley/linuxcnc/configs/SuperMax/SuperMax.ini
PID TTY STAT TIME COMMAND
1688 ? S 0:00 milltask -ini /home/bradley/linuxcnc/configs/SuperMax/SuperMax.ini
PID TTY STAT TIME COMMAND
1688 ? S 0:00 milltask -ini /home/bradley/linuxcnc/configs/SuperMax/SuperMax.ini
PID TTY STAT TIME COMMAND
1688 ? S 0:00 milltask -ini /home/bradley/linuxcnc/configs/SuperMax/SuperMax.ini
PID TTY STAT TIME COMMAND
1688 ? S 0:00 milltask -ini /home/bradley/linuxcnc/configs/SuperMax/SuperMax.ini
PID TTY STAT TIME COMMAND
1688 ? S 0:00 milltask -ini /home/bradley/linuxcnc/configs/SuperMax/SuperMax.ini
PID TTY STAT TIME COMMAND
1688 ? S 0:00 milltask -ini /home/bradley/linuxcnc/configs/SuperMax/SuperMax.ini
PID TTY STAT TIME COMMAND
1688 ? S 0:00 milltask -ini /home/bradley/linuxcnc/configs/SuperMax/SuperMax.ini
PID TTY STAT TIME COMMAND
1688 ? S 0:00 milltask -ini /home/bradley/linuxcnc/configs/SuperMax/SuperMax.ini
PID TTY STAT TIME COMMAND
1688 ? S 0:00 milltask -ini /home/bradley/linuxcnc/configs/SuperMax/SuperMax.ini
PID TTY STAT TIME COMMAND
1688 ? S 0:00 milltask -ini /home/bradley/linuxcnc/configs/SuperMax/SuperMax.ini
PID TTY STAT TIME COMMAND
1688 ? S 0:00 milltask -ini /home/bradley/linuxcnc/configs/SuperMax/SuperMax.ini
PID TTY STAT TIME COMMAND
1688 ? S 0:00 milltask -ini /home/bradley/linuxcnc/configs/SuperMax/SuperMax.ini
PID TTY STAT TIME COMMAND
1688 ? S 0:00 milltask -ini /home/bradley/linuxcnc/configs/SuperMax/SuperMax.ini
PID TTY STAT TIME COMMAND
1688 ? S 0:00 milltask -ini /home/bradley/linuxcnc/configs/SuperMax/SuperMax.ini
PID TTY STAT TIME COMMAND
1688 ? S 0:00 milltask -ini /home/bradley/linuxcnc/configs/SuperMax/SuperMax.ini
PID TTY STAT TIME COMMAND
/usr/bin/linuxcnc: line 381: 1688 Killed $EMCTASK -ini "$INIFILE"
Stopping realtime threads
Unloading hal components
Kernel message information:
[ 50.968355] I-pipe: Domain RTAI registered.
[ 50.968360] RTAI[hal]: <3.8.1> mounted over IPIPE-NOTHREADS 2.6-03.
[ 50.968362] RTAI[hal]: compiled with gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) .
[ 50.968396] RTAI[hal]: mounted (IPIPE-NOTHREADS, IMMEDIATE (INTERNAL IRQs DISPATCHED), ISOL_CPUS_MASK: 0).
[ 50.968398] PIPELINE layers:
[ 50.968400] f8466e20 9ac15d93 RTAI 200
[ 50.968401] c085cb20 0 Linux 100
[ 50.984495] RTAI[malloc]: global heap size = 2097152 bytes, <BSD>.
[ 50.984622] RTAI[sched]: IMMEDIATE, MP, USER/KERNEL SPACE: <with RTAI OWN KTASKs>, kstacks pool size = 524288 bytes.
[ 50.984626] RTAI[sched]: hard timer type/freq = APIC/12556305(Hz); default timing: periodic; linear timed lists.
[ 50.984628] RTAI[sched]: Linux timer freq = 250 (Hz), TimeBase freq = 3215149000 hz.
[ 50.984629] RTAI[sched]: timer setup = 999 ns, resched latency = 2943 ns.
[ 50.984727] RTAI[usi]: enabled.
[ 51.005548] RTAI[math]: loaded.
[ 51.156206] hm2: loading Mesa HostMot2 driver version 0.15
[ 51.158536] hm2_pci: loading Mesa AnyIO HostMot2 driver version 0.7
[ 51.158563] alloc irq_desc for 20 on node -1
[ 51.158565] alloc kstat_irqs on node -1
[ 51.158570] hm2_pci 0000:03:05.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
[ 51.158573] hm2_pci: discovered 5i25 at 0000:03:05.0
[ 51.158891] hm2/hm2_5i25.0: Smart Serial Firmware Version 43
[ 51.244566] hm2/hm2_5i25.0: 34 I/O Pins used:
[ 51.244569] hm2/hm2_5i25.0: IO Pin 000 (P3-01): StepGen #0, pin Direction (Output)
[ 51.244571] hm2/hm2_5i25.0: IO Pin 001 (P3-14): StepGen #0, pin Step (Output)
[ 51.244573] hm2/hm2_5i25.0: IO Pin 002 (P3-02): StepGen #1, pin Direction (Output)
[ 51.244575] hm2/hm2_5i25.0: IO Pin 003 (P3-15): StepGen #1, pin Step (Output)
[ 51.244578] hm2/hm2_5i25.0: IO Pin 004 (P3-03): StepGen #2, pin Direction (Output)
[ 51.244580] hm2/hm2_5i25.0: IO Pin 005 (P3-16): StepGen #2, pin Step (Output)
[ 51.244582] hm2/hm2_5i25.0: IO Pin 006 (P3-04): StepGen #3, pin Direction (Output)
[ 51.244584] hm2/hm2_5i25.0: IO Pin 007 (P3-17): StepGen #3, pin Step (Output)
[ 51.244586] hm2/hm2_5i25.0: IO Pin 008 (P3-05): StepGen #4, pin Direction (Output)
[ 51.244588] hm2/hm2_5i25.0: IO Pin 009 (P3-06): StepGen #4, pin Step (Output)
[ 51.244590] hm2/hm2_5i25.0: IO Pin 010 (P3-07): Smart Serial Interface #0, pin TxData0 (Output)
[ 51.244593] hm2/hm2_5i25.0: IO Pin 011 (P3-08): Smart Serial Interface #0, pin RxData0 (Input)
[ 51.244595] hm2/hm2_5i25.0: IO Pin 012 (P3-09): IOPort
[ 51.244596] hm2/hm2_5i25.0: IO Pin 013 (P3-10): IOPort
[ 51.244598] hm2/hm2_5i25.0: IO Pin 014 (P3-11): Encoder #0, pin Index (Input)
[ 51.244600] hm2/hm2_5i25.0: IO Pin 015 (P3-12): Encoder #0, pin B (Input)
[ 51.244603] hm2/hm2_5i25.0: IO Pin 016 (P3-13): Encoder #0, pin A (Input)
[ 51.244605] hm2/hm2_5i25.0: IO Pin 017 (P2-01): StepGen #5, pin Direction (Output)
[ 51.244607] hm2/hm2_5i25.0: IO Pin 018 (P2-14): StepGen #5, pin Step (Output)
[ 51.244609] hm2/hm2_5i25.0: IO Pin 019 (P2-02): StepGen #6, pin Direction (Output)
[ 51.244611] hm2/hm2_5i25.0: IO Pin 020 (P2-15): StepGen #6, pin Step (Output)
[ 51.244613] hm2/hm2_5i25.0: IO Pin 021 (P2-03): StepGen #7, pin Direction (Output)
[ 51.244615] hm2/hm2_5i25.0: IO Pin 022 (P2-16): StepGen #7, pin Step (Output)
[ 51.244617] hm2/hm2_5i25.0: IO Pin 023 (P2-04): StepGen #8, pin Direction (Output)
[ 51.244620] hm2/hm2_5i25.0: IO Pin 024 (P2-17): StepGen #8, pin Step (Output)
[ 51.244622] hm2/hm2_5i25.0: IO Pin 025 (P2-05): StepGen #9, pin Direction (Output)
[ 51.244624] hm2/hm2_5i25.0: IO Pin 026 (P2-06): StepGen #9, pin Step (Output)
[ 51.244626] hm2/hm2_5i25.0: IO Pin 027 (P2-07): IOPort
[ 51.244627] hm2/hm2_5i25.0: IO Pin 028 (P2-08): IOPort
[ 51.244629] hm2/hm2_5i25.0: IO Pin 029 (P2-09): IOPort
[ 51.244631] hm2/hm2_5i25.0: IO Pin 030 (P2-10): IOPort
[ 51.244633] hm2/hm2_5i25.0: IO Pin 031 (P2-11): Encoder #1, pin Index (Input)
[ 51.244635] hm2/hm2_5i25.0: IO Pin 032 (P2-12): Encoder #1, pin B (Input)
[ 51.244637] hm2/hm2_5i25.0: IO Pin 033 (P2-13): Encoder #1, pin A (Input)
[ 51.244680] hm2/hm2_5i25.0: registered
[ 51.244682] hm2_5i25.0: initialized AnyIO board at 0000:03:05.0
[ 51.250982] classicladder_rt: module license 'LGPL' taints kernel.
[ 51.250985] Disabling lock debugging due to kernel taint
[ 51.251876] creating ladder-state
[ 59.800881] hm2_5i25.0: dropping AnyIO board at 0000:03:05.0
[ 59.800886] hm2/hm2_5i25.0: unregistered
[ 59.800903] hm2_pci 0000:03:05.0: PCI INT A disabled
[ 59.800923] hm2_pci: driver unloaded
[ 59.802469] hm2: unloading
[ 61.885545] RTAI[math]: unloaded.
[ 61.903793] SCHED releases registered named ALIEN RTGLBH
[ 61.932301] RTAI[malloc]: unloaded.
[ 62.043568] RTAI[sched]: unloaded (forced hard/soft/hard transitions: traps 0, syscalls 0).
[ 62.045127] I-pipe: Domain RTAI unregistered.
[ 62.045172] RTAI[hal]: unmounted.Please Log in or Create an account to join the conversation.
03 Aug 2015 15:46 - 03 Aug 2015 15:47 #61137
by cncbasher
Replied by cncbasher on topic USRMOT: ERROR: command timeout
you have a configuration error , probably from an very old config sample .
post your config files as an archive ,
post your config files as an archive ,
Last edit: 03 Aug 2015 15:47 by cncbasher.
Please Log in or Create an account to join the conversation.
- reliantkill
-
- Offline
- New Member
-
Less
More
- Posts: 10
- Thank you received: 1
01 Sep 2015 12:01 - 01 Sep 2015 13:29 #61979
by reliantkill
Replied by reliantkill on topic USRMOT: ERROR: command timeout
I have the same error. I have been trying to configure Modbus serial. the TCP modbus runs fine but I cannot get the modbus serial to work
but never mind, I check my configuration file custom.clp and I had an L for serial port ? I don't know how it got there.... and I had garbage big number for Modbus_Master _time_inter_frame= 1023456789 so I set it to 10. now its working fine. I am using a CLICK PLC controller from automation direct and I configure port 2 to mudbus slave not port 3 because I don't have a rs232 to rs485 converter. I also using a USB to serial converter that linux identified it as: Prolific "PL-2303" this is a link where to find it, no I am not working for them! just want to share the solution.
because I tried to use pci serial and could not make it work. this serial adapter and port2 of the CLICK PLC is a point to point configuration and it will not work to connect more than one device to ClassicLadder modbus. For multidrop network you need a rs232 to rs485 adapter to run multiple devices or slave nodes. I have some experience with Allen Bradley but I am zero in Linux but I am having so much fun, and everytime I make something work I want to run to the street and tell everybody regardless of the time been 1:00am. My Network is working!!!
www.securitytobuy.com/index.php?main_pag...ab15301d9fe4de974590
but never mind, I check my configuration file custom.clp and I had an L for serial port ? I don't know how it got there.... and I had garbage big number for Modbus_Master _time_inter_frame= 1023456789 so I set it to 10. now its working fine. I am using a CLICK PLC controller from automation direct and I configure port 2 to mudbus slave not port 3 because I don't have a rs232 to rs485 converter. I also using a USB to serial converter that linux identified it as: Prolific "PL-2303" this is a link where to find it, no I am not working for them! just want to share the solution.
because I tried to use pci serial and could not make it work. this serial adapter and port2 of the CLICK PLC is a point to point configuration and it will not work to connect more than one device to ClassicLadder modbus. For multidrop network you need a rs232 to rs485 adapter to run multiple devices or slave nodes. I have some experience with Allen Bradley but I am zero in Linux but I am having so much fun, and everytime I make something work I want to run to the street and tell everybody regardless of the time been 1:00am. My Network is working!!!
www.securitytobuy.com/index.php?main_pag...ab15301d9fe4de974590
Last edit: 01 Sep 2015 13:29 by reliantkill.
Please Log in or Create an account to join the conversation.
- bottleworks
- Offline
- Senior Member
-
Less
More
- Posts: 73
- Thank you received: 0
02 Sep 2015 12:07 - 02 Sep 2015 12:08 #62040
by bottleworks
Replied by bottleworks on topic USRMOT: ERROR: command timeout
My issue wasn't a configuration issue. The config had been used untouched for years for a machine used everyday. It only gets turned off when we loose power. A power surge caused some surge protection feature to reset the BIOS. The default settings were causing the error. Once realizing what was going on, I disabled quiet n' cool and C1E (or something like that). That resolved the issue for me. So, BIOS issues...
Last edit: 02 Sep 2015 12:08 by bottleworks.
Please Log in or Create an account to join the conversation.
- Todd Zuercher
-
- Away
- Platinum Member
-
Less
More
- Posts: 4978
- Thank you received: 1376
02 Sep 2015 23:58 #62067
by Todd Zuercher
Replied by Todd Zuercher on topic USRMOT: ERROR: command timeout
If powering down the PC caused the BIOS to reset to the factory defaults, then the CMOS battery on the motherboard is almost certainly dead. (Not at all surprising on an older PC.)
Please Log in or Create an account to join the conversation.
- bottleworks
- Offline
- Senior Member
-
Less
More
- Posts: 73
- Thank you received: 0
13 Oct 2015 08:40 #63727
by bottleworks
In my case (as noted above), it was caused by a power surge. The motherboard is only a few years old. I installed a new battery when I built the system. The battery is still good today. I had another surge today, so I took a photo. I've attached a photo of the prompt for those who haven't seen this before.
Replied by bottleworks on topic USRMOT: ERROR: command timeout
If powering down the PC caused the BIOS to reset to the factory defaults, then the CMOS battery on the motherboard is almost certainly dead. (Not at all surprising on an older PC.)
In my case (as noted above), it was caused by a power surge. The motherboard is only a few years old. I installed a new battery when I built the system. The battery is still good today. I had another surge today, so I took a photo. I've attached a photo of the prompt for those who haven't seen this before.
Please Log in or Create an account to join the conversation.
Time to create page: 0.088 seconds