similar to: NUT UPS Driver developer?

[Bill: I think the list server didn't recognize your address below. Forwarding manually.] > From: Bill Elliot <bill at handiwerks.com> > Subject: Initial review of ONEAC driver > Date: February 28, 2012 1:14:27 PM EST > To: nut-upsdev at lists.alioth.debian.org > > > At Arnaud's request, here is the 'svn di' patch for the Oneac driver and > man

In order to get the Oneac UPS (models ON700XAU, ON1000XAU, ON1500XAU) to work with NUT, I had to make a few minor modifications to the oneac driver. I've attached a patch with all the modifications. I tried to ensure that my modifications would not break any existing functionality, but I could not be sure without a legacy Oneac UPS to test against. In my investigation, I found out that the

On Jan 28, 2008 7:47 AM, Arnaud Quette <aquette at alioth.debian.org> wrote: > + * driver.list: add compatibility information for [...] > + - Oneac XAU models Here's an excerpt from my conversation with Jacob Schmier on the Oneac model numbers: "The model numbers you listed (ON700, ON1000, ON1500, ON2000) comprise the Universal-Mount ON Series family (circa 2005). Each

From private E-mail: > > My question to you is how I should go about getting > > the changes back into the system. My work has been exclusively on the ONEAC > > driver and man page. The driver .c file is almost completely redone. > >how can you warrant compat? >Ie, if it's a full rewrite, what have you done to ensure that >currently supported devices will still

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

Tim, The UPS will be a PC104 device (www.rtd.com to give you a quick visual of what that is), which means it will actually be physically stacked together with the power supply it is supporting. So cable length won't be an issue, as it will be communicating through USB in the PCIe bus to the CPU. Rob -----Original Message----- From: Nut-upsdev [mailto:nut-upsdev-bounces+rgroner=rtd.com at

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

Rob - Just out of curiosity, will this device also have any network monitoring connectivity, or just USB? Not sure what market you are targeting, but even as a small business/home compute user, I find that the distance limitations of USB often cause me grief, and myself, I would love to see a network alternative as well . . . Perhaps support for a network dongle on the USB port? More

So, going with the proposed initial design, I created a report descriptor to describe the battery. I thought that I'd then see how NUT responded to it. The good news is that the descriptor showed up and all of the paths were correct. Unfortunately, after that, nothing happened...no reports were requested, and it just kept timing out. Is there some minimum amount of functionality I need to

Hmm...well, after it gets the report descriptor, NUT then gets each of the reports defined in there, so that's good. But after that, there are no more messages (no more reports being requested...the NUT debug info just shows "libusb_get_interrupt: Connection timed out" repeatedly). I put in some enticing values into the report descriptor, like shutdownimminent and discharging and

Success! Turns out NUT was looking for some pretty specific paths, which I printed out to the screen as it looked for them. Once I added some bits in UPS.PowerSummary.PresentStatus.*, then it started checking for those and getting reports. I think I'm finally starting to get it....If I want this UPS to use just the generic usbhid-ups driver, then I'm going to have to structure my

Dear Sir , Can anyone tell me how to upload new ups driver to NUT website ? Best regards, Bluefish [cid:image001.jpg at 01D07C3E.C4ADB780] ?? ?? ?? ?????? ?????(??)???? ??????????107?????467?(?????) ??????5?1?A?2?4? 1-4F, Building 5, YuSheng lndustrial Park, No.467, Section Xixiang, National Highway 107, Xixiang, Bao An District, Shenzhen, China Tel: + 86-755-8601-6601 Ext. 8598 Fax:

Hi, Recently I got three units of this nobreak [0]: The intention is connect it with some file server and/or web server. I found the NUT via FreeNAS [1] , and the contribuition [2] of Ulisses and Rodrigo about this vendor SMS, in Brazil. But, initially, i'm trying to apply the Ulisses patch (for smsbrasil driver) in a Debian Server, with no success. Can anyone help me about the patch in

2010/10/13 Vitaly Lavrov > I found bug in nut/drivers/megatec.c - force shutdown may dont work. > See patch. > could you please give a try to blazer, since it is set to replace megatec with 2.6.0. Arjen will quite probably comment on your patch usefulness within the blazer scope. thanks for your contrib. cheers, Arnaud -- Linux / Unix Expert R&D - Eaton -

please subscribe to the list: http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev On Feb 19, 2014, at 7:52 AM, Thiago Tiedtke dos Reis wrote: > If I try to access the port /dev/ttyUSB0 using minicon (minicom -D /dev/ttyUSB0) or cat ( cat /dev/ttyUSB0 ), the access to device is denied. even as root? > Then, I try these instructions [0], but nothing changes when I try to

Hi Elio, once more, your email was blocked due to the 40 Kb limits... note that here, NUT Monitor screenshots were not needed. upsc output is sufficient. From: Elio Parisi <E.Parisi at riello-ups.com> > To: "nut-upsdev at lists.alioth.debian.org" < > nut-upsdev at lists.alioth.debian.org> > Cc: > Date: Fri, 23 Nov 2012 15:05:49 +0100 > Subject: Riello patch

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

Hello I'm new on this list, nice to meet you My configuration : OS : Ubuntu server 10.04.1 LTS NUT : nut 2.4.3-1ubuntu3.1 from Ubuntu package UPS : APC Back-UPS ES 530 My problem : When restarting twice nut in the same time. I can see 2 instance of /lib/nut/usbhid-ups driver when using : ps aux | grep usbhid-ups I know that's not normal to restart nut twice at the same moment but it

Things are going along well, but there is one remaining area of confusion...."units". I understand exponents now...it's basically how you pass decimal values. That's easy enough. But "units"....in other words, I have a voltage I want to put in a report. If I include in the report descriptor the fact that it is actually a voltage, with units of "volts",

Hi Charles, I'll try the blazer_ser and the nutdrv_qx with version 2.7.1 later. Below, the result of 'lsusb -vvv' requested: Bus 004 Device 002: ID 04b4:5500 Cypress Semiconductor Corp. HID->COM RS232 Adapter Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.00 bDeviceClass 0 (Defined at Interface level)