How to change the digit format in the string indicator ?

[reteb]

In LV 7 I can cascade ( daisy chain ) various I/O Assistants ( each for another GPIB instrument ) and write and query to and from each GPIB instrument.

I can have the queried data of each separate GPIB instrument display in a separate front panel string indicator.

However, each front panel character string indicator seems to be length limited so that part of the digits in each character string gets lost.

I failed to find where to change the character string format of the displayed data as read in thru the I/O Assistants.

Where should I search ?
Thanks for help.

[altenbach]

String indicators don't "format" any data, they just diplay it (of course you also have to option of /code or hexadecimal if desired).

I dont use GBIB, but if it is really just a string indicator there are two possibilities:
-- The string data gets truncated somewhere in the code. It could be that the byte count in GPIB read is to small for your application.
-- The indicator is simply too small for the data. In this case you can just enlarge it and even display a scroll bar.

It is difficult to say more without seeing the code. How long is the expected string and how many characters do you actually see?

[TommyTestBoy]

I agree with the previous post - most likely the data is being truncated somewhere in your code. I assume that inside of Instrument I/O Assistant you see the data parsed correctly, and it is only when you run the VI that you see this truncation behavior? Are you reading binary data or ASCII data from the instrument? It would be helpful if you gave an example of what the data in the indicator should be and what you are actually getting. Attaching a VI that demonstrates the problem would also be helpful.

[reteb]

Thanks alot.

Indirectly and for a surprising reason you helped me out.

Your assumption that the data were correctly parsed in the I/O Assistant and were truncated ( actually even corrupted ) only when running the vi, made me think over where the data truncation/corruption could have arisen in my GPIB system chains ( six GPIB instruments, partly daisy chained, partly star chained, but five of the six instruments were released from their cables while keeping all cables piggy backed ).

Quite surprisingly it appeared that the data were already corrupted in the I/O Assistant ( after having released all GPIB instruments but one from their GPIB cables ) so that the unterminated cables must have been the reason of the data clutter.

After reattaching the n
onpowered remaining GPIB instruments to their cables, the data truncation and corruption was over.

This was quite a good ( hardware ) lesson for me....

Thanks again.
You laid me on the scent.