[Nut-upsuser] blazer_usb for SVEN Power Pro+ 500 USB

2011-03-18 Thread Sergey Talchuk
Hello guys,

Please help me to resolve the issue.
I bought 'SVEN Power Pro+ 500 USB' UPS few days ago and tried to setup
NUT 2.6.0 to work with it.
blazer_ups driver doesn't recognize the UPS :(
The Manufacturer provides 'PowerD' software for linux with
installation instractions on a CD (see example below).

   ===---  Welcom to PowerManager System! -===-
Copyright(C) 2001 Richcomm Technologies, Inc. 2001.10 .
+-+==+The Current Time Settings +===+-+
System Shutdown Delay Time When AC Power Failed:[250]  Sec.
System Shutdown Delay Time When Battery Low:[25]  Sec.
Turn off UPS after System Shutdown: YES
+-+
The Com Addr Connectted With UPS : 0x3f8
Interval of  warning :  [5] Sec
==

Unfortunately, the source tarball is not provided so I can't build it
for my NAS.
The binary package requires some new libraries (libc.so.6):

ldd PowerD

libpthread.so.0 = /lib/libpthread.so.0 (0x)
libc.so.6 = not found (0x)
libc.so.0 = /lib/libc.so.0 (0x)
/lib/ld-uClibc.so.0 = /lib/ld-uClibc.so.0 (0x)
==

That is why I decided to use NUT package.

1. OS name and version:
-Linux 2.4.28 i486
2. exact NUT version:
-NUT 2.6.0
3. NUT installation method:
-from source tarball
4. Exact device name and related information:
-SVEN Power Pro+ 500 USB
-Serial Number: K2300611
-http://en.sven.ru/catalog/ups/power_pro_plus_500.htm?tab=techchar
---
1.
cat driver.list | grep -i sven
SVEN  ups   2 Power Pro+ series USB   blazer_usb
SVEN  ups   2 Power Smart RM 2000   USB   blazer_usb
2. lsusb output
Bus 002 Device 001: ID :
Bus 002 Device 002: ID 0925:1234 Lakeview Research
Bus 001 Device 001: ID :
3. My ups.conf
[sven]
driver = blazer_usb
subdriver = krauler #phoenix
vendorid = 0925
productid = 1234
port = auto
desc = Power Pro+ 500
4. I tried both subdrivers: krauler and phoenix
TRACE:
a) subdriver = krauler
blazer_usb -D -a sven
Network UPS Tools - Megatec/Q1 protocol USB driver 0.03 (2.6.0)
   0.00 send_to_all: SETINFO driver.parameter.subdriver krauler
   0.006124 send_to_all: SETINFO driver.parameter.vendorid 0925
   0.010692 send_to_all: SETINFO driver.parameter.productid 1234
   0.015513 send_to_all: SETINFO driver.parameter.port auto
   0.019833 debug level is '5'
   0.035048 Checking device (/) (002/001)
   0.039655 - VendorID: 
   0.044173 - ProductID: 
   0.047967 - Manufacturer: unknown
   0.062021 - Product: USB OHCI Root Hub
   0.065824 - Serial Number: c2ea5000
   0.069610 - Bus: 002
   0.073535 Trying to match device
   0.077535 Device does not match - skipping
   0.081861 Checking device (0925/1234) (002/002)
   0.105296 - VendorID: 0925
   0.109045 - ProductID: 1234
   0.113067 - Manufacturer: ?
   0.116558 - Product: UPS USB MON V1.4
   0.120422 - Serial Number: unknown
   0.124274 - Bus: 002
   0.127727 Trying to match device
   0.131620 Device matches
   0.135701 send_to_all: SETINFO ups.vendorid 0925
   0.139549 send_to_all: SETINFO ups.productid 1234
   0.142180 send_to_all: SETINFO device.type ups
   0.143618 send_to_all: SETINFO driver.version 2.6.0
   0.145048 send_to_all: SETINFO driver.version.internal 0.03
   0.146483 send_to_all: SETINFO driver.name blazer_usb
   0.147638 Trying megatec protocol...
   0.148781 send: Q1
   0.153752 blazer_status: short reply
   0.154925 Status read 1 failed
   0.156041 send: Q1
   0.162260 blazer_status: short reply
   0.163434 Status read 2 failed
   0.164553 send: Q1
   0.168647 blazer_status: short reply
   0.169820 Status read 3 failed
   0.172152 Trying mustek protocol...
   0.175677 send: QS
   0.179201 read: QS
   0.192951 blazer_status: short reply
   0.196494 Status read 1 failed
   0.200014 send: QS
   0.203858 read: QS
   0.207451 blazer_status: short reply
   0.211282 Status read 2 failed
   0.212426 send: QS
   0.213547 read: QS
   0.214728 blazer_status: short reply
   0.215860 Status read 3 failed
   0.216971 Trying megatec/old protocol...
   0.218309 send: D
   0.219431 read: D
   0.231061 blazer_status: short reply
   0.234855 Status read 1 failed
   0.238379 send: D
   0.241454 read: D
   0.242663 blazer_status: short reply
   0.243796 Status read 2 failed
   0.244910 send: D
   0.246031 read: D
   0.247212 blazer_status: short reply
   0.248343 Status read 3 failed
   0.249417 No supported UPS detected
b) subdriver = phoenix
blazer_usb -D -a sven
Network UPS Tools - Megatec/Q1 protocol USB driver 0.03 (2.6.0)
   0.00 send_to_all: SETINFO driver.parameter.subdriver 

Re: [Nut-upsuser] blazer_usb for SVEN Power Pro+ 500 USB

2011-03-18 Thread Arjen de Korte

Citeren Sergey Talchuk tals1...@gmail.com:


2. lsusb output
Bus 002 Device 001: ID :
Bus 002 Device 002: ID 0925:1234 Lakeview Research


Your UPS might be supported by the 'richcomm_usb' driver. It is most  
certainly not supported by the 'blazer_usb' driver.


Best regards, Arjen
--
Please keep list traffic on the list (off-list replies will be rejected)


___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser