similar to: mge galaxy 6000 three-phase supported or not?

Hi all! I'm wondering if there's anyone doing any hacking on the snmp-ups driver at the moment. I've started looking at implementing 3phase-support, and this uncovered some rather unpleasant stuff in the snmp-ups driver that I really need to fix in order to get things sane. Those of you that's allergic to SNMP might want to stop reading now, this is rather icky ;)

We use HP R5500XR UPS, and they all have SNMP cards. These devices supposedly use the IETF MIB, but in order to get the SNMP driver to talk to them I have had to hack it slightly. I'd like to see these UPS proplerly supported in the official nut release (mostly so I don't have to faff around patching and repackaging when a new version comes out) and would be more than happy to provide

Hi, I got a shiny pair of new PowerWare 9155 UPS (3 input phaes, one output phase), running parallel. Since I didn't want to install a Windows box to run Powerwares software I now went nut(s) ;-) So far things look pretty good, snmp-ups talks to both ups using the pw mib. Though I get these messages, when I start the driver: [ups2] nut_snmp_get: 1.3.6.1.4.1.534.1.4.4.1.3: Error in packet:

Hi, I got a shiny pair of new PowerWare 9155 UPS (3 input phaes, one output phase), running parallel. Since I didn't want to install a Windows box to run Powerwares software I now went nut(s) ;-) So far things look pretty good, snmp-ups talks to both ups using the pw mib. Though I get these messages, when I start the driver: [ups2] nut_snmp_get: 1.3.6.1.4.1.534.1.4.4.1.3: Error in packet:

[I'm switching my dev address to @gmail.com instead of @mgeups... please, update your bookmark] Peter Selinger wrote: > > Arnaud Quette wrote: > > > > Here is the status of PSE (Peter Selinger) NUT patches > > for newhidups (hidparser, apc support, ...). > > > > - nut-cvs-patch-REOPEN-2005-08-24: > > approved and applied on Development tree > >

--- Arjen de Korte <nut+users at de-korte.org> wrote: > > > I also did: > > > > # ./megatec_usb -DDDDD -x vendor=06da -x mfr=OMRON > > /dev/usb/hiddev0 > > Please have a look at 'man 8 megatec_usb' again. > > You probably need to specify the '-x vendorid' and > '-x productid' options > and most likely, the

--- Arjen de Korte <nut+users at de-korte.org> wrote: > > > I also did: > > > > # ./megatec_usb -DDDDD -x vendor=06da -x mfr=OMRON > > /dev/usb/hiddev0 > > Please have a look at 'man 8 megatec_usb' again. > > You probably need to specify the '-x vendorid' and > '-x productid' options > and most likely, the

Hello, At my workplace I have exact UPS config as stated in the subject (APC MGE Galaxy 5500 + AP9635CH). I have it set up to work with snmp-ups NUT driver. Despite many readings from *upsc* command I am not receiving "On Line Status" (ups.status OL) nor "On Battery Status" (ups.status OB) and therefore I can't get my systems to shutdown during a power outage event.

Here's a patch (against 2.2.2) which adds battery.temperature to the ietf-mib snmp driver. While looking at ietfmib.h I noticed that the value for IETF_OID_IN_LINES is actually that for upsOutputNumLines.0. Does anyone know whether that's deliberate or a typo? -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/x-patch

mateuszx via Nut-upsdev <nut-upsdev at alioth-lists.debian.net> writes: > At my workplace I have exact UPS config as stated in the subject (APC MGE > Galaxy 5500 + AP9635CH). > I have it set up to work with snmp-ups NUT driver. > Despite many readings from *upsc* command I am not receiving "On Line > Status" (ups.status OL) nor "On Battery Status"

Hello, At my workplace I have exact UPS config as stated in the subject (APC MGE Galaxy 5500 + AP9635CH). I have it set up to work with snmp-ups NUT driver. Despite many readings from *upsc* command I am not receiving "On Line Status" (ups.status OL) nor "On Battery Status" (ups.status OB) and therefore I can't get my systems to shutdown during a power outage event.

Also, which version of NUT is involved? There were recently PRs (merged to master-branch, eventually will be in 2.8.1) about more SNMP-UPS support including APCs e.g. 1674, 1679, 1113 (should be in 2.8.0)... Many distros still ship 2.7.4... Jim On Tue, Feb 28, 2023, 00:57 Greg Troxel <gdt at lexort.com> wrote: > mateuszx via Nut-upsdev <nut-upsdev at alioth-lists.debian.net>

Thanks to Olli, I can now talk to my PW9125 via SNMP: > upsc cscfups001@localhost ambient.temperature: 031.0 battery.charge: 090.0 battery.runtime: 2640.0 battery.voltage: 055.5 driver.name: snmp-ups driver.parameter.mibs: pw driver.parameter.port: cscfups001.cs.uwaterloo.ca driver.version: 2.1.0 driver.version.internal: 0.41 input.frequency: 060.0 input.voltage: 120.0 output.current: 020.0

Hi, I would like to contribute code to make the SNMP driver compatible with HP's AF401A UPS module. It is also compatible with HP's older SNMP modules. It's just a new mib specification plus the necessary changes to snmp-ups.c Several sources have told me that these UPSs use the cpqpower.mib, but comparing that mib at http://www.snmplink.org/cgi-bin/nd/m/Ent/H/Hewlett

hi @ all, i use nut with mge comet ex 7 rt (mge-shut driver). Is ist possible, that upsmon loses states? I obtain onbatt and online messages every time, but sometimes there are no lowbatt and/or shutdown messages. regrads, miroslav -- SHALTEV.ORG @ http://www.shaltev.de

I've got an update on this case Using tkmib I discovered that my UPS (NMC per say) sends its state by OID 1.3.6.1.4.1.318.1.1.1.11.1.1.0 .iso.org.dod.internet.private.enterprises.apc.products.hardware.ups.upsState.upsBasicState.upsBasicStateOutputState.0 = 0001010000000000001000000000000000000000000000000000000000000000 (mib used for this snmpget was powernet441.mib) (I got a description about

So what would it take me to edit NUT's code for my case to work? My Network Management Card sends its output state using unfortunately only (I guess so) this OID: 1.3.6.1.4.1.318.1.1.1.11.1.1.0 Weirdly the standard way of obtaining Battery Status (drivers/apc-mib.c) 1.3.6.1.4.1.318.1.1.1.2.1.1.0 gives me good results. Unfortunately power status OID's value type differs (my: 64 digits

One good intro to this is https://github.com/networkupstools/nut/blob/master/docs/snmp-subdrivers.txt although it focuses on adding new subdrivers - but more or less the same workflow applies to extending existing ones. Sometimes it helps to generate a new one for a currently-partially-supported device, and then compare with existing subdriver (using meld or similar GUI helps a lot) to port the

Well thanks, The solution for my problem was kinda easy (still need some testing though): found out my ups status is a string, so then I changed the way snmp-ups.c gets the status. Had to change *nut_snmp_get_int *to *nut_snmp_get_str *at around line 3470, then grab fourth char out, use *strtol *function to then send it to *su_status_set *function. I created my copy of *apc-mib.c *with my OID at

Hi, I'm having a hard time configuring a Mustek Powermust 600VA ups to work via USB with nut. I read somewhere that nut works OK via the rs232 cable, but unfortunately I don't have a COM port in my computer. The kernel detects the ups as an Xbox pad :) and loads the xpad module. I tried running /lib/nut/megatec with different /dev/ttySx but it displays megatec protocol UPS was not