similar to: APC SMC1500 question

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

Thanks d tbsky, Actually, my nut server is connected via usb. APC looks to be a very common UPS brand. I wonder whether there is another version of the usbhid server or another server for this UPS ? Laurent ?Le 25/05/2024 07:00, ? d tbsky ? <tbskyd at gmail.com <mailto:tbskyd at gmail.com>> a ?crit : d tbsky <tbskyd at gmail.com <mailto:tbskyd at gmail.com>> > >

Laurent Taieb <laurenttaieb at free.fr> > > Thanks d tbsky, > Actually, my nut server is connected via usb. APC looks to be a very common UPS brand. > I wonder whether there is another version of the usbhid server or another server for this UPS ? > > Laurent if you want to use full usbhid, you need to find APC models which support it(like Back-UPS Pro). normally newer

Thanks tbskyd As the UPS also communicates via Ethernet, I was wondering whether some non usb drivers would have been developed to collect ups data. Right now, I?m only getting basic emails from APC when the ups is on battery or back to power. Thanks Laurent > Le 25 mai 2024 ? 14:10, d tbsky <tbskyd at gmail.com> a ?crit : > > ?Laurent Taieb <laurenttaieb at free.fr>

Gene's posting: https://alioth-lists.debian.net/pipermail/nut-upsuser/2020-January/011654.html contains a NUT 2.7.4 update for the APC Smart-UPS_1500 device dump at https://networkupstools.org/ddl/APC/Smart-UPS_1500.html Please note the changes since the 2.7.2 report, e.g. ups.delay.start is no longer supported. Roger

Is that with both UPSes on same machine? A quick guess would be that insufficient data points to identify the device are configured (vendorid, productid, serial...) in ups.conf, so both drivers connect to the first match. I'd expect them to conflict and one would die or both loop reconnecting, if both are running at once, though. Also, which NUT version? Custom build from GitHub or an

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 "Application Note #176 Modbus Implementation in APC Smart-UPS" The APC "announcement" appeared on their site in their user blogs by an APC employee, here:

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>

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

On Wed, 8 Jan 2020, Gene Heskett wrote: > On Wednesday 08 January 2020 06:44:03 Roger Price wrote: >> I am surprised that there is no ups.delay.start for this UPS. > My new APC Smart-UPS_1500 doesn't have it either. Hello Gene, The NUT 2.7.2 "device dump library" entry for the APC Smart-UPS 1500 at https://networkupstools.org/ddl/APC/Smart-UPS_1500.html shows an entry

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

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

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 "pollonly" in the usbhid-ups man page, but it didn't help me. Could someone explain me what does this means exactly ? What are

Sounds like some other program is holding the port. Have you stopped other NUT drivers for the device (e.g. via auto-resuscitating services) before starting this one? Does udev, ugen or similar facility have the configuration to hand off this device to NUT run-time user? (BTW, if you are now testing a custom build - was it configured to use same accounts as pre-packaged variant)? On Fri, Mar 24,

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

Hello fellow NUTs :) It is my great pleasure to get a bit of sunshine from other people's work, and announce that the initial pull request for `apc_modbus` NUT driver has recently been merged to the main NUT codebase, so it would be part of an eventual 2.8.1 release. Great thanks go to Axel Gembe for the implementation, and to numerous community members for testing as well as their bug-fix

Hello fellow NUTs :) It is my great pleasure to get a bit of sunshine from other people's work, and announce that the initial pull request for `apc_modbus` NUT driver has recently been merged to the main NUT codebase, so it would be part of an eventual 2.8.1 release. Great thanks go to Axel Gembe for the implementation, and to numerous community members for testing as well as their bug-fix

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