Hexadecimal to "readable" string

[ian_fung]

Dear smercurio_fc

Thanks for the advice...

I just wish to point out that the VI was not lock by any password... all that you need to do is CTRL+M

So, it's for public 😉

[smercurio_fc]

Yes, I'm well aware of that. But there's a lot of new people using LabVIEW that don't yet know that and would get quite annoyed at that. Just saying.

[ian_fung]

I am sorry if that does not make anyone new to labview learn about using CTRL+M as well...

All I was doing to trying to help. Let's put a full stop here. Thanks for your advice.

[shivels]

Hi,

I have a file which contains alphabet words and decimal values.  After the file is processed, it comes out looking like the attachment.  I convert the file to hexadecimal.  I then convert the hexadecimal values to decimal values.  I am able to find the original decimal values in my converted array.  I am now trying to locate the alphabet words in the file.  I have converted the hex string into a byte array and get ASCII values, but when I convert those using an ASCII table, I get non-sense words.  I think there is a simple conversion step I am missing.

Adam 

[smercurio_fc]

I do not understand these statements:

---

I convert the file to hexadecimal.  I then convert the hexadecimal values to decimal values. 

---

If you're looking for the text information simply read the file as a text file directly, and then search the string using, for example, Match Pattern:

Message Edited by smercurio_fc on 08-08-2008 10:07 AM

[Catlan]

Hi everyone,

This is my first messge on this forum, so please be indulgent if I forget something... thank you in advance 🙂

I have an hexadecimal values file that I want to convert into readable text.

The thing is that some hexadecimal values, for instance FF are converted using octal arry to string to ÿ where in the extended ascii table, FF is for nbsp (non breaking space). I looked further into text presentations and it seems that FF (or 00FF) is actually ÿ but in UNICODE format whereas UNICODE is not activated in my labview.ini file (i checked it).

Cold anyone help me on this matter, it seems that I may have missed something.

thank you very much in advance for your help.

Regards,

Thomas

[RavensFan]

Where do you see that FF corresponds to a non-breaking space?  I don't actually think there is a defined standard for the extended portion of the ASCII character set.  While they would typically be the same, I think there can be differences between computers or OS's or whatever on what some of the extended characters actually are.  I had never heard of FF meaning a non-breaking space.

Here is a link http://www.ascii-code.com that lists one of the variations of the ASCII table and FF is not listed as a non-breaking space but as "Latin small letter y with diaeresis".

Upon further review, I see that a non-breaking space is decimal 160 or hex A0 in the extended character set.

[Catlan]

Hello Raven's fan,

First of all, thanks for your fast answer.

You're right, there is not common standard for extended ASCII.

For instance, following this link http://ascii-table.com/ascii-extended-pc-list.php FF is the ascii code for nbsp.

On the same link, we can see that HEX 98 is the code for ÿ...

I'm trying to sort out an issue on SEMI SECS1 standard were characters are not translated correctly once converted in Text format. I was guessing that the ASCII table used by my customer is not the proper one, reason why many characters appear to be squares when they should be translated (to my mind) into nbsp...

thank you again for your help.

Regards,

Thomas