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 February 29, 2008 2:56 PM, W. Keith Miller <keith.miller at stonebranch.com> wrote:> > 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 which V96 responds with.The oneac driver in the trunk of the NUT (Network UPS Tools) should see the 'OZ' family. You can see the changeset here: http://boxster.ghz.cc/projects/nut/changeset/1217> 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.What OS are you using NUT on? Can you communicate with the Oneac UPS using MopUPS? You can download a trial version here: http://connectivity.chloridepower.com/download_viewCategory.asp?c=1 Here's how I did it: I did most of my development/investigation on Linux. When my Oneac UPS wouldn't work with NUT, I noticed that the UPS was responding with 'OZ', even though it was an ON series. This is why I patched the driver. I connected the Oneac UPS to MopUPS (the program Oneac told me to use) and looked at the data being passed to/from the UPS over the serial link (strace -x -e trace=open,read,write,close -p <pid>). I saw that MopUPS was writing a few specific characters to the UPS that got a response ('%', '^', and '&' characters). Next, I either modified the oneac driver for NUT or wrote my own application (can't remember which) to send these characters and I printed the responses. I found an ONEAC protocol doc on the NUT website (http://www.networkupstools.org/protocols/oneac.html), but it is a bit old. Someone from Oneac, I won't say who, confirmed to me that this protocol is over 10 years old and only partially supported today. I don't know exactly how much of the protocol is still supported and I don't know what additional data the UPS is sending when it responds to the queries. Since the communication protocol is all ASCII, I figure it can't be too hard to figure at least some of it out. I don't have the Oneac UPS in my possession anymore, so I can't do any further work on this driver. I hope you find this information useful. Jacob
On Friday, February 29, 2008 4:29 PM, W. Keith Miller <keith.miller at stonebranch.com> wrote:> > I use Linux mostly (got some Openbsd too).however we have > MopUPS for windows with a serial cable (now where did that > cable get off too!?).Chloride Power (Oneac parent company) has a Linux versions of MopUPS available as well. These are what I was using along w/ 30 day trial licenses. The packages are RPMs, but I used alien to convert them into formats that suite me. I used a serial (RS232) to USB converter cable (Oneac part number CK-7USBU) to communicate with the UPS because I didn't have any free serial ports. It has a Prolific PS-2303 chip inside it and works wonderfully under Linux.> Mopups has a terminal session you can actually communicate to > the UPS. > Since I have a V96 at home I can pretty much keep Windows > MopUPS and Linux connected to the unit anytime as necessary. > I do remember just running through the ascii character set > and seeing what responses I got back with regard to the > MopUPS display.Interesting. I guess I never got that far with MopUPS. Are the responses also raw ascii? I didn't have time to figure out how all the raw ascii responses I was getting related to the UPS and exactly how much of the old protocol was still supported/accurate.> I'd be happy to lend my UPS and time to get this driver in > good shape. > We have ON900, ON900 Extended Run-time, ON1300, ON2000 V96, > ON2000 V92. > I have more access (put perhaps not share time) to a ON1100 > Rackmount with extended battery.Do your ON900 report themselves as 'ON' family? If so, you can test out the new driver with them as well to make sure I didn't break anything.> I'll have to see if I can get a checkout and compile the new > driver to see how it responds.Let me know how it works out for you.> As a heavy Oneac customer do you think if I asked for the > protocols that might help?I really don't think Oneac will give you their protocols. I met with a few of the higher ups in their R&D organization to discuss it a little over a year ago. They didn't seem to interested unless the company I work for were to partner with them exclusively and sign a NDA. They were even less interested when I mentioned using the information in relation to the NUT project.> William
On Monday, March 03, 2008 11:09 PM, W. Keith Miller <keith.miller at stonebranch.com> wrote:> I also have the Oneac V96 MIB for SNMP. You think the NUT > guys would want that?I believe that Arnaud Quette is the maintainer for the snmp-ups driver, so this would be his decision. I have the MIB for the ManageUPS NET Adapter II used with the Oneac Universal-Mount ON Series. They can be found online in the user manual zip file (http://connectivity.chloridepower.com/files/manual_manageups-ii.zip). I have the SNMP adaptor, but I don't have one of the UM ON Series available to me for testing at the moment. ~Jacob