Nut upsdev - Mar 2012 - AEG - PROTECT HOME support using NUT with serial protocol

hi,

i own a aeg protect home (think it is a 600 VA) which has a serial and 
an usb port.

using this hack in ups.conf:
  [bestupsname]
        driver = bestups
        port = /dev/ttyUSB0
        ID = FOR,750,230,230,11.0,13.5
        desc = "home-server"

i start the driver with:
   ./bestups -a bestupsname -D -q

and after adding some debugging it seems to work (not yet in 
production). i first started by looking at the protocol and it is very 
very similar to www.networkupstols.org/ups-protocols/megatec.html at 
least protocol wise.

but i have a few problems

==== problem 1 ===using FOR is wrong as it then reports as a different device
than it
actually is. should i add a new device string, say APH?

==== problem 2 ===i would like to use the usb protocol but i don't know
where to start.

lsusb
Bus 003 Device 003: ID 0665:5161 Cypress Semiconductor USB to Serial

dmesg
[10684.669013] usb 3-2: new low speed USB device using uhci_hcd and 
address 3
[10684.833060] usb 3-2: New USB device found, idVendor=0665, idProduct=5161
[10684.833063] usb 3-2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
[10684.833065] usb 3-2: Product: USB to Serial
[10684.833067] usb 3-2: Manufacturer: Cypress Semiconductor
[10684.875129] generic-usb 0003:0665:5161.0005: hiddev96,hidraw3: USB 
HID v1.00 Device [Cypress Semiconductor USB to Serial] on 
usb-0000:00:1a.2-2/input0

maybe there exists such an implementation for usb already. last time i 
implemented the protecthome driver i found bestups to be what i actually 
wanted but then i already invested a lot of time in writing protecthome.c;


=== summary ==maybe someone can help me with this problems. i will post a spec
of what
i have found so far in my blog soon.

thanks in advance

2012/3/29 Joachim Schiele <js at lastlog.de>
> hi,
>
> i own a aeg protect home (think it is a 600 VA) which has a serial and an
> usb port.
>
> using this hack in ups.conf:
>  [bestupsname]
>       driver = bestups
>       port = /dev/ttyUSB0
>       ID = FOR,750,230,230,11.0,13.5
>       desc = "home-server"
>
> i start the driver with:
>  ./bestups -a bestupsname -D -q
>
the bestups driver is indeed part of the large "Q1 protocol" family:
https://alioth.debian.org/pm/task.php?func=detailtask&project_task_id=493&group_id=30602&group_project_id=318

> and after adding some debugging it seems to work (not yet in production).
> i first started by looking at the protocol and it is very very similar to
> www.networkupstols.org/ups-protocols/megatec.html at least protocol wise.
>
so the way to go is blazer_ser or blazer_usb

> but i have a few problems
>
> ==== problem 1 ===> using FOR is wrong as it then reports as a different
device than it
> actually is. should i add a new device string, say APH?
>
> ==== problem 2 ===> i would like to use the usb protocol but i don't
know where to start.
>
> lsusb
> Bus 003 Device 003: ID 0665:5161 Cypress Semiconductor USB to Serial
>
confirming blazer_usb support

cheers,
Arnaud
-- 
Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20120329/0b20ad00/attachment.html>