[Nut-upsuser] online zinto usv

[Charles Lepple]

[cc'ing the list again - please use "reply all" or "reply to list".]

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