EchterAgo
commented
11 months ago Great to hear this.
Good to see that it reads the delays correctly on yours:
0.196059 [D5] send_to_all: SETINFO ups.delay.shutdown "180"
0.196089 [D5] send_to_all: SETINFO ups.delay.start "0"
0.196120 [D5] send_to_all: SETINFO ups.delay.reboot "8"On mine it somehow reads 0 here despite there being a delay when doing shutdown, maybe a firmware bug, I'll try upgrading to latest soon.
All looks pretty good. battery.date.maintenance is not what I see on the front panel, I see battery.date which is what I set when I replaced the batteries last.
This is what I used for battery.date.maintenance:
And this is what I used for battery.date:
On my unit battery.date matches what I can see in the menu, not sure how battery.date.maintenance is calculated though. I wonder why your maintenance timestamp is before the installation timestamp.
Thanks for the dev work! Make sure the readme for this driver includes the (obvious) step to enable Modbus on the device itself.
You're welcome. Yes, there should be a section on how to enable Modbus in the manual page.
I will follow this ticket for a stable enough commit to build and run this on my main system.
Note that at least on Debian you can build it like this and integrate it with the Debian package by copying the apc_modbus driver into /lib/nut:
./configure \
--with-drivers=usbhid-ups,apc_modbus \
--with-usb \
--prefix= --sysconfdir=/etc/nut --with-statepath=/run/nut \
--with-user=nut --with-group=nut \
--with-modbus --with-modbus-includes=-I/home/ago/src/libmodbus/prefix/include/modbus --with-modbus-libs="-L/home/ago/src/libmodbus/prefix/lib -lmodbus"Note that you'll have to keep around the libmodbus prefix for that to work.
WiredWonder
jimklimov
PrplHaz4
EetuRasilainen
p8218
From APCUPSD (http://apcupsd.cvs.sourceforge.net/viewvc/apcupsd/apcupsd/ReleaseNotes?pathrev=Release-3_14_11): "APC publicly released documentation[1] on a new UPS control and monitoring protocol, loosely referred to as MODBUS (after the historic industrial control protocol it is based on). The new protocol operates over RS232 serial lines as well as USB connections and is intended to supplement APC's proprietary Microlink protocol. Microlink is not going away, but APC has realized that third parties require access to UPS status and control information. Rather than publicly open Microlink, they have created another protocol to operate along side it.
Many existing Microlink UPSes can be upgraded to support MODBUS via a firmware update. See [2]. Certain older models are not upgradeable. APC support will be your best contact for determining if your UPS supports a MODBUS upgrade the information linked below does not make it clear."
[1] http://www.apc.com/whitepaper/?an=176 [2] http://www.schneider-electric.us/support/index?page=content&country=ITB&lang=EN&id=FA164737 [3] http://www.apcupsd.com/manual/manual.html
Add support for MODBUS over RS232 and USB in NUT. This effort must be synchronized with the general Modbus support in NUT ( #50 )
Implementation notes: