Nut upsuser - May 2010 - MGE-UTALK regression since nut-server-2.2.2

Hi all !

I have communication issues between my station and my old Pulsar EX10 UPS,
(U-Talk) connected by RS232, when using v2.4.1 of nut-server.

I tried to come back to version 2.2.2 and then, communication start and is
operational.

Maybe it's linked to bug 498655, but i haven't seen any answer ?
http://www.mail-archive.com/debian-bugs-dist at lists.debian.org/msg566711.html

Here are results of my tests (differences are in *red*):
Results of nut-server v2.4.1

[root at xxx ups]# mge-utalk -DDDDDDDD -a pex10
Network UPS Tools - MGE UPS SYSTEMS/U-Talk driver *0.89 (2.4.1)*
send_to_all: SETINFO driver.parameter.port "/dev/ttyS0"
debug level is '8'
mge_command: sending [S]
mge_command: sending [i]
mge_command: sending [0D]
mge_command: sending [0A]
mge_command: *received 0 byte(s)*
send_to_all: SETINFO ups.mfr "MGE UPS SYSTEMS"
send_to_all: SETINFO driver.version.internal "0.89"
mge_command: sending [S]
mge_command: sending [i]
mge_command: sending [ ]
mge_command: sending [1]
mge_command: sending [0D]
mge_command: sending [0A]
mge_command: received 0 byte(s)
initinfo: 'Si 1' unavailable, switching to 'Si' command
mge_command: sending [S]
mge_command: sending [i]
mge_command: sending [0D]
mge_command: sending [0A]
mge_command: received 0 byte(s)
send_to_all: SETINFO ups.firmware "unknown"
mge_command: sending [A]
mge_command: sending [i]
mge_command: sending [0D]
mge_command: sending [0A]
...


Results of nut-server v2.2.2

[root at xxx ups]# mge-utalk -DDDDDDDD -a pex10
Network UPS Tools - MGE UPS SYSTEMS/U-Talk driver *0.88 (2.2.2)*
debug level is '8'
mge_command: sending [S]
mge_command: sending [i]
mge_command: sending [0D]
mge_command: sending [0A]
mge_command: *received -1 byte(s)*
mge_command: sending [Z]
mge_command: sending [0D]
mge_command: sending [0A]
mge_command: sending [Z]
mge_command: sending [0D]
mge_command: sending [0A]
mge_command: sending [A]
mge_command: sending [x]
mge_command: sending [ ]
mge_command: sending [1]
mge_command: sending [0D]
mge_command: sending [0A]
mge_command: sending [S]
mge_command: sending [i]
mge_command: sending [ ]
mge_command: sending [1]
mge_command: sending [0D]
mge_command: sending [0A]
mge_command: received 13 byte(s)
Got model name: Pulsar EX10
mge_command: sending [A]
mge_command: sending [i]
mge_command: sending [0D]
mge_command: sending [0A]
mge_command: received 3 byte(s)
mge_command: sending [S]
mge_command: sending [s]
mge_command: sending [0D]
mge_command: sending [0A]
mge_command: received 8 byte(s)
Syst Stat >0xx00000<

Package :
 - nut-server-2.4.1-5mdv2010.0.x86_64.rpm
or
 - nut-server-2.2.2-5mdv2009.0.x86_64.rpm

Does anyone know about it ?
I think it's a software bug but I'm waiting for yours opinions.

Thanks !
S?bastien LEFEVRE.
-------------- section suivante --------------
Une pi?ce jointe HTML a ?t? enlev?e...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20100516/923c79f9/attachment.htm>

Citeren S?bastien Lefevre <lefevre.seb op gmail.com>:
> I have communication issues between my station and my old Pulsar EX10 UPS,
> (U-Talk) connected by RS232, when using v2.4.1 of nut-server.
[...]
> Does anyone know about it ?
> I think it's a software bug but I'm waiting for yours opinions.
This regression has been fixed more than a year ago. Either upgrade to  
nut-2.4.3 or keep the old nut-2.2.2 driver while upgrading the rest of  
the package. You can use any combination of nut-2.0.5 (or better)  
driver and server.

When reporting bugs, please try the latest released (or development)  
version first.

Best regards, Arjen
-- 
Please keep list traffic on the list