similar to: APC Easy UPS

It seems the `libmodbus` library or headers were not found, or something similar - so the driver against it was not built. Did you install `libmodbus-dev` before the build? What does `config.log` in the build root say (and.or the summary shown after you run the `configure` script)? On Sat, Sep 16, 2023 at 7:46?PM FatGear <fatgear1 at free.fr> wrote: > Hi, > > I don't know what

Hello there, I don't think that's working,? I have done all your repo but i don't know how it's supposed to work. I have a idea, change vendor id and product id? to make the driver try to connect to the ups, what do you think of that ? With this driver maybe : usbhid-ups FatGear Le 16/09/2023 ? 20:40, Jim Klimov a ?crit?: > It seems the `libmodbus` library or headers were

Well, now that the `subdriver` option got added to `usbhid-ups` too, you can at least try that (by building again the current master). See command-line help for the subdrivers it would currently recognize, and copy e.g. the first word as the matching option, e.g.: ./drivers/usbhid-ups -DDDDDD -d1 -s test -x port=auto -x vendorid=... -x productid=... -x subdriver=... and try to lockpick your

Hello There, I tried your advice and i don't think it works either, See the logs, " /tmp/nut# ./drivers/usbhid-ups -DDDDDD -d1 -s test -x port=auto -x vendorid=... -x productid=... -x subdriver=... Network UPS Tools - Generic HID driver 0.52 (2.8.0-2557-g81fca30b2) USB communication driver (libusb 1.0) 0.46 ?? 0.000000??? [D3] main_arg: var='port' val='auto' ??

<facepalm ;)> the ellispis "something=..." were supposed to be replaced by your device ID numbers, etc. On Sat, Sep 23, 2023, 18:26 FatGear <fatgear1 at free.fr> wrote: > Hello There, > > I tried your advice and i don't think it works either, > > See the logs, > > " > > /tmp/nut# ./drivers/usbhid-ups -DDDDDD -d1 -s test -x port=auto -x

Hi, Am I hitting some limit in match? Consider the following example: > tst<-seq(100,125,by=.2)%in%seq(0,800,by=.1) > sum(tst) [1] 76 > seq(100,125,by=.2) [1] 100.0 100.2 100.4 100.6 100.8 101.0 101.2 101.4 101.6 101.8 102.0 102.2 [13] 102.4 102.6 102.8 103.0 103.2 103.4 103.6 103.8 104.0 104.2 104.4 104.6 [25] 104.8 105.0 105.2 105.4 105.6 105.8 106.0 106.2 106.4 106.6 106.8

Hi, Am I hitting some limit in match? Consider the following example: > tst<-seq(100,125,by=.2)%in%seq(0,800,by=.1) > sum(tst) [1] 76 > seq(100,125,by=.2) [1] 100.0 100.2 100.4 100.6 100.8 101.0 101.2 101.4 101.6 101.8 102.0 102.2 [13] 102.4 102.6 102.8 103.0 103.2 103.4 103.6 103.8 104.0 104.2 104.4 104.6 [25] 104.8 105.0 105.2 105.4 105.6 105.8 106.0 106.2 106.4 106.6 106.8

Hello, I am working on getting NUT working with my Smart-UPS 900 UPS (with the C c= able) For several years, I have used the apcupsd product, but because of the nagios support for nut, I am working on switching over. Under apcupsd, I get tons of information from my UPS: # /usr/local/sbin/apcaccess status DATE : Sat Jul 09 12:56:41 CDT 2005 HOSTNAME : homer RELEASE : 3.8.6 UPSNAME :

Hi, The patch below adds support for a pair of old (circa 1993) APC Smart-UPS 600 devices that I have. They don't support the query mechanism of newer APC devices 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

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:

Thanks for the help, with the apcsmart-old driver it works again! Didn't notice my UPS is now so "old" ;-) Here is the output of upsc with apcsmart-old driver: battery.alarm.threshold: 0 battery.charge: 100.0 battery.charge.restart: 00 battery.date: 11/22/06 battery.packs: 001 battery.packs.bad: 000 battery.runtime: 540 battery.runtime.low: 120 battery.voltage: 53.73

Hello, We have a APC SMART-UPS 2200 which gives the following status information: battery.alarm.threshold: 0 battery.charge: 089.0 battery.charge.restart: 00 battery.date: 01/10/04 battery.packs: 000 battery.runtime: 21180 battery.runtime.low: 120 battery.voltage: 52.95 battery.voltage.nominal: 048 driver.name: apcsmart driver.parameter.pollinterval: 2 driver.parameter.port: /dev/ttyS0

Hi all, Thought I'd forward this on, as the apcsmart driver doesn't appear to have any support for this (admittedly obscure) setting and it doesn't seem to be listed at http://www.networkupstools.org/protocols/apcsmart.html. Hope someone finds it useful. Later, Russ -- Russell Odom http://www.gloomytrousers.co.uk/ Fast, cheap, good: pick two. -------- Original Message --------

Hi Paul, > I have another NUT client for your client-projects[1] page: MonAMI[2]. > > MonAMI aims to be a "universal sensor framework". The data gathered from > MonAMI's NUT plugin can be sent to any of the output plugins. Currently, > these include Ganglia, Nagios, KSysguard and a file-logger (amongst others). interesting though I've not had time to

Hi, I'm running this command: # upsrw -s "battery.date=2013Jun7" -u ups-mon-IT "IT-APC-BOTTOMRIGHT at 127.0.0.1" Password: OK but I'm getting this listing: # upsc IT-APC-BOTTOMRIGHT at 127.0.0.1 battery.alarm.threshold: 0 battery.charge: 100.0 battery.charge.restart: 15 battery.date: 01/10/06 battery.packs: 000 battery.runtime: 1440 battery.runtime.low: 120

Hi, One of my APC devices reports: "unacceptable utility voltage rate of change". I believe it has something to do with input voltage fluctuating too fast maybe even beneath or over the input voltage thresholds. Should I worry about this? should I measure input voltage? (I suppose I'd need more than multimeter readings. Maybe an oscilloscope or a multimeter that can record

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

Hi, I have two types of UPS devices and one of them (APC) gave me a false "low battery" alert. I can't reproduce the problem... Also, there was nothing apparently wrong with the UPS at the time of the false alert. All I could do was grab the driver values within a minute after the "low battery" notification. These are the values: battery.runtime.low : 120

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

Using nut v2.2.2, and the APC serial cable. I have a client who's APC SMART-UPS 1500 (circa 2000) is always reporting LB. The batteries were old so they were replaced two weeks ago with brand new batteries. UPS still reported low batteries... I ran a calibration and a test on the unit (using the nut upscmd utility) During those tests, the battery charge on the unit goes to zero and slowly