WXHC-HD04 pendant not working after update to 2.7.9

deargonaut
Topic Author
Offline
New Member

9 years 4 months ago #94995 by deargonaut

WXHC-HD04 pendant not working after update to 2.7.9 was created by deargonaut

Hi all,

This will be my first post here.
I've been using LinuxCNC for almost two years now and I could always find my the answer to any of my questions. But now, unfortunately, I can't find it anywhere.

So as the topic title mentions: I've updated tot LinuxCNC 2.7.9 and now my wireless XHC-HD04 pendant doesn't work anymore.
I really don't have any more info except the following error. When starting the xhc-hd04 cli it works as well when starting linuxcnc with the sim.hb04 config. I've matched the sim config with my ini. But it keeps failing.
Can someone help me?

Big Thanks!

Code:

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
Found file(lib): /usr/share/linuxcnc/hallib/xhc-hb04.tcl
Shutting down and cleaning up LinuxCNC...
Running HAL shutdown script
Killing task linuxcncsvr, PID=15972
xhc-hb04: waiting for XHC-HB04 device
xhc-hb04: found XHC-HB04 device
xhc-hb04: connection lost, cleaning up
[timestamp] [threadID] facility level [function call] <message>
--------------------------------------------------------------------------------
Removing HAL_LIB, RTAPI, and Real Time OS modules
Removing NML shared memory segments

Debug file information:
xhc-hb04.tcl: using std_start_pause_button
missing operator at _@_
in expression "600.0 _@_800.0"
    (parsing expression "600.0 800.0")
    invoked from within
"expr {600.0 800.0}"
    ("uplevel" body line 1)
    invoked from within
"uplevel [list expr $v]"
    (procedure "setp" line 2)
    invoked from within
"setp pendant_util.amux$idx-in0 $std_accel"
    (procedure "wheel_setup" line 134)
    invoked from within
"wheel_setup  $::XHC_HB04_CONFIG(jogmode)"
    invoked from within
"if { ![namespace exists ::tp] || ([::tp::passnumber] != 0) } {
  connect_pins    ;# per ini file items: [XHC_HB04_BUTTONS]buttonname=pin
  wheel_setup..."
    (file "/usr/share/linuxcnc/hallib/xhc-hb04.tcl" line 556)
    invoked from within
"source $filename"
    invoked from within
"set result [source $filename]"
    (file "/usr/bin/haltcl" line 55)
15972
  PID TTY      STAT   TIME COMMAND
Stopping realtime threads
Unloading hal components
[ 0.000000] [00003e92] libusbx: error [do_close] Device handle closed while transfer was still being processed, but the device is still connected as far as we know
[ 0.000019] [00003e92] libusbx: warning [do_close] A cancellation for an in-flight transfer hasn't completed but closing the device handle

EDIT
I've got some more debugging. When I run the hxc-hb04 CLI and starting up LinuxCNC I get this:

Code:

[213.343543] [000014eb] libusbx: error [submit_bulk_transfer] submiturb failed error -1 errno=16
[213.343563] [000014eb] libusbx: error [submit_control_transfer] submiturb failed error -1 errno=16
[213.343571] [000014eb] libusbx: error [submit_control_transfer] submiturb failed error -1 errno=16
[213.343578] [000014eb] libusbx: error [submit_control_transfer] submiturb failed error -1 errno=16
[213.343585] [000014eb] libusbx: error [submit_control_transfer] submiturb failed error -1 errno=16
[213.343592] [000014eb] libusbx: error [submit_control_transfer] submiturb failed error -1 errno=16
[213.343599] [000014eb] libusbx: error [submit_control_transfer] submiturb failed error -1 errno=16
xhc-hb04: connection lost, cleaning up
[213.343607] [000014eb] libusbx: error [op_release_interface] release interface failed, error -1 errno 22
xhc-hb04: waiting for XHC-HB04 device
xhc-hb04: found XHC-HB04 device

I don't know what it means, but there are errors involved ;-)

Please Log in to join the conversation.

dgarrett
Offline
Platinum Member

9 years 4 months ago #95013 by dgarrett

Replied by dgarrett on topic WXHC-HD04 pendant not working after update to 2.7.9

Code:

missing operator at _@_
in expression "600.0 _@_800.0"
...
"setp pendant_util.amux$idx-in0 $std_accel"

From the above error, my guess is your ini configuration
is defining one or more [AXIS_n]MAX_ACCELERATION items
in more than one place.

For instance settings like these will give the above error:

Code:

[AXIS_0]
MAX_ACCELERATION = 600
...
MAX_ACCELERATION = 800
...

Please Log in to join the conversation.

deargonaut
Topic Author
Offline
New Member

9 years 4 months ago #95027 by deargonaut

Replied by deargonaut on topic WXHC-HD04 pendant not working after update to 2.7.9

Thanks @dgarrett for pointing into the right direction.

I didn't had multiple MAX_ACCELERATION within one axis stanza.
But I had multiple values throughout the file

Code:

[AXIS_0]MAX_ACCELERATION = 600
...
[AXIS_1]MAX_ACCELERATION = 800

I've resolved that and now it works like a charm!

Please Log in to join the conversation.

Time to create page: 0.095 seconds