similar to: Cyberpower CP550SL/AE550 Serial

Hello, I have the Cyberpower USB CP550SL RT< whats its called when i bought it :) (AE550 according to upsc) and i think its missing some monitor options such as load, wattage use, temp..etc (shows in powerpanel pro,personal ed under win) ..it seem to be really lacking the only options i get are battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.runtime: 4560

Hi, I finally got the serial cable for this CyberPower CP550SL / AE550, and have successfully tested the genericups type 7 driver. The shutdown delay is about 2 minutes after the shutdown signal, and that signal needs to be rather long, I got it to work with 20 seconds. I suspect that all CyberPower UPSes that are compatible with the Windows UPS service are type 7. All references to the

So I just bought one of these fabulous CyberPower UPS devices from BestBuy hoping I could control it with my machine. Luckily, I found NUT! I've got the SVN sources and compiled and installed them but I haven't been able to get it to recognize the usb AE550. When I plug the usb cable in I see this in syslog: Feb 6 22:36:56 mythbox kernel: usb 1-1: new low speed USB device using

Hope it's not too rude to just drop this here for y'all... Checking device (0764/0501) (001/005) - VendorID: 0764 - ProductID: 0501 - Manufacturer: CPS - Product: UPS AE550 - Serial Number: unknown This one and their 485 don't provide a load measurement -- the Windows drivers kick it onto battery for a timed period and measure the drain to guess the runtime -- apparently all their

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

Here are couple of things I tried. 1) Changed the USB cable. Same problem 2) I put an old CyberPower CP550SL w/USB&SERIAL and it recognize it right away via the USB port I don?t know if that will give you any insight or eliminate certain things with the Tripp Lite SMART1300LCDT or not. Sent from Mail for Windows 10 From: Charles Lepple Sent: Tuesday, August 18, 2015 6:37 PM To: Johnny

On Aug 19, 2015, at 9:00 AM, Charles Lepple <clepple at gmail.com> wrote: > > On Aug 19, 2015, at 12:08 AM, Johnny Wong <e430benz98 at yahoo.com> wrote: >> >> Here are couple of things I tried. >> >> 1) Changed the USB cable. Same problem >> 2) I put an old CyberPower CP550SL w/USB&SERIAL and it recognize it right away via the USB

Peter Selinger wrote, > Hi Joe, > > I read between the lines that (a) you are using the newhidups driver, > and (b) it is working. Is this correct? You might want to post the > output of "upsc" just for the record. Whups, I should've been more clear and less terse -- it's been a long weekend putting the machines these are supporting into production! This

I have gotten the links to the ./configure for NUT for NAS4Free see nas4free build makefile http://sourceforge.net/p/nas4free/code/ ... t/Makefile config files: http://sourceforge.net/p/nas4free/code/ ... nut/files/ I hope this give some insights On Wednesday, August 19, 2015 6:00 AM, Charles Lepple <clepple at gmail.com> wrote: On Aug 19, 2015, at 12:08 AM, Johnny Wong

Hi, I recently bought a Nitram Elite 2005 UPS and i installed nut to monitor it. Unfortunatly, i often have timeout errors (20 timeout per days): Broadcast Message from aurelien at berkelium (no tty) at 18:05 CET... Communications with UPS Nitram at localhost lost Broadcast Message from aurelien at berkelium (no tty) at 18:05 CET... Communications with UPS Nitram(AT)localhost

Hi, I recently bought a Nitram Elite 2005 UPS and i installed nut to monitor it. Unfortunatly, i often have timeout errors (20 timeout per days): Broadcast Message from aurelien at berkelium (no tty) at 18:05 CET... Communications with UPS Nitram at localhost lost Broadcast Message from aurelien at berkelium (no tty) at 18:05 CET... Communications with UPS Nitram(AT)localhost

Debian sid package v. 2.6.4-2.3 UPS nitram elite 2002 700VA (serial port) MOBO A7V8X-X ================================ Hi list, Everything work fine, except after an AC supply shortage: the UPS don't come back to a normal behavior, it stays on battery (of course, it works right w/o any cable). Is there something I can do recover a normal behavior? JY -- Too much of a good thing is

Hello, I've just finish a new driver for the Nitram UPS Elite 2005 500VA (compiled and tested with nut-2.0.1 and nut-2.1.0). Currently, all Nitram UPS are made by CyberPower, but the protocol is different than cyberpower.c. I don't have other model to test with, but I think this driver could monitor all Nitram 2005 UPS. I don't have the protocol specifications and thus some parts

Hi, Since Sharps communication protocols are "top secret", I'm trying to port their sync software to linux. I'm new to wine, so this might be silly, but after hours of googling and searching for solutions I'm posting this. After installing DCOM98.exe, the Desktop software installed, and it runs. Only problem is it doesn't detect the device connected to the serial port

I've just noticed that cpsups isn't listed anymore in driver.list. Any reason not have removed it from the source too? Still on the way to 2.4; any update on your confidence level to remove nitram and cyberpower too? -- Arnaud

On 04/06/2014 at 09:44, Bruno Salvador <bruno.salvador at gmail.com> wrote: > What Douglas can do is to patch the solis executable in > /usr/local/libexec/nut/solis inside freenas, with the patches that I have > posted in the forum: Dear guys, Following your suggestions I was able to make NUT recognize my UPS model. Actually, the only modification I had to introduce in solis.c

Hi, I've installed Nut 2.0.5 on a RedHat 9 box. I have a GeekSquad 1500 UPS. (GeekSquad is a BestBuy brand) I've found out that it's actually a CyberPower 1500 AVR LCD. I'm using it with the serial cable. I'm unable to get it working with any of the drivers provided with NUT. I've tried cpsups, cyberpower and powerpanel. here's the output of the different drivers

On Mon, May 30, 2016 at 06:13:51PM +0200, Peter Wu wrote: > Do you have any suggestions for the case where the pcieport driver > refuses to put the bridge in D3 (because the BIOS is too old)? In that > case the nouveau driver needs to fallback to the DSM method (but not > when runtime PM is deliberately disabled by writing control=on). Do you know what Windows does then? I think we

Hello. Trouble to communicate with APC SmartUPS via serial port. UPS connected to the com1 port on windows host. Communication witch hyperterm works well. There is a log: YSM ^ASmart-UPS SC1000 n5S0713T63247 m03/29/07 L240.0 B27.10 apcupsd also can communicate with the UPS and works well. running apcsmart -a ups gives the following: com1: device reports different attributes than what were set