search for: artu

...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 "/sbin/shutdown -h +0" NOTIFYCMD /usr/local/bin/upssched-script NOTIFYFLAG ONLINE SYSLOG+WALL+EXEC NOTIFYFLAG ONBATT SYSLOG+WALL+EXEC NOTIFYFLAG LOWBATT SYSLOG+WALL+EXEC NOTIFYFLAG FSD SYSLOG+WALL+EXEC NOTIFYFLAG COMMOK SYSLOG+WALL+EXEC NOTIFYFLAG COMMBAD SY...

...>> > ?Maybe I have missing someting. I have exported my configuration to a .dev file, and then used for dummy ups, configured as dummy. Do i need to make circular tests (timer configuration) or may I do them manually? Just beacuse the only command allowed in dummy mode (upscmd -l dummy at artu) is load.off > Under the Bugs heading, the man page says "Instant commands are not yet supported in Dummy Mode..." - one of the use cases was automated developer testing of NUT, and there isn't much use in simulating all of the commands in that case. "load.off" is proba...

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 /var/run/nut/...

...o 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 > > Init SSL without certificate database > > Error: Driver not connected > > aehm, was the blazer_usb driver running? > ?This was tested with ? ?nutdrv_qx.... rroot at artu:~# upsdrvctl start Network UPS Tools - UPS driver controller 2.7.2 Network UPS T...

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 > Driver failed to start (exit status=1) > > root at artu:~# upsd > Network UPS To...

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 2.7.2 Network UP...

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

On Mon, 3 Jul 2017, Andrea de Lutti wrote: > 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_. Thi...

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

...#39;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.... > > rroot 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) > > but with blazer_usb seems better.... &gt...

...ntu1 (Installed from Ubuntu Software Center) Device name: Elite UPS 800VA (http://www.elit-ups.com/ita/pro_ups.html, discontinued) I can provider their *not working* linux monitoring tool Here is the result from starting upsdrvctl <http://networkupstools.org/docs/man/bcmxcp_usb.html> 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) Supported UPS detected with megatec protocol Rating information unavailable Vendor information unavailable No values provided for battery high/low voltages in ups.conf...

...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 recommend testing the shutdown procedure and making sure >> that everything works as expected on power failures. >> Please, let us know the results of these tests, so that we can add a >> more informed report about your devic...

> root at artu:~# /lib/nut/nutdrv_qx -a Elit -u nut -DDDDD > Network UPS Tools - Generic Q* USB/Serial driver 0.06 (2.7.2) > USB communication driver 0.32 > 0.000000 debug level is '5' ... > 0.574759 send: Q1 > 0.807418 received 46 (40) > 0.807475 read: (225.3...

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) Supported UPS detected with megatec protocol Rating information unavailable Vendor information unavailable No values provided for battery high/low voltages in ups.conf...

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) Supported UPS detected with megatec protocol Rating information unavailable Vendor information unavailable No values provided for battery high/low voltages in ups.conf...

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

...4.2 LTS > NUT Version: Nut 2.7.2-4Ubuntu1 (Installed from Ubuntu Software Center) > Device name: Elite UPS 800VA (http://www.elit-ups.com/ita/pro_ups.html, discontinued) I can provider their *not working* linux monitoring tool > > Here is the result from starting upsdrvctl > 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) > Supported UPS detected with megatec protocol > Rating information unavailable > Vendor information unavailable > No values provided for battery...

On Jun 8, 2017, at 9:15 AM, Andrea de Lutti <adelutti at gmail.com> wrote: > > 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 > Use the name from ups.conf in front of "@localhost". > Trying with nutdrv_qx, protocol megatec the driver does not start... > What if you try nutdrv_qx without specifying megatec? (It...

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 recommend testing the shutdown procedure and making sure > that everything works as expected on power failures. > Please, let us know the results of these tests, so that we can add a > more informed report about your device to...

...nsition. > ?Maybe I have missing someting. I have exported my configuration to a .dev file, and then used for dummy ups, configured as dummy. Do i need to make circular tests (timer configuration) or may I do them manually? Just beacuse the only command allowed in dummy mode (upscmd -l dummy at artu) is load.off > > Does the runtime calibration test alter the values of ups.conf? Or do I > have to change it manually? Which would be the right procedure for changing > the battery for calibrating NUT (over the manufacturer's suggestions)? > > The automatic calibration/batte...