[Nut-upsuser] amacrox ap1000 problems

[Dimitri Ognibene]

the output of  sudo /lib/nut/megatec_usb -u root -DDD -a ap1000&>megatec_usb.log

Checking device (0665/5161) (008/004)
- VendorID: 0665
- ProductID: 5161
- Manufacturer: Cypress Semiconductor
- Product: USB to Serial
- Serial Number: unknown
- Bus: 008
Trying to match device
Device matches
DTR=1, RTS=0
Starting UPS detection process...
Asking for UPS information [I]...
I => FAILED [short read]
I detail: (1 bytes) => 49
Asking for UPS status [Q1]...
get_data_phoenix: got so far [Q1^M]
Q1 => FAILED [short read]
Q1 detail: (2 bytes) => 51 31
Asking for UPS status [Q1]...
get_data_phoenix: got so far [Q1^M]
Q1 => FAILED [short read]
Q1 detail: (2 bytes) => 51 31
Asking for UPS status [Q1]...
get_data_phoenix: got so far [Q1^M]
Q1 => FAILED [short read]
Q1 detail: (2 bytes) => 51 31
Asking for UPS status [Q1]...
get_data_phoenix: got so far [Q1^M]
Q1 => FAILED [short read]
Q1 detail: (2 bytes) => 51 31
Asking for UPS status [Q1]...
get_data_phoenix: got so far [Q1^M]
Q1 => FAILED [short read]
Q1 detail: (2 bytes) => 51 31
5 out of 5 detection attempts failed (minimum failures: 2).
Megatec protocol UPS not detected.
Network UPS Tools - Megatec protocol driver 1.6 (2.4.1)
Serial-over-USB transport layer 0.10


the output of   sudo /lib/nut/blazer_usb -u root -DDD -a ap1000 is

Checking device (0665/5161) (008/004)
- VendorID: 0665
- ProductID: 5161
- Manufacturer: Cypress Semiconductor
- Product: USB to Serial
- Serial Number: unknown
- Bus: 008
Trying to match device
Device matches
Trying megatec protocol...
send: Q1
read: Q1
blazer_status: short reply
Status read 1 failed
send: Q1
read: Q1
blazer_status: short reply
Status read 2 failed
send: Q1
read: Q1
blazer_status: short reply
Status read 3 failed
Trying mustek protocol...
send: QS
read: (231.6 231.6 231.6 024 49.9 27.0 --.- 00001001
blazer_status: non numerical value [--.-]
Status read in 1 tries
Supported UPS detected with mustek protocol
send: F
read: #220.0 005 24.00 50.0
Ratings read in 1 tries
send: I
read: I
blazer_vendor: short reply
Vendor information read 1 failed
send: I
read: I
blazer_vendor: short reply
Vendor information read 2 failed
send: I
read: I
blazer_vendor: short reply
Vendor information read 3 failed
Vendor information unavailable
Battery runtime will not be calculated (runtimecal not set)
send: QS
read: (231.6 231.6 231.6 023 49.9 27.0 --.- 00001001
blazer_status: non numerical value [--.-]


On 2 April 2010 21:22, Arjen de Korte <nut+users at de-korte.org> wrote:
> Citeren Charles Lepple <clepple at gmail.com>:
>
>> If you can, you might want to upgrade to NUT 2.4.3 to take advantage of
>> the blazer_usb driver which has more debugging code than megatec_usb.
>
> The blazer_usb driver in nut-2.4.1 is also well worth trying, since it too
> has better debugging facilities than the megatec_usb driver. Make sure to
> read 'man 8 blazer' before use. Post the output of
>
>    /path/to/blazer_usb -u root -DDD -a ap1000
>
> to see if this is just a permissions problem or if there is something else
> causing a problem.
>
> Best regards, Arjen
> --
> Please keep list traffic on the list
>
>
> _______________________________________________
> Nut-upsuser mailing list
> Nut-upsuser at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
>



-- 
 I am a dog chasing cars… I wouldn’t know what to do with one if I caught it.
I just do things. (Nolan's Joker)

The answer is inside you, but it's wrong (Guzzanti)

If we knew what it was we were doing, it would not be called research,
would it? (Einstein)

http://www.mrwiggleslovesyou.com/rehab333.html

Dimitri Ognibene
PhD
Istituto di Scienze e Tecnologie della Cognizione,
Consiglio Nazionale delle Ricerche (ISTC-CNR),
via S. Martino della Battaglia, 44
00185 Rome

Skype: dimitri.ognibene