HEX Problem

[Detox92]

Hi again,

I could really do with some help regarding sending commands using the code display string.

Basically i am need to send a HEX string of 02 08 00 xx xx 00 00 20 00 03 to a bluetooth device as a command.

The xx represent the changing data hex that i am sending.

The problem i am having is that i can send the command no problem by writing out a full string and using the \ code display input: \02\08\00\xx\xx\00\00\20\00\03 and this has the required effect.

When i send the same concatenated string i have issues.... 1st set \02\08\00 2nd set is my data 3rd set is \00\00\\20\00\03  but i dont get a code display output that i need, i get \02\b\009624\00\00\s\00\03

Im sorry if this doesnt make much sense but in my head i think it sounds ok!

Many thanks

Alex

[crossrulz]

Since you are talking about commands in Hex, you should display your strings in Hex mode.  It will make reading the code a lot easier.

[kbbersch]

I'd like to see your actual code but you don't need all the slash characters.  The slash designates a non-viewable character so if enter \20 you'll end up with a space (ASCII 20d) which will the show as \s.  To enter "20 08 00" using codes display you would enter "20\s08\s00".  You're better off not using codes display since it only affects what you see, not the data that's sent.

[kbbersch]

---

@crossrulz wrote:

Since you are talking about commands in Hex, you should display your strings in Hex mode.  It will make reading the code a lot easier.

---

I don't think hex mode display would help in this case.  It might be somewhat confusing since it displays spaces that aren't really there.

[camerond]

You are sending exactly what you told the computer to send. If you consistently show your constants and indicators in hex, you'll see it right off. Displaying things in hex mode in LabVIEW always shows a space every two characters (4 bytes) to make it easier to keep your place, but a "space" character in hex is 0x20 (shows up as 20), so there's no chance of confusion. To me, the "\ codes" display is often more difficult to interpret, but sometimes necessary (i.e., if you're writing a regex).

Cameron

[Detox92]

Hi,

Ok when i send the command as HEX i see 0208 0038 3832 3400 0020 0003   This as the output command

0208 00 is ok

00 0020 0003 also ok

38 3832 34 as my data to send is incorrect  im trying to send 8624 and it sends 3836 3234  instead (the ASCII version being converted to HEX i presume.)

Sorry if i am missing something simple here but im dammed if i can work it out.

Thanks again

[crossrulz]

---

@kbbersch wrote:

---

@crossrulz wrote:

Since you are talking about commands in Hex, you should display your strings in Hex mode.  It will make reading the code a lot easier.

---

I don't think hex mode display would help in this case.  It might be somewhat confusing since it displays spaces that aren't really there.

---

Not really.  It just separates the data into 16 bit groupings, which makes it easier to read.  It is a lot more clear that the \ codes display.

[kbbersch]

Don't use hex display or codes display.  Just use normal display.  The display does NOT change what is sent, only the way you see it.

[kbbersch]

Hex display can be clearer if you need to see the hex values of the ASCII characters.  That's not what is needed here.  The OP needs to send ASCII HEX two characters at a time seperated by spaces, or at least that's what I'm readin and the way most instruments that I'm familiar with work.  Since that's what's needed NORMAL display will show what is being sent.  HEX disply will show the hex value of the ASCII characters being sent, which would be very conusing since what you see is nothing like what is being sent.

[Detox92]

Understood.

When i send a string in this view it shows in ascii characters, but i need to modify this string in each loop which is why i have been trying to see that i happening.

I find if i input the string with code display i have no issues sending the command.

Can i convert the HEX data i have to Ascii and then concatenate it into the string??

Thanks

Alex