05-05-2006 07:34 AM
05-05-2006 07:47 AM
Hi,
I'm not shure but maybe that prperty only belongs to the serial read ?
I do a lot of serial communication with VISA and I have never seen an x00 (or any other character) send out at the beginnig without having wired it.
Have you checked the string you send out? (place an sring indicator set to hex or \-display or use such an indicator as a custom probe)
05-08-2006 06:56 AM - edited 05-08-2006 06:56 AM
Hello!
Thanks for reply, I created a Indicator in Hex for the String in Hex, but there wasn´t a 0x00 (NUL), only the 0x20 (the zero) was showed. I bypassed the serial line and recorded the communication and viewed the logfile in an Hex editor, where I can see the NUL.
If I use Hyperterm, then it works in the proper way...(I can see in the logfile of the serial communication a 0x20 at the beginning of the string...)
My Problem is, that my reciever interprete the NUL sign in a wrong way so the whole string seem to contains no numeric values.
What are the reasons for that option with discarding NUL Characters? Is this a newer or older type of Character used for Serial Comm?
How can I force Labview to not send that NUL Character?
I use Labview 7.1 with Win2K SP4 on an AMD Athlon 900Mhz
Greetings
cand. Ing Sebastian Neumeyer
Message Edited by Seppfish on 05-08-2006 06:57 AM
05-08-2006 07:23 AM