Read from HEX file error....expecting D(hex) but output A(hex)

[RavensFan]

Perhaps the scope is doing an internal conversion of 0A to 0D?

The question still needs to be answered, what is the source of this data?  What program or hardware is creating this data file?

Message Edited by Ravens Fan on 10-01-2007 01:55 PM

[PJS]

I used the binary file read, and displayed to a string hex displayed.  It shows exactly what your hex editor shows.

Message Edited by Stradis on 10-01-2007 01:56 PM

[Marc_A]

Right click the Read From Text File node and uncheck "Convert EOL." This is on by default and converts end-of-line characters to the platform specific equivalent.

[RavensFan]

Good call Mark.  Doing that I see 7 0A's and 42 0D's.

The fact that there are supposed to be 0A's and 0D's in the file wasn't clearly stated in the other posts.  When I did my examination, I saw the first 0A and investigated it directly from the text file without using Labview and found it was truly a 0A.  Thus a "where is the problem?"

[FredFred]

Thanks alot stradis,

That helped out my problem.

In the future I will use the read from binary file to extract hex data.

FredFred