[Nut-upsuser] Info for decoding report from UPS

[Jim Klimov]

So, do you plan to write some new program for that UPS instead of trying to
use NUT? (Note there are also regular Windows builds on CI - with some
caveats so far).

I'm commuting now so can't find links easily, but can suggest you to peruse
the issue/PR tracker, there's a discussion about an SMS Brazil device with
links to PoC Python "driver" that's relatively straightforward. Or read up
NUT drivers, nutdrv_qx, blazer, and some others for megatec protocol
dialects. NUT website should have a protocol library with formal
definitions for some of those.

But really, not reinventing the wheel (at least, checking if ours does
roll) might be the faster option ;)

Jim


On Thu, Sep 14, 2023, 13:07 Alessandro Mandelli <mandelli.alessandro at ngi.it>
wrote:

> Thanks. I forgot to mention I am developing in c# for Windows.
>
> Porting or using existing ports seems like an effort with swinging results.
>
> My prototype 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 <jimklimov+nut at gmail.com>
> *Inviato:* giovedì 14 settembre 2023 11:48
> *A:* Alessandro Mandelli <mandelli.alessandro at ngi.it>
> *Cc:* nut-upsuser at 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 of a loosely similar product.
>
>
>
> Try following
> https://github.com/networkupstools/nut/wiki/Building-NUT-for-in%E2%80%90place-upgrades-or-non%E2%80%90disruptive-tests
> for example, to check if it would "just work" now?
>
>
>
> Jim
>
>
>
>
>
> On Thu, Sep 14, 2023 at 9:40 AM Alessandro Mandelli via Nut-upsuser <
> nut-upsuser at alioth-lists.debian.net> wrote:
>
> 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 was able to query the UPS and receive an
> answer, though I am not sure how to decode the report.
>
> The UPS is generic, non branded with VID/PID 0925/1234.
>
> The report is 6 bytes long and raw data look like “0x01 0x04 0x02 0xDE
> 0xFE 0xFF”. (The fifth byte changes now and then).
>
> Any help pointing me to the right decoding table would be much appreciated.
>
>
>
> Cheers
>
> _______________________________________________
> Nut-upsuser mailing list
> Nut-upsuser at alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20230914/2a030154/attachment.htm>