Re: Record timestamp does not update (Debian Linux only)

[Ralph Lange <ralph.lange@gmx.de>]

Hi Michael,

This behavior is expected and correct.
You have to set the PP property on your OUT link to process the 
destination after the value has been written.

I do not see any reason why this could depend on the Linux distribution, 
though. Probably in one case your target record is local (OUT link needs 
PP), in the other case the target record is remote (processing depends 
on the PP property of the target field, which is usually true for .VAL 
fields).

HTH,
~Ralph


On 23/09/2014 11:11, Michael Ritzert wrote:
> Dear all,
>
> I just found this problem on two different Debian machines (testing,
> unstable), x86_64. On Scientific Linux (6.5), also x86_64, the problem
> does not show up. With softIoc from base 3.14.12.4 for this DB:
>
> record(ao, "VOLT:set")
> {
>     field(VAL,  "5")
>     field(PINI, "1")
> }
>
> record(calcout, "VOLT:calc")
> {
>     field(OOPT, "When Non-zero")
>     field(DOPT, "Use OCAL")
>     field(OCAL, "A")
>     field(CALC, "1")
>     field(OUT,  "VOLT:set")
>     field(INPA, "VOLT:req CP")
> }
>
> record(ao, "VOLT:req")
> {
>     field(VAL,  "5")
>     field(PINI, "1")
> }
>
> I see that the time stamp of VOLT:set does not change when writing to
> VOLT:req, but the value changes as expected:
>
> TIME: 2014-09-23 18:04:16.464355407     TPRO: 0             TSE: 0
> TSEL:CONSTANT       UDF: 0              VAL: 5
>
> TIME: 2014-09-23 18:04:16.464355407     TPRO: 0             TSE: 0
> TSEL:CONSTANT       UDF: 0              VAL: 2
>
> TIME: 2014-09-23 18:04:16.464355407     TPRO: 0             TSE: 0
> TSEL:CONSTANT       UDF: 0              VAL: 0
>
> after IOC initialization, caput VOLT:req 2, and caput VOLT:req 0
> respectively.
>
> The time stamps of VOLT:calc and VOLT:req are updated as expected.
>
> Can anybody reproduce this behavior?
>
> Best regards,
> Michael Ritzert