Experimental Physics and
Industrial Control System

Here is the bug fix.
Dirk

On 01.04.2015 14:03, Dirk Zimoch wrote:

On 01.04.2015 12:07, Isabella Rey wrote:

Hi Ralph,

Yes, but with %s the device receives something like:

load_curve 675892112117108115101461161201160 3870\r\n

You are right. And I think that is a bug.

Dirk

The null character corresponds to the 0 at the end of the waveform (I've
checked it with small strings)

Isabella

On 1 April 2015 at 10:44, Ralph Lange <[email protected]
<mailto:[email protected]>> wrote:

    Have you tried using "%s" for the string output?

    ~Ralph



    On 01/04/2015 10:44, Isabella Rey wrote:

        Hi All,

        I have a device to which I need to send a file path followed by
        a number:

        example:
        load_curve C:\pulse.txt 3870

        The file path is stored in the database as a waveform of chars.
        When I run the protocol stream device sends (what I think is) a
        null terminator after the file path:

        device receives:
        load_curve C:\pulse.txt\x00 3870

        Is there any way of getting rid of the \x00 terminator?

        Below I copy my protocol and the database records.

        Cheers,
        Isabella


        I've defined the protocol in stream device as:
        load_curve
        {
             out "load_curve %(\$1)c %(\$2)i";
             in "%(\$1:\$2)b";
        }

        and in the database I have:

        record(bo, "DEV:LOAD_CURVE") {
           field(DTYP, "stream")
           field(OUT, "@my.proto load_curve(DEV:CURVE_FILE, DEV:VPI)
        $(PORT)")
        }

        record(waveform, "DEV:CURVE_FILE") {
           field(DESC, "File path")
           field(DTYP, "Soft Channel")
           field(NELM, "256")
           field(FTVL, "CHAR")
        }