Re: [Nut-upsuser] Empty readings from sensors (MEC0003)

2021-08-13 Thread Charles Lepple via Nut-upsuser 
On Aug 13, 2021, at 7:32 AM, Manuel Wolfshant wrote:
> 
>> [...]   2.135215 read: (000.0 000.0 000.0 000 00.0 0.00 00.0 
> As far as I can see, the UPS is sending exclusively zeroes so there isn't 
> much that the drivers could do.
> 
I agree that the logs seem to be showing that the UPS is sending all zeroes, 
but I do remember some discussion about sending additional setup commands to 
make the UPS start sending actual data. A quick search of the email archives 
(matching MEC0003) turned up some branches that @zykh was working on, but I 
can't tell how those discussions were resolved.

___
Nut-upsuser mailing list
Nut-upsuser@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Empty readings from sensors (MEC0003)

2021-08-13 Thread Manuel Wolfshant 

On 8/12/21 3:04 PM, Артем Кудрявцев via Nut-upsuser wrote:

Hello!

Help me to understand this problem please. I'm trying to monitor UPS 
Lanches LANCHES L900II-S 3/1 6KVA and i can't receive sensor readings 
from it. Just zeros on all parameters.


Tried nutdrv_qx and blazer_usb drivers, same results on both. So my 
question is, what kind of problem is it? Bad motherboard on UPS, lack 
of sensors at all or it is driver/software problem and just need to 
find correct driver for it?


This is the output from blazer_usb:

root@sp-pm-i-nom:/lib/nut# ./blazer_usb -a ups -D
Network UPS Tools - Megatec/Q1 protocol USB driver 0.12 (2.7.4)
   0.00     debug level is '5'
   0.120897     Checking device (1D6B/0003) (004/001)
   0.121058     - VendorID: 1d6b
   0.121064     - ProductID: 0003
   0.121068     - Manufacturer: unknown
   0.121071     - Product: unknown
   0.121074     - Serial Number: unknown
   0.121079     - Bus: 004
   0.121084     - Device release number: 0404
   0.121089     Trying to match device
   0.121096     Device does not match - skipping
   0.121104     Checking device (0001/) (003/007)
   0.122212     - VendorID: 0001
   0.11     - ProductID: 
   0.17     - Manufacturer: unknown
   0.122231     - Product: MEC0003
   0.122236     - Serial Number: unknown
   0.122240     - Bus: 003
   0.122244     - Device release number: 0100
   0.122249     Trying to match device
   0.122254     Device matches
   0.122283     nut_usb_set_altinterface: skipped 
usb_set_altinterface(udev, 0)

   0.122297     send_to_all: SETINFO ups.vendorid "0001"
   0.122304     send_to_all: SETINFO ups.productid ""
   0.122329     send_to_all: SETINFO device.type "ups"
   0.122338     send_to_all: SETINFO driver.version "2.7.4"
   0.122345     send_to_all: SETINFO driver.version.internal "0.12"
   0.122352     send_to_all: SETINFO driver.name  
"blazer_usb"

   0.122357     Trying megatec protocol...
   0.122364     send: Q1
   0.125028     received 47 (40)
   0.125056     read: (000.0 000.0 000.0 000 00.0 0.00 00.0 
[...]
   0.129293     send: Q1
   0.132023     received 47 (40)
   0.132033     read: (000.0 000.0 000.0 000 00.0 0.00 00.0 
[...]   2.135215     read: (000.0 000.0 000.0 000 00.0 0.00 00.0 



As far as I can see, the UPS is sending exclusively zeroes so there 
isn't much that the drivers could do.


___
Nut-upsuser mailing list
Nut-upsuser@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

[Nut-upsuser] Empty readings from sensors (MEC0003)

2021-08-13 Thread Артем Кудрявцев via Nut-upsuser 
Hello!

Help me to understand this problem please. I'm trying to monitor UPS
Lanches LANCHES L900II-S 3/1 6KVA and i can't receive sensor readings from
it. Just zeros on all parameters.

Tried nutdrv_qx and blazer_usb drivers, same results on both. So my
question is, what kind of problem is it? Bad motherboard on UPS, lack of
sensors at all or it is driver/software problem and just need to find
correct driver for it?

This is the output from blazer_usb:

root@sp-pm-i-nom:/lib/nut# ./blazer_usb -a ups -D
Network UPS Tools - Megatec/Q1 protocol USB driver 0.12 (2.7.4)
   0.00 debug level is '5'
   0.120897 Checking device (1D6B/0003) (004/001)
   0.121058 - VendorID: 1d6b
   0.121064 - ProductID: 0003
   0.121068 - Manufacturer: unknown
   0.121071 - Product: unknown
   0.121074 - Serial Number: unknown
   0.121079 - Bus: 004
   0.121084 - Device release number: 0404
   0.121089 Trying to match device
   0.121096 Device does not match - skipping
   0.121104 Checking device (0001/) (003/007)
   0.122212 - VendorID: 0001
   0.11 - ProductID: 
   0.17 - Manufacturer: unknown
   0.122231 - Product: MEC0003
   0.122236 - Serial Number: unknown
   0.122240 - Bus: 003
   0.122244 - Device release number: 0100
   0.122249 Trying to match device
   0.122254 Device matches
   0.122283 nut_usb_set_altinterface: skipped
usb_set_altinterface(udev, 0)
   0.122297 send_to_all: SETINFO ups.vendorid "0001"
   0.122304 send_to_all: SETINFO ups.productid ""
   0.122329 send_to_all: SETINFO device.type "ups"
   0.122338 send_to_all: SETINFO driver.version "2.7.4"
   0.122345 send_to_all: SETINFO driver.version.internal "0.12"
   0.122352 send_to_all: SETINFO driver.name "blazer_usb"
   0.122357 Trying megatec protocol...
   0.122364 send: Q1
   0.125028 received 47 (40)
   0.125056 read: (000.0 000.0 000.0 000 00.0 0.00 00.0 
   0.125072 send_to_all: SETINFO input.voltage "0.0"
   0.125078 send_to_all: SETINFO input.voltage.fault "0.0"
   0.125085 send_to_all: SETINFO output.voltage "0.0"
   0.125123 send_to_all: SETINFO ups.load "0"
   0.125129 send_to_all: SETINFO input.frequency "0.0"
   0.125138 send_to_all: SETINFO battery.voltage "0.00"
   0.125141 send_to_all: SETINFO ups.temperature "0.0"
   0.125145 send_to_all: SETINFO ups.beeper.status "disabled"
   0.125149 send_to_all: SETINFO ups.type "online"
   0.125155 send_to_all: SETINFO ups.status "OL"
   0.125159 Status read in 1 tries
   0.125164 Supported UPS detected with megatec protocol
   0.125168 send: F
   0.126851 received 22 (35)
   0.126868 read: #000.0 0.0 00.00 00.0
   0.126893 send_to_all: SETINFO input.voltage.nominal "0"
   0.126900 send_to_all: SETINFO input.current.nominal "0.0"
   0.126905 send_to_all: SETINFO battery.voltage.nominal "0.0"
   0.126909 send_to_all: SETINFO input.frequency.nominal "0"
   0.126912 Ratings read in 1 tries
   0.126917 send: I
   0.129190 received 39 (35)
   0.129199 read: #
   0.129207 send_to_all: SETINFO ups.mfr ""
   0.129211 send_to_all: SETINFO ups.model ""
   0.129215 send_to_all: SETINFO ups.firmware ""
   0.129219 Vendor information read in 1 tries
   0.129223 No values provided for battery high/low voltages in ups.conf

   0.129228 send_to_all: SETINFO battery.voltage.low "0.00"
   0.129232 send_to_all: SETINFO battery.voltage.high "0.00"
   0.129235 Using 'guestimation' (low: 0.00, high: 0.00)!
   0.129238 Battery runtime will not be calculated (runtimecal not set)
   0.129243 send_to_all: SETINFO ups.delay.start "180"
   0.129246 send_to_all: SETINFO ups.delay.shutdown "30"
   0.129251 send_to_all: ADDCMD beeper.toggle
   0.129255 send_to_all: ADDCMD load.off
   0.129258 send_to_all: ADDCMD load.on
   0.129262 send_to_all: ADDCMD shutdown.return
   0.129265 send_to_all: ADDCMD shutdown.stayoff
   0.129271 send_to_all: ADDCMD shutdown.stop
   0.129276 send_to_all: ADDCMD test.battery.start
   0.129284 send_to_all: ADDCMD test.battery.start.deep
   0.129288 send_to_all: ADDCMD test.battery.start.quick
   0.129291 send_to_all: ADDCMD test.battery.stop
   0.129293 send: Q1
   0.132023 received 47 (40)
   0.132033 read: (000.0 000.0 000.0 000 00.0 0.00 00.0 
   0.132052 send_to_all: DATAOK
   0.132116 dstate_init: sock /var/run/nut/blazer_usb-ups open on fd 5
   0.132121 send_to_all: SETINFO driver.parameter.pollinterval "2"
   0.132125 send_to_all: SETINFO driver.parameter.synchronous "no"
   0.132130 send_to_all: SETINFO device.mfr ""
   0.132133 send_to_all: SETINFO device.model ""
   0.132137 send: Q1
   0.134914 received 47 (40)
   0.134923 read: (000.0 000.0 000.0 000 00.0 0.00 00.0 
   1.870391 new