Re: [Nut-upsuser] Info for decoding report from UPS

2023-09-14 Thread Jim Klimov via Nut-upsuser
: UPS USB MON V1.4 > > ups.productid: 1234 > > ups.serial: unknown > > ups.status: OL > > ups.vendorid: 0925 > > > > > > > > > > *Da:* Jim Klimov > *Inviato:* giovedì 14 settembre 2023 15:21 > *A:* Alessandro Mandelli > *Cc:* Arnaud Quette vi

Re: [Nut-upsuser] Info for decoding report from UPS

2023-09-14 Thread Jim Klimov via Nut-upsuser
e is working, at least as proof of concept. I’d just like some > directions to decode the raw reports. > > > > Thanks for your help. > > > > > > *Da:* Jim Klimov > *Inviato:* giovedì 14 settembre 2023 11:48 > *A:* Alessandro Mandelli > *Cc:* nut-upsuser@alioth-lists.de

Re: [Nut-upsuser] Info for decoding report from UPS

2023-09-14 Thread Jim Klimov via Nut-upsuser
* nut-upsuser@alioth-lists.debian.net > *Oggetto:* Re: [Nut-upsuser] Info for decoding report from UPS > > > > Seems like recent work on nutdrv_qx subdriver armac (merged to master last > month) could handle it, or some older QX drivers like richcomm if it is a > different brew

Re: [Nut-upsuser] Info for decoding report from UPS

2023-09-14 Thread Jim Klimov via Nut-upsuser
Seems like recent work on nutdrv_qx subdriver armac (merged to master last month) could handle it, or some older QX drivers like richcomm if it is a different brew of a loosely similar product. Try following

[Nut-upsuser] Info for decoding report from UPS

2023-09-14 Thread Alessandro Mandelli via Nut-upsuser
Hi, everybody, I just subscribed, though I've been lurking around for some time. I searched for my question in the archive, but I wasn't able to find an answer. Sorry if this question has been asked before. I am in the process of writing an interfacing software. After some trial and error, I