search for: linevoltage

...d command emerge nut. All has passed successfully. I use UPS POWERCOM BNT-1500AP. It is connected to serial port 1, i.e. for my system it/dev/tts/0. In/etc/nut/ups.conf [powercom] driver = powercom port = /dev/tts/0 desc = "PowerCom BNT-1500AP on IP-PBX" modelname = "BNT-1500AP" linevoltage = 230 type = KIN1500AP also trying: [powercom] driver = powercom port = /dev/tts/0 desc = "PowerCom BNT-1500AP on IP-PBX" modelname = "BNT-1500AP" linevoltage = 230 type = Egys At start by a command/etc/init.d/upsdrv start gives out the following: * Starting UPS drivers .....

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Has anyone used nut with a XPCC UPS, in particular one of the XVRT units? Their supplied monitoring tool "works", but I'd really prefer to use nut if possible. I've systematically gone through each of the drivers in /lib/nut and none seem to talk with the unit properly. I'll be talking with a XPCC support person tomorrow, though

...e: (null) input.voltage: -0.1 output.voltage: 57.6 STATUS: OB upsc with UPS connected to the mains: Network UPS Tools upsd 2.0.4 Connected to UPS [Inform]: powercom-ttyS0 Synchronizing...done root@marto:/home/marto# upsc Inform@localhost battery.charge: 108.8 driver.name: powercom driver.parameter.linevoltage: 220 driver.parameter.port: /dev/ttyS0 driver.parameter.shutdownArguments: {{1,0},y} driver.parameter.type: Egys driver.version: 2.0.4 driver.version.internal: $ Revision: 0.5 $ input.frequency: 49.10 input.voltage: 234.3 input.voltage.nominal: 220 output.frequency: 49.10 output.voltage: 234.3 ups....

...o run as user root, because otherwise the command "telinit 0" from the notifyme script does not have the permission to execute. Currently the output of "upsc Inform@localhost" when the UPS is connected to the mains is: battery.charge: 97.7 driver.name: powercom driver.parameter.linevoltage: 220 driver.parameter.port: /dev/ttyS0 driver.parameter.type: KIN1500AP driver.version: 2.0.4 driver.version.internal: $ Revision: 0.5 $ input.frequency: 49.61 input.voltage: 236.3 input.voltage.nominal: 220 output.frequency: 49.61 output.voltage: 236.3 ups.load: 36.7 ups.mfr: PowerCom ups.model: U...

...t;>> >>>>> Network UPS Tools - UPS driver controller 2.8.0 >>>>> Network UPS Tools - Generic HID driver 0.47 (2.8.0) >>>>> USB communication driver (libusb 1.0) 0.43 >>>>> Using subdriver: Belkin/Liebert HID 0.18 >>>>> LineVoltage exponent looks wrong, but not correcting. >>>>> LineVoltage exponent looks wrong, but not correcting. >>>>> LineVoltage exponent looks wrong, but not correcting. >>>>> ConfigVoltage exponent looks wrong, but not correcting. >>>>> >>&...

...UPS supports logging of the "boost" or "buck" lights? BATTERY: ads-bsh-fwd4# upsc ups1 battery.charge: 158.9 <-- Wierd driver.name: powercom driver.parameter.batteryPercentage: {5.0000,0.3268,-825.00,0.46511,0} driver.parameter.frequency: {0.00020997,0.0} driver.parameter.linevoltage: 110 driver.parameter.loadPercentage: {6.1343,-0.3808,1.075,0.1811} driver.parameter.manufacturer: PowerCom driver.parameter.methodOfFlowControl: dtr0rts1 driver.parameter.numOfBytesFromUPS: 16 driver.parameter.pollinterval: 2 driver.parameter.port: /dev/cuaa0 driver.parameter.shutdownArguments: {{...

So, this is the result of upsc Inform@localhost with the UPS connected to the mains: battery.charge: 97.7 driver.name: powercom driver.parameter.linevoltage: 220 driver.parameter.port: /dev/ttyS0 driver.parameter.type: KIN1500AP driver.version: 2.0.4 driver.version.internal: $ Revision: 0.5 $ input.frequency: 49.61 input.voltage: 236.3 input.voltage.nominal: 220 output.frequency: 49.10 output.voltage: 236.3 ups.load: 38.9 ups.mfr: PowerCom ups.model: U...

Dino, Alexey, there are a number of users suffering issues with your Powercom devices. Could you (Dino, and Keven if possible) please have a look at the below one, from Angela, and check for a fix? I've scheduled to release 2.6.1 next week, and having that fixed is part of the list. 2011/5/16 Angela Williams <angierfw at gmail.com> > Hi All > > On Friday 13 May 2011 at

...pport ( BNT-400/500/600/800/801/1000/1200/1500/2000AP 220-240V ) - add Powercom's King Pro model support ( KIN-425/525/625/800/1000/1200/1500/1600/2200/3000/5000AP[-RM] 100-120,200-240 V) - add Powercom's Imperial model support ( IMP-xxxAP, IMD-xxxAP ) Only for BNT/KIN/IMP/IMD: power and linevoltage whould detect automatically now also you don't need any other coefficients in ups.conf added shutdown.stayoff and shutdown.return commands start battery.test on driver start Tested on: BNT-1200AP Known bugs: - strange battery level on BNT1200AP ( & may be on other models) - can't...

