similar to: Contact-closure 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 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

[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 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. >

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

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 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)

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

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 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

On Dec 17, 2015, at 4:51 PM, R?bert SZAKSZ <robert at szaksz.eu> wrote: > > and I find out that on UPS pin 1 should be about 3V. > If the voltage is not presented the UPS interface doesn't work. Actually, does it have a maximum voltage listed? Often, vendors will list the minimum threshold voltage, so if it can accept 3-12V, you could wire it directly. -- Charles Lepple

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

Dear Daniele, I have some news regarding the Driver: I applied the patch you sent me (https://github.com/zykh/nut/tree/issue-441) and it works correctly (obviously in Level 5 of Debug I see "missing CR...etc.."). As for now there are 2 modification I'd like to suggest you: - For Online Type UPSs the Megatec protocol describes that the battery voltage is provided in the form of V

On Aug 19, 2018, at 3:31 PM, Glenn Ramsey <gr at componic.co.nz> wrote: > > Hi, > > I'm building a DIY UPS for a Raspberry Pi using a 12V SLA battery, charger, and > an off the shelf 5V regulator. To monitor the battery level I'd like to use an > Arduino or similar type device. Since the Arduino can have a serial over USB > connection with the Pi I'd like

On Nov 5, 2015, at 11:33 AM, Rob Groner <rgroner at RTD.com> wrote: > > Having dealt with the USB portion of our UPS, I?m now reviewing our serial port communication. I?ve looked over some of the drivers in NUT to see how they handle it so I can get an idea of what the ?standard? is for how to accomplish it. I?d like to do something simple and human readable. The de facto standard

Hi Charles, I'll try the blazer_ser and the nutdrv_qx with version 2.7.1 later. Below, the result of 'lsusb -vvv' requested: Bus 004 Device 002: ID 04b4:5500 Cypress Semiconductor Corp. HID->COM RS232 Adapter Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.00 bDeviceClass 0 (Defined at Interface level)

On Jun 2, 2014, at 12:25 PM, Andreas Lausch / TBT wrote: > > Hi, > > thanks for the reply. > > On 2014-05-29 05:21, Charles Lepple wrote: >>> Now my questions: >>> 1. should the blazer_ser's high voltage be the voltage during charging >>> or right after I've unplugged it from the mains? >> sounds like during charging (or more

Hi, thanks for the reply. On 2014-05-29 05:21, Charles Lepple wrote: >> Now my questions: >> 1. should the blazer_ser's high voltage be the voltage during charging >> or right after I've unplugged it from the mains? > sounds like during charging (or more accurately, during float charging at the end of the cycle): > >

Having done my fresh 5.0 install a couple months ago I'm slowly getting things back in to working condition. Decided last night to try setting up lmsensors. Got it all set up (modules, etc taken care of) and it runs and reports values, but some of 'em a clearly wrong with the default sensors.conf Trying to use the old sensors.conf I used on Centos 4 produces even more whacked-out results,