networkupstools / nut

The Network UPS Tools repository. UPS management protocol Informational RFC 9271 published by IETF at https://www.rfc-editor.org/info/rfc9271 Please star NUT on GitHub, this helps with sponsorships!
https://networkupstools.org/
Other
2.08k stars 351 forks source link

Smart-UPS 750 input.voltage #348

Open MurtFolak opened 7 years ago

MurtFolak commented 7 years ago

Hello,

i can't get the "input.voltage" in http://networkupstools.org/ddl/APC/Smart-UPS_750.html it is listed but here it looks like this:

Init SSL without certificate database
battery.charge: 100
battery.charge.low: 10
battery.charge.warning: 50
battery.runtime: 8760
battery.runtime.low: 120
battery.type: PbAc
battery.voltage: 27.3
battery.voltage.nominal: 24.0
device.mfr: American Power Conversion
device.model: Smart-UPS 750
device.serial: Axxxx
device.type: ups
driver.name: usbhid-ups
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.version: 2.7.2
driver.version.data: APC HID 0.95
driver.version.internal: 0.38
ups.beeper.status: disabled
ups.delay.shutdown: 20
ups.firmware: UPS 08.3 / ID=18
ups.mfr: American Power Conversion
ups.mfr.date: 2012/10/12
ups.model: Smart-UPS 750
ups.productid: 0003
ups.serial: Axxxxx
ups.status: OL
ups.timer.reboot: -1
ups.timer.shutdown: -1
ups.vendorid: 051d

how can I get the Value?

Thank you!

clepple commented 7 years ago

(edited to adjust the formatting)

Note that the ups.firmware format is similar to the following models:

It is possible that your UPS has a MODBUS interface, which is not yet implemented in NUT (see issue #139)

dynek commented 6 years ago

Same problem with my SMT750I - do we have more info since end 2016 regarding modbus? Doesn't look like it according to issues/PR I was able to find.

battery.charge: 100
battery.charge.low: 10
battery.charge.warning: 50
battery.runtime: 3480
battery.runtime.low: 120
battery.type: PbAc
battery.voltage: 27.0
battery.voltage.nominal: 24.0
device.mfr: American Power Conversion
device.model: Smart-UPS 750
device.serial: AS1243******
device.type: ups
driver.name: usbhid-ups
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 10
driver.parameter.port: /dev/ttyS1
driver.parameter.synchronous: no
driver.version: 2.7.4
driver.version.data: APC HID 0.96
driver.version.internal: 0.41
ups.beeper.status: enabled
ups.delay.shutdown: 20
ups.firmware: UPS 08.3 / ID=18
ups.mfr: American Power Conversion
ups.mfr.date: 2012/10/24
ups.model: Smart-UPS 750
ups.productid: 0003
ups.serial: AS1243******
ups.status: OL
ups.timer.reboot: -1
ups.timer.shutdown: -1
ups.vendorid: 051d
Kh3nsu commented 1 year ago

Hello, Sorry for digging up this really really Old issue. But is there a fix for this? As the Problem still persists with my SMT750I. I know there is a smart card for the ups which is around 80€ (https://www.office-partner.de/apc-ap9620-1793700) which delivers legacy communication protocol.

Any Otter solutions?

jimklimov commented 1 year ago

UPDATE: Sorry, thought about another issue, with APC MIB (not HID).

For APC modbus, a ticket at #139 is still waiting for someone to code and test a driver - possibly absorb apcupsd in the process (their latest releases could talk modbus, then development apparently went dormant half a decade ago).

jimklimov commented 1 year ago

1868 may be of interest...

As an APC customer, you can try asking for the protocol.

Seqway commented 10 months ago

I will once again push this up here. Any news to get voltage values via USB ? How can I help for USB connection ?

jimklimov commented 10 months ago

@Seqway : did you have a chance to re-check if the current codebase (with apc_modbus and currently a custom-built libmodbus and NUT against it) does the trick - assuming the device also talks that protocol? See https://github.com/networkupstools/nut/wiki/APC-UPS-with-Modbus-protocol for details.

Otherwise, did you check if the current NUT codebase (git master or a recent 2.8.1 release) with usbhid-ups have gained the ability by way of changes here and there since 2.7.4 (7 years ago or so)?

If not, please see docs in source about generation of USB HID subdrivers - you would need to "explore" the device and have a driver source generated, then compare it to the existing one to transplant possible new data points that your device exposes.

It may also be that it just does not report that level of detail...