search for: 0095b

Hey guys, I built my own 940-0024C cable as described here: http://www.networkupstools.org/cables/940-0024C.jpg My problem is that I can't receive anything. Sending (e.g. through minicom or my own application) works fine. Nut itself is not able to detect My UPS or anything else. <snip> [myups] driver = apcsmart port = /dev/ttyS0 cable = 940?0024C # also tested without cable option

I have been running a Smart-UPS RT 3000 VA using nut successfully over the 940-0095B cable for a couple of years. I have just received a second unit, but it is slightly different in 3 ways that I have found so far. 1. It's a Smart-UPS RT 3000 XL 2. The 940-0095B cable now uses an RJ45 connector at the UPS end. 3. It now requires a baud rate of 9600 instead of the 2400 used...

Hi, I have two APC UPS models and I am trying to find out if it is possible to cut power down via serial connection in Ubuntu Server 12.04.1 AMD64 system. I have models: APC Back-UPS Pro 650 (BP650SI) APC Back-UPS 650 (BK650MI) I have also APC serial cables 940-0020C and 940-0095B. Is this possible with my current hardware? If it isn't possible, could you recommend model(s) on which has this feature? Does it exist models with which user is able to control the power per power socket? Tero

...driver can't make contact through the serial port. Since this is rack-mounted, it comes with a 940-1524 serial cable. As far as I can tell, this is supposed to work with smart signaling. Here's my ups.conf: [myups] driver = apcsmart port = /dev/ttyS0 cable = 940-0095B sdtype = 0 Here's a session which illustrates the problem: [root]# ls -l /dev/ttyS0 crw------- 1 nut nut 4, 64 Jun 4 14:28 /dev/ttyS0 [root]# /usr/local/nut/bin/upsdrvctl start Network UPS Tools - UPS driver controller 2.0.5 Network UPS Tools (version 2.0.5) - APC Smart protocol dri...

...he UPS and works well. running apcsmart -a ups gives the following: com1: device reports different attributes than what were set unable to detect an APC Smart protocol UPS on port com1 check the cabling, port name or model name and try again ups.conf: [ups] driver=apcsmart port=com1 cable=940-0095B desc="test" Sysinternals Portmon captures the following activity on com1: 0.00009862 apcsmart.exe IRP_MJ_WRITE Serial0 SUCCESS Length 1: 59 Y 0.00001090 apcsmart.exe IRP_MJ_READ Serial0 SUCCESS Length 1: 53 S 0.00000950 apcsmart.exe...

...n the current version of nut. Is it possible for you to try current version of nut ? There should be apcsmart-old present in your build as well, so if it's not possible - you can use the previous version easily. > ups.conf: > [ups] > driver=apcsmart > port=com1 > cable=940-0095B > desc="test" > > Sysinternals Portmon captures the following activity on com1: > > 0.00009862 apcsmart.exe IRP_MJ_WRITE Serial0 SUCCESS Length 1: 59 Y > 0.00001090 apcsmart.exe IRP_MJ_READ Serial0 SUCCESS Length 1: 53...

...but do respond to the full Smart-UPS command set: battery.alarm.threshold: 0 battery.charge: 100.0 battery.charge.restart: 00 battery.date: 02/22/93 battery.runtime: 2040 battery.runtime.low: 120 battery.voltage: 27.67 battery.voltage.nominal: 024 driver.name: apcsmart driver.parameter.cable: 940-0095B driver.parameter.pollinterval: 2 driver.parameter.port: /dev/ttyS0 driver.version: 2.2.0 driver.version.internal: 1.99.8 input.frequency: 50.00 input.quality: FF input.sensitivity: L input.transfer.high: 260 input.transfer.low: 196 input.transfer.reason: R input.voltage: 239.3 input.voltage.maximum...

Sorry for a bit longer delay than I anticipated, I was stuffed with the work. This is the next iteration of the patch adding some functionality to apcsmart driver, and relying on 'ignorelb' recently added. Follow up from previous thread: http://www.mail-archive.com/nut-upsdev at lists.alioth.debian.org/msg02331.html Main differences is that V3 is split into many small patches, so the

This patch introduces a handful of new options, I mentioned earlier in: http://www.mail-archive.com/nut-upsdev at lists.alioth.debian.org/msg02088.html See the large commit message in the follow-up for the details and rationale. I realize it's a bit larger diff - so if it's required I can split it into few smaller ones. Michal Soltys (1): APC smart driver update and new features.

...to your computer. # # Possible generic choices for <cable> are: # simple, smart, ether, usb # # Or a specific cable model number may be used: # 940-0119A, 940-0127A, 940-0128A, 940-0020B, # 940-0020C, 940-0023A, 940-0024B, 940-0024C, # 940-1524C, 940-0024G, 940-0095A, 940-0095B, # 940-0095C, M-04-02-2000 # #UPSCABLE smart UPSCABLE usb # To get apcupsd to work, in addition to defining the cable # above, you must also define a UPSTYPE, which corresponds to # the type of UPS you have (see the Description for more details). # You must also specify a DEVICE, sometimes ref...

This is 2nd version of the earlier patch featuring a few new features and fixes to the apcsmart driver, following the remarks in: http://www.mail-archive.com/nut-upsdev at lists.alioth.debian.org/msg02294.html Major changes from v1: - handle battery.charge and battery.runtime checks at main.c level - handle "immutable but writable" conflict gracefully at driver level -