String data type for recording data

[spandy16]

I am using a IO_LINK CALL FB for reading data from sensor and when I record the Vendor ID or Name in String datatype I get the first two characters missing. I know that it's because of the string datatype. But then how to address the Record area so that I get the full text displayed.

 

[JesperMP]

I have no idea what is the problem or what it is you must achieve or how you have done it.
But I am taking a guess that your problem has to do with that for STRINGs the values in the two first bytes represent the reserved number of characters and the actually used number of characters.
Depending on what you want to do, you have to start reading the content of the STRING from the 3rd byte.

 

[spandy16]

I have no idea what is the problem or what it is you must achieve or how you have done it.
But I am taking a guess that your problem has to do with that for STRINGs the values in the two first bytes represent the reserved number of characters and the actually used number of characters.
Depending on what you want to do, you have to start reading the content of the STRING from the 3rd byte.

yes you are true..that I need to read to 3rd byte so that the whole information is displayed. I am sorry for not displaying screenshots as I work on a different station and there is no internet connectivity there.

I have made for e.g. a Output var "Record1" with string type. Then in my FB there is a field 'RECORD_IOL_DATA' and there I wrote "Record1". So when I observe the values in watch table I get first two char in the string clipped. So I wanted an easy solution for this.

 

[JesperMP]

Not sure what you mean by 'clipped'.

Anyway, you cannot observe a STRING in a VAT. So I am not sure what you are doing.
But you can observe a series of CHARs. Just be aware to start from the 3rd byte.

 

[spandy16]

Not sure what you mean by 'clipped'.

Anyway, you cannot observe a STRING in a VAT. So I am not sure what you are doing.
But you can observe a series of CHARs. Just be aware to start from the 3rd byte.

By 'clipped' I meant that... If the sensor vendorname is 'ABC AG' and by calling the FB with index specific to vendorname, I get a result 'C AG'. I hope you get what I mean.

And about observing the string I meant that I wanted the sensor vendorname to be displayed in my HMI interface.

I might be wrong here trying to write the data to a datatype STRING. But with chars everytime I have to transfer it to a variable so that I can display the result in the output field in HMI. And it's not just one information I want. It's like more than 20 different parameters which I want to read.

 

[randomFire]

Because as Jesper said, you need to start your string from the 3rd byte. The first 2 bytes are reserved by the system.