similar to: oneac driver patch

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

I have a V96 and have access to a V92 ON series UPS. I can tell you right off the oneac drivers don't see the family OZ with V96 responds with. I'd be willing to help out with this driver as I have a data center full of them plus one at home. However my C is weak. William

[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

Folks Has anyone any experience with these? http://www.automation.siemens.co.uk/main/business%20groups/power/ups/products/ups%20systems/single%20phase/ http://www.automation.siemens.co.uk/main/business%20groups/power/ups/products/ups%20systems/single%20phase/Siemens%20leaflet%20UPS%20Series%20A.pdf They look a very solid machine, I've got a chance to pick one up for NZ$50 with an extra

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

Hi all. I'm working on an update to the ONEAC driver and have a request from a user that I am not sure how to handle. The UPS can be communicated with through a couple different methods (e.g. Serial, network). If a UPS shutdown command comes through the network interface, the user wants NUT (serial connection) to signal the supported systems to shutdown. What is the "right"

Hi Arnaud, Hi Scott, Hi list, Here is a patch to support the Zinto D from ONLINE USV-Systeme AG. I already sent a version to Russell Kroll (2006-04-09), without no response and I cannot find support for Zinto in svn until now. I found a discussion on this list about the Xanto from ONLINE, but the Zinto seems to use different commands. The commands are quite similar to those for Opti-UPS, so I

I get the following error on r809 (but it looks like the code change happened here). Does HIDDevice_t need to be defined/changed in one of the headers? if gcc -DHAVE_CONFIG_H -I. -I../../drivers -I../include -I../../include -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/hal -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -DINET6 -O2 -D_REENTRANT -DNETSNMP_USE_INLINE -Wall -Dlinux -I.

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

I'm looking for someone who might be interested in enriching the ONEAC UPS driver in the NUT library. Should be someone who has done NUT UPS driver dev before and likes working with a really good UPS. Email me back at this address or ... david at oneac.com thx -------------- next part -------------- An HTML attachment was scrubbed... URL:

An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20120214/96cc8043/attachment.html>

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

I tested your fix (newhidups -DDD /dev/null) using both and APC Back-UPS 350 an APC Smart-UPS RT 2000 XL. No more segmentation fault due to the fixed-size array. ~Jacob -----Original Message----- From: nut-upsdev-bounces@lists.alioth.debian.org [mailto:nut-upsdev-bounces@lists.alioth.debian.org] On Behalf Of Peter Selinger Sent: Monday, October 16, 2006 12:12 PM To: Schmier, Jacob Cc: NUT

--- Arjen de Korte <nut+users at de-korte.org> wrote: > > > I also did: > > > > # ./megatec_usb -DDDDD -x vendor=06da -x mfr=OMRON > > /dev/usb/hiddev0 > > Please have a look at 'man 8 megatec_usb' again. > > You probably need to specify the '-x vendorid' and > '-x productid' options > and most likely, the

--- Arjen de Korte <nut+users at de-korte.org> wrote: > > > I also did: > > > > # ./megatec_usb -DDDDD -x vendor=06da -x mfr=OMRON > > /dev/usb/hiddev0 > > Please have a look at 'man 8 megatec_usb' again. > > You probably need to specify the '-x vendorid' and > '-x productid' options > and most likely, the

This is the patch to include SVN revision level in version number displays. There should be two enclosures; the patch itself and a new source file. common/upsversion.c. upversion.c defines a single function. upsversion(), that returns a version string for display. Some Makefile trickery ensures that this file will be recompiled whenever the project's SVN revision level has changed since it

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

I ran into the following issue today and would like some feedback from the group. Setup: I am using a MGE Pulsar Evolution 2200 UPS connected through a Belkin (F5U218-MOB) 4-Port USB Hub. Scenario: The newhidups subdriver_matcher function calls belkin_subdriver->belkin_claim. The belkin_claim function in belkin-hid.c matches the VendorID of the hub to Belkin's VendorID (0x050d), causing

Dear Andreas, some googling revealed, you created a driver for the xanto series of online-usv.de. In what state it is currently? I've to manage a S2000 and would like to use nut for it, is it usable by now? Do you need another tester? TIA, Pete

Hi, I'm having a hard time configuring a Mustek Powermust 600VA ups to work via USB with nut. I read somewhere that nut works OK via the rs232 cable, but unfortunately I don't have a COM port in my computer. The kernel detects the ups as an Xbox pad :) and loads the xpad module. I tried running /lib/nut/megatec with different /dev/ttySx but it displays megatec protocol UPS was not