the different result after building and on developing

[Nuclamer]

Who does anyone know this? I tested 'string to byte array'. I input the same parameter, but the result is different. How to get the same result?

Thank you for taking the time to read my question.

[Bob_Schor]

From the really tiny picture you posted (and attached), I cannot tell what you did, nor what you got.  Do you have a little VI that you would like us to look at? Please attach a VI (a LabVIEW file with the extension ".vi") and we will try it out and explain its behavior.

Bob Schor

[Nuclamer]

Block diagram is all like picture. I just used string to byte array. I didn't insert others.

[Bob_Schor]

You wrote a VI and say that it gives "different result after building and on developing".  I cannot see the code, only a very tiny (unreadable on my laptop) picture that I cannot "run".  I asked you to post the code itself, that is, the VI that doesn't work.  You failed to do so.  OK.

So what do you mean by "after building" (what does that mean, and precisely what did you do?) and "on developing" (same question, what did you do?).  

Is there anyone near you who knows LabVIEW?  Show her (or him) your code ad explain the problem.

Bob Schor

[Nuclamer]

Thank you for your reply, and sorry for the poor explanation.

My LabVIEW version is 2017.

My code is like the followings,

'string' control (named String) is connected with 'string to byte array'. 'string to byte array' is connected with 'array' indicator (named unsigned byte array).

When I run the VI on developing,

I input '사랑입니다.' in string control. The output (value of unsigned byte array) is 172 192 145 183 133 199 200 178 ....

I make executable file.' After building'  means executable file.

When I execute executable file by LabVIEW runtime 2017,

I input '사랑입니다.' in string control. The output (value of unsigned byte array) is 187 231 182 251 192 212 180 207 ....

I input the same input parameter (사랑입니다.), but I got the different output value.

[Nuclamer · Accepted solution]

I solved this. I have to change the setup('program name'.ini file) for executable.

[GerdW]

Hi Nuclamer,

---

@Nuclamer wrote:

When I run the VI on developing,

I input '사랑입니다.' in string control. The output (value of unsigned byte array) is 172 192 145 183 133 199 200 178 ....

I make executable file.' After building'  means executable file.

When I execute executable file by LabVIEW runtime 2017,

I input '사랑입니다.' in string control. The output (value of unsigned byte array) is 187 231 182 251 192 212 180 207 ....

I input the same input parameter (사랑입니다.), but I got the different output value.

---

I even cannot copy and paste your Korean chars into my English LV2016 string control, all I get are question marks (ASCII 63)…

When the StringToU8Array gives different result then you paste different data into the string control.

What happens when you show the input string in a string indicator set to show "hex display"?

When I input the hex values of your desired input string then I also get those byte values after conversion to U8 array:

[Yamaeda]

---

@Nuclamer wrote:

I solved this. I have to change the setup('program name'.ini file) for executable.

---

What did you need to change?