[Nut-upsuser] [SOLVED]Re: Re: Debian Squeeze / Powerware 9135 450KVA UPS
Gregory Skelton
gregory.skelton at gmail.com
Fri Jan 13 01:53:42 UTC 2012
Hi Kjell,
Thank you for your quick reply, I ended up checking out the unstable
version of nut in Debian version 2.6.2. With the exact same setup,
driver 2.6.2 work for me.
I appreciate the help.
Best,
Greg
On Thu, Jan 12, 2012 at 5:36 PM, Kjell Claesson
<kjell.claesson at epost.tidanet.se> wrote:
> torsdagen den 12 januari 2012 15.30.02 skrev Gregory Skelton:
>> Hi,
>>
> Hi Gregory,
>
>> I have more information, I did some more digging and found a debugging
>> mode for the driver.. So this what I'm seeing. Any ideas how I get
>> around the "PW_COMMAND_START_BYTE"?
>>
>> Thanks for any help.
>> Greg
>>
> Have made the mail a little shorter. By the way you should
> get the same output with only 2 D.
>
> ./bcmxcp -a powerware -DD -i 5 -x baud_rate=9600
>
> But now to the problem
>
> 8<----------snip----------------
>>
>> 1.156360 Length of Config_block: 48
>>
>> 1.156366 Length of statistics map: 62
>>
>> 1.156371 Length of command list: 4047
>>
>> 1.156375 Length of outlet_block: 33650
>
> This is not normal every output should have length 8,
> so you should have 33650/8 = 4206.25 outlets.
>
>>
>> 1.156380 Length of alarm_block: 34179
>
> And this make the error. Because the driver set up the outlets now.
> Do you have a firmware before Rev: AE ?
>
>> 2.157495 Receive error (PW_COMMAND_START_BYTE): 0!!!
>>
>> 3.158599 Receive error (PW_COMMAND_START_BYTE): 0!!!
>>
>> 4.159701 Receive error (PW_COMMAND_START_BYTE): 0!!!
>>
>> 4.159712 Communications with UPS lost: Error executing command
>> 4.159717 Could not communicate with the ups
>> </snip>
>
> This may be fixable by reading the firmware revision and skip this
> setup of outlet blocks.
>
> Regards
> Kjell
>
>
>
More information about the Nut-upsuser
mailing list