search for: 800va

...ost of all the new megatec driver. 2007/6/10, esva2 at inbox.lv <esva2 at inbox.lv>: > Dear "Network UPS Tools" developers, > > Sorry for this mail, but we have some question! > Maybe you can help us. Did you product "NUT" supported "Mustek > PowerMust 800VA" UPS??? We have some problem with this model. All work fine > but when we start > use "upsmon" it don't shutdown our server correct. First halted UPS > and our server don't have time to start "shutdown -h +0". > > We use "mustek". Please hel...

Hi, It's just to confirme that I've tested and NUTUPS is working fine with hardware below: Manufacturer: LACERDA Hardware: NEW ORION 800VA Driver: blazer_usb Thanks for that. Regards, Alex. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20140618/3a98edf3/attachment.html>

Hello, I use a UPS APC 800VA. Use it with Openmediavault + Ups Nut plugin. My UPS is not in your list. :( I try in "Driver configuration directive" driver = usbhid-ups port = auto I have this in the log : omvhome upsmon[21683]: Poll UPS [ups at localhost] failed - Driver not connected Khampol.

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

Hi, I just acquired a Ritmo AS-800VA. Unfortunately, it doesn't work out of the box with nut - so I had to do a bit of reverse engineering on the protocol to get it working. Am now posting my findings here in the hope it will get this added to the next release. There are also 1000VA and 12000VA versions that this should work with...

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

Greets... ..just bought a cheap UPS today, works in debian 7.0 wrt nut 2.6.4 using richcomm_usb driver... ....output of upsc..... //// root at debian7:~# upsc starpower at localhost device.mfr: Richcomm dry-contact to USB solution device.model: UPS USB MON V1.4 device.serial: unknown device.type: ups driver.name: richcomm_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto

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

> 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 140.0 222.6 015 49.9 13.8 30.0 00001001 > 0.807516 qx_process_answer:

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

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)

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

Sorry, I didn't received it... I don't have any REPLBATT message, but when in battery test I have OL CAL status: it would be good to have the result. Anyway I still not receive any email on any test (power cord disconnected and/or reconnected for example) 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

> > , but when in battery test I have OL CAL status: it would be good to > have the result. > > "OL CAL" or "OB CAL"? If the UPS is powering the load from the battery > during calibration, it should report "OB CAL". The ONBATT handler in > NOTIFYCMD can check for CAL at that point. > > I don't think we considered the case where CAL is

> > > Bear in mind that upsmon runs as user "nut" on Ubuntu, as does the > NOTIFYCMD script. At one point, you said that the script is in /root, which > is not commonly readable by other users. Does the script work if you move > it to, say, /usr/local/bin? > > (With Ubuntu 16.04, there should be some error messages from upsmon in > 'journalctl'

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_. This means that the argument to

On Jul 3, 2017, at 11:06 AM, Andrea de Lutti <adelutti at gmail.com> wrote: > > ?I would like that NOTIFYCMD points to upssched?. > If I understand correctly, Roger is pointing out that your configuration is confusing upssched and upssched-script. Since you are using Ubuntu, upsmon.conf should contain "NOTIFYCMD /sbin/upssched". Similarly, upssched.conf should contain

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

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 >