Re: [Nut-upsuser] HP R3000 XR, warning or perhaps error

2007-04-18 Thread Arnaud Quette

2007/4/17, Kjell Claesson [EMAIL PROTECTED]:

...
 Network UPS Tools - UPS driver controller 2.0.5
 Network UPS Tools - BCMXCP UPS driver 0.11 (2.0.5)

 Communications with UPS lost: Error executing command
 Communications with UPS lost: Error executing command
 Communications with UPS lost: Error executing command
 Communications with UPS re-established
 Connected to UPS on /dev/ttyS0 baudrate: 9600
 Model = HP R3000 XR  3000VA
 Firmware = Inve:01.09 Netw:03.60
 Shutdown delay =  120 seconds
 #

 It all seems to work but the initial errors or warnings concern me. I'm
 running stable 2.05 built from source.

This come from the baudhunting function in the driver.
If you set the baud_rate in the ups.conf to 9600 You don't get this
errors.
...


can't this be filtered to avoid user confusion?

Arnaud
--
Linux / Unix Expert - MGE UPS SYSTEMS - RD Dpt
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://people.debian.org/~aquette/
OpenSource Developer - http://arnaud.quette.free.fr/

___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser


Re: [Nut-upsuser] HP R3000 XR, warning or perhaps error

2007-04-18 Thread Kjell Claesson
Hi
ons 2007-04-18 klockan 15:51 +0800 skrev Gregory Orange:
 Arnaud Quette wrote:
  2007/4/17, Kjell Claesson [EMAIL PROTECTED]:
   It all seems to work but the initial errors or warnings concern me. I'm
   running stable 2.05 built from source.
 
  This come from the baudhunting function in the driver.
  If you set the baud_rate in the ups.conf to 9600 You don't get this
  errors.
  ...
  
  can't this be filtered to avoid user confusion?
 

Yes. I take this up of list with Arjen. The error is due to the
fact that is use the 'normal' communication function during baudhunting.

And it test to communicate 3 times before it say that it lost the
communication. And because it try on the wrong speed it fails all
attempt and cast an error.

 (Oops, sending to list this time)
 
 Or for another suggestion, the message could be changed to something like:
 No baud rate specified in UPS configuration file ups.conf, attempting 
 baud rate auto detection...
 Attempting communication at 2400 baud... failed
 Attempting communication at 4800 baud... failed
 Attempting communication at 9600 baud... success
 
 That would make it look less like debug info and more like useful output 
 for a user like me who is somewhere in between naive and proficient.

This could be done.

Regards
Kjell





___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser