similar to: etapro driver

Hello NUT ! In order to fill info structure I'm putting in the drivers, I need to gather a lot of information. The information I need, at best, is : - For each USB UPS, the pair VendorID ProductID - For each pair Driver/UPS supported, how was made the driver ? By the manufacturer, by reverse engineering, ... - Who contributed to which driver - Who is the "maintener" of each driver

Hi everyone, I'm new in the upsdev team, nice to meet you ! I'm currently doing an internship at MGE UPS, working with Arnaud Quette for the NUT project. I'll work for 2 months on the reworking of the configuration files for NUT and creation of libupsconfig and upsconfig libraries. (task 280 and 281 of the NUT project) My planning is as follow : Week 27 : Become used with the

It seems the `libmodbus` library or headers were not found, or something similar - so the driver against it was not built. Did you install `libmodbus-dev` before the build? What does `config.log` in the build root say (and.or the summary shown after you run the `configure` script)? On Sat, Sep 16, 2023 at 7:46?PM FatGear <fatgear1 at free.fr> wrote: > Hi, > > I don't know what

Hello there, I don't think that's working,? I have done all your repo but i don't know how it's supposed to work. I have a idea, change vendor id and product id? to make the driver try to connect to the ups, what do you think of that ? With this driver maybe : usbhid-ups FatGear Le 16/09/2023 ? 20:40, Jim Klimov a ?crit?: > It seems the `libmodbus` library or headers were

Just a little tiny detail : ============================================================================== > --- trunk/scripts/hotplug/libhid.usermap (original) > +++ trunk/scripts/hotplug/libhid.usermap Fri Aug 25 19:18:19 2006 > @@ -21,5 +21,7 @@ > libhidups 0x0003 0x09ae 0x1003 0x0000 0x0000 0x00 0x00 0x00 0x00

Hi fellows, I would like to welcome a new member in the Development Team: Jonathan Dion, who is a trainee engineer from the ENSIMAG school, and who will work on the Configuration sub project. He will soon post a draft specification (off list link) to start discussing that subject. This sub project has long been postponed, and I'm sure Jonathan will produce good work on this, allowing us to

Hello ups-dev Arnaud asked me to add a function upsdrv_print_ups_list the drivers upsdrv_print_ups_list : why This function would print the vendorId and the productId of the UPS supported by the driver (for USB driver at least). It could then be parsed by a tool (that I'll have to make too), whose the goal would be to automagically generate 4 sort of file : - fdi file for HAL - udev rules

Hello nut-upsdev ! It's me again ! Since my last email about the new formalism for NUT configuration files, no objection was drawn. I propose then to make official this new formalism. Here can be find the grammar of the formalism : http://opensource.mgeups.com/projects/nut-config/grammar.od I made a parser for the new formalism and put sample files and a test program on my branch (JD-NewConf

Well, now that the `subdriver` option got added to `usbhid-ups` too, you can at least try that (by building again the current master). See command-line help for the subdrivers it would currently recognize, and copy e.g. the first word as the matching option, e.g.: ./drivers/usbhid-ups -DDDDDD -d1 -s test -x port=auto -x vendorid=... -x productid=... -x subdriver=... and try to lockpick your

Hi ups-dev ! I bring you some news about my work : it works ^_^ you can now try out the new configuration formalism. I modified upsd, the drivers and upsmon to use the new formalism and the new parser (via the libupsconfig library) The SVN link : svn co svn://svn.debian.org/nut/branches/JD-NewConf How to use it : To test it, I propose that you execute the following commands : Go to the

On Jun 17, 2019, at 3:00 PM, David Zomaya <David_Zomaya at tripplite.com> wrote: > > Hi Network UPS Tools Support, > > I’m not sure if this is a question for the “user group” or the developer group”. The config files will be useful for -users, but I'd say the development list is probably better for discussing potential changes. > My name is David Zomaya and I work at

Hello All, This is my first post to the list & I have tried to do as much searching and debugging on my own as I can bear. Please HELP! I am currently using up to date Centos 5.2 32-bit - kernel version: 2.6.18-92.1.10.el5PAE #1 SMP. I am using a Tripplite OMNIVS1500 via usb connection. I am using the tripplite_usb driver. I have tried to user versions 2.2.0 from an rpm, 2.2.2 & and the

To try and work through the initial drops, I repeated the previous steps that worked on the physical machine on the CentOS 7.6 virtual machine. The drops continued to occur, but it seems that the driver always reconnects. My initial inclination is to work through and see at what point I get the drops to stop, and I think I will do that next (inputs welcome). From a standpoint of “how much does

Hi Charles and Jonathan, I am going through my over 300 unread NUT messages, and I just discovered this one from mid-December. At the time, I was trying to clean up the tripplite subdriver of newhidups, but never got the information I needed. I have enabled this driver now, but it is marked "experimental". The driver is still incomplete, in the sense that there are many unmapped device

Hi Jonathan and Charles, yes, the Tripp-Lite HID subdriver was under development. I started it based on the debug output posted by somebody on this list a few weeks ago, but then I either didn't get the information I needed, or got too busy to act on it. That driver is still incomplete, in the sense that there are many unmapped device variables. Jonathan, if you run this driver, could you

Hello There, I tried your advice and i don't think it works either, See the logs, " /tmp/nut# ./drivers/usbhid-ups -DDDDDD -d1 -s test -x port=auto -x vendorid=... -x productid=... -x subdriver=... Network UPS Tools - Generic HID driver 0.52 (2.8.0-2557-g81fca30b2) USB communication driver (libusb 1.0) 0.46 ?? 0.000000??? [D3] main_arg: var='port' val='auto' ??

<facepalm ;)> the ellispis "something=..." were supposed to be replaced by your device ID numbers, etc. On Sat, Sep 23, 2023, 18:26 FatGear <fatgear1 at free.fr> wrote: > Hello There, > > I tried your advice and i don't think it works either, > > See the logs, > > " > > /tmp/nut# ./drivers/usbhid-ups -DDDDDD -d1 -s test -x port=auto -x

Here is the general procedure to do this: First, you must compile nut yourself on ubuntu, with the patch, then rename the existing NUT binaries to backup files and copy over your modified binaries to where the original binaries were. However, since these patches are local, if the nut package maintainer for Ubuntu releases a new package, your patches will be overwritten. To fix this, after you

Unfortunately I do not use the latest versions of NUT, the driver I created, solis, was changed, not by me, and now does not work on my nobreak, which I used to create the driver. greetings Silvino B. Magalhaes Em qua, 19 de jun de 2019 às 03:39, Manuel Wolfshant < wolfy at nobugconsulting.ro> escreveu: > On 6/19/19 5:59 AM, Charles Lepple wrote: > > > “The

Hi, First of all I'd like to congratulate everyone engaged in this great project. I've been following this list since late 2014, when I acquired an APC UPS model BZ1200BR. APC bought a Brazilian company named Microsol, which NUT package had drivers for Solis and Rhino models. Since that time, I started developing a new driver for the models below, as a way to support my own device, but