similar to: Adding More Variables from the CyberPower MIB

On October 31, 2017 2:32:36 AM GMT+01:00, Ben Kamen <ben at benkamen.net> wrote: >Hey all, > > >?I'm feeling spunky... and want to update nut to handle the new v2.0 >MIB from CyberPower. > >I've looked at the cyberpower v0.1 .c/.h and being new to working on >nut to this level -- anything anyone has to offer on adding code >besides the obvious? >

On 11/02/2017 01:52 AM, Jim Klimov wrote: > > I believe the main reason for a new set of .c/.h files here would be if the new MIB is defined in a separate subtree. The top-level mapping binds the vendor entry OIDs (often "hidden" so one has to know where to poke). It may also be higher in the list of snmp-ups.h, in case the device also serves the older MIB but you'd prefer the

Chugging along... Question for the gang -- CyberPower lists other items in their MIB for controlling PD units and some other things. Does NUT support all that and should I make an effort to get all that in or should we skip for now and get UPS primary ingredients inserted and tested? just wondering, ?-Ben -- Ben Kamen - O.D.T., S.P.

Hey all, ?I'm feeling spunky... and want to update nut to handle the new v2.0 MIB from CyberPower. I've looked at the cyberpower v0.1 .c/.h and being new to working on nut to this level -- anything anyone has to offer on adding code besides the obvious? like: should the 0.1 and 2.0 coexist somehow? (maybe different files) (also, is there a list of all the parms I can match up from the

On November 2, 2017 5:31:42 AM GMT+01:00, Ben Kamen <ben at benkamen.net> wrote: >On 10/31/2017 01:13 AM, Jim Klimov wrote: >> If the new data is in a separate OID tree, it can quite be a new MIB. >Otherwise you can use the UNIQUE flag and set the preferred (e.g. >newer, more precise) source for a value first in the list of same-named >mappings in existing file - if

On 10/31/2017 01:13 AM, Jim Klimov wrote: > If the new data is in a separate OID tree, it can quite be a new MIB. Otherwise you can use the UNIQUE flag and set the preferred (e.g. newer, more precise) source for a value first in the list of same-named mappings in existing file - if there's a hit on an actual device, it will be used and not iterated onwards. The flag is not yet supported for

I did a bunch of work on this today. It should be all set to go. This patch is to add support for the Cyberpower RMCARD snmp cards. I basically copied the driver for bestpower, changed the name and updated the mib map. I have this running on two separate systems (two separate ups's) and it looks good. The only thing I could not figure out was updating the Makefile.am (my aclocal/libtools

The list of status bits we're seeing has increased over the years. Currently for instance, the usbhid-ups driver has defined no less than 20 status bits (and I intend to add two more in the next couple of days, FRANGE and FANFAIL): #define STATUS_ONLINE 0x00001 /* on line */ #define STATUS_DISCHRG 0x00002 /* discharging */ #define STATUS_CHRG 0x00004 /*

On Sun, 2 Aug 2020, Todd Benivegna wrote: > How would you write the SHUTDOWNCMD line with multiple commands?  I’ve been > looking at the manual and see that you have to escape the internal “ but am > still a little confused on how to do this exactly. This assumes that you use the Bash shell in your default environment. It will need adaption if you use Dash. In .bashrc define

Hey all, I recently got an RMCARD205 for my Cyber UPS.... if I use no MIBS line in the config file, I get this: > Network UPS Tools - UPS driver controller 2.6.5 > Network UPS Tools - Generic SNMP UPS driver 0.68 (2.6.5) > No matching MIB found for sysOID '.1.3.6.1.4.1.3808.1.1.1'! > Please report it to NUT developers, with an 'upsc' output for your device. >

On 10 June 2017 23:26:47 EEST, Tim Dawson <tadawson at tpcsvc.com> wrote: >Build from source, and done . . . wasting your time looking for a less >out of date RPM is pointless. . . RPM, .deb, etc are almost always >downrev. . . > >- Tim > >On June 10, 2017 2:06:42 PM CDT, Ben Kamen <ben at benkamen.net> wrote: >>Hey all, >> >> I recently got an

Thank you!  Sorry for another bonehead question…. Do I replace <myups> with the IP address of the NUT Server/Synology?  I’m assuming I would use this version for use in Dash with Ubuntu, correct? -- Todd Benivegna // todd at benivegna.com On Aug 3, 2020, 5:33 AM -0400, Roger Price <roger at rogerprice.org>, wrote: > On Sun, 2 Aug 2020, Todd Benivegna wrote: > > > How would

On June 11, 2017 8:58:11 AM GMT+02:00, Manuel Wolfshant <wolfy at nobugconsulting.ro> wrote: >On 10 June 2017 23:26:47 EEST, Tim Dawson <tadawson at tpcsvc.com> wrote: >>Build from source, and done . . . wasting your time looking for a less >>out of date RPM is pointless. . . RPM, .deb, etc are almost always >>downrev. . . >> >>- Tim >>

Build from source, and done . . . wasting your time looking for a less out of date RPM is pointless. . . RPM, .deb, etc are almost always downrev. . . - Tim On June 10, 2017 2:06:42 PM CDT, Ben Kamen <ben at benkamen.net> wrote: >Hey all, > > I recently got an RMCARD205 for my Cyber UPS.... > >if I use no MIBS line in the config file, I get this: > > >> Network

One disadvantage of handling it through a script is that is will not be done by default. Most users probably don't know about the problem of burning batteries, as it is not very common. A potential problem with Eric Wilde's patch is that it is not general enough; some UPS models have an boolean OVERHEAT flag although they don't report the actual temperature. So the UPSOVERTEMP

Hello All, I want to thank everyone who reads and responds to this group. You have all been an invaluable help to me. I now have a working Samba 3.0.1 LDAP PDC and domain member server using winbind (both servers are running Slackware 9.1). I also have virtual users and groups using nss_ldap from www.padl.com, without pam or users/groups in /etc/passwd or /etc/group only in the LDAP backend....

Hello Daniel! On Tue, Sep 29, 2020 at 6:23 PM Daniel F. Dickinson <cshore at thecshore.com> wrote: > > Hello joão, > > To get more responses you should plaintext email (standard for open source development mailing lists) instead of HTML mail. I just can't believe that I was sending HTML e-mail. Thank you very very much for bringing this to my attention. I hope it is ok now.

On Tue, 29 Sep 2020, João Luis Meloni Assirati wrote: > The UPS I am developing a driver to is able to report several flags for > critical hardware conditions, like overheat, overload, inverter failure, > output short etc. What should be the correct policy of operation when such a > condition occurs? I think that the an UPS in such a condition is not reliable > and therefore a

Arjen, I read the following in the upgrade notes and just wanted to see what the status was for the cyberpower driver? The note reads: - The cpsups and nitram drivers have been replaced by the powerpanel driver, and removed from the tree. The cyberpower driver may suffer the same in the future. What does this mean to me -- a cyberpower user? -- David C. Rankin, J.D.,P.E. Rankin Law

Hi, guys. I have a new CyberPower PR2200 which I'm trying to control using NUT. It has a serial port and I'm connected serially. I am using the cyberpower driver and before a power failure it seems to mostly be working: jeff@backup:~$ upsc cyberpower@localhost battery.charge: 000 driver.name: cyberpower driver.parameter.port: /dev/ttyS0 driver.version: 2.0.4 driver.version.internal: 1.00