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

2023-09-14 Thread Jim Klimov via Nut-upsuser
One tool for one job :) You can have another protocol client with GUI. NUT includes a python (qt5 or gtk) set of UI clients. On Thu, Sep 14, 2023, 17:06 Alessandro Mandelli wrote: > It works, but I got an allergy for CLI > > > > PS C:\Program Files (x86)\NUT\bin> .\upsc.exe UPS > > device.mfr:

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

2023-09-14 Thread Alessandro Mandelli via Nut-upsuser
It works, but I got an allergy for CLI PS C:\Program Files (x86)\NUT\bin> .\upsc.exe UPS device.mfr: Richcomm dry-contact to USB solution device.model: UPS USB MON V1.4 device.serial: unknown device.type: ups driver.debug: 0 driver.flag.allow_killpower: 0 driver.name: richcomm_usb

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

2023-09-14 Thread Jim Klimov via Nut-upsuser
Ah, I see. My take is that using or adapting something that exists is easier than starting from scratch - but to each their own. Surely you'll learn a lot :) Still, just to clarify: after the NUT v2.8.0 release I began a slow revival of old NUT for Windows effort (abandoned a decade ago at

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

2023-09-14 Thread Alessandro Mandelli via Nut-upsuser
Yeah, existing packages and libraries don’t work for me, introduce overhead and require fiddling well beyond the capabilities of a standard user. I’d like a native win64 app. Anyway, thanks for your help Da: Jim Klimov Inviato: giovedì 14 settembre 2023 13:17 A: Alessandro Mandelli

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

2023-09-14 Thread Jim Klimov via Nut-upsuser
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

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

2023-09-14 Thread Alessandro Mandelli via Nut-upsuser
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

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