Johnny Wong
2015-Aug-17 15:56 UTC
[Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3
> What does that revision number correspond to in FreeBSD release numbers? (e.g. 9.3, 10.0)FreeBSD 10.2-RELEASE #0 r286738M the last person probably wasn't able to give the ./configure probably because most people uses the precompiled iso to install NAS4Free.? if you need the ./configure I might have to look for their source on GitHub or something. /usr/local/libexec/nut/usbhid-ups -a upstl1300 -DDD Network UPS Tools - Generic HID driver 0.39 (2.7.3) USB communication driver 0.32 ?? 0.000000???? debug level is '3' ?? 0.006296???? upsdrv_initups... ?? 0.007180???? Checking device (0781/5583) (/dev/usb//dev/ugen0.6) ?? 0.013441???? - VendorID: 0781 ?? 0.013456???? - ProductID: 5583 ?? 0.013464???? - Manufacturer: SanDisk ?? 0.013472???? - Product: Ultra Fit ?? 0.013480???? - Serial Number: 4C530123150905117592 ?? 0.013487???? - Bus: /dev/usb ?? 0.013495???? Trying to match device ?? 0.013518???? Device does not match - skipping ?? 0.013551???? Checking device (09AE/3016) (/dev/usb//dev/ugen0.5) ?? 0.278818???? - VendorID: 09ae ?? 0.278835???? - ProductID: 3016 ?? 0.278843???? - Manufacturer: unknown ?? 0.278852???? - Product: unknown ?? 0.278859???? - Serial Number: unknown ?? 0.278867???? - Bus: /dev/usb ?? 0.278876???? Trying to match device ?? 0.278925???? Device matches ?? 0.278937???? nut_usb_set_altinterface: skipped usb_set_altinterface(udev, 0) ?? 0.306126???? HID descriptor, method 1: (9 bytes) => 09 21 11 01 00 01 22 6e 03 ?? 0.306148???? HID descriptor, method 2: (9 bytes) => 09 21 11 01 00 01 22 6e 03 ?? 0.306156???? HID descriptor length 878 ?? 5.279939???? Unable to get Report descriptor: Input/output error ?? 5.279997???? Checking device (046D/C509) (/dev/usb//dev/ugen0.4) ?? 5.287000???? - VendorID: 046d ?? 5.287013???? - ProductID: c509 ?? 5.287020???? - Manufacturer: Logitech ?? 5.287026???? - Product: USB Receiver ?? 5.287032???? - Serial Number: unknown ?? 5.287038???? - Bus: /dev/usb ?? 5.287047???? Trying to match device ?? 5.287060???? Device does not match - skipping ?? 5.287086???? Checking device (0557/2419) (/dev/usb//dev/ugen0.3) ?? 5.287156???? - VendorID: 0557 ?? 5.287167???? - ProductID: 2419 ?? 5.287174???? - Manufacturer: unknown ?? 5.287180???? - Product: unknown ?? 5.287185???? - Serial Number: unknown ?? 5.287191???? - Bus: /dev/usb ?? 5.287197???? Trying to match device ?? 5.287206???? Device does not match - skipping ?? 5.287227???? Checking device (0000/0001) (/dev/usb//dev/ugen0.2) ?? 5.287285???? - VendorID: 0000 ?? 5.287295???? - ProductID: 0001 ?? 5.287302???? - Manufacturer: unknown ?? 5.287308???? - Product: unknown ?? 5.287314???? - Serial Number: unknown ?? 5.287320???? - Bus: /dev/usb ?? 5.287326???? Trying to match device ?? 5.287334???? Device does not match - skipping ?? 5.287353???? Checking device (0000/0000) (/dev/usb//dev/ugen0.1) ?? 5.287427???? - VendorID: 0000 ?? 5.287436???? - ProductID: 0000 ?? 5.287443???? - Manufacturer: 0x8086 ?? 5.287448???? - Product: XHCI root HUB ?? 5.287454???? - Serial Number: unknown ?? 5.287460???? - Bus: /dev/usb ?? 5.287466???? Trying to match device ?? 5.287474???? Device does not match - skipping ?? 5.287508???? No appropriate HID device found ?? 5.287519???? No matching HID UPS found Here is the ups.conf if needed cat /var/etc/ups.conf [upstl1300] ??????? driver = usbhid-ups ??????? port = auto ??????? pollfreq = 30 ??????? productid = 3016 Let me know what other information is required, I'll try my best to obtain it. Regards, Johnny Wong On Monday, August 17, 2015 5:27 AM, Charles Lepple <clepple at gmail.com> wrote: On Aug 17, 2015, at 1:00 AM, Johnny Wong <e430benz98 at yahoo.com> wrote:> > OS = NAS4Free (FreeBSD Revision: 199506)What does that revision number correspond to in FreeBSD release numbers? (e.g. 9.3, 10.0)> NUT Version = 2.7.3 for other parts of NUT version is listed below > NUT is part of the NAS4Free distribution > Device = Tripp Lite SMART1300LCDT URL http://www.tripplite.com/line-interactive-ups-system-desktop-tower-1300va-120v-usb-port-lcd-screen~SMART1300LCDT/ >? > PROBLEM:? NUT is ABLE to see the UPS BUT it is not getting the right(?) descriptor?? I am using the usbhid-ups driver set.? I have tried others, tripplite, tripplite_usb, and blazer_usb and none works.? This is the closest I can see it being ?working?For that USB ID (09AE/3016), usbhid-ups is the correct driver.> According to http://www.networkupstools.org/ddl/Tripp_Lite/SMART1300LCDT.html. It was ?verified? working with NUT version 2.6.4?In a message on nut-upsdev, Marco Walther just cited this thread: http://thread.gmane.org/gmane.comp.monitoring.nut.devel/6482 which mentions that the UPS works on Debian Linux 7.1. Marco's patch is against NUT 2.7.3, and it just corrects some scaling of the variables, so it would have gotten well past the problem you mentioned. It sounds like this might be an issue with the FreeBSD USB stack. I am not familiar with NAS4Free, but what do you get when you start the driver in debug mode? You will need to get to a root shell, then run something like "/usr/local/libexec/nut/usbhid-ups -a upsname -DDD" (replacing "upsname" with the name in ups.conf). Apologies in advance if you need to go hunting for the exact path of the driver or ups.conf: the last person to have an issue with NAS4Free did not get back to the NUT lists with the ./configure settings that NAS4Free uses to compile NUT. [please use reply-all] -- Charles Lepple clepple at gmail -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20150817/86d32ba1/attachment-0001.html>
Charles Lepple
2015-Aug-18 12:43 UTC
[Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3
On Aug 17, 2015, at 11:56 AM, Johnny Wong <e430benz98 at yahoo.com> wrote:> > > What does that revision number correspond to in FreeBSD release numbers? (e.g. 9.3, 10.0) > > FreeBSD 10.2-RELEASE #0 r286738MOkay, thanks. I think this is the first report of FreeBSD 10.2, so hopefully it is not an issue inherent in the OS. I will see if I can upgrade one of my machines to test with another UPS brand.> the last person probably wasn't able to give the ./configure probably because most people uses the precompiled iso to install NAS4Free. if you need the ./configure I might have to look for their source on GitHub or something.True, most people won't need to know the ./configure parameters. It looks like you found the driver path and the UPS name, so we're set for now. However, if you run across that part of the source code, it might be useful for later in case we need to rebuild a driver.> > /usr/local/libexec/nut/usbhid-ups -a upstl1300 -DDD > Network UPS Tools - Generic HID driver 0.39 (2.7.3) > USB communication driver 0.32 > 0.000000 debug level is '3' > 0.006296 upsdrv_initups...[...]> 0.013551 Checking device (09AE/3016) (/dev/usb//dev/ugen0.5) > 0.278818 - VendorID: 09ae > 0.278835 - ProductID: 3016 > 0.278843 - Manufacturer: unknown > 0.278852 - Product: unknown > 0.278859 - Serial Number: unknown > 0.278867 - Bus: /dev/usb > 0.278876 Trying to match device > 0.278925 Device matches > 0.278937 nut_usb_set_altinterface: skipped usb_set_altinterface(udev, 0)Just for grins, can you try adding "usb_set_altinterface" to the ups.conf section for your UPS, and see if that changes this part of the log? (That is, after "[upstl1300]").> 0.306126 HID descriptor, method 1: (9 bytes) => 09 21 11 01 00 01 22 6e 03 > 0.306148 HID descriptor, method 2: (9 bytes) => 09 21 11 01 00 01 22 6e 03 > 0.306156 HID descriptor length 878 > 5.279939 Unable to get Report descriptor: Input/output errorMy other concern is that FreeBSD might not allow the method that we use to retrieve the Report Descriptor. What do the following commands return (need to run them as root)? usbconfig -u 0 -a 5 dump_device_desc usbconfig -u 0 -a 5 dump_curr_config_desc usbconfig -u 0 -a 5 do_request 0x81 0x06 0x2200 0 0x100 (I'm guessing on "-u 0 -a 5" based on .../dev/ugen0.5 -- that might change if the UPS USB cable is unplugged and re-inserted.)> cat /var/etc/ups.conf > [upstl1300] > driver = usbhid-ups > port = auto > pollfreq = 30 > productid = 3016 > > Let me know what other information is required, I'll try my best to obtain it.Thanks for sending ups.conf. That's all I can think of for now. -- Charles Lepple clepple at gmail
Johnny Wong
2015-Aug-18 17:05 UTC
[Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3
Here are all the usbconfig outputs you have requested.
I have left a message with the Dev for NAS4Free to give up the ./configure for
NUT portion.? I am hoping they will...
usbconfig -u 0 -a 5 dump_device_desc?
datanas: ~# usbconfig -u 0 -a 5 dump_device_desc
ugen0.5: <TRIPP LITE UPS Tripp Lite> at usbus0, cfg=0 md=HOST spd=LOW
(1.5Mbps) pwr=ON (100mA)? bLength = 0x0012
? bDescriptorType = 0x0001
? bcdUSB = 0x0110
? bDeviceClass = 0x0000? <Probed by interface class>
? bDeviceSubClass = 0x0000
? bDeviceProtocol = 0x0000
? bMaxPacketSize0 = 0x0008
? idVendor = 0x09ae
? idProduct = 0x3016
? bcdDevice = 0x0002
? iManufacturer = 0x0003? <retrieving string failed>
? iProduct = 0x0001? <TRIPP LITE UPS>
? iSerialNumber = 0x0005? <retrieving string failed>
? bNumConfigurations = 0x0001
usbconfig -u 0 -a 5 dump_curr_config_desc
?datanas: ~# usbconfig -u 0 -a 5 dump_curr_config_desc
ugen0.5: <TRIPP LITE UPS Tripp Lite> at usbus0, cfg=0 md=HOST spd=LOW
(1.5Mbps) pwr=ON (100mA)
?Configuration index 0??? bLength = 0x0009
??? bDescriptorType = 0x0002
??? wTotalLength = 0x0022
??? bNumInterfaces = 0x0001
??? bConfigurationValue = 0x0001
??? iConfiguration = 0x0000? <no string>
??? bmAttributes = 0x00a0
??? bMaxPower = 0x0032??? Interface 0
????? bLength = 0x0009
????? bDescriptorType = 0x0004
????? bInterfaceNumber = 0x0000
????? bAlternateSetting = 0x0000
????? bNumEndpoints = 0x0001
????? bInterfaceClass = 0x0003? <HID device>
????? bInterfaceSubClass = 0x0000
????? bInterfaceProtocol = 0x0000
????? iInterface = 0x0000? <no string>????? Additional Descriptor?????
bLength = 0x09
????? bDescriptorType = 0x21
????? bDescriptorSubType = 0x11
?????? RAW dump:
?????? 0x00 | 0x09, 0x21, 0x11, 0x01, 0x00, 0x01, 0x22, 0x6e,
?????? 0x08 | 0x03???? Endpoint 0
??????? bLength = 0x0007
??????? bDescriptorType = 0x0005
??????? bEndpointAddress = 0x0081? <IN>
??????? bmAttributes = 0x0003? <INTERRUPT>
??????? wMaxPacketSize = 0x0008
??????? bInterval = 0x000c
??????? bRefresh = 0x0000
??????? bSynchAddress = 0x0000
usbconfig -u 0 -a 5 do_request 0x81 0x06 0x2200 0 0x100
?datanas: ~# usbconfig -u 0 -a 5 do_request 0x81 0x06 0x2200 0 0x100
REQUEST = <0x05 0x84 0x09 0x04 0xa1 0x01 0x09 0x24 0xa1 0x00 0x85 0x28 0x09
0xfe 0x79 0x01 0x75 0x08 0x95 0x01 0x15 0x00 0x26 0xff 0x00 0xb1 0x03 0x85 0x29
0x09 0xff 0x79 0x05 0xb1 0x03 0x85 0x2b 0x09 0xfd 0x79 0x03 0xb1 0x03 0x09 0x1a
0xa1 0x02 0x85 0x30 0x09 0x40 0x67 0x21 0xd1 0xf0 0x00 0x55 0x07 0xb1 0x83 0x85
0x31 0x09 0x30 0x75 0x10 0x95 0x01 0x15 0x00 0x27 0xff 0xff 0x00 0x00 0x67 0x21
0xd1 0xf0 0x00 0x55 0x01 0xb1 0x02 0xc0 0x85 0x11 0x09 0x5a 0x75 0x08 0x95 0x01
0x15 0x01 0x25 0x03 0x65 0x00 0x55 0x00 0xb1 0x82 0x09 0x02 0xa1 0x02 0x85 0x32
0x75 0x01 0x95 0x07 0x15 0x00 0x25 0x01 0x81 0x03 0xb1 0x03 0x09 0x62 0x95 0x01
0xb1 0xa2 0x09 0x62 0x81 0xa2 0xb1 0x01 0x81 0x01 0x09 0x69 0xb1 0xa2 0x09 0x69
0x81 0xa2 0x95 0x06 0xb1 0x01 0x81 0x01 0x05 0x85 0x09 0xd0 0x95 0x01 0x81 0xa2
0x09 0xd0 0xb1 0xa2 0x81 0x01 0xb1 0x01 0x95 0x06 0x09 0x42 0x09 0x46 0x09 0x44
0x09 0x45 0x09 0x47 0x09 0x4b 0x81 0xa2 0x09 0x42 0x09 0x46 0x09 0x44 0x09 0x45
0x09 0x47 0x09 0x4b 0xb1 0xa2 0xc0 0x85 0x2a 0x09 0x89 0x79 0x07 0x75 0x08 0x95
0x01 0x15 0x00 0x26 0xff 0x00 0xb1 0x03 0x85 0x62 0x09 0x8f 0x79 0x08 0xb1 0x03
0x85 0x33 0x09 0x2c 0xb1 0x03 0x85 0x34 0x09 0x66 0x81 0xa2 0x09 0x66 0xb1 0xa2
0x85 0x3a 0x09 0x29 0xb1 0xa2 0x85 0x37 0x09 0x67 0xb1 0x03 0x85 0x36 0x09 0x83
0xb1 0x03 0x85><$(yu&)y+y0 at
g!U10u'g!UZu%eU2u%bbiiBFDEGKBFDEGK*yu&by3,4ff:)7g6>
On Tuesday, August 18, 2015 5:44 AM, Charles Lepple <clepple at
gmail.com> wrote:
On Aug 17, 2015, at 11:56 AM, Johnny Wong <e430benz98 at yahoo.com>
wrote:>
> > What does that revision number correspond to in FreeBSD release
numbers? (e.g. 9.3, 10.0)
>
> FreeBSD 10.2-RELEASE #0 r286738M
Okay, thanks. I think this is the first report of FreeBSD 10.2, so hopefully it
is not an issue inherent in the OS. I will see if I can upgrade one of my
machines to test with another UPS brand.
> the last person probably wasn't able to give the ./configure probably
because most people uses the precompiled iso to install NAS4Free.? if you need
the ./configure I might have to look for their source on GitHub or something.
True, most people won't need to know the ./configure parameters. It looks
like you found the driver path and the UPS name, so we're set for now.
However, if you run across that part of the source code, it might be useful for
later in case we need to rebuild a driver.
>
> /usr/local/libexec/nut/usbhid-ups -a upstl1300 -DDD
> Network UPS Tools - Generic HID driver 0.39 (2.7.3)
> USB communication driver 0.32
>? ? 0.000000? ? debug level is '3'
>? ? 0.006296? ? upsdrv_initups...
[...]>? 0.013551? ? Checking device (09AE/3016) (/dev/usb//dev/ugen0.5)
>? ? 0.278818? ? - VendorID: 09ae
>? ? 0.278835? ? - ProductID: 3016
>? ? 0.278843? ? - Manufacturer: unknown
>? ? 0.278852? ? - Product: unknown
>? ? 0.278859? ? - Serial Number: unknown
>? ? 0.278867? ? - Bus: /dev/usb
>? ? 0.278876? ? Trying to match device
>? ? 0.278925? ? Device matches
>? ? 0.278937? ? nut_usb_set_altinterface: skipped usb_set_altinterface(udev,
0)
Just for grins, can you try adding "usb_set_altinterface" to the
ups.conf section for your UPS, and see if that changes this part of the log?
(That is, after "[upstl1300]").
>? ? 0.306126? ? HID descriptor, method 1: (9 bytes) => 09 21 11 01 00 01
22 6e 03
>? ? 0.306148? ? HID descriptor, method 2: (9 bytes) => 09 21 11 01 00 01
22 6e 03
>? ? 0.306156? ? HID descriptor length 878
>? ? 5.279939? ? Unable to get Report descriptor: Input/output error
My other concern is that FreeBSD might not allow the method that we use to
retrieve the Report Descriptor.
What do the following commands return (need to run them as root)?
usbconfig -u 0 -a 5 dump_device_desc
usbconfig -u 0 -a 5 dump_curr_config_desc
usbconfig -u 0 -a 5 do_request 0x81 0x06 0x2200 0 0x100
(I'm guessing on "-u 0 -a 5" based on .../dev/ugen0.5 -- that
might change if the UPS USB cable is unplugged and re-inserted.)
> cat /var/etc/ups.conf
> [upstl1300]
>? ? ? ? driver = usbhid-ups
>? ? ? ? port = auto
>? ? ? ? pollfreq = 30
>? ? ? ? productid = 3016
>
> Let me know what other information is required, I'll try my best to
obtain it.
Thanks for sending ups.conf. That's all I can think of for now.
--
Charles Lepple
clepple at gmail
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20150818/c687979a/attachment-0001.html>
Johnny Wong
2015-Aug-18 19:28 UTC
[Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3
So when the UPS is communicating with the driver... it seems to work.? Problem
is now that it keeps disconnecting.? Any recommendation on how to keep the
drivers from disconnecting using the usb_set_altinterface?? (PS.? Is there a
specific value to use?)? Or this confirms there is an issue with the usbhid-ups
driver with the FreeBSD 10.2 kernel?
upsc upstl1300
battery.charge: 100
battery.charge.low: 10
battery.charge.warning: 30
battery.runtime: 709
battery.type: PbAC
battery.voltage: 0.0
battery.voltage.nominal: 24.0
device.type: ups
driver.flag.usb_set_altinterface: enabled
driver.name: usbhid-ups
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 15
driver.parameter.port: /dev/ugen0.5
driver.parameter.productid: 3016
driver.parameter.synchronous: no
driver.version: 2.7.3
driver.version.data: TrippLite HID 0.81
driver.version.internal: 0.39
input.frequency: 5990.0
input.transfer.high: 150.0
input.transfer.low: 92.0
input.voltage: 0.0
input.voltage.nominal: 120
output.current: 260.00
output.frequency: 5990.0
output.frequency.nominal: 60
output.voltage: 0.0
output.voltage.nominal: 120
ups.beeper.status: enabled
ups.delay.shutdown: 20
ups.delay.start: 30
ups.load: 40
ups.power: 288.0
ups.power.nominal: 1300
ups.productid: 3016
ups.status: OL
ups.timer.reboot: 65535
ups.timer.shutdown: 65535
ups.timer.start: 65535
ups.vendorid: 09ae
ups.watchdog.status: 0
On Tuesday, August 18, 2015 5:44 AM, Charles Lepple <clepple at
gmail.com> wrote:
On Aug 17, 2015, at 11:56 AM, Johnny Wong <e430benz98 at yahoo.com>
wrote:>
> > What does that revision number correspond to in FreeBSD release
numbers? (e.g. 9.3, 10.0)
>
> FreeBSD 10.2-RELEASE #0 r286738M
Okay, thanks. I think this is the first report of FreeBSD 10.2, so hopefully it
is not an issue inherent in the OS. I will see if I can upgrade one of my
machines to test with another UPS brand.
> the last person probably wasn't able to give the ./configure probably
because most people uses the precompiled iso to install NAS4Free.? if you need
the ./configure I might have to look for their source on GitHub or something.
True, most people won't need to know the ./configure parameters. It looks
like you found the driver path and the UPS name, so we're set for now.
However, if you run across that part of the source code, it might be useful for
later in case we need to rebuild a driver.
>
> /usr/local/libexec/nut/usbhid-ups -a upstl1300 -DDD
> Network UPS Tools - Generic HID driver 0.39 (2.7.3)
> USB communication driver 0.32
>? ? 0.000000? ? debug level is '3'
>? ? 0.006296? ? upsdrv_initups...
[...]>? 0.013551? ? Checking device (09AE/3016) (/dev/usb//dev/ugen0.5)
>? ? 0.278818? ? - VendorID: 09ae
>? ? 0.278835? ? - ProductID: 3016
>? ? 0.278843? ? - Manufacturer: unknown
>? ? 0.278852? ? - Product: unknown
>? ? 0.278859? ? - Serial Number: unknown
>? ? 0.278867? ? - Bus: /dev/usb
>? ? 0.278876? ? Trying to match device
>? ? 0.278925? ? Device matches
>? ? 0.278937? ? nut_usb_set_altinterface: skipped usb_set_altinterface(udev,
0)
Just for grins, can you try adding "usb_set_altinterface" to the
ups.conf section for your UPS, and see if that changes this part of the log?
(That is, after "[upstl1300]").
>? ? 0.306126? ? HID descriptor, method 1: (9 bytes) => 09 21 11 01 00 01
22 6e 03
>? ? 0.306148? ? HID descriptor, method 2: (9 bytes) => 09 21 11 01 00 01
22 6e 03
>? ? 0.306156? ? HID descriptor length 878
>? ? 5.279939? ? Unable to get Report descriptor: Input/output error
My other concern is that FreeBSD might not allow the method that we use to
retrieve the Report Descriptor.
What do the following commands return (need to run them as root)?
usbconfig -u 0 -a 5 dump_device_desc
usbconfig -u 0 -a 5 dump_curr_config_desc
usbconfig -u 0 -a 5 do_request 0x81 0x06 0x2200 0 0x100
(I'm guessing on "-u 0 -a 5" based on .../dev/ugen0.5 -- that
might change if the UPS USB cable is unplugged and re-inserted.)
> cat /var/etc/ups.conf
> [upstl1300]
>? ? ? ? driver = usbhid-ups
>? ? ? ? port = auto
>? ? ? ? pollfreq = 30
>? ? ? ? productid = 3016
>
> Let me know what other information is required, I'll try my best to
obtain it.
Thanks for sending ups.conf. That's all I can think of for now.
--
Charles Lepple
clepple at gmail
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20150818/3934145b/attachment-0001.html>