similar to: Problem to connect to APC SC1500

Displaying 20 results from an estimated 100 matches similar to: "Problem to connect to APC SC1500"

2015 May 13
0
Problem connecting to APC Smart UPS SC1000 on Windows
Hello. I have problem with connecting to APC SC1000 using NUT port for windows 2.6.5-6. Last working version is NUT 2.6.1-1. With the same config files it works well. c:\NUT\bin>apcsmart.exe -a SC1000 Network UPS Tools - APC Smart protocol driver 3.1 (Windows-v2.6.5-5-7-g72f380c) APC command table version 3.1 w32_serial_open (COM3) setting initial state on COM3 0000007C = w32_serial_open
2013 May 11
1
blazer_ser problem on windows NUT 2.6.5-3780M
Hi, I have a bunch of UPSs, most connected to pcs with Linux working 100% with NUT. The only one I have a problem with, is connected to Windows 7 64bit, and I used the straight MSI installed from the website named NUT-Installer-2.6.5-4.msi Took me a while to find a way to get it to work, but it is ugly for now. Just starting up the service results in a NUT not working at all, and I tracked it
2013 Jan 30
3
bug report: apcsmart (WIN) 940-0024C connect fail, problem with command 'E'
Dear Ladies and Gentlemen, I have several old, yet functioning APC Smart-UPS (Model 600LS, Part AP600I, Firmware 6JI, no EEPROM, from 1991). They are not supported by Powerchute any more. I run NUT 2.6.5-4 on Windows XP SP3. I use COM1 port with cable 940-0024C. The connection fails with APC Smart protocol driver 3.0 (2.6.3-3534:3540M), APC command table version 3.0 or higher - it works with APC
2016 Jul 20
0
port for powercom
Ok, so I previously thought I had to use usbhid-ups but when I eventually got it going this is what I got:- This Powercom device (0d9f/0002) is not supported by usbhid-ups. Please use the 'powercom' driver instead. So I switched to the powercom driver, but I have tried a whole bunch of likely suspects for the port setting, none of which have worked Tried so far:- com1 with these
2012 May 10
3
battery.charge and other fixes needed for X-Power Tigra 1kVA
Hello all, been 5 years since I posted on this list, glad to be back :) I have a number of X-power Tigra 1kVA online UPS units. From some knowledgeable folks working for the local distributor, I learnt that from inside this looked like a Best 610 ups unit. Before, I had this UPS hooked via serial to my Windows 2003 server. For monitoring, some winpilot/upspilot software was also provided.
2013 Apr 02
3
blazer driver: Possible bugs with battery packs
Hello all, long time away from this list, glad to be around again! I have this Powercom Vanguard VGN VGD-20K31. Some details of this model: * 3-phase input, single phase output * Model has 240V / 12V9AH x 20 x 2SET, plus another set of 20 batteries. All in all, 3 sets * Serial connection to Windows 2k3 server with UPSMon Now I was strongly considering replacing the bundled no-good upsmoon
2009 Jun 25
1
Runaway apcsmart process
On several occasions I have seen the apcsmart process runaway using 100% CPU while filling my syslog partition by logging the following syslog entries at an incredible rate. I have seen up to 21,800 log entries PER SECOND of the following nature: --[snip]-- Jun 25 10:06:38 servername apcsmart[4012]: Communications with UPS lost: Communications with UPS lost - check cabling Jun 25 10:06:38
2011 Feb 15
2
[Bug 535583] Excessive logging by apcsmart program
2011/2/15 Lupe Christoph > On Monday, 2011-02-14 at 21:54:20 -0000, Arnaud Quette wrote: > > I definitely need more info! > > please reply to ALL: > > > - what is the exact model and date of manufacturing? > > SmartUPS 300I NET. I have the serial number (GS9809283199) but no date. > it seems to be a recent model. > - are you sure this unit is ok? > >
2011 Feb 15
2
[Bug 535583] Excessive logging by apcsmart program
2011/2/15 Lupe Christoph > On Monday, 2011-02-14 at 21:54:20 -0000, Arnaud Quette wrote: > > I definitely need more info! > > please reply to ALL: > > > - what is the exact model and date of manufacturing? > > SmartUPS 300I NET. I have the serial number (GS9809283199) but no date. > it seems to be a recent model. > - are you sure this unit is ok? > >
2006 Jun 19
2
Fw: Backups 300VA (BK-300C) Drivers
[BackUPS] driver = apcsmart port = /dev/ttyS0 desc "Back-UPS BK-300 @ Cap a l'orignal" > ----- Original Message ----- > From: "Charles Lepple" <clepple@gmail.com> > To: "NUT-MList" <nut-upsdev@lists.alioth.debian.org> > Sent: Monday, June 19, 2006 2:38 PM > Subject: Re: [Nut-upsdev] Backups 300VA (BK-300C) Drivers >
2013 May 07
2
Problems with USB-serial converters -- please advise on code fix
Hello! I've ran into this annoying issue when setting up a new server. I have an APC SmartUPS hooked up on a USB-serial converter on /dev/ttyUSB0. This works nicely, until: hub 3-0:1.0: port 1 disabled by hub (EMI?), re-enabling... pl2303 ttyUSB0: pl2303 converter now disconnected from ttyUSB0 usb 3-1: pl2303 converter now attached to ttyUSB1 apcsmart gets into an infinite loop of this:
2007 Jun 04
2
APCsmart serial port problem
I have a new APC Smart-UPS SUA2200RM2U. I've had no success with the manufacturer's PowerChute software and smart signaling, so I have decided to try NUT. The smartups 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:
2011 Jul 19
2
KIN-1500AP RM + Windows 2008 64-bit Standard R2 SP1 (nut 2.6.1)
I have only RS-232 on the box (meanwhile, it was manufactured on march of 2011) Here is my configs: nut.conf: * * MODE = netserver ups.conf: * * [KIN1500] driver = powercom port = notUsed desc = "Powercom KING PRO KIN-1500AP RM" upsd.conf: * * LISTEN 192.168.1.2 3493 upsd.users: * * [monuser] password = xxxxxxxx upsmon master
2008 Apr 18
2
My APC ups shutdown but doesn't start again
Hello, My APC Ups uses nut to manage all systems connected to it. But if online power failed until it shutdown, it not restart automatically after the power returned. It stay down until i restart it. When i execute the command: # upsc siUps1 it output me this: battery.alarm.threshold: L battery.charge: 018.0 battery.charge.restart: 15 battery.date: 03/31/07 battery.runtime: 120
2006 Jun 19
4
Backups 300VA (BK-300C) Drivers
Hi, What driver should i use with APC BK-300C ? Michale Plourde Digicom Technologies
2009 Mar 19
0
plz add support of APC sc1500i by NUT
thanks for these info. 2009/3/19 Artyom Mikhailov <artyom.mikhailov at gmail.com> > Hi there, > > Great project you have - NUT, thx for the development! > I just thought it might be usefull to let you know that APC SC1500I ups can > be found supported by NUT. > I used the following settings: > [sc1500i] > driver = apcsmart > port = /dev/ttyUSB0
2006 Feb 12
0
Re: sending personalized emails efficiently
Hi Tom, I noticed this message from you saying that you can use ActionMailer to efficiently do high volume mailing systems. I need to create something that mails out once a day to all my users status updates. But I must admit I don''t see how you can make ActionMailer do all these efficiences you state since it''s API is so limited. Specifically I don''t see how to NOT
2007 Dec 18
2
Problem with APC SMART SC 1500
Hello, I want to manage my SMART APC with nut 2.0.3 on Fedora Core 4. But i have this output at start of my ups: D?marrage de apcsmart :Network UPS Tools (version 2.0.3) - APC Smart protocol driver Driver version 1.99.7, command table version 2.0 Detected Smart-UPS SC1500 [5S0713T66466] on /dev/ttyS0 [ OK ] D?marrage de upsd
2011 Jan 25
1
[RFC] Updates to ACP smart driver
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.
2011 Feb 07
4
[PATCH/RFC v2 0/3] Updates to ACP smart driver
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 -