[Nut-upsdev] Aegis protect d3000

[Jim Klimov]

uHello and welcome!

  I've seen similar behavior when libusb (used by the NUT driver here)
could not take full control of the USB device node (something else in the
OS or pass-throughs of a virtualization stack "owned" it too).

  Check if nut-driver.service start-up logs (assuming systemd-aware
packaging), or /var/log/syslog or /var/log/messages complain about
something like this.

  Alternatively, stop the NUT service and run the driver program from
command line with added debug verbosity option, e.g.:

  usbhid-ups -a ups -DDDDDD -d 1

(not sure OTOH if `-d` option was in NUT 2.7.4 already - it lets the driver
collect data, print it out and exit after e.g. 1 loop cycle; if not - these
datapoints would be seen as "dstate" changes in the debug trace).

  This might glean some light onto why it won't see more info. Maybe MGE
HID is not a suitable USB mapping table, etc.

Also note that 2.7.4 is a rather old release of NUT. Consider getting a
newer package or building your own from source.

Jim


On Wed, Feb 7, 2024, 07:49 MAGNAVAL Adrien via Nut-upsdev <
nut-upsdev at alioth-lists.debian.net> wrote:

> Hi, first sorry for my English but it’s not my native language.
> I tried nut v 2.7.4 to get monitoring my arg protect d3000 ups via usb
> I use several drive in the liste but, only usbhid-ups get some info and
> work
> But the are not a lot of inforoot at DARYL:/home/magade# upsc ups
> Init SSL without certificate database
> device.mfr: PPC
> device.model: USB UPS
> device.type: ups
> driver.name: usbhid-ups
> driver.parameter.pollfreq: 30
> driver.parameter.pollinterval: 2
> driver.parameter.port: auto
> driver.parameter.productid: 0003
> driver.parameter.synchronous: no
> driver.version: 2.7.4
> driver.version.data: MGE HID 1.40
> driver.version.internal: 0.41
> ups.mfr: PPC
> ups.model: USB UPS
> ups.productid: 0003
> ups.status: OB
> ups.vendorid: 06da
> root at DARYL:/home/magade# upsc ups
> Init SSL without certificate database
> device.mfr: PPC
> device.model: USB UPS
> device.type: ups
> driver.name: usbhid-ups
> driver.parameter.pollfreq: 30
> driver.parameter.pollinterval: 2
> driver.parameter.port: auto
> driver.parameter.productid: 0003
> driver.parameter.synchronous: no
> driver.version: 2.7.4
> driver.version.data: MGE HID 1.40
> driver.version.internal: 0.41
> ups.mfr: PPC
> ups.model: USB UPS
> ups.productid: 0003
> ups.status: OB
> ups.vendorid: 06da
>
> Also, my ups is in dual conversion mode so perhaps it is normal to get
> this :ups.status: OB
>
> Please, may you help me to get it work, I’m not a dev but only only linux
> user. I will do my best to make what you need to test some cmd.
> If it is useful, I can try to monitoring USBMon with Wireshark or other
> stuff like that.
>
> Many thanks in advance
>
> _______________________________________________
> Nut-upsdev mailing list
> Nut-upsdev at alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsdev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/nut-upsdev/attachments/20240207/ead5de7c/attachment-0001.htm>