Experimental Physics and
Industrial Control System

Mark Rivers via Tech-talk <tech-talk at aps.anl.gov> · Tue, 3 Mar 2020 14:24:20 +0000

> What is the expected behaviour here - in general should NORD on a char waveform be including the NULL terminator or not?

In the asyn device support for the input waveform record NORD does not include the NULL terminator.  That is because that device support does not know if it is reading ASCII or binary data.  It does always NULL terminate the buffer in case it is ASCII data.  If the number of bytes read is exactly equal to NELM then it decrements NORD so that the NULL is not included in NORD.

I believe this has always been the behavior on input waveform records.

On output waveform records the behavior of NORD has changed a couple of times.  You can see this by searching for "nord" in the release notes:

https://epics-modules.github.io/master/asyn/R4-39/RELEASE_NOTES.html

Mark

________________________________
From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of Thomas Willemsen - UKRI STFC via Tech-talk <tech-talk at aps.anl.gov>
Sent: Tuesday, March 3, 2020 7:05 AM
To: tech-talk at aps.anl.gov
Subject: NORD on a char waveform record

Hi,

We have recently updated several support modules, including streamdevice, and have noticed the following change in behaviour:

We have a device whose stream device protocol file looks like:

    InTerminator = CR;

    OutTerminator = CR;

    get_MEASUREMENTS {

        out "MM,1111111111111111";

        in "MM,1111111111111111%s";

    }

Linked to a record that looks like:

    record(waveform, "$(P)STATUS:RAW")

    {

        field(DTYP, "stream")

        field(FTVL, "CHAR")

        field(NELM, "512")

        field(INP, "@kynctm3k.proto get_MEASUREMENTS $(PORT)")

        field(SCAN, "1 second")

    }

The messages to and from the device look as follows:

    2020/03/03 11:55:09.948 localhost:52209 write 20

    MM,1111111111111111\r

    2020/03/03 11:55:09.951 localhost:52209 read 164

    MM,1111111111111111,+FFFFFFF,+004.000,-FFFFFFF,+008.000,-FFFFFFF,+012.000,+FFFFFFF,+016.000,+FFFFFFF,+020.000,-FFFFFFF,+024.000,+FFFFFFF,+028.000,-FFFFFFF,+032.000\r

Under streamdevice 2.5.10, this sets the NORD field of the waveform to 144. Under streamdevice 2.8.10, the NORD field is set to 145 - but

the actual string is unchanged, suggesting that the NULL terminator may now be being included in the NORD count. Unfortunately this broke

one of our drivers, which checked the length of the response before doing some processing.

What is the expected behaviour here - in general should NORD on a char waveform be including the NULL terminator or not?

Thanks,

Tom

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System