Alan Spark
2017-02-13 11:59:43 UTC
Hi,
We have a SURTD3000RMXLI and would like to monitor its status by way
of daily emails or alerts when something goes wrong with the battery.
I have looked at the PowerChute software and although it can talk to
the UPS and report status information, it really is too heavyweight
for our needs and is not compatible with our target Ubuntu server.
We've tried apsupcd on one of our USB UPS devices and it works
perfectly but on this serial based one things are proving more
difficult. We are using the 940-1525A cable.
These are the configuration settings that I am using (currently on
Windows via a USB to serial cable but I have also tried on Ubuntu
using a direct serial connection and get the same results):
UPSCABLE 940-0625A
UPSTYPE apcsmart
DEVICE COM4
UPSCLASS standalone
UPSMODE disable
I get the error "PANIC! Cannot communicate with UPS via serial port."
with these settings.
Does anyone have any experience using our particular UPS with apsupcd
or have any idea why it doesn't work? Am I using the wrong protocol?
Regards,
Alan
We have a SURTD3000RMXLI and would like to monitor its status by way
of daily emails or alerts when something goes wrong with the battery.
I have looked at the PowerChute software and although it can talk to
the UPS and report status information, it really is too heavyweight
for our needs and is not compatible with our target Ubuntu server.
We've tried apsupcd on one of our USB UPS devices and it works
perfectly but on this serial based one things are proving more
difficult. We are using the 940-1525A cable.
These are the configuration settings that I am using (currently on
Windows via a USB to serial cable but I have also tried on Ubuntu
using a direct serial connection and get the same results):
UPSCABLE 940-0625A
UPSTYPE apcsmart
DEVICE COM4
UPSCLASS standalone
UPSMODE disable
I get the error "PANIC! Cannot communicate with UPS via serial port."
with these settings.
Does anyone have any experience using our particular UPS with apsupcd
or have any idea why it doesn't work? Am I using the wrong protocol?
Regards,
Alan