[Nut-upsuser] online zinto usv

[Carsten Burkhardt]

Hello again,

I have the Online Zinto A finally in use.

-search
lsusb -d 06da: -v
Bus 005 Device 009: ID 06da:0601 Phoenixtec Power Co., Ltd

-add rule
/lib/udev/rules.d/52-nut-usbups.rules
# Online USV-Systeme AG
#  Online Zinto A - blazer_usb
ATTR{idVendor}=="06da", ATTR{idProduct}=="0601", MODE="664", GROUP="nut"

-configure
/etc/nut/ups.conf
[zinto]
 driver=blazer_usb
  subdriver = phoenix
#subdriver = cypress
#subdriver = ippon
#subdriver = krauler
#protocol = zinto
vendorid = 06da
productid = 0601
desc = "Zinto via USB"
port = auto

-check
/lib/nut/blazer_usb -u nut -a zinto -DDD
Network UPS Tools - Megatec/Q1 protocol USB driver 0.03 (2.4.3)
   0.000000     debug level is '3'
   0.083087     Checking device (06DA/0601) (005/031)
   0.105142     - VendorID: 06da
   0.105226     - ProductID: 0601
   0.105260     - Manufacturer: ONLINE
   0.105293     - Product: ZINTO
   0.105324     - Serial Number: unknown
   0.105355     - Bus: 005
   0.105385     Trying to match device
   0.105675     Device matches

-start
/etc/init.d/nut start
Starting Network UPS Tools: driver(s) upsd upsmon.

-control
upsc zinto at localhost
battery.voltage: 27.30
battery.voltage.nominal: 24.0
beeper.status: enabled
device.type: ups
driver.name: blazer_usb
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.productid: 0601
driver.parameter.subdriver: phoenix
driver.parameter.vendorid: 06da
driver.version: 2.4.3
driver.version.internal: 0.03
input.current.nominal: 4.0
input.frequency: 50.0
input.frequency.nominal: 50
input.voltage: 235.7
input.voltage.fault: 235.7
input.voltage.nominal: 230
output.voltage: 235.7
ups.delay.shutdown: 30
ups.delay.start: 180
ups.load: 20
ups.productid: 0601
ups.status: OL
ups.temperature: 66.6
ups.type: offline / line interactive
ups.vendorid: 06da

-- 
MfG
Carsten Burkhardt
> On Mon, Jan 3, 2011 at 11:45 AM, Carsten Burkhardt <c.burkhardt at b-c-s.de>
> wrote:
>> Hello,
>>
>> many thanks for your assitance.
>>
>>>>> The help got unfortunately time outs (explore.txt)
>>>>
>>>> Looking at the VendorID and ProductID, it is likelt that this device
>>>> is
>>>> recognized as a /dev/tttyUSB(0|1...) device. As such you should
>>>> probably
>>>> point the blazer_ser or megatec drivers to this port.
>>
>> I do not have /dev/ttyUSB.
>
> Arjen mentioned it was likely, but you never can tell.
>
>> If I point to /dev/bus/usb/001/006 the blazer
>> or megatec "Driver failed to start".
>
> The /dev/bus/usb/* nodes are not interchangeable with /dev/ttyUSB*
> nodes. The serial drivers such as blazer_ser and megatec need tty
> interfaces.
>
>>> Also note that after you run usbhid-ups, the /dev/ttyUSB* device nodes
>>> may not be there anymore. The easiest thing to do is simply unplug and
>>> re-plug the USB cable (you only need to do this once).
>>
>> Also on a plug cycle a ttyUSB do not create.
>
> Did you try setting the subdriver, vendorid and productid settings per
> the blazer_usb message as well? (Sorry if I missed that - I didn't see
> your configuration in the list of attachments.)
>
> "Network UPS Tools - Megatec/Q1 protocol USB driver 0.03 (2.4.3)
> Network UPS Tools - UPS driver controller 2.4.3
>
> No supported devices found. Please check your device availability with
> 'lsusb'
> and make sure you have an up-to-date version of NUT. If this does not
> help,
> try running the driver with at least 'subdriver', 'vendorid' and
> 'productid'
> options specified. Please refer to the man page for details about these
> options
> (man 8 blazer).
>
> Driver failed to start (exit status=1)"
>
> --
> - Charles Lepple

-- 
MfG
Carsten Burkhardt