similar to: Generic UPS with serial port

Hi, I'm new to this list and I have a question concerning using the genericups driver (type 22) with the Cyberpower 485 in serial mode. When running the driver in debug mode: genericups -a myupsname_genericups22 -DDDDDD I observe the following statuses as the mains power dies, switching over to battery power, and then letting it discharge. Initially, with mains power on, status =

Hi, I'm trying to configure my ups with nut which is a locally made one. It uses a rs232 port to talk to the computer and comes with a software called "Powermanager Lite" which is provided by Richcomm and supports Windows, Linux and UNIX. According to the manual it uses the Richcomm circuitry to talk to the computer and uses a drycontact protocol. Unfortunately I couldn't

Hello, I am trying to understand how to create a custom configuration for the genericups driver. My system simply signals RI on a serial port on low battery. That's it, nothing else. This serial port is also being used for communications so the other lines are going to be changing all the time, unrelated to the UPS state. Is there a "null" upstype I can use, and then add LB=RNG?

I have a Gamatronic Smart Compact 750. I have it connected to my linux machine via serial cable and am running nut 2.0.3. There is no interruption in power, but the ups is reporting OB (on battery). Is there a configuration option I am missing? The relevant ups.conf entry is: [Gamatronic] port = /dev/ttyS1 desc = "Home Gamatronic UPS" driver = genericups

I tried to find a search button for the mailing list but could not. So rtfm me with the link please. If not.. I have an old Deltec PowerRite Pro 2 UPS which has a 9 pin serial cable. By trial and error Im pretty sure I found LB = DCD, but can not get the combination for OB / OL. No matter what I do I get the results below. driver.name: genericups driver.parameter.CP: CTS driver.parameter.LB:

Hello, I have one UPS Infosec XP Pro 2500 RM and it works with windows sw RUPS2000. Now I want to install this UPS as virtual server on vmware ESXi vMA - (SUSE SLES 11SP2 linux). On this linux I have NUT 2.6.0 and I stopped now with configuration of genericups driver. Working cable (direct cable pin1-pin1 ... pin9-pin9) connection on Windows: PIN | PC | UPS

Hi everybody, I've got an Unitek iZi UPS 525 with a serial interface. The supplied cable looks fairly simple: RX->RX , TX->TX and GND->GND. Using this cable and Minicom with 2400 8N1 I'm able to issue commands to the UPS using the "Megatec Protocol" http://www.networkupstools.org/protocols/megatec.html so I know the UPS is fairly "intelligent" :-) and the

I am using nut 2.2.2 and I have a CyberPower CP550SL. According to the drivers list, I should be using genericups with upstype set to 7, but when I try that and when I run upsc I get: driver.name: genericups driver.parameter.LB: 04 driver.parameter.pollinterval: 2 driver.parameter.port: /dev/ups driver.parameter.upstype: 7 driver.version: 2.2.2 driver.version.internal: 1.34 ups.mfr: CyberPower

I am using nut 2.2.2 and I have a CyberPower CP550SL. According to the drivers list, I should be using genericups with upstype set to 7, but when I try that and when I run upsc I get: driver.name: genericups driver.parameter.LB: 04 driver.parameter.pollinterval: 2 driver.parameter.port: /dev/ups driver.parameter.upstype: 7 driver.version: 2.2.2 driver.version.internal: 1.34 ups.mfr: CyberPower

Hello, ahgu >I have a unisys UPS, I probed the RS232 and notice that pin 2, >(receive data) is going from -6v (OL) to 12v(OB), but I don't see the >setting for the genericups. Seems nobody else is using the RD pin? >Any driver I can use? >Thanks >-Andrew Try RX as signal name (not RD). -- Best regards, Sergiy mailto:rendol@mail.zp.ua

