Nut upsuser - Aug 2018 - TrippLite SMX1500LCDT FreeBSD 11.2 trouble

After "No device" error the driver does not seem to be able to
communicate with the UPS (as seen before with the port build):

 # /usr/local/ups/bin/usbhid-ups -a ups -DDDD -u root
Network UPS Tools - Generic HID driver 0.53 (v2.7.4-603-gb14c3b42.7.4.1)
USB communication driver 0.37
   0.000000     [D1] debug level is '4'
   0.002560     [D1] upsdrv_initups...
   0.002748     [D2] nut_libusb_open: checking device 1 of 6.
   0.002813     [D2] nut_libusb_open: - VendorID: 0000.
   0.002819     [D2] nut_libusb_open: - ProductID: 0000.
   0.002823     [D2] nut_libusb_open: - Manufacturer: Intel.
   0.002826     [D2] nut_libusb_open: - Product: EHCI root HUB.
   0.002829     [D2] nut_libusb_open: - Serial Number: unknown.
   0.002832     [D2] nut_libusb_open: - Bus: 001.
   0.002836     [D2] nut_libusb_open: - Device release number: 0100.
   0.002839     [D2] nut_libusb_open: trying to match device...
   0.002847     [D2] nut_libusb_open: device does not match - skipping.
   0.002861     [D2] nut_libusb_open: checking device 2 of 6.
   0.002893     [D2] nut_libusb_open: - VendorID: 0000.
   0.002897     [D2] nut_libusb_open: - ProductID: 0000.
   0.002900     [D2] nut_libusb_open: - Manufacturer: 0x8086.
   0.002903     [D2] nut_libusb_open: - Product: XHCI root HUB.
   0.002906     [D2] nut_libusb_open: - Serial Number: unknown.
   0.002910     [D2] nut_libusb_open: - Bus: 000.
   0.002913     [D2] nut_libusb_open: - Device release number: 0100.
   0.002916     [D2] nut_libusb_open: trying to match device...
   0.002920     [D2] nut_libusb_open: device does not match - skipping.
   0.002930     [D2] nut_libusb_open: checking device 3 of 6.
   0.002960     [D2] nut_libusb_open: - VendorID: 0000.
   0.002964     [D2] nut_libusb_open: - ProductID: 0000.
   0.002967     [D2] nut_libusb_open: - Manufacturer: Intel.
   0.002970     [D2] nut_libusb_open: - Product: EHCI root HUB.
   0.002974     [D2] nut_libusb_open: - Serial Number: unknown.
   0.002977     [D2] nut_libusb_open: - Bus: 002.
   0.002980     [D2] nut_libusb_open: - Device release number: 0100.
   0.002983     [D2] nut_libusb_open: trying to match device...
   0.002987     [D2] nut_libusb_open: device does not match - skipping.
   0.002997     [D2] nut_libusb_open: checking device 4 of 6.
   0.003020     [D2] nut_libusb_open: - VendorID: 8087.
   0.003024     [D2] nut_libusb_open: - ProductID: 0024.
   0.003027     [D2] nut_libusb_open: - Manufacturer: unknown.
   0.003030     [D2] nut_libusb_open: - Product: unknown.
   0.003033     [D2] nut_libusb_open: - Serial Number: unknown.
   0.003036     [D2] nut_libusb_open: - Bus: 001.
   0.003040     [D2] nut_libusb_open: - Device release number: 0000.
   0.003043     [D2] nut_libusb_open: trying to match device...
   0.003047     [D2] nut_libusb_open: device does not match - skipping.
   0.003057     [D2] nut_libusb_open: checking device 5 of 6.
   0.003079     [D2] nut_libusb_open: - VendorID: 8087.
   0.003083     [D2] nut_libusb_open: - ProductID: 0024.
   0.003087     [D2] nut_libusb_open: - Manufacturer: unknown.
   0.003090     [D2] nut_libusb_open: - Product: unknown.
   0.003093     [D2] nut_libusb_open: - Serial Number: unknown.
   0.003096     [D2] nut_libusb_open: - Bus: 002.
   0.003099     [D2] nut_libusb_open: - Device release number: 0000.
   0.003102     [D2] nut_libusb_open: trying to match device...
   0.003106     [D2] nut_libusb_open: device does not match - skipping.
   0.003116     [D2] nut_libusb_open: checking device 6 of 6.
   0.033517     [D2] nut_libusb_open: - VendorID: 09ae.
   0.033531     [D2] nut_libusb_open: - ProductID: 3016.
   0.033536     [D2] nut_libusb_open: - Manufacturer: unknown.
   0.033540     [D2] nut_libusb_open: - Product: unknown.
   0.033543     [D2] nut_libusb_open: - Serial Number: unknown.
   0.033547     [D2] nut_libusb_open: - Bus: 001.
   0.033550     [D2] nut_libusb_open: - Device release number: 0002.
   0.033554     [D2] nut_libusb_open: trying to match device...
   0.033576     [D2] nut_libusb_open: device matches.
   0.033590     [D3] nut_usb_claim_interface:
libusb_kernel_driver_active() returned 0 (no driver active).
   0.033596     [D2] nut_libusb_open: claimed interface 0 successfully.
   0.033601     [D3] nut_usb_set_altinterface: skipped
libusb_set_interface_alt_setting(udev, 0, 0).
   0.043711     [D2] nut_libusb_open: unable to get HID descriptor (No device).
   0.043723     [D2] nut_libusb_open: warning! Couldn't retrieve HID
descriptor with method 1.
   0.043727     [D2] nut_libusb_open: Eaton device v2.02. Skipping
method 2 for retrieving HID descriptor.
   0.043731     [D2] nut_libusb_open: unable to retrieve any HID descriptor.
   0.043762     [D2] nut_libusb_open: no appropriate HID device found.
   0.043768     No matching HID UPS found
   0.043782     [D1] upsdrv_cleanup...

usbconfig commands return the following:

# usbconfig -u 1 -a 3 dump_curr_config_desc

ugen1.3: <Tripp Lite TRIPP LITE UPS> at usbus1, 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, 0x68,
       0x08 | 0x03

     Endpoint 0
        bLength = 0x0007
        bDescriptorType = 0x0005
        bEndpointAddress = 0x0081  <IN>
        bmAttributes = 0x0003  <INTERRUPT>
        wMaxPacketSize = 0x0008
        bInterval = 0x000c
        bRefresh = 0x0000
        bSynchAddress = 0x0000

# usbconfig -u 1 -a 3 do_request 0x81 0x06 0x2200 0 0x100
REQUEST = <ERROR>

On Mon, Aug 20, 2018 at 3:39 PM, Charles Lepple <clepple at gmail.com>
wrote:
> On Aug 20, 2018, at 7:40 AM, Valentin Merkulov <schnobel at
ickis.net> wrote:
>>
>> Attached are config.log and usbhid-ups output with -u root (gzipped).
>> Now driver output looks a lot like the one from port build.
>
> If memory serves, this was the sort of error we were seeing from 3016
devices on Linux:
>
>    0.154899     [D1] Path: UPS.PowerSummary.iManufacturer, Type: Feature,
ReportID: 0x2b, Offset: 0, Size: 8, Value: 3
>    0.167518     nut_libusb_get_report: No device.
>    0.167531     [D1] Can't retrieve Report 30 (No device).
>
> After you see the "No device" error, does the UPS reattach under
a new /dev node? Do the usbconfig commands return any data?
>

I cannot unplug/re-plug USB though, because currently I'm away from
the hardware location.

On Mon, Aug 20, 2018 at 4:07 PM, Valentin Merkulov <schnobel at ickis.net>
wrote:
> After "No device" error the driver does not seem to be able to
> communicate with the UPS (as seen before with the port build):

Understood about unplugging USB - others with the 3016 devices have proposed
various methods with USB hubs that have per-port power switching, etc. to
simulate unplugging. I am not a fan of the concept, but I recognize that others
have made more significant investments than the single UPS that I bought.

After you get access to the UPS, what if you try running the driver with
"interrupt_only"? Reference:
https://github.com/networkupstools/nut/issues/300#issuecomment-414481547
> On Aug 20, 2018, at 9:19 AM, Valentin Merkulov <schnobel at
ickis.net> wrote:
> 
> I cannot unplug/re-plug USB though, because currently I'm away from
> the hardware location.
> 
> On Mon, Aug 20, 2018 at 4:07 PM, Valentin Merkulov <schnobel at
ickis.net> wrote:
>> After "No device" error the driver does not seem to be able
to
>> communicate with the UPS (as seen before with the port build):