Re: Inconsistency in devAsynOctet for stringout and waveform records

[Eric Norum <wenorum@lbl.gov>]

So the device at the other end of the wire will see ‘\0’ characters?  That doesn’t seem right to me. 

I think that the existing behaviour is correct.  stringout records send strings — and no trailing ‘\0’.  waveform records send blocks of arbitrary bytes.

On Jul 23, 2016, at 4:11 PM, Mark Rivers <rivers@cars.uchicago.edu> wrote:

So writing a string to a waveform record with Channel Access or dbpf also sets NORD to include the nil byte.

So my conclusion is that the stringout behavior in devAsynOctet is incorrect, it is not including the nil byte in the call to writeIt, but it should be.

Mark