similar to: New APC "SMT" UPSes support MODBUS, will there be support in NUT?

Hello Ted, 2013/9/11 Ted Mittelstaedt <tedm at mittelstaedt.us> > Hi All, > > About a month ago APC announced they were including MODBUS protocol > support in their new APC UPSes. The technical note on this is here: > > http://www.apcmedia.com/**salestools/MPAO-98KJ7F/MPAO-**98KJ7F_R0_EN.pdf<http://www.apcmedia.com/salestools/MPAO-98KJ7F/MPAO-98KJ7F_R0_EN.pdf>

> I suspect you will want the newer version for production (there was some > issue regarding the popups when certain events happen), but let's get this > version working first before changing another variable. Appreciate that. Agreed. > For reference, I think the source code to NUT.exe is here: > https://github.com/networkupstools/nut/blob/Windows-v2.6.5- >

Hi! I was wonering if there is a driver that supports communicating with a Modbus aware device over IP. I have a solar/wind invertor that can broadcast its state and I would like to monitor the batteries. If they discarge to a certain voltage or come to a defined state, I would perform a shutdown. All of this information id provided in Modbus holding registers. This could of course be done

Hi I installed a program through Wine without much of a problem But then It flashes a Error message Saying "Microsoft Visual C++ Runtime Error" I assume I need to install the Visual C++ libraries through WineTricks. to at least to try to fix the Problem I got Winetricks installed and Ready...I think. Now I just need a walkthrough on how to install the Visual C++ Libraries through

Hi Ted there was a drift from the initial topic. worth a new thread! 2014-07-27 9:13 GMT+02:00 Ted Mittelstaedt <tedm at mittelstaedt.us>: > On 7/26/2014 12:18 PM, Arnaud Quette wrote: > >> 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

Hello, this is to let you know I will start working on a modbus driver for the PhoenixContact QUINT-UPS industrial DC UPS, model 2320461. https://www.phoenixcontact.com/online/portal/us?uri=pxc-oc-itemdetail:pid=2320461&library=usen&pcck=P-22-07-01-01&tab=1 I will reuse some parts of the nutdrv-modbus branch, but this will be a model specific driver, not a generic one. Unfortunately

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

On Jul 9, 2014, at 11:24 AM, Ted Mittelstaedt <tedm at mittelstaedt.us> wrote: > Someone could write a driver for MODBUS for NUT, all of the information > and materials are available to do it. The simple fact of it is that the > reason no one has done so is that the apcupsd program is available. You're right, it's the microlink protocol that they have been promising to

Hello, I have tried to use the blazer_ser driver to interface with my UPS. nut is not able to detect the UPS. I have not been able to find much info regarding Socomec UPS support in nut. Socomec does publish a description of the serial protocol for these UPS's, which can be found here: http://www.socomec.com/download-jbus-modbus.html(select UPS OTHER for device model, 1-5KVA for device power

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 7/9/2014 6:51 AM, Charles Lepple wrote: > 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

On 7/9/2014 4:16 PM, Charles Lepple wrote: > On Jul 9, 2014, at 11:24 AM, Ted Mittelstaedt<tedm at mittelstaedt.us> > wrote: > >> Someone could write a driver for MODBUS for NUT, all of the >> information and materials are available to do it. The simple fact >> of it is that the reason no one has done so is that the apcupsd >> program is available. > >

Yeah, I have its datasheet (it's a Xantrex XW invertor by the way). I do not know why creating a more-or-less generic driver is an issue. Of course, there are Modbus beasts that can scare everyone but mostly one would need to read either intreger or float numbers out of Modbus registers in order to decide whether or not to start or stop the shutdown process. 24 ???? 2017 ?. 19:25:14

Hello mailing List. I manage 2 UPS via NUT, an APC Smart-UPS_1500 and an ?EATON 5S 1500. I can get load information on the EATON but not on the APC. Actually upsc doesn?t give much information on the APC. Does someone know whether this is a driver limitation or a configuration issue ? Many thanks for your views. Laurent PS: my goal is to monitor the UPS and raise alarms if upsc detects

d tbsky <tbskyd at gmail.com> > > Laurent Taieb via Nut-upsuser > > > > Hello mailing List. > > > > I manage 2 UPS via NUT, an APC Smart-UPS_1500 and an EATON 5S 1500. > > > > I can get load information on the EATON but not on the APC. > > > > Actually upsc doesn?t give much information on the APC. > > > > Does someone know

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

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

Le Tue, 16 Dec 2014 15:36:29 +0100 Frantz de Germain <frantz at info.univ-angers.fr> ?crivait: > Hello, > > I'm testing an APC SMT3000RMI2U connected to an USB port with Nut 2.7.2. I've > got the message : > > "interrupt pipe disabled (add 'pollonly' flag to 'ups.conf' to get rid of this message)" > > I've been looking for

On Jan 9, 2020, at 4:39 PM, Gene Heskett <gheskett at shentel.net> wrote: > > So for starters, what's the best ./configure command line? There’s this page for matching the layout of an existing Debian install: https://github.com/networkupstools/nut/wiki/Building-NUT-on-Debian,-Raspbian-and-Ubuntu But remind me, what are you hoping to get from the later version of NUT? (We don’t

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