Displaying 20 results from an estimated 2000 matches similar to: "APC protocols and drivers (was: Documenting the NUT driver-qualification process)"
2014 Jul 26
0
Documenting the NUT driver-qualification process
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
2014 Jul 09
5
Documenting the NUT driver-qualification process
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
2014 Jul 09
2
Documenting the NUT driver-qualification process
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
2014 Jul 09
0
Documenting the NUT driver-qualification process
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
2014 Jul 10
1
Documenting the NUT driver-qualification process
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.
>
>
2014 Jul 09
0
Documenting the NUT driver-qualification process
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
2014 Dec 17
2
interrupt pipe disabled [APC SMT3000RMI2U]
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
2014 Dec 17
0
interrupt pipe disabled [APC SMT3000RMI2U]
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
2024 May 25
1
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
2024 May 25
1
APC SMC1500 question
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>>
>
>
2024 May 25
1
APC SMC1500 question
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
2024 May 25
1
APC SMC1500 question
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>
2014 Dec 17
2
interrupt pipe disabled [APC SMT3000RMI2U]
On Dec 17, 2014, at 3:46 AM, Frantz de Germain <frantz at info.univ-angers.fr> wrote:
> This seems to me a little bit complicated :-( Instead, can I use the
> apcsmart driver with the provided 940-0625a c?ble (RJ45/DB9 connectors) ? Or
> do I need to acquire an AP9620 SmartSlot expansion card, as I've seen in the
> Hardware compatibility list page ?
It sounds like you might
2013 Sep 13
0
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>
2013 Sep 11
2
New APC "SMT" UPSes support MODBUS, will there be support in NUT?
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:
2024 May 24
2
APC SMC1500 question
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
2013 Feb 26
1
APC SMX3000RMLV2UNC with AP9631 NUT compatibility via network
I have an APC SMX3000RMLV2UNC UPS, with installed network card model AP9631.
http://www.apc.com/resource/include/techspec_index.cfm?base_sku=SMX3000RMLV2UNC
http://www.apc.com/resource/include/techspec_index.cfm?base_sku=AP9631
I planned to use network connectivity with this unit and apcupsd, but have not
this far. The UPS is shared by multiple servers, so a USB or Serial connection
via the
2014 Dec 16
4
interrupt pipe disabled
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
2014 Dec 16
0
interrupt pipe disabled
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
2017 Jun 24
2
NUT supporting Modbus TCP
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