Hi,
I have been blessed with the "Numeric 2000 Plus" UPS, suspected to be
of
2KVA rating. This UPS does not figure in the list of UPS recognised by NUT.
However I get lucky with megatec driver.
Here is the log...
-----------------------------------------------------------------------------------------------------
Network UPS Tools - Megatec protocol driver 1.5 (2.0.5)
Carlos Rodrigues (c) 2003-2006
debug level is '3'
Starting UPS detection process...
Attempting to detect the UPS...
Sending "Q1" command...
"Q1" command successful.
Attempting to detect the UPS...
Sending "Q1" command...
"Q1" command successful.
Attempting to detect the UPS...
Sending "Q1" command...
"Q1" command successful.
Attempting to detect the UPS...
Sending "Q1" command...
"Q1" command successful.
Attempting to detect the UPS...
Sending "Q1" command...
"Q1" command successful.
0 out of 5 detection attempts failed (minimum failures: 2).
Asking for UPS information ("I" command)...
UPS information: NUMERIC 2000 Plus VER 40643N
Megatec protocol UPS detected [NUMERIC 2000 Plus VER 40643N].
Asking for UPS power ratings ("F" command)...
UPS power ratings: 230.0 8.7 36.00 50.0
Asking for UPS status ("Q1" command)...
UPS status: 210.1 210.1 209.0 011 49.4 41.0 40.0 00001001
36.0V battery, present voltage (41.0V) outside of supported intervals.
This UPS has an unsupported combination of battery voltage/number of batteries.
Done setting up the UPS.
Asking for UPS status ("Q1" command)...
UPS status: 210.1 210.1 209.0 010 49.4 41.0 40.0 00001001
dstate_init: sock /var/lib/nut/Numeric open on fd 5
Asking for UPS status ("Q1" command)...
UPS status: 210.1 210.1 209.0 012 49.4 41.0 40.0 00001001
---------------------------------------------------------------------------------------------------------
Following the mailing list, I did the "full charge/discharge" to
tackle the unsupported combination of battery situation
Then I added the following lines to the ups.conf
[Numeric]
driver = megatec
port = /dev/upslink
desc = "Numeric 2000 LI"
battvolts = 30.4:41.0
lowbatt = 25
Now "upsc Numeric" command returns the following:
$ upsc Numeric
battery.charge: 100.0
battery.voltage: 41.00
battery.voltage.nominal: 36.0
driver.name: megatec
driver.parameter.battvolts: 30.4:41.0
driver.parameter.lowbatt: 25
driver.parameter.pollinterval: 2
driver.parameter.port: /dev/upslink
driver.version: 2.4.1
driver.version.internal: 1.6
input.frequency: 49.2
input.frequency.nominal: 50.0
input.voltage: 210.1
input.voltage.fault: 210.1
input.voltage.maximum: 213.1
input.voltage.minimum: 208.6
input.voltage.nominal: 230.0
output.voltage: 209.0
ups.beeper.status: enabled
ups.delay.shutdown: 0
ups.delay.start: 2
ups.load: 12.0
ups.mfr: NUMERIC
ups.model: 2000 Plus VER 40643N
ups.serial: unknown
ups.status: OL
ups.temperature: 40.0
ups.type: standby
Is this all that needs to be done for an unspported UPS ?
Just running the NUT-monitor app, I noticed that the "Time Remaining"
info is not available. Does this look OK ?
Regards
Sathish
Citeren Holla <holla.net op gmail.com>: [...]> Is this all that needs to be done for an unspported UPS ?This is enough to add it to the list of supported devices. You may wish to make sure that shutting down also works by running 'upsmon -c fsd' on the system that is designated as master for this UPS. You also seem to have an awfully outdated version of NUT, so upgrading is recommended.> Just running the NUT-monitor app, I noticed that the "Time Remaining" > info is not available. Does this look OK ?Yes. This is not supported on devices using the Megatec/Q1 protocol, simply because there is no definition for this in the protocol. If this is important to you, an upgrade to nut-2.4.1 or later is needed. The blazer_ser driver (which supersedes the megatec driver) in that release will report an estimated runtime left if given the proper parameters in ups.conf. Make sure to read 'man 8 blazer' before asking for help. Best regards, Arjen -- Please keep list traffic on the list
Citeren Holla <holla.net op gmail.com>:>>> tej nut-monitor-1.1 # upsc Numeric >>> battery.charge: nan ? ?<==============>>> battery.lowbatt: 25 >>> battery.runtime: 0 >> >> This is probably due to some broken integer dividing, resulting in loss of >> precision. Just fixed in the trunk. > > Yes, I checked the trunk and it is working. Thanks.Good to know.> I want to clarify one point. I had specified > > default.battery.lowbatt = 50 > > My understanding was that when the ups battery charge reaches 50%, > NUT will initiate the shutdown. But in my testing, even when the > charge went down to 30% nothing happened. Shutdown was > started only when the UPS reported low battery condition (which > is dangerously low for a proper shutdown). > > Is my understanding correct ?See 'man 8 blazer' for a list of recognized options. The above one isn't one of them, so specifying it won't make the driver shutdown any sooner. The clone driver which can be run on top of any other driver will allow you to shutdown the loads based on battery.charge and battery.runtime. See 'man 8 clone'. Best regards, Arjen -- Please keep list traffic on the list