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, 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 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 > > > > Using 'guestimation' (low: -0.866667, high: -1.083333)! > > Battery runtime will not be calculated (runtimecal not set) > > What does "upsc" show for this UPS? > > Note that the blazer_usb driver is no longer maintained. Its replacement > is nutdrv_qx: > > http://networkupstools.org/docs/man/nutdrv_qx.html-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20170608/e8039602/attachment.html>
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 should autodetect.) If that doesn't work, please try to get some logs - they will look like this: http://lists.alioth.debian.org/pipermail/nut-upsuser/2017-March/010555.html The author of the driver recommends a debug level of 5: "-DDDDD" (Note that we are not looking for the debug output for upsdrvctl, but rather for nutdrv_qx. If you pass "-D" flags to upsdrvctl, it should tell you how to start the driver in debug mode instead.)
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 UPS Tools - Generic Q* USB/Serial driver 0.06 (2.7.2) USB communication driver 0.32 Device not supported! Device not supported! Driver failed to start (exit status=1)> If that doesn't work, please try to get some logs - they will look like > this: > > http://lists.alioth.debian.org/pipermail/nut-upsuser/ > 2017-March/010555.html > > The author of the driver recommends a debug level of 5: "-DDDDD" > > (Note that we are not looking for the debug output for upsdrvctl, but > rather for nutdrv_qx. If you pass "-D" flags to upsdrvctl, it should tell > you how to start the driver in debug mode instead.)?Here is the output of debug level 5:? 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.001187 upsdrv_initups... 0.414464 Checking device (1D6B/0001) (006/001) 0.477567 - VendorID: 1d6b 0.477611 - ProductID: 0001 0.477619 - Manufacturer: unknown 0.477627 - Product: unknown 0.477634 - Serial Number: unknown 0.477648 - Bus: 006 0.477656 Trying to match device 0.477668 Device does not match - skipping 0.477784 Checking device (1D6B/0001) (005/001) 0.541404 - VendorID: 1d6b 0.541733 - ProductID: 0001 0.541933 - Manufacturer: unknown 0.542124 - Product: unknown 0.543843 - Serial Number: unknown 0.543897 - Bus: 005 0.543935 Trying to match device 0.543978 Device does not match - skipping 0.544122 Checking device (FFFF/0000) (004/004) 0.561393 - VendorID: ffff 0.561428 - ProductID: 0000 0.561438 - Manufacturer: 0.561443 - Product: 010937 0.561457 - Serial Number: 0.561461 - Bus: 004 0.561466 Trying to match device 0.561473 Device matches 0.565355 send_to_all: SETINFO ups.vendorid "ffff" 0.565815 send_to_all: SETINFO ups.productid "0000" 0.566137 send: QGS 0.566421 read: QGS 0.566708 qx_process_answer: short reply (input.voltage) 0.567007 send: QGS 0.567377 read: QGS 0.567668 qx_process_answer: short reply (input.voltage) 0.567965 send: QGS 0.568256 read: QGS 0.568609 qx_process_answer: short reply (input.voltage) 0.568952 send: M 0.569310 read: M 0.569498 voltronic_qs_protocol: invalid protocol [M] 0.569678 ups_infoval_set: failed to preprocess value [ups.firmware.aux: M] 0.569866 send: M 0.570071 read: M 0.570262 voltronic_qs_protocol: invalid protocol [M] 0.570460 ups_infoval_set: failed to preprocess value [ups.firmware.aux: M] 0.570653 send: M 0.570834 read: M 0.571024 voltronic_qs_protocol: invalid protocol [M] 0.571213 ups_infoval_set: failed to preprocess value [ups.firmware.aux: M] 0.571405 send: QS 0.571587 read: QS 0.571781 qx_process_answer: short reply (input.voltage) 0.571973 send: QS 0.572155 read: QS 0.572343 qx_process_answer: short reply (input.voltage) 0.572532 send: QS 0.572716 read: QS 0.572903 qx_process_answer: short reply (input.voltage) 0.573093 send: D 0.573288 read: D 0.573481 qx_process_answer: short reply (input.voltage) 0.573673 send: D 0.573853 read: D 0.574041 qx_process_answer: short reply (input.voltage) 0.574236 send: D 0.574414 read: D 0.574600 qx_process_answer: short reply (input.voltage) 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: short reply (input.voltage) 0.807548 send: Q1 1.041418 received 46 (40) 1.041472 read: (225.3 140.0 224.5 015 49.9 13.9 30.0 00001001 1.041487 qx_process_answer: short reply (input.voltage) 1.041508 send: Q1 1.275423 received 46 (40) 1.275476 read: (225.3 140.0 222.6 015 49.9 13.9 30.0 00001001 1.275489 qx_process_answer: short reply (input.voltage) 1.275511 send: Q1 1.509410 received 46 (40) 1.509463 read: (225.3 140.0 222.6 015 49.9 13.9 30.0 00001001 1.509501 qx_process_answer: short reply (input.voltage) 1.509566 send: Q1 1.743299 received 46 (40) 1.743344 read: (225.3 140.0 222.6 015 49.9 13.9 30.0 00001001 1.743353 qx_process_answer: short reply (input.voltage) 1.743365 send: Q1 1.976367 received 46 (40) 1.976428 read: (225.3 140.0 222.6 015 49.9 13.9 30.0 00001001 1.976441 qx_process_answer: short reply (input.voltage) 1.976453 send: Q1 2.438350 received 46 (40) 2.438409 read: (225.3 140.0 224.5 015 49.9 13.9 30.0 00001001 2.438453 qx_process_answer: short reply (input.voltage) 2.438523 send: Q1 2.672338 received 46 (40) 2.672398 read: (225.3 140.0 224.5 015 49.9 13.9 30.0 00001001 2.672411 qx_process_answer: short reply (input.voltage) 2.672422 send: Q1 2.906353 received 46 (40) 2.906411 read: (225.3 140.0 224.5 015 49.9 13.9 30.0 00001001 2.906424 qx_process_answer: short reply (input.voltage) 2.906444 send: Q1 3.140343 received 46 (40) 3.140400 read: (225.3 140.0 224.5 015 49.9 13.9 30.0 00001001 3.140443 qx_process_answer: short reply (input.voltage) 3.140512 send: Q1 3.374274 received 46 (40) 3.374321 read: (225.3 140.0 224.5 015 49.9 13.9 30.0 00001001 3.374329 qx_process_answer: short reply (input.voltage) 3.374337 send: Q1 3.608246 received 46 (40) 3.608291 read: (225.3 140.0 224.5 015 49.9 13.9 30.0 00001001 3.608299 qx_process_answer: short reply (input.voltage) 3.608313 Device not supported! 3.608319 Device not supported! ?It seems I am not so lucky... Thank you lots, Andrea? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20170609/0b2f8a1f/attachment.html>