[Nut-upsdev] Re: [Nut-upsuser] Network UPS Tools version 2.0.5
released
Kjell Claesson
kjell.claesson at epost.tidanet.se
Wed Jan 17 17:40:37 CET 2007
Hi.
Yes Arnaud i check this out.
ons 2007-01-17 klockan 03:29 +0100 skrev Henning Brauer:
> * Arnaud Quette <aquette.dev at gmail.com> [2007-01-15 16:44]:
> > Network UPS Tools version 2.0.5 has been released.
>
> bcmxcp stopped working with my compaqs completely. 2.0.3 works.
>
Have you tested 2.0.4 ? It should work as it use the same driver as
2.0.3.
Recomend you to set the baud_rate in ups.conf.
Then you don't see all the baudhunting errors.
The problem come from reading the 'ups topology data'.
I suppose you are building from source so can you comment out
this in the bcmxcp.c file.
from line 735 to 741 in bcmxcp.c.
Like this:
---------------------------------------------------------------------
/* Get information on Phases from UPS */
/* res = command_read_sequence(PW_UPS_TOP_DATA_REQ, answer);
if (res <= 0)
fatal_with_errno("Could not communicate with the ups");
nphases = (answer[0] & 0x0F) +1;
dstate_setinfo("input.phases", "%d", nphases); */
---------------------------------------------------------------------
And change line 59
int nphases = 0;
to
int nphases = 1;
Then build and test the driver.
I check why it is returning a request command 9.
It may be that the topology data block is not implemented in
the compaq ups.
Regards
Kjell
Thanks for reporting this. Sorry that it had to be in the
release and not in the testing or trunk.
> paploo # /usr/local/bin/bcmxcp -a UPS-5 -DDDD
> Network UPS Tools - BCMXCP UPS driver 0.11 (2.0.5)
>
> debug level is '4'
> Receive error (PW_COMMAND_START_BYTE): -1!!!
>
> Receive error (PW_COMMAND_START_BYTE): -1!!!
>
> Receive error (PW_COMMAND_START_BYTE): -1!!!
>
> Communications with UPS lost: Error executing command
> Receive error (PW_COMMAND_START_BYTE): -1!!!
>
> Receive error (PW_COMMAND_START_BYTE): -1!!!
>
> Receive error (PW_COMMAND_START_BYTE): -1!!!
>
> Communications with UPS lost: Error executing command
> Receive error (PW_COMMAND_START_BYTE): -1!!!
>
> Receive error (PW_COMMAND_START_BYTE): -1!!!
>
> Receive error (PW_COMMAND_START_BYTE): -1!!!
>
> Communications with UPS lost: Error executing command
> Communications with UPS re-established
> Connected to UPS on /dev/ttyj2 baudrate: 9600
> Communications with UPS lost: Receive error (Request command): 9!!!
>
> Communications with UPS lost: Receive error (Request command): 9!!!
>
> Communications with UPS lost: Receive error (Request command): 9!!!
>
> Communications with UPS lost: Error executing command
> Could not communicate with the ups
>
> 2.0.3:
> Network UPS Tools - BCMXCP UPS driver 0.10 (2.0.3)
>
> Communications with UPS lost: Error executing command
> Communications with UPS lost: Error executing command
> Communications with UPS lost: Error executing command
> Connected to UPS on /dev/ttyj2 baudrate: 9600
> Model = COMPAQ UPS 3000VA
> Firmware = 00.91
> Shutdown delay = 120 seconds
> Network UPS Tools - BCMXCP UPS driver 0.10 (2.0.3)
>
> Communications with UPS lost: Error executing command
> Communications with UPS lost: Error executing command
> Communications with UPS lost: Error executing command
> Communications with UPS lost: Error executing command
> Connected to UPS on /dev/ttyj3 baudrate: 19200
> Model = COMPAQ UPS 3000VA
> Firmware = 01.09
> Shutdown delay = 120 seconds
>
>
More information about the Nut-upsdev
mailing list