similar to: Fwd: Initial review of ONEAC driver

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

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

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

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:

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"

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

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

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

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

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

Hi, To to build an RPM from the nut 2.0.3 source I've corrected the old nut.spec.in file. Please find a copy of the slightly updated spec file attached. The changes are documented at the bottom of the spec file. Regards, Will -------------- next part -------------- # don't know how different I can do this %define majorver 2.0 %define version 2.0.3 %define relver 1 %define nutuser

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

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

--- 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

LinkedIn ------------ Carter Cheng requested to add you as a connection on LinkedIn: ------------------------------------------ Jian, I'd like to add you to my professional network on LinkedIn. - Carter Accept invitation from Carter Cheng

automx I am pleased to announce automx a tool that makes setting up a mail account easy. All your users need to provide is real name, mail address and password. Their mail client and automx will safely handle the rest. Say goodbye to mistyped server settings! Put an end to endless phone calls trying to coach users to configure settings, whose dialogs they can't find. Raise user satisfaction,