No. Each array element is supposed to be a complete Cstring. So it has to be terminated with a null. You have not done that. Only the elements in quotation marks have it, because the compiler adds one to the end of a defined constant string automatically.
As Whandall has pointed out, the values not in quotation marks won't work at all because they aren't pointers. If you fix that, actually you don't need to think about null termination because it will be done for you.
aarg:
No. Each array element is supposed to be a complete Cstring. So it has to be terminated with a null. You have not done that. Only the elements in quotation marks have it, because the compiler adds one to the end of a defined constant string automatically.
rich_330:
Is there any way to get the 0x9f and 0x80 values?
I think I'm more after the hex value you to be sent rather char if that makes sense?
Im trying to interface with an existing 232 protocol.
No, you can't print those values because they are control codes in code page C1 (i.e. non-printable characters). Well, I showed you that you can print y-umlaut. But the Euro symbol doesn't exist in that code page.
So why are you concerned that the values are non-printable by a serial monitor or client? Why would you even expect them to be printable? I thought that was the thing that didn't work... now it sounds like there is some other requirement that you haven't told us about that is failing. What doesn't work currently?
You sure could have saved us some time by mentioning this "device protocol" up front.