similar to: Contact-closure UPS

No progress has been made: cable is UPS - PC 6 - 3 7 - 5 9 - 2 for ./blazer_ser -DDDDD -a infosec 0.000000 send_to_all: SETINFO driver.parameter.port "/dev/ttyS1" 0.000323 debug level is '5' 0.103068 send_to_all: SETINFO device.type "ups" 0.103104 send_to_all: SETINFO driver.version "2.7.3" 0.103118 send_to_all: SETINFO

On Dec 17, 2015, at 4:51 PM, R?bert SZAKSZ <robert at szaksz.eu> wrote: > > Which output PIN on PC side is during whole communication on drivers blazer_ser or nutdrv_qx stable on Logical 0 (+12V)? > I want make small power source with one resistor (1k) and 3V zenner diode and put on UPS Pin1. I always forget which signals are inverted, but for upsdrv_qx: "By default the

Hi Charles, I am done with few things: I made the cable - looks good, because I see some activities. I upgraded NUT to 2.7.3. but I have no success to start driver(this are the outputs) nut.cfg MODE = netserver ups.conf [infosec] driver = nutdrv_qx (or blazer_ser) port = /dev/ttyS1 desc = "XP Pro 2500 RM" output(nutdrv_qx cmd upsdrvctl -DDD start) Network UPS

Hi Charles, >----- Original Message ----- >From: "Charles Lepple" <clepple at gmail.com> >To: "R?bert SZAKSZ" <robert at szaksz.eu> >Cc: nut-upsuser at lists.alioth.debian.org >Sent: Monday, November 16, 2015 3:20:17 PM >Subject: Re: [Nut-upsuser] Contact-closure UPS > >[please use reply-all when responding - the list does not modify the

On Nov 20, 2015, at 12:17 PM, R?bert SZAKSZ <robert at szaksz.eu> wrote: > > No progress has been made: > > cable is UPS - PC > 6 - 3 > 7 - 5 > 9 - 2 > Maybe pins 4 and 7 (ground) both need to be connected on the UPS side? > for ./blazer_ser -DDDDD -a infosec > 0.000000 send_to_all: SETINFO driver.parameter.port "/dev/ttyS1" > 0.000323

[please use reply-all when responding - the list does not modify the reply-to header.] > On Nov 16, 2015, at 8:24 AM, R?bert SZAKSZ <robert at szaksz.eu> wrote: > > 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

On Nov 16, 2015, at 3:57 PM, R?bert SZAKSZ <robert at szaksz.eu> wrote: > > Thank you for your answer, so I want to try make the "smart" cable, but should I use: > http://www.networkupstools.org/ups-protocols/megatec.html (cable mentioned by you - above 3 wire cable)? If I am reading the code correctly, it does not need anything other than Tx/Rx/Ground (ser_open() sets

> On Nov 21, 2015, at 2:43 AM, R?bert SZAKSZ <robert at szaksz.eu> wrote: > > I mesured it and on DC and it shows 0 V (zero V). > May be the information (pls. see attachment) that UPS PIN1 should bee keept HI is mandatory. Should I connect it to PC PIN4 DTR? Certainly possible. blazer_ser and nutdrv_qx should set DTR high and RTS low by default, but that can be adjusted. >

On Nov 19, 2015, at 12:04 PM, R?bert SZAKSZ <robert at szaksz.eu> wrote: > output(nutdrv_qx cmd upsdrvctl -DDD start) > > Network UPS Tools - UPS driver controller 2.7.3 > 0.000000 > If you're not a NUT core developer, chances are that you're told to enable debugging > to see why a driver isn't working for you. We're sorry for the confusion, but this is

On Nov 21, 2015, at 8:54 AM, R?bert SZAKSZ <robert at szaksz.eu> wrote: >> If the UPS is capable of the smart protocol, I still think that is worth trying first. But it's up to you. > I am not 100% sure that smart protocol is capable, because the only one place where it is mentioned is the picture I sended you. But your original email mentioned "UPS TxD" and

>On Nov 20, 2015, at 12:17 PM, R?bert SZAKSZ <robert at szaksz.eu> wrote: >> >> No progress has been made: >> >> cable is UPS - PC >> 6 - 3 >> 7 - 5 >> 9 - 2 >> > >Maybe pins 4 and 7 (ground) both need to be connected on the UPS side? I connected both to pin 5 >Unfortunately, I don't think there is a safe way (in software)

>> On Nov 21, 2015, at 2:43 AM, R?bert SZAKSZ <robert at szaksz.eu> wrote: >> >> I mesured it and on DC and it shows 0 V (zero V). >> May be the information (pls. see attachment) that UPS PIN1 should bee keept HI is mandatory. Should I connect it to PC PIN4 DTR? > >Certainly possible. blazer_ser and nutdrv_qx should set DTR high and RTS low by default, but

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

Hello again! I'm yet again the guy from the blazer_usb problem and the ATCL one too. This time I have a third UPS (the last one In my collection) that i'm trying to make work instead of the ATCL one since there's no driver for it on windows. This UPS is another no-brand box (actually it is a "kozumi", but that's just a rebrand), and apparently it's much more basic

On Mar 28, 2014, at 9:08 AM, Bill S wrote: > On Fri, Mar 28, 2014 at 8:12 AM, Charles Lepple <clepple at gmail.com> wrote: > > <<Snip>> >> >> I'll be honest, I haven't really done much with the CGI scripts lately. For debugging values, it is probably better to be closer to the driver. I'd recommend using "upsc" or the driver logs.

On Oct 31, 2020, at 10:53 PM, Charles Lepple <clepple at gmail.com> wrote: > > On Oct 31, 2020, at 8:30 PM, Gene Heskett <gheskett at shentel.net> wrote: >> >>> battery.voltage: 16.0 >> At that voltage, 5 of the 12 cells are shorted >>> battery.voltage.nominal: 24 > > The 16.0 is a scaled version of the fixed (bogus) 24.0 V reading, similar

Hi, Could somebody please help me get this one to work using the close contact information. I can not get it to detect off line Config: OpenSuse 11.0 NUT 2.2.2 [cyberpower] driver = genericups port = /dev/ttyS1 mfr = "Cyberpower" model = "PR1500LCDRTXL2U" desc = "Cyberpower PR1500LCDRTXL2U - Serial/contact"

Good morning again, I have finished some tests and the driver works perfectly for shutting down the server and a client, both Ubuntu 16.04. I have to change the battery, I am unable to test with 100% load and now I have 5 minutes of battery power with a load of 18%. I am still unable to send email notifications, I have enabled all the warnings in upsmon.conf: NOTIFYFLAG ONLINE

On Fri, Mar 28, 2014 at 8:12 AM, Charles Lepple <clepple at gmail.com> wrote: <<Snip>> > > I'll be honest, I haven't really done much with the CGI scripts lately. For debugging values, it is probably better to be closer to the driver. I'd recommend using "upsc" or the driver logs. > > To that end, the .ac.txt and .bat.txt files both show 24.0 V:

Hi David As per the link http://www.llondel.org/ups.shtml & the final testing paragraph. I have set up a Lantech UPS similiar to your write up for your Powersure Proactive and Powersure Personal UPS's On LOW BATT it shuts down OK. BUT as with other many UPS's during the wait period from low batt to start of shutdown ... IE [SHUTDOWNCMD "/sbin/shutdown -h +20"]