similar to: [PATCH]Support full capabilities on older Smart-UPS 600

G'day y'all, Here's a tiny patch set for drivers/apcsmart.c and drivers/apcsmart.h. Adds APC SmartUPS 1250 ("8QD" case) + 940-0024C recognition to apcsmart. (Unpatched apcsmart.c v1.99.8 misidentifies the SmartUPS 1250 as a "dumb" UPS.) For NUT 2.0.5+. NUT 2.0.5: Patches apply successfully. Builds successfully. Works as expected under Ubuntu 7.04. NUT 2.2:

Hi there, I am using an old (really old) APC Smart-UPS 600. It worked fine under apcupsd but when I tried NUT it did not work. The error I was getting was: sudo /lib/nut/apcsmart -DDD /dev/ttyS1 Network UPS Tools (version 2.0.4) - APC Smart protocol driver Driver version 1.99.8, command table version 2.0 debug level is '3' Attempting firmware lookup Firmware: [D4] Not found in

2009/5/3 Thomas Juerges > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi Arnaud, > Hi Thomas, > I just checked the 2.4.1 version of nut and found that you forgot to add > my old UPS model (APC Smart-UPS 900). I guess it is because you were > busy at the time when I sent you the patch. So here it goes again. :) > uh, right sorry. I was pretty sure I applied

Hey Jarett, 2009/2/24 <jarett.stevens at usermail.com> > After upgrading to the 2.4.1 version, I wasn't able to read as many > variables from my UPS. After a bit of experimentation, I determined that > the firmware on my UPS was different than what is currently in the > apcsmart driver, though it had worked before. I located my firmware > version (5ZM), and added in

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 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 -

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.

Dir list! I'm using nut for many years on my home "server" without problems running on Debian 6.x nut version 2.4.3 Now I have decided to move to Debian 10. I have started from zero and install new system on a different disk. I have successfully installed new nut version 2.7.4 I've found one issue, that new version see always "low battery" state. Excerpt from syslog:

As I requested here: https://bugzilla.redhat.com/show_bug.cgi?id=678793 Add support for Matrix-UPS firmware 0XM/0XI with additional commands Description of problem: The attached patch adds support for Matrix-UPS revision strings 0XI and 0XM to the apcsmart driver. The revision string itself isn't completely opaque--it is made up of different parts as documented on

Greetings all! A recent news item got me thinking that a problem stated therein could provide a teasing little exercise in R programming. http://www.bbc.co.uk/news/uk-england-cambridgeshire-17680326 Cambridge University hosts first European 'maths Olympiad' for girls The first European girls-only "mathematical Olympiad" competition is being hosted by Cambridge

I was check out that is the connection between driver-monitor-server-client is working or not. I was put my server directly on power cable, keep control cable connection and use command: $ watch upsc APC600 I was switch to battery, after 2-3 second it show that is on battery OB and after it shutdown because of low battery LO. I think that systemd scripts some what unsynchronized, but after it

The blowfish crypt(3) mechanism supports the use of a "cost value" for password encryption. The cost value is encoded into the encrypted password that is stored in master.passwd. On OpenBSD, this cost value can be set in login.conf. FreeBSD does not currently support the cost value. The cost value is the base-2 logarithm of the number of rounds of encryption to use so

Hello, I have error on compiling time I tried on HP-UX 11.00 system with gcc version 3.1 to compile samba source Samba latest version source was dowloaded from www.us1.samba.org/samba/ftp I attached log file with this error thank you. begin 600 samba_make.log.doc M(R!M86ME#0HO=7-R+VQO8V%L+W-A;6)A+V)I;B(@+410241$25(](B]U<W(O M;&]C86PO<V%M8F$O=F%R+VQO8VMS(B

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

On 2014-01-14 10:12, dstrr wrote: > 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. >

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

Charles, here is the command(s) output using uhidd.... # uhidd -v -u /dev/ugen1.3ugen1.3[0]-> HID interface ugen1.3[0]-> Report descriptor size = 27 ugen1.3[0]-> Kernel driver is active ugen1.3[0]-> kernel driver detached! ugen1.3[0]-> Find IN interrupt ep: 0x81 packet_size=0x8 # /usr/local/libexec/nut/blazer_usb -a UPSonic -u root -DDDD 0.000000 debug level is

would someone be kind enough to paste the code below into an R session ( ir you can paste it into a file and just source it ) and take a look at it ? I must be doing something wrong but i can't find it. I start out with a zoo object that has 100 elements in it. then, i only want to keep the rows in which the bid and the ask are both grester than zero. ( maybe my logic is wrong there ? ).

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

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 previously.