RE: Rounding in conversion of ao record

[Mark Rivers <rivers@cars.uchicago.edu>]

I don't understand why you would be seeing rounding with the asynFloat64 device support with the modbus TCP driver.  Are you talking about my asyn Modbus driver?  What version?  That should be writing the VAL field of the record with no conversion to epicsInt32.  It does not use the RVAL field.  I have tested that, and I know that others are using it.

Please explain exactly what you are seeing with the asynFloat64 device support with the Modbus driver.

Mark

________________________________________
From: haquin [haquin@ganil.fr]
Sent: Thursday, February 21, 2013 8:02 AM
To: Mark Rivers
Cc: tech-talk
Subject: Re: Rounding in conversion of ao record

Hello Mark,

I discovered this using asynFloat64 device support (with modbusTCP driver), then made a specific test with Raw Soft
Channel and finally looked in the code of the ao record and in the convert function there is a cast to (epicsInt32) ...
Regards
Christophe

Le 21/02/2013 14:52, Mark Rivers a écrit :
> Conversion to epicsInt32 is not normally part of the operation of the ao record.  What device support are you using?
>
> Mark
>
> ________________________________________
> From: tech-talk-bounces@aps.anl.gov [tech-talk-bounces@aps.anl.gov] on behalf of haquin [haquin@ganil.fr]
> Sent: Thursday, February 21, 2013 7:12 AM
> To: tech-talk
> Subject: Rounding in conversion of ao record
>
> Hi people,
>
> There is a rounding operation (cast to (epicsInt32)) when using the conversion of the ao record,
> hence, with this conversion only integer is output, no float ...
> This is surprising and not equivalent to what is done for the ai record.
>
> Could this be changed ?
>
> Regards,
> Christophe
>
>