LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

String Array Displays Hexadecimal Strings but Probe Shows Weird ASCII

Solved!
Go to solution

EDIT: I have learned that the LabVIEW doesn't display hexadecimal code automatically, and that this must be selected in the string indicators manually. It also appears that in order to make a probe read hexadecimal, that I must make my own customized one (though I have not tried that yet). So I am going to call this topic as solved.

 

I'm using Parker Lord's LabVIEW code to read data from one of their IMUs (3DMGX5-IMU), and everything seems to be working as intended with that code. However, when I attempt to read the 1D string array of hexadecimal strings from their sub-VI with anything other than a 1D string array indicator I get a weird glob of symbols (maybe ASCII?) instead of a hexadecimal string array. This can be seen in the attached picture.

 

My original intent was to convert the hex strings from sub-VI to a single precision float that I could then chart to see useful data from the IMU. I immediately noticed that the (indexed) string being passed into my for loop did not display as hexadecimal, and therefore I wouldn't be able to convert them. Poking around, I noticed that I am seemingly unable to even probe the output of their sub-VI to see the 1D string array correctly as an array of hexadecimal strings. However, if I right-click on the sub-VI output and insert an indicator, the array is displayed as expected.

 

I can't seem to find any reason why this would be occurring so far. Does anyone know why I am only able to see the hexadecimal strings in the 1D string array through an indicator and not through any other means? Is it possible that the 1D array indicator is performing some sort of string conversion?

 

Thanks in advance for any pointers. I've also attached my VI.

Download All
0 Kudos
Message 1 of 2
(670 Views)
Solution
Accepted by topic author curiositas

If you right-click on an element of "Valid Msg Array (0x Display)" you will see that the display mode is set to "Hex"

paul_cardinale_0-1678898515790.png

Unfortunately, when probing an array of strings, it always uses the "Normal Display" setting.

But you could create your own custom probe.

 

"If you weren't supposed to push it, it wouldn't be a button."
Message 2 of 2
(645 Views)