similar to: nut-scanner -U: device requirements

Hello there, I am currently developing a USB HID device (HID Power Devices approach). I need to build up the whole HID Power device stack (not from scratch, generic HID is working as I am basing the code on the TinyUSB library). I was wondering whether there is any tool or approach you guys could propose for testing/ development of the device? I don't assume that there is any tool out

Hello there, I am coming to this mailing list as suggested in the Github repo issues panel: https://github.com/networkupstools/nut/issues/1873#issuecomment-1475408950 I would like to create a new UPS device that communicate with the outer world over USB. The USB protocol can be either CDC serial or HID. I am looking for an existing protocol that can be legally used by me, so I don't need

On 2023-03-20, ?ukasz Przenios?o <lukasz at przenioslo.com> wrote: > I would like to create a new UPS device that communicate with the outer=20 > world over USB. The USB protocol can be either CDC serial or HID. I am=20 > looking for an existing protocol that can be legally used by me, so I=20 > don't need to come up with a new protocol + ask anyone to add any new=20 >

Hi, I didn't see in the HCL any Vertiv support. The specific unit I'm considering is: ( https://www.amazon.com/gp/product/B07BYD6RLN) - "Vertiv Liebert PSA5 1500VA 900W line-Interactive UPS with AVR Technology and Battery Backup, 10 outlets and Three-Year, Full Unit Replacement Warranty (PSA5-1500MT120)" Has anyone worked with this (or even UPS from Vertiv) and had success (or

Hi all, I use libvirt-go in my agent to attach rbd volumes. I ofen suffer the issue of incosistent of domain dump xml and domain persistent xml file. For example, when I try to attach volume, the the domain by ?virConnectListAllDomains? api from libvirt tell me the vdf or 0x0a is empty, but when attach it with the vdf device or 0x0a address, qemu return the error duplicated with vdf or PCI

Well thanks, The solution for my problem was kinda easy (still need some testing though): found out my ups status is a string, so then I changed the way snmp-ups.c gets the status. Had to change *nut_snmp_get_int *to *nut_snmp_get_str *at around line 3470, then grab fourth char out, use *strtol *function to then send it to *su_status_set *function. I created my copy of *apc-mib.c *with my OID at

Dear R-devel, I did a systematic comparison of write.csv with similar functions, and observed two asymptotic inefficiencies that could be improved. 1. write.csv is quadratic time (N^2) in the number of columns N. Can write.csv be improved to use a linear time algorithm, so it can handle CSV files with larger numbers of columns? For more details including figures and session info, please see

Looking at this code, it's way more than I was looking for, too. I just need a replacement for the in-tree driver. I have a volume. I have about a half dozen pods that use that volume. I just need the same capabilities as the in-tree driver to satisfy that need. I want to use kadalu to replace the hacky thing I'm still doing using hostpath_pv, but last time I checked, it didn't build

One good intro to this is https://github.com/networkupstools/nut/blob/master/docs/snmp-subdrivers.txt although it focuses on adding new subdrivers - but more or less the same workflow applies to extending existing ones. Sometimes it helps to generate a new one for a currently-partially-supported device, and then compare with existing subdriver (using meld or similar GUI helps a lot) to port the