search for: schnobel

...gnificant 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 se...

...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.15489...

Attached are config.log and usbhid-ups output with -u root (gzipped). Now driver output looks a lot like the one from port build. On Mon, Aug 20, 2018 at 1:42 PM, Charles Lepple <clepple at gmail.com> wrote: > On Aug 20, 2018, at 1:03 AM, Valentin Merkulov <schnobel at ickis.net> wrote: >> >> 0.033412 [D3] nut_usb_claim_interface: failed to claim USB >> device (Other error). >> 0.033417 [D3] nut_usb_claim_interface: failed to detach kernel >> driver from USB device (Other error). > > I am not as familiar with...

...nterface: failed to claim USB device (Other error). 0.033448 Can't claim USB device 09ae:3016 (Other error). 0.033456 [D1] upsdrv_cleanup... On Mon, Aug 20, 2018 at 4:33 AM, Charles Lepple <clepple at gmail.com> wrote: > On Aug 19, 2018, at 3:03 PM, Valentin Merkulov <schnobel at ickis.net> wrote: >> >> Here is what I get: >> >> # 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) >> > [...] > > Hmm, that may be an issue...

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.PowerSum...

...1 0x03 0x85 0x36 0x09 0x83 0xb1 0x03 0x85 0x38 0x09 0x8c 0xb1 0xa2 0x85><$(yu&)y+y0 at g!U10u'g!UZu%eU2u%bbiiBFDEGKBFDEGK*yu&by3,4ff7g68> On Sun, Aug 19, 2018 at 9:00 PM, Charles Lepple <clepple at gmail.com> wrote: > On Aug 19, 2018, at 2:04 AM, Valentin Merkulov <schnobel at ickis.net> wrote: >> >> Hi Everyone, >> >> I'm having trouble getting TrippLite SMX1500LCDT to work on FreeBSD >> 11.2, nut 2.7.4 installed from FreeBSD port. >> >> The debug output is rather big when I'm starting usbhid-ups initially, >&gt...

Hi Everyone, I'm having trouble getting TrippLite SMX1500LCDT to work on FreeBSD 11.2, nut 2.7.4 installed from FreeBSD port. The debug output is rather big when I'm starting usbhid-ups initially, Please find that attached (gzipped to comply with message size limit). Subsequently, until I unplug and replug the USB cable, I'm geting a shorter debug output, like this: Network UPS

On Aug 19, 2018, at 2:04 AM, Valentin Merkulov <schnobel at ickis.net> wrote: > > Hi Everyone, > > I'm having trouble getting TrippLite SMX1500LCDT to work on FreeBSD > 11.2, nut 2.7.4 installed from FreeBSD port. > > The debug output is rather big when I'm starting usbhid-ups initially, > Please find that attached (...

On Aug 19, 2018, at 3:03 PM, Valentin Merkulov <schnobel at ickis.net> wrote: > > Here is what I get: > > # 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) > [...] Hmm, that may be an issue on the NUT side, then. (You might see i...

On Aug 20, 2018, at 1:03 AM, Valentin Merkulov <schnobel at ickis.net> wrote: > > 0.033412 [D3] nut_usb_claim_interface: failed to claim USB > device (Other error). > 0.033417 [D3] nut_usb_claim_interface: failed to detach kernel > driver from USB device (Other error). I am not as familiar with this branch (I mostly worked...

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):

With interruptonly the driver output goes into a loop (is it an expected behavior?) After I interrupt the loop and launch the driver again, it would return "No matching HID device found" until I unplug / re-plug USB cable. Gzipped output is attached. > On Wed, Aug 22, 2018 at 3:49 PM Charles Lepple <clepple at gmail.com> wrote: > > After you get access to the UPS, what