Uroš Gaber
2015-Sep-18 10:27 UTC
[Nut-upsdev] [HCL] Micropower LCD 1000 supported by blazer_usb
Device web page http://www.samurai-power.com/samurai-smart-1000-lcd UPS is marked as Micropower LCD 1000, but in Slovenia is remarked as Samurai LCD 1000 [ups] driver = blazer_usb port = auto vendorid = 0001 productid = 0000 upsc ups Init SSL without certificate database battery.charge: 100 battery.voltage: 27.40 battery.voltage.high: 26.00 battery.voltage.low: 20.80 battery.voltage.nominal: 24.0 device.type: ups driver.name: blazer_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.parameter.productid: 0000 driver.parameter.vendorid: 0001 driver.version: 2.7.1 driver.version.internal: 0.10 input.current.nominal: 4.0 input.frequency: 50.0 input.frequency.nominal: 50 input.voltage: 235.2 input.voltage.fault: 235.2 input.voltage.nominal: 230 output.voltage: 234.7 ups.beeper.status: enabled ups.delay.shutdown: 30 ups.delay.start: 180 ups.load: 5 ups.productid: 0000 ups.status: OL ups.type: offline / line interactive ups.vendorid: 0001 NUT version 2.7.1 Shutdown sequence working, onbattery nofity too. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20150918/cb348d4d/attachment.html>
Charles Lepple
2015-Sep-21 02:21 UTC
[Nut-upsdev] [HCL] Micropower LCD 1000 supported by blazer_usb
On Sep 18, 2015, at 6:27 AM, Uro? Gaber <uros.gaber at gmail.com> wrote:> > NUT version 2.7.1 >Thanks for testing. The blazer_usb driver is being phased out - can you test the nutdrv_qx driver (a superset of blazer* and other Q*-protocol drivers) to see if there are any regressions? -- Charles Lepple clepple at gmail
Charles Lepple
2015-Sep-21 12:21 UTC
[Nut-upsdev] [HCL] Micropower LCD 1000 supported by blazer_usb
On Sep 21, 2015, at 7:38 AM, Charles Lepple <clepple at gmail.com> wrote:> > (please keep the list CC'd) > >> On Sep 21, 2015, at 5:09 AM, Uro? Gaber <uros.gaber at gmail.com <mailto:uros.gaber at gmail.com>> wrote: >> >> Hi. >> No for me nutdrv_qx driver is not working with this UPS. >> Here's log: >> Sep 21 11:06:39 server_main upsd[50449]: listening on 127.0.0.1 port 3493 >> Sep 21 11:06:39 server_main upsd[50449]: Can't connect to UPS [ups] (nutdrv_qx-ups): No such file or directory >> Sep 21 11:06:39 server_main upsd[50450]: Startup successful >> Sep 21 11:06:39 server_main kernel: [255930.977833] usb 2-1.6: usbfs: USBDEVFS_CONTROL failed cmd nutdrv_qx rqt 128 rq 6 len 255 ret -110 >> Sep 21 11:06:40 server_main upsd[50450]: User upsmon at 127.0.0.1 <mailto:upsmon at 127.0.0.1> logged into UPS [ups] >> Sep 21 11:06:35 server_main upsmon[50420]: UPS [ups at localhost]: connect failed: Connection failure: Connection refused >> Sep 21 11:06:40 server_main upsmon[50420]: Poll UPS [ups at localhost] failed - Driver not connected > > That's strange. Can you make sure that both the old blazer_usb and nutdrv_qx processes have been killed, and start nutdrv_qx with one or two -D flags? > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20150921/8f0d5e2d/attachment.html>