Alexa Catalin
2017-Oct-30 13:19 UTC
[Nut-upsuser] Problems in communication with Mustek PowerMust 1060 LCD
System: Cenots Linux 6.9 Application: nut-2.7.5-0.20170613gitb1314c6 [with usb 0.1 from distro] Device: Mustek PowerMust 1060 LCD Comunication log file: dump.txt We are looking at the possibility of successful communicating with this device UPS Mustek PowerMust 1060 LCD. PS: wolfy on the list gives me assistance and i can install any new compiled nut version from sources. Thanks, Catalin. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20171030/1b11bc12/attachment.html> -------------- next part -------------- 0.000000 [D1] debug level is '3' 0.004712 [D2] Checking device (1D6B/0002) (002/001) 0.004746 [D2] - VendorID: 1d6b 0.004756 [D2] - ProductID: 0002 0.004764 [D2] - Manufacturer: Linux 2.6.32-696.13.2.el6.x86_64 ehci_hcd 0.004773 [D2] - Product: EHCI Host Controller 0.004781 [D2] - Serial Number: 0000:00:1d.0 0.004789 [D2] - Bus: 002 0.004797 [D2] - Device release number: 0206 0.004805 [D2] Trying to match device 0.004814 [D2] Device does not match - skipping 0.004826 [D2] Checking device (0665/5161) (001/003) 2.004392 [D2] - VendorID: 0665 2.004420 [D2] - ProductID: 5161 2.004532 [D2] - Manufacturer: unknown 2.004541 [D2] - Product: unknown 2.004550 [D2] - Serial Number: unknown 2.004558 [D2] - Bus: 001 2.004567 [D2] - Device release number: 0002 2.004575 [D2] Trying to match device 2.004619 [D2] Device matches 2.004648 [D3] nut_usb_set_altinterface: skipped usb_set_altinterface(udev, 0) 2.004679 [D2] Skipping megatec protocol... 2.004689 [D2] Trying mustek protocol... 2.731556 [D3] send: QS 2.737382 [D3] read: (229.7 231.6 229.7 023 50.1 27.5 --.- 00001001 2.737456 [D2] blazer_status: non numerical value [--.-] 2.737477 [D2] Status read in 1 tries 2.737486 Supported UPS detected with mustek protocol 7.737351 [D3] send: error sending control message: Connection timed out 7.737382 [D2] blazer_rating: short reply 7.737483 [D1] Rating read 1 failed 12.737303 [D3] send: error sending control message: Connection timed out 12.737347 [D2] blazer_rating: short reply 12.739509 [D1] Rating read 2 failed 13.019570 [D3] send: F 13.025314 [D3] read: (231.7 229.7 231.6 023 50.1 27.5 --.- 00001001 13.025344 [D2] blazer_rating: invalid start character [28] 13.025359 [D1] Rating read 3 failed 13.025368 Rating information unavailable 13.025378 No values provided for battery high/low voltages in ups.conf 13.025398 Using 'guestimation' (low: -0.866667, high: -1.083333)! 13.025408 Battery runtime will not be calculated (runtimecal not set) 18.025409 [D3] send: error sending control message: Connection timed out 18.025529 [D2] blazer_status: short reply 18.026837 [D1] Communications with UPS lost: status read failed! 18.027010 [D2] dstate_init: sock /var/run/nut/blazer_usb-serverups open on fd 5 23.026403 [D3] send: error sending control message: Connection timed out 23.026442 [D2] blazer_status: short reply 23.026453 [D1] Communications with UPS lost: status read failed! 23.197877 [D3] send: QS 23.202242 [D3] read: #230.0 004 24.00 50.0 23.202271 [D2] blazer_status: short reply 23.202281 [D1] Communications with UPS lost: status read failed! 30.028309 [D3] send: error sending control message: Connection timed out 30.028341 [D2] blazer_status: short reply 30.028351 Communications with UPS lost: status read failed! 33.482321 [D3] send: QS 33.488175 [D3] read: (231.6 229.7 229.7 022 50.1 27.5 --.- 00001001 33.488232 [D2] blazer_status: non numerical value [--.-] 33.488249 Communications with UPS re-established 38.488260 [D3] send: error sending control message: Connection timed out 38.518540 [D2] blazer_status: short reply 38.518560 [D1] Communications with UPS lost: status read failed! 43.518381 [D3] send: error sending control message: Connection timed out 43.518421 [D2] blazer_status: short reply 43.518433 [D1] Communications with UPS lost: status read failed! 43.770366 [D3] send: QS 43.776087 [D3] read: (229.7 229.7 229.7 023 50.1 27.5 --.- 00001001 43.776150 [D2] blazer_status: non numerical value [--.-] 50.520298 [D3] send: error sending control message: Connection timed out 50.520333 [D2] blazer_status: short reply 50.520345 [D1] Communications with UPS lost: status read failed! 54.056946 [D3] send: QS 54.063021 [D3] read: (229.7 229.7 229.7 023 50.1 27.5 --.- 00001001 54.063073 [D2] blazer_status: non numerical value [--.-] 59.062382 [D3] send: error sending control message: Connection timed out 59.062417 [D2] blazer_status: short reply 59.062429 [D1] Communications with UPS lost: status read failed! 64.062323 [D3] send: error sending control message: Connection timed out 64.062360 [D2] blazer_status: short reply 64.062372 [D1] Communications with UPS lost: status read failed! 64.345607 [D3] send: QS 64.352967 [D3] read: (229.7 229.7 229.7 023 50.1 27.5 --.- 00001001 64.353017 [D2] blazer_status: non numerical value [--.-] 71.064279 [D3] send: error sending control message: Connection timed out 71.064316 [D2] blazer_status: short reply 71.064328 [D1] Communications with UPS lost: status read failed! 74.633933 [D3] send: QS 74.639903 [D3] read: (229.7 229.7 231.7 023 50.1 27.5 --.- 00001001 74.639962 [D2] blazer_status: non numerical value [--.-] 79.639367 [D3] send: error sending control message: Connection timed out 79.639403 [D2] blazer_status: short reply 79.639500 [D1] Communications with UPS lost: status read failed! 84.639325 [D3] send: error sending control message: Connection timed out 84.639361 [D2] blazer_status: short reply 84.639461 [D1] Communications with UPS lost: status read failed! 84.922214 [D3] send: QS 84.930832 [D3] read: (231.7 231.7 231.7 024 50.1 27.5 --.- 00001001 84.930888 [D2] blazer_status: non numerical value [--.-] 91.651420 [D3] send: error sending control message: Connection timed out 91.651512 [D2] blazer_status: short reply 91.651524 [D1] Communications with UPS lost: status read failed! 95.211669 [D3] send: QS 95.217766 [D3] read: (229.7 231.7 231.7 024 50.1 27.5 --.- 00001001 95.217822 [D2] blazer_status: non numerical value [--.-] 100.217362 [D3] send: error sending control message: Connection timed out 100.217480 [D2] blazer_status: short reply 100.217493 [D1] Communications with UPS lost: status read failed! 105.217310 [D3] send: error sending control message: Connection timed out 105.217346 [D2] blazer_status: short reply 105.217359 [D1] Communications with UPS lost: status read failed! 105.500082 [D3] send: QS 105.508672 [D3] read: (231.7 231.7 231.7 022 50.1 27.5 --.- 00001001 105.508720 [D2] blazer_status: non numerical value [--.-] 112.219272 [D3] send: error sending control message: Connection timed out 112.219310 [D2] blazer_status: short reply 112.219378 [D1] Communications with UPS lost: status read failed!
Manuel Wolfshant
2017-Nov-11 07:15 UTC
[Nut-upsuser] Problems in communication with Mustek PowerMust 1060 LCD
On 10/30/2017 03:19 PM, Alexa Catalin wrote:> System: Cenots Linux 6.9 > Application: nut-2.7.5-0.20170613gitb1314c6? [with usb 0.1 from distro] > Device:??Mustek PowerMust 1060 LCD > Comunication log file: dump.txt > > We are looking at the possibility of successful communicating with > this device UPS?Mustek PowerMust 1060 LCD. > > PS: wolfy on the list gives me assistance and i can install any new > compiled nut version from sources. >Hi list Anyone with ideas on this one ? It looks like the driver communicates with the device but something is amiss.. and I am not at all familiar with the code so I cannot fiddle with it. ??? wolfy> > Thanks, > Catalin. > > dump.txt > > > 0.000000 [D1] debug level is '3' > 0.004826 [D2] Checking device (0665/5161) (001/003) > 2.004392 [D2] - VendorID: 0665 > 2.004420 [D2] - ProductID: 5161 > 2.004532 [D2] - Manufacturer: unknown > 2.004541 [D2] - Product: unknown > 2.004550 [D2] - Serial Number: unknown > 2.004558 [D2] - Bus: 001 > 2.004567 [D2] - Device release number: 0002 > 2.004575 [D2] Trying to match device > 2.004619 [D2] Device matches > 2.004648 [D3] nut_usb_set_altinterface: skipped usb_set_altinterface(udev, 0) > 2.004679 [D2] Skipping megatec protocol... > 2.004689 [D2] Trying mustek protocol... > 2.731556 [D3] send: QS > 2.737382 [D3] read: (229.7 231.6 229.7 023 50.1 27.5 --.- 00001001 > 2.737456 [D2] blazer_status: non numerical value [--.-] > 2.737477 [D2] Status read in 1 tries > 2.737486 Supported UPS detected with mustek protocol > 7.737351 [D3] send: error sending control message: Connection timed out > 7.737382 [D2] blazer_rating: short reply > 7.737483 [D1] Rating read 1 failed > 12.737303 [D3] send: error sending control message: Connection timed out > 12.737347 [D2] blazer_rating: short reply > 12.739509 [D1] Rating read 2 failed > 13.019570 [D3] send: F > 13.025314 [D3] read: (231.7 229.7 231.6 023 50.1 27.5 --.- 00001001 > 13.025344 [D2] blazer_rating: invalid start character [28] > 13.025359 [D1] Rating read 3 failed > 13.025368 Rating information unavailable > 13.025378 No values provided for battery high/low voltages in ups.conf > > 13.025398 Using 'guestimation' (low: -0.866667, high: -1.083333)! > 13.025408 Battery runtime will not be calculated (runtimecal not set) > 18.025409 [D3] send: error sending control message: Connection timed out > 18.025529 [D2] blazer_status: short reply > 18.026837 [D1] Communications with UPS lost: status read failed! > 18.027010 [D2] dstate_init: sock /var/run/nut/blazer_usb-serverups open on fd 5 > 23.026403 [D3] send: error sending control message: Connection timed out > 23.026442 [D2] blazer_status: short reply > 23.026453 [D1] Communications with UPS lost: status read failed! > 23.197877 [D3] send: QS > 23.202242 [D3] read: #230.0 004 24.00 50.0 > 23.202271 [D2] blazer_status: short reply > 23.202281 [D1] Communications with UPS lost: status read failed! > 30.028309 [D3] send: error sending control message: Connection timed out > 30.028341 [D2] blazer_status: short reply > 30.028351 Communications with UPS lost: status read failed! > 33.482321 [D3] send: QS > 33.488175 [D3] read: (231.6 229.7 229.7 022 50.1 27.5 --.- 00001001 > 33.488232 [D2] blazer_status: non numerical value [--.-] > 33.488249 Communications with UPS re-established > 38.488260 [D3] send: error sending control message: Connection timed out > 38.518540 [D2] blazer_status: short reply > 38.518560 [D1] Communications with UPS lost: status read failed! > 43.518381 [D3] send: error sending control message: Connection timed out > 43.518421 [D2] blazer_status: short reply > 43.518433 [D1] Communications with UPS lost: status read failed! > 43.770366 [D3] send: QS > 43.776087 [D3] read: (229.7 229.7 229.7 023 50.1 27.5 --.- 00001001 > 43.776150 [D2] blazer_status: non numerical value [--.-] > 50.520298 [D3] send: error sending control message: Connection timed out > 50.520333 [D2] blazer_status: short reply > 50.520345 [D1] Communications with UPS lost: status read failed! > 54.056946 [D3] send: QS > 54.063021 [D3] read: (229.7 229.7 229.7 023 50.1 27.5 --.- 00001001 > 54.063073 [D2] blazer_status: non numerical value [--.-] > 59.062382 [D3] send: error sending control message: Connection timed out > 59.062417 [D2] blazer_status: short reply > 59.062429 [D1] Communications with UPS lost: status read failed! > 64.062323 [D3] send: error sending control message: Connection timed out > 64.062360 [D2] blazer_status: short reply > 64.062372 [D1] Communications with UPS lost: status read failed! > 64.345607 [D3] send: QS > 64.352967 [D3] read: (229.7 229.7 229.7 023 50.1 27.5 --.- 00001001 > 64.353017 [D2] blazer_status: non numerical value [--.-] > 71.064279 [D3] send: error sending control message: Connection timed out > 71.064316 [D2] blazer_status: short reply > 71.064328 [D1] Communications with UPS lost: status read failed! > 74.633933 [D3] send: QS > 74.639903 [D3] read: (229.7 229.7 231.7 023 50.1 27.5 --.- 00001001 > 74.639962 [D2] blazer_status: non numerical value [--.-] > 79.639367 [D3] send: error sending control message: Connection timed out > 79.639403 [D2] blazer_status: short reply > 79.639500 [D1] Communications with UPS lost: status read failed! > 84.639325 [D3] send: error sending control message: Connection timed out > 84.639361 [D2] blazer_status: short reply > 84.639461 [D1] Communications with UPS lost: status read failed! > 84.922214 [D3] send: QS > 84.930832 [D3] read: (231.7 231.7 231.7 024 50.1 27.5 --.- 00001001 > 84.930888 [D2] blazer_status: non numerical value [--.-] > 91.651420 [D3] send: error sending control message: Connection timed out > 91.651512 [D2] blazer_status: short reply > 91.651524 [D1] Communications with UPS lost: status read failed! > 95.211669 [D3] send: QS > 95.217766 [D3] read: (229.7 231.7 231.7 024 50.1 27.5 --.- 00001001 > 95.217822 [D2] blazer_status: non numerical value [--.-] > 100.217362 [D3] send: error sending control message: Connection timed out > 100.217480 [D2] blazer_status: short reply > 100.217493 [D1] Communications with UPS lost: status read failed! > 105.217310 [D3] send: error sending control message: Connection timed out > 105.217346 [D2] blazer_status: short reply > 105.217359 [D1] Communications with UPS lost: status read failed! > 105.500082 [D3] send: QS > 105.508672 [D3] read: (231.7 231.7 231.7 022 50.1 27.5 --.- 00001001 > 105.508720 [D2] blazer_status: non numerical value [--.-] > 112.219272 [D3] send: error sending control message: Connection timed out > 112.219310 [D2] blazer_status: short reply > 112.219378 [D1] Communications with UPS lost: status read failed!-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20171111/62557e0d/attachment.html>
Daniele Pezzini
2017-Nov-12 23:46 UTC
[Nut-upsuser] Problems in communication with Mustek PowerMust 1060 LCD
Since we get valid replies (when we get any), I'm assuming we're speaking the right 'dialect' and using the right (or an almost right) serial-over-USB implementation. Apparently, after a successful query, it takes the device ~10 seconds to reply (see how, when trying to read the reply to the 'QS' query at ~23s, we actually get the reply -the one starting with a '#'- to the 'F' query sent at ~13s, and when trying to read the reply to the latter, we actually get the reply to a 'QS' query, probably the one sent at ~3s). If that's really the case, I'm not sure there's much we can do... you could try to ease the pace of the polling to match the time the device needs to reply, so that every new poll will get the reply to the last one (e.g. setting 'pollinterval', or 'i' arg, to 10 seconds or something like that). Also, you could try another serial-over-USB subdriver (namely the 'phoenix' one, instead of the default 'cypress' one, but feel free to try also the other ones). Finally, if you end up with a usable setup and if the device still needs 10s to answer our queries, consider using the 'norating' and 'novendor' flags, since it's not likely that we get any reply to those queries in time to process them (and then they could even be seen as 'pollution' to the next status queries).
Seemingly Similar Threads
- Problems in communication with Mustek PowerMust 1060 LCD
- [BUG] nut 2.4.3+: UPS EP-1K: Firmware fault: USB-Interface crashes with nut.org monitoring if driver polling time <15 sec
- Sven Power Pro 1000+
- Problem with nut 2.4.1 & Ippon 2000 Smart power on FreeBSD
- connection pb with blazer_usb with infusec UPS