On 09.05.2021 21:51, Hans Petter Selasky wrote: [I'M ANSWERING TO BOTH MESSAGES IN THIS ONE]
Could you do: usbdump -i usbusX -f Y -s 65536 -vvv Where X.Y are the numbers after ugen for this device.
I'll do ASAP and return with results, but see below.
Are you certain that NUT only execute exactly the same commands like the windows tool for this UPS?
Of course, not! I'm sure, it is other sequence of commands at least, as NUT has generic driver for many UPSes which share one protocol, and it it not replication of Windows software.
Does apcupsd work for this device too? I've never used NUT myself.
Nope, it is another (not APC-compatible) protocol. > Then connect the device and run nut. nut is very slow in detecting UPSes and it can not "wait" for device to connect, so it simply can not find compatible device, as it is disconnected already. Maybe, I'll be lucky and will be able to "catch" long enough connection for nut to detect UPS and request information at leas one time. > If you don't run nut, does the same attach/detach happen? Oh. Looks like here is miscommunication. attach/detach happens WITHOUT nut on FreeBSD. But it DOESN'T even when software IS NOT installed on Windows. So: (1) Windows WITHOUT Vendor-provided software: NO DETACH, "solid" connection. (2) Windows WITH Vendor-provided software: NO DETACH, "solid" connection. (3) FreeBSD WITHOUT nut: DETACH and re-attech in the loop. (4) FreeBSD WITH nut: try to catch this combination, but it is not-trivial and fragile, not usable in production now, as UPS have detached itself before nut could start typically. -- // Lev Serebryakov _______________________________________________ freebsd-usb@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
