similar to: Patch for optiups to support Zinto D from ONLINE

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

Hello, today I'm fighting with a Online Zinto 1000 (lsusb.txt) produced by Phoenixtec/Eaton ;-) http://www.eaton.com/EatonCom/OurCompany/NewsandEvents/NewsList/CT_141334 I have tested different drivers without success (please see attachments usbhid-ups.txt, bcmxcp_usb.txt, blazer_usb.txt) The help got unfortunately time outs (explore.txt)

Hi, today I have tested the Zinto 800 with blazer_ser and blazer_usb on Citrix Server 7.0. Both works fine. upsc-Output (blazer_ser): battery.charge: 94 battery.voltage: 25.70 battery.voltage.high: 26.00 battery.voltage.low: 20.80 battery.voltage.nominal: 24.0 device.mfr: device.model: ZINTO 800 device.type: ups driver.name: blazer_ser driver.parameter.pollinterval: 2 driver.parameter.port:

Hello, I have a Yunto e a Zanto ups connected with usb with id 06da:0002 and 06da:0601. I have seen that people had some success using megatec driver. But now megatec is replaced by blazer-usb and I am not able to use my upses under nut. Can you help me? Thanks! Mario

Philipp Leusmann wrote: > > Ok, I tried this and my results seem to bet he same as reported. Then I > think I=B4ll have to stick with the windows-driver at least on my main > machine.=20 > Or is there anything I can help to fix this driver? I don't know why we can't read anything from this device. There are many ways in which one could make a buggy device that works with

2006/1/27, Peter Selinger <selinger@mathstat.dal.ca>: > > ... > battery.mfr.date, which is probably the more accurate interpretation. > > I think the naming should be changed to propose both: - battery.date.mfr: Battery manufacturing date - battery.date.change: Battery change date Any comments? Arnaud -------------- next part -------------- An HTML attachment was scrubbed...

Heya, after I bought an OptiUPS VS 575C and discovering it won't work with Linux (silly me) I sniffed the protocol, found out it's very similiar to the protocol in the powercom driver, so I ended up adding support for that UPS to that driver. The patch is against the current git HEAD and works fine for me since weeks now. The shutdown sequence also works fine (on Archlinux). This is my

2006/10/2, Peter Selinger <selinger@mathstat.dal.ca>: > Arnaud Quette wrote: > > > > 2006/9/29, Peter Selinger <selinger@mathstat.dal.ca>: > > > > > I don't really understand the purpose of the "Testing" branch. It has > > > not been touched since July, as far as I can see. I also don't > > > understand NUT's release

On 1/13/07, Peter Selinger <selinger@mathstat.dal.ca> wrote: > > The question is when exactly this should be converted to a number. > > Should this be done in upscli_splitname() or in upscli_connect()? The > > latter would require a change in the prototypes of upscli_splitname() > > and upscli_connect(), and an attendant change in all the existing > > clients.

On 10/15/06, Peter Selinger <selinger@mathstat.dal.ca> wrote: > I have converted NUT's build system to Automake/Libtool. Right now, > the new build system is contained in the "automake" branch, at: Wow... this is really nice. Thanks for taking the time to do the conversion. > drivers/Doxyfile - this seems to belong to Charles. Perhaps >

Charles Lepple wrote: > > On 11/9/06, Peter Selinger <selinger-guest@alioth.debian.org> wrote: > > Author: selinger-guest > > Date: Fri Nov 10 05:57:37 2006 > > New Revision: 578 > > @@ -566,72 +567,72 @@ > > > > AC_MSG_CHECKING(driver path) > > AC_ARG_WITH(drvpath, > > -AC_HELP_STRING([--with-drvpath=PATH], [where to install ups

Oh oops, I see you already did. -- Peter selinger wrote: > > You could send it without "submitting" it. That's the advantage of > patches - they can be discussed. There are lots of eyeballs here that > might see what's wrong. Thanks, -- Peter > > Eric S. Raymond wrote: > > > > Peter Selinger <selinger at mathstat.dal.ca>: > > > I

Arnaud, you changed the "if" part, perhaps you'd like to change the "else" part, too? Changing the output format of HIDDumpTree() has the potential to break the functionality of scripts/subdriver/path-to-subdriver.sh; I don't think it does in this instance, but I have not checked it. Perhaps it would be good to add a comment in the source code as a caution. -- Peter

I have checked in a cleaned-up version of patch #302111 (Belkin support) into CVS. See cvs diff -uN -r before_PSE_2 -r after_PSE_2 to check the difference. Here is the CHANGES entry: Tue Sep 13 20:50:14 UTC 2005 / Peter Selinger <selinger@users.sourceforge.net> - newhidups: added Belkin support. Also added some new variables and instant commands (some of these were already used by

Fellows, back for 4 days, the baby and the mother are now at home, and the father is... hem, well not so fresh ;-) For those interested in some pictures: http://benjamin.quette.free.fr/ 2006/11/16, Peter Selinger <selinger@mathstat.dal.ca>: > ... > Arnaud: could you please amend the instructions on the NUT download > website http://www.networkupstools.org/source.html (Development

On 2/10/06, Charles Lepple <clepple@gmail.com> wrote: > On 2/10/06, Peter Selinger <selinger@mathstat.dal.ca> wrote: > > Charles Lepple wrote: > > > > > > > [...] The only thing I had to correct manually is > > > > that a few of my binary files were inaccurately classified as text > > > > files (and thus subject to the \r\n

[moving to upsdev as it's now off topic for upsusers] 2006/8/30, Peter Selinger <selinger@mathstat.dal.ca>: [snip] > > the threaded method would allow, with some sub-drv config, to launch > > the polling thread and/or the interrupt thread. Either feeding the > > core is not important since the core wouldn't care about that. > > I think is may make sense to

I'm happy to have had a quick look at this thread... 2007/5/17, Peter Selinger <selinger at mathstat.dal.ca>: > ... > as you know, I haven't had much time to work on NUT. Now my wife is > expecting our first baby in 1 week, so I don't think I will get back > to it in the foreseeable future. I didn't knew before! what a good news: all my congratulations to you

I think someone tried this recently, although I cannot find the post any more. It may be helpful, but it is not guaranteed that we will find anything. Could you please keep the discussion on the mailing list? Thanks, -- Peter Philipp Leusmann wrote: > > Wouldn't it help to sniff usb-communication with the windows driver? > > Philipp > > > -----Urspr=FCngliche

Hi James, thanks for the feedback. The output you get seems generally fine, except for battery.voltage: 0.0 and output.voltage: 164.0; these values are consistent with what Phil DeBoest reported. Upsmon normally executes the shutdown command when you reach the "low battery" threshold, as decided by the UPS and/or driver. It does so by looking at ups.status, not battery.charge. --