Wireless XHC-HB04 pendant 'always connected'
01 Aug 2017 19:27 #96856
by hwylie
Wireless XHC-HB04 pendant 'always connected' was created by hwylie
Evidently, no error is reported by 'libusb_control_transfer' (called from 'xhc-hb04.cc') when the wireless pendant (model WHB04-L) is switched off.
This means 'require_pendant' in INI stanza [XHC_HB04_CONFIG] has no effect: HAL pin xhc-hb04.connected is always asserted.
Is this a limitation of the XHC (wireless) pendant / USB dongle design, or is there a workaround to correctly acquire pendant status?
LCNC version is current Master (Debian OS).
This means 'require_pendant' in INI stanza [XHC_HB04_CONFIG] has no effect: HAL pin xhc-hb04.connected is always asserted.
Is this a limitation of the XHC (wireless) pendant / USB dongle design, or is there a workaround to correctly acquire pendant status?
LCNC version is current Master (Debian OS).
Please Log in or Create an account to join the conversation.
01 Aug 2017 19:41 - 01 Aug 2017 19:51 #96857
by dgarrett
Replied by dgarrett on topic Wireless XHC-HB04 pendant 'always connected'
Connection loss occurs when you remove the usb connection.
excerpt: configs/sim/axis/xhc-hb04/README
github.com/LinuxCNC/linuxcnc/blob/master...axis/xhc-hb04/README
From the man page
linuxcnc.org/docs/devel/html/man/man1/xhc-hb04.1.html
excerpt: configs/sim/axis/xhc-hb04/README
Ref:When require_pendant = no, the xhc-hb04 hal pins will be created even if the pendant is not connected at startup. A new connection, a disconnect, and a reconnect are supported.
github.com/LinuxCNC/linuxcnc/blob/master...axis/xhc-hb04/README
From the man page
Ref:(bit out) xhc-hb04.connected True when connection to the pendant is established over the USB interface.
linuxcnc.org/docs/devel/html/man/man1/xhc-hb04.1.html
Last edit: 01 Aug 2017 19:51 by dgarrett.
Please Log in or Create an account to join the conversation.
02 Aug 2017 06:57 #96881
by hwylie
Replied by hwylie on topic Wireless XHC-HB04 pendant 'always connected'
Thank you - 'libusb' scope being only the USB interface, it is understood that HID status is an application layer issue - and as for wireless USB devices in general, the driver is unaware of absence of device power, wireless link error rate, etc.
Please Log in or Create an account to join the conversation.
Time to create page: 0.105 seconds