similar to: Help with Elite 800VA usb UPS

Thanks a lot, I will do it and keep you informed. Best regards Andrea 2017-06-12 12:34 GMT+02:00 Manuel Wolfshant <wolfy at nobugconsulting.ro>: > On 06/12/2017 12:56 PM, Andrea de Lutti wrote: > > > >> > I have also successfully tested the battery... >> > >> > upscmd -uadmin -pups Elit at artu test.battery.start.quick >> >> I would also

So....seems so better... Each time I rebbot, I miss the /var/run/nut folder... root at artu:~# upsdrvctl start Network UPS Tools - UPS driver controller 2.7.2 Network UPS Tools - Megatec/Q1 protocol USB driver 0.11 (2.7.2) Can't chdir to /var/run/nut: No such file or directory Driver failed to start (exit status=1) root at artu:~# upsd Network UPS Tools upsd 2.7.2 fopen

Thank you for your reply Charles, this is the "upsc" result: root at artu:~# upsc ups at localhost Init SSL without certificate database Error: Unknown UPS Trying with nutdrv_qx, protocol megatec the driver does not start... 2017-06-08 14:47 GMT+02:00 Charles Lepple <clepple at gmail.com>: > On Jun 7, 2017, at 12:54 AM, Andrea de Lutti <adelutti at gmail.com> wrote:

Hi, it's me again. I haven't yet tested my UPS with full load, but I have tried to insert some values in ups.conf, I have kept the example on the blazer_usb driver help page: runtimecal = 240,100,720,50 When I try to start the driver, I receive root at artu:~# upsdrvctl start Network UPS Tools - UPS driver controller 2.7.2 Network UPS Tools - Megatec/Q1 protocol USB driver 0.11 (2.7.2)

> > > root at artu:~# upsc Elit at artu > > Init SSL without certificate database > > battery.voltage: 13.90 > > battery.voltage.high: -1.08 > > battery.voltage.low: -0.87 > > device.type: ups > > driver.name: blazer_usb > > driver.parameter.pollinterval: 2 > > driver.parameter.port: auto > > driver.version: 2.7.2 > >

> > hmm, apparently the UPS doesn't close the replies to our queries with > the expected CR and we (I) did not consider that case in nutdrv_qx -- > noted: > https://github.com/networkupstools/nut/issues/441 > > But blazer_usb, being less strict on the terminating CR of Q1 replies, > should work with your device. > > > root at artu:~# upsc Elit at artu > >

Thanks mates, as suggested I have added runtimecal = 240,100,720,50 default.battery.voltage.low = 10.4 default.battery.voltage.high = 13.8 (the actual charging voltage) In ups.conf I have also added the startup procedure in rc.local file, everything is fine... I have only to make a deep test. Is there a way to add a NOTIFYMSG value for the battery test? Thank you lots Andrea

Use the name from ups.conf in front of "@localhost". ?The re?sult is quite different ;) root at artu:~# upsc Elit at artu Init SSL without certificate database Error: Driver not connected > What if you try nutdrv_qx without specifying megatec? (It should > autodetect.) > ?Here is the result: ? root at artu:~# upsdrvctl start Network UPS Tools - UPS driver controller

On Jun 29, 2017, at 6:52 AM, Andrea de Lutti wrote: >>> Anyway I still not receive any email on any test (power cord disconnected and/or reconnected for example) >> >> Oh, I misinterpreted "working script" as a script that was sending email, rather than work-in-progress. Does that same command work from the command line? Can you add something like "logger"

On Jun 7, 2017, at 12:54 AM, Andrea de Lutti <adelutti at gmail.com> wrote: > > > Hi, I have tried several drivers for make my Elite UPS working. > With blazer_usb I can contact it, but I have no informations. This is the best result. > > OS: Ubuntu Xenial 16.04.2 LTS > NUT Version: Nut 2.7.2-4Ubuntu1 (Installed from Ubuntu Software Center) > Device name: Elite UPS

Ok, I am running NUT in dummy mode. I have added a new ups in ups.conf [dummy] driver = dummy-ups port = upsc.dev desc = "dummy ups for testing purposes" upsc.dev has been generated by exporting the Elit configuration. I have added the monitor line in upsmon.conf and the "exec" flags (all the events) MONITOR dummy at artu 1 user pass master SHUTDOWNCMD

Hi, it's me again. I haven't yet tested my UPS with full load, but I have tried to insert some values in ups.conf, I have kept the example on the blazer_usb driver hel page: runtimecal = 240,100,720,50 When I try to start the driver, I receive root at artu:~# upsdrvctl start Network UPS Tools - UPS driver controller 2.7.2 Network UPS Tools - Megatec/Q1 protocol USB driver 0.11 (2.7.2)

> > > > MONITOR dummy at artu 1 user pass master >> SHUTDOWNCMD "/sbin/shutdown -h +0" >> NOTIFYCMD /usr/local/bin/upssched-script >> > > Hi, As far as I can see, what you are getting in syslog corresponds > correctly to what you have specified. You have specified that upsmon is to > call upssched-script _directly_. This means that the argument

2017-06-11 14:10 GMT+02:00 Andrea de Lutti <adelutti at gmail.com>: > So....seems so better... > > Each time I rebbot, I miss the /var/run/nut folder... > > root at artu:~# upsdrvctl start > Network UPS Tools - UPS driver controller 2.7.2 > Network UPS Tools - Megatec/Q1 protocol USB driver 0.11 (2.7.2) > Can't chdir to /var/run/nut: No such file or directory >

> Starting the driver with debug level 5 seems happier, but continue to cycle It is meant to 'cycle', it's working correctly. When you run the driver normally (i.e. not in debug mode), you don't see all that output (plus, after having established a connection with the device, the driver goes into the background), but it's doing exactly the same thing. > nutdrv_qx....

On Jun 27, 2017, at 9:23 AM, Andrea de Lutti <adelutti at gmail.com> wrote: > > Sorry, I didn't received it... You should be subscribed to the list now. > I don't have any REPLBATT message Right, you would only get REPLBATT messages when the UPS reports that the battery *needs to be replaced* (and then at regular intervals per the upsmon.conf parameters). > , but

On Jun 26, 2017, at 7:03 AM, Andrea de Lutti <adelutti at gmail.com> wrote: > > Are there no warnings for battery test? not sure if you saw my reply on 2016-06-17: Do you mean a notification that a test is in progress, or something for the results? There is the REPLBATT message in upsmon when the battery test fails, but I don't think the generic Qx protocol supports the RB

Thank you lots! Finally I have everything working! Which are the ups.status I can use with ups in dummy mode? I have seen only OB, LB, OL... thank you Andrea 2017-07-04 19:55 GMT+02:00 Charles Lepple <clepple at gmail.com>: > On Jul 3, 2017, at 11:06 AM, Andrea de Lutti <adelutti at gmail.com> wrote: > > > > ?I would like that NOTIFYCMD points to upssched?. > >

Good morning again, I have finished some tests and the driver works perfectly for shutting down the server and a client, both Ubuntu 16.04. I have to change the battery, I am unable to test with 100% load and now I have 5 minutes of battery power with a load of 18%. I am still unable to send email notifications, I have enabled all the warnings in upsmon.conf: NOTIFYFLAG ONLINE

On Jun 16, 2017, at 2:20 AM, Andrea de Lutti <adelutti at gmail.com> wrote: > Using 'guestimation' (low: -0.866667, high: -1.083333)! > Initial battery charge undetermined > Driver failed to start (exit status=1) The "low" and "high" voltages should correspond to the battery voltage when it is discharged (LB) and charged, respectively. For a 12V