...Network UPS Tools - UPS driver controller 2.8.0 >>>>>>> Network UPS Tools - Generic HID driver 0.47 (2.8.0) >>>>>>> USB communication driver (libusb 1.0) 0.43 >>>>>>> Using subdriver: Belkin/Liebert HID 0.18 >>>>>>> LineVoltage exponent looks wrong, but not correcting. >>>>>>> LineVoltage exponent looks wrong, but not correcting. >>>>>>> LineVoltage exponent looks wrong, but not correcting. >>>>>>> ConfigVoltage exponent looks wrong, but not correcting. >&g...

...Network UPS Tools - UPS driver controller 2.8.0 >>>>>>> Network UPS Tools - Generic HID driver 0.47 (2.8.0) >>>>>>> USB communication driver (libusb 1.0) 0.43 >>>>>>> Using subdriver: Belkin/Liebert HID 0.18 >>>>>>> LineVoltage exponent looks wrong, but not correcting. >>>>>>> LineVoltage exponent looks wrong, but not correcting. >>>>>>> LineVoltage exponent looks wrong, but not correcting. >>>>>>> ConfigVoltage exponent looks wrong, but not correcting. >&g...

...Aug 16 14:11:09 marto upsmon[7731]: Master privileges unavailable on UPS [Inform@localhost] Aug 16 14:11:09 marto upsmon[7731]: Reason: Access denied Can you tell me where my error is, my configuration files are: ups.conf: [Inform] driver = powercom port = /dev/ttyS0 desc = "inform guard" linevoltage = 220 type = KIN1500AP upsd.conf: ACL all 0.0.0.0/0 ACL localhost 127.0.0.1/32 ACCEPT localhost REJECT all ups.users: root password = pwd allowfrom = localhost actions = SET instcmds = ALL marto password = pwd allowfrom = localhost upsmon master upsmon.conf: MONITOR Inform@localhost 1 marto pwd ma...

...c-desktop kernel: [ 3049.671558] generic-usb 0003:0D9F:0004.0005: hiddev96,hidraw1: USB HID v1.00 Device [POWERCOM Co.,LTD HID UPS Battery] on usb-0000:00:1d.0-1/input0 Here's my etc/nut/ups.conf file: Code: # /etc/nut/ups.conf [Ultra] driver = powercom port = port=/dev/hidraw1 linevoltage = 120 manufacturer = Ultra modelname = ULTRA 700VA type = Trust methodOfFlowControl=dtr0rts1 shutdownArguments = {{7,10},y} Here's what I get when I run sudo upsdrvctl start: Code: eric at eric-desktop:~$ sudo upsdrvctl start Network UPS Tools - UPS driver controller 2.4...

...quot;. But it seems that there is still missing usablity. I was wondering if anybody found any better configs? ---- excerpt of ups.conf [AVR1500] driver = powercom port = /dev/ttyS0 desc = "PowerCom BNT-1500AP" modelname = "BNT-1500AP" linevoltage = 120 type = KIN1500AP --------------------------------------

Hi! I've tried the Fenton Driver for my UPS. The Powercom driver doesn't work. Here is the results: Network UPS Tools - UPS driver controller 2.0.0 Network UPS Tools - Fenton UPS driver 1.21 (2.0.0) Unknown ups - please report this ID string: #PCM SMK-1000 2001 V9.0 Detected Unknown MK-1000 on /dev/ttyS0 Have you any ideas to make it compartible with NUT. Thanks! With

Hi, Nut versions: 2.2.0 and 2.0.2 (powercom -x type=KIN1500AP -x linevoltage=220) I've got the above mentioned serial UPS and have found some problems using it. 1) under linux 2.6.12 select() timed out on reading the serial port in NONBLOCK mode. Not sure about this one, seems most likely a kernel problem, since it's working OK in 2.6.20. But on the other hand...

Hi, I have a little problem with PowerCom BNT600AP after running driver I see: root@rask> powercom -D /dev/ttyS1 Network UPS Tools - PowerCom and similars protocol UPS driver $ Revision: 0.5 $ (2.0.2) debug level is '1' Values of arguments: manufacturer : 'PowerCom' model name : 'Unknown' serial number : 'Unknown' line

...rg>. # # Driver failed to start (exit status=1) [POWERCOM] driver = powercom port=/dev/serial/by-id/usb-POWERCOM_CO.__LTD._USB_to_Serial-if00-port0 # -> ../../ttyUSB0 manufacturer "PowerCom" linevoltage "120" modelname "RCD-UPS2000D" serialnumber "40206430906" type "ULT" # # This configuration's output: # # upsdrvctl -u nut -D start POWERCOM # Network UPS Tools - UPS driver controller 2.4.1...

...d Driver failed to start (exit status=1) ? Nut version nut-2.2.2-3.el5 on kernel 2.6.18-308.11.1.el5PAE ? If we try using the powercom driver it complains it is a usbhid-ups and if we try some of the powercom settings in the ups.conf the usbhid-ups driver rejects them as unknown (ie) model = , linevoltage = .... ? lsusb -vd 0d9f:0004|sed -ne '/^\w/p;/\bi/p'? returns Protocol spec without prior Class and Subclass spec at line 4297 Bus 005 Device 002: ID 0d9f:0004 Powercom Co., Ltd Device Descriptor: ? idVendor?????????? 0x0d9f Powercom Co., Ltd ? idProduct????????? 0x0004 ? iManufacturer???...