On 23/01/16 16:52, Charles Lepple wrote: > [please use reply-all to include the list on your response] > > On Jan 23, 2016, at 11:14 AM, Tim Clarke <tim.clarke at manifest.co.uk> wrote: >> Centos 6.7 >> Linux man8.m1.manifest.co.uk 2.6.32-573.12.1.el6.i686 #1 SMP Tue Dec 15 >> 18:25:17 UTC 2015 i686 i686 i386 GNU/Linux >> >> Installed: >> nut.i686

Centos 6.7 Linux man8.m1.manifest.co.uk 2.6.32-573.12.1.el6.i686 #1 SMP Tue Dec 15 18:25:17 UTC 2015 i686 i686 i386 GNU/Linux Installed: nut.i686 2.6.5-2.el6 @epel nut-cgi.i686 2.6.5-2.el6 @epel nut-client.i686 2.6.5-2.el6 @epel I'm struggling to control an

This code, added to drivers/genericups.h, supports the CyberPower SL series UPSes. I've tested with my 725SL - the online/on battery transition, and low battery status, and finally the shutdown signal all work as expected. *** genericups.h.orig Sun Nov 2 16:54:24 2003 --- genericups.h Mon Oct 3 13:49:00 2005 *************** *** 220,225 **** --- 220,234 ---- TIOCM_ST

On Jun 20, 2013, at 9:48 PM, Reed Hedges wrote: > UPSPORT=/dev/ttyS0 > > # type cablep kill t powerok battok cableok > robot --- RI 0 /RI --- --- > ? > > Is there an equivalent of ?---? in genericups? I think it's pretty much any value other than a valid

Hi All. I was wondering of someone on the list could guide me to the correct driver for the following UPS: Fuden Electronics PCSTAR PT1000. http://www.fuden.com.tw/uninterruptible_power_supply_ups_off-Line_pcstar-1.h tm I have found that with the genericups upstype=7 driver I can see the ups.status going from "OL" to "OB" when I unplug the UPS. Any ideas? Thanks for

> +22 = Gamatronic UPSs with alarm interface > + [CP=RTS] [OL=CTS] [LB=\-DCD] [SD=DTR] > + > +22 = CyberPower SL seriess > + [CP=RTS] [OL=CTS] [LB=\-CAR] [SD=DTR] > + > + This part of the patch is no good. While TIOCM_CAR is equivalent to TIOCM_CD (at least in some implementations) CAR certainly isn't handled the same as DCD by genericups. It won't be

Hello, I have a UPS connected to my server with the following: Server is Suse 10.1 Nut version is?Network UPS Tools - Generic UPS driver 1.32 (2.0.4) I installed this around 2005 and cannot remember how I installed the software. ups.conf: [sdrups] driver = genericups port = /dev/ttyS0 desc = "For Server & Backup" upstype = 9 upsd.conf: ACL all 0.0.0.0/0 ACL localhost

Hi, Is there any way to debug a failure of NUT to shut a machine down AFTER the even occurs? (Be it a config issue {Though the standard "It hasn't changed since install" applies}, or a UPS failure, or a program failure). Its showing up (after reboot) as : valhalla# upsc robanton at localhost driver.name: genericups driver.parameter.pollinterval: 2 driver.parameter.port:

Hello, I got this information from the manufacturer of my ups Kobian/Mercury and were tested wtih powstatd on Linux (Works OK). Now i want to configure it with NUT and i didn't have any luck (it always says OB) Initiliasation for monitoring: RTS = 1 (High) Main power fail: CTS = 0 (Low) Batter low: DCD = 0 (Low) Kill UPS: DTR = 0 (Low) How would the ups.conf look like? Reagards, Lep

On Sunday 08 December 2019 21:48:03 Charles Lepple wrote: > On Dec 7, 2019, at 7:01 PM, Gene Heskett <gheskett at shentel.net> wrote: > > What driver do I now put in /etc/nut/ups.conf? hid-generic doesn't > > seem to want to talk to it, and the original name _(usbhid-ups) > > doesn't work from new mobo. Oh wait, I can't spell. But that didn't > >