search for: smartmod

...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 servername apcsmart[4012]: smartmode: ser_send_char failed: Input/output error Jun 25 10:06:38 servername apcsmart[4012]: smartmode: ser_send_char failed: Input/output error Jun 25 10:06:38 servername apcsmart[4012]: smartmode: ser_send_char failed: Input/output error Jun 25 10:06:38 servername apcsmart[4012]: smartmode: ser_send_cha...

...ut -1, ReadTotalTimeoutMultiplier -1 vmin_ 1, vtime_ 0 action 0 vtime 0, vmin -1 ReadTotalTimeoutConstant -2, ReadIntervalTimeout -1, ReadTotalTimeoutMultiplier -1 vmin_ -1, vtime_ 0 COM3: device reports different attributes than requested Communications with UPS lost: serial port read error: 1381(smartmode): Input/out put error Communications with UPS lost: serial port read error: 1392(smartmode): Input/out put error Communications with UPS lost: serial port read error: 1381(smartmode): Input/out put error Communications with UPS lost: serial port read error: 1392(smartmode): Input/out put error Com...

...ut -1, ReadTotalTimeoutMultiplier -1 vmin_ 1, vtime_ 0 action 0 vtime 0, vmin -1 ReadTotalTimeoutConstant -2, ReadIntervalTimeout -1, ReadTotalTimeoutMultiplier -1 vmin_ -1, vtime_ 0 COM4: device reports different attributes than requested Communications with UPS lost: serial port read error: 1381(smartmode): Input/output error Communications with UPS lost: serial port read error: 1392(smartmode): Input/output error Communications with UPS lost: serial port read error: 1381(smartmode): Input/output error Communications with UPS lost: serial port read error: 1392(smartmode): Input/output error Communi...

...ebugging output, either because it does not tell > us enough or because I don't manage to capture it. > > I would have thought finding the place in the code where it is trying to > reset the UPS connection wouldn't be this hard. > this is not the problem. This code is in the smartmode() function of apcsmart.c: http://svn.debian.org/wsvn/nut/trunk/drivers/apcsmart.c we see the 5 attempts to go to smart mode ('Y' command), but my aim is to understand why it is failing, and how to cleanly solve this without impacting support for other units. Some more questions: - how ar...

...ebugging output, either because it does not tell > us enough or because I don't manage to capture it. > > I would have thought finding the place in the code where it is trying to > reset the UPS connection wouldn't be this hard. > this is not the problem. This code is in the smartmode() function of apcsmart.c: http://svn.debian.org/wsvn/nut/trunk/drivers/apcsmart.c we see the 5 attempts to go to smart mode ('Y' command), but my aim is to understand why it is failing, and how to cleanly solve this without impacting support for other units. Some more questions: - how ar...

...h.debian.org> > Sent: Monday, June 19, 2006 2:38 PM > Subject: Re: [Nut-upsdev] Backups 300VA (BK-300C) Drivers > > > > On 6/19/06, Michael Plourde <mplourde@digicom.ca> wrote: > > > I had used apcsmart driver and I got this error: > > > > > > smartmode: ser_send_char failed: Resource temporarily unavailable > > > Unable to detect an APC Smart protocol UPS on port /dev/ttyS0 > > > Check the cabling, port name or model name and try again > > > Driver failed to start (exit status=1) > > > > > > Any idea...

Hi, What driver should i use with APC BK-300C ? Michale Plourde Digicom Technologies

...SB-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: apcsmart[2285]: smartmode: issuing 'Y' failed: Input/output error while upsd becomes unhappy: upsd[2311]: Data for UPS [apc] is stale - check driver (because now it can't talk to the UPS) After this, a shutdown usually follows, though my understanding is that this should only happen on battery power. This...

...he 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 driver Driver version 1.99.8, command table version 2.0 smartmode: ser_send_char failed: Input/output error Unable to detect an APC Smart protocol UPS on port /dev/ttyS0 Check the cabling, port name or model name and try again Driver failed to start (exit status=1) [root]# ls -l /dev/ttyS0 crw--w---- 1 root root 4, 64 Jun 4 14:28 /dev/ttyS0 The ownership of th...

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.

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 -

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