search for: upslink

...ure since I'm just opening this "APC Modbus Pandora box" >> but if I understand correctly, your new unit is a microlink one. >> > > MAYBE. > > HIS UPS is a BackUPS not a SmartUPS. Originally the APC BackUPS DID NOT > SUPPORT any Smart protocol (the original UPSLink protocol) > > But over the years it's been observed that APC has somewhat "fudged" on > the BackUPS UPSes. Newer ones did appear to implement the UPSlink > protocol over USB. > > Microlink protocol is officially only for APC SmartUPSes. Officially, > what your s...

...ansion card, as I've seen in the > Hardware compatibility list page ? It sounds like you might need the AP9620: http://news.gmane.org/find-root.php?message_id=512C533A.8010706%40sagebrushnetworks.com Otherwise, I imagine that the DB9 just provides serial Microlink, instead of the older UPSLink protocol that the 'apcsmart' driver supports. Also, I don't think we have any confirmation of the variables that the AP9620 provides. Here is the list of full 'upsc' output for various APC models: http://buildbot.networkupstools.org/~buildbot/cayman/docs/latest/ddl/APC/inde...

> Also, I don't think we have any confirmation of the variables that the AP9620 provides. Here is the list of full 'upsc' output for various APC models: > > http://buildbot.networkupstools.org/~buildbot/cayman/docs/latest/ddl/APC/index.html Frantz, Actually, it would be useful if you could send a copy of the output of 'upsc', 'upscmd -l' and

Hi Eric, sorry for the lag, summer time... I'm first seconding Charles comments 2014-07-09 12:31 GMT+02:00 Eric S. Raymond <esr at thyrsus.com>: > I think the time for me to get involved in NUT documentation has come > again. > welcome back > Late last week I had to buy a UPS under time pressure. The Eaton unit > that thus project gifted me with in 2006(?) died

...------------------------------------------------------------- Following the mailing list, I did the "full charge/discharge" to tackle the unsupported combination of battery situation Then I added the following lines to the ups.conf [Numeric] driver = megatec port = /dev/upslink desc = "Numeric 2000 LI" battvolts = 30.4:41.0 lowbatt = 25 Now "upsc Numeric" command returns the following: $ upsc Numeric battery.charge: 100.0 battery.voltage: 41.00 battery.voltage.nominal: 36.0 driver.name: megatec driver.parameter.battvolts: 30....

I think the time for me to get involved in NUT documentation has come again. Late last week I had to buy a UPS under time pressure. The Eaton unit that thus project gifted me with in 2006(?) died during a severe thunderstorm watch, so it was off to MicroCenter to get a replacement pronto. I wound up buying an APC BN700MC. It was what they had in the performance range I needed. The removable

On Jul 9, 2014, at 6:31 AM, Eric S. Raymond <esr at thyrsus.com> wrote: > What I'd like to do is this: confer in real-time, perhaps via IRC, > with someone who knows this process. Ask about every step (thought > processes and diagnostics). *Write them down* and turn this into a > document on how to qualify and support a new device. Happy to help, but scheduling something

...a > proprietary MODBUS-over-USB protocol that they have not publicly > documented [1]. That is not true. The MODBUS protocol has been documented by APC and the open source apcupsd program supports it. The proprietary protocol APC uses is yet another protocol they call microlink. And the UPSLink protocol that NUT supports is still available via use of an add-on card. Plus, many of the APC UPSes (the backups line) are simple UPSes and don't use either the smartlink or the modbus protocol they use a variant of the old upslink over usb. Someone could write a driver for MODBUS for NUT...

Le Tue, 16 Dec 2014 20:38:50 -0500 Charles Lepple <clepple at gmail.com> ?crivait: > On Dec 16, 2014, at 9:45 AM, Frantz de Germain <frantz at info.univ-angers.fr> wrote: > > > Bye the way I just realize that I can't retrieve the ups.load, among other > > thing :-( > > To the best of my knowledge, Microlink is not supported by any third-party tools

On Dec 16, 2014, at 9:45 AM, Frantz de Germain <frantz at info.univ-angers.fr> wrote: > Bye the way I just realize that I can't retrieve the ups.load, among other > thing :-( To the best of my knowledge, Microlink is not supported by any third-party tools (including NUT), but some variables are exposed via standard USB HID. Apparently, ups.load is not one of them. Your UPS might

...s is the non-managed UPS market, the so-called "desktop" UPSes that are 500va or less with runtimes of less than 5 minutes, fully loaded. With more expensive UPSes, other factors than marketing against a competitor are more important. Some of these factors are: Protocols like APC's UPSLink predate USB Power-HID USB Power-HID also does not carry all datapoints that a UPS maker may want to make available Older mainframes did not have USB only Serial. A modern UPS maker may want to produce new UPSes that work with older equipment. There is no public standards-body standard for UPS d...

...the so-called "desktop" UPSes that are > 500va or less with runtimes of less than 5 minutes, fully loaded. With > more expensive UPSes, other factors than marketing against a competitor > are more important. > > Some of these factors are: > > Protocols like APC's UPSLink predate USB Power-HID > > USB Power-HID also does not carry all datapoints that a UPS maker may > want to make available > > Older mainframes did not have USB only Serial. A modern UPS maker may > want to produce new UPSes that work with older equipment. > > There is no pub...

Dear Hyouko, Thank you very much ! Best regards, Bluefish -----????----- ???: hyouko at gmail.com [mailto:hyouko at gmail.com] ????: 2015?4?23? 7:25 ???: ??(bluefish_wei) ??: nut-upsdev at lists.alioth.debian.org ??: Re: [Nut-upsdev] How to upload new ups driver to NUT 2015-04-21 8:23 GMT+02:00 ??(bluefish_wei) <bluefish_wei at voltronicpower.com.cn>: > Can anyone tell me how to