Hex & Reading board VI

[dhanna]

forget how bothersome linking VI's is!! 

[johnsold]

Zip all the VIs and attach one file.

Lynn

[GerdW · Accepted solution]

Hi dhanna,

in your array you defined a HEX number like "6065710800000699" in an I64 array.

In your connect.vi you defined an I32 number which CANNOT hold that number. Thus it gets coerced to I32-MAX of 0x7FFF.FFFF…

Always use the correct datatype. Create constants by right-clicking the corresponding terminal…

[dhanna]

think whats needed is now there?

[GerdW]

Hi dhanna,

yes, it's all there.

You need to learn how to use those different datatypes and after that change the datatype of your numeric constant!

[dhanna]

shouldnt matter about the representations as all i've done is change the original array to have that new hex code (which represents a different board) in. as opposed one of the boards it had (606578000000000E)

[GerdW]

Hi dhanna,

I can't comment on what you changed and what you didn't changed.

All I see is a coercion dot and a datatype mismatch!

I suggested a possible solution. You might look for other solutions if mine is no option for you…

[dhanna]

got it!! one of the data types had to be 64, so kudos!!
the other mistake was i mistyped a number into my Hex code........ 😞

thanks guys, shall give kudos for our help