05-14-2008 10:18 AM - edited 05-14-2008 10:19 AM
05-14-2008 10:26 AM
05-14-2008 10:26 AM - edited 05-14-2008 10:28 AM

05-14-2008 10:28 AM
05-14-2008 10:34 AM - edited 05-14-2008 10:34 AM
05-14-2008 10:51 AM - edited 05-14-2008 10:59 AM
05-14-2008 11:47 AM - edited 05-14-2008 11:51 AM
Message Edited by russelldav on 05-14-2008 11:49 AM
Message Edited by russelldav on 05-14-2008 11:49 AM
Edit: I just noticed in "Array 2" the correct data is there, it's just separated by a word that equals 0.
05-14-2008 11:53 AM
JeffOverton - thanks for providing an example. I can't open anything newer than 7.1 though I'm sorry.
05-14-2008 12:08 PM
05-14-2008 12:08 PM - edited 05-14-2008 12:09 PM
Typecast is the only reasonable way to do all this. As type, you just create a diagram constant of an empty I16 array an all will be correct on the receiving end.
russelldav wrote:
I can't use the example where the "type" is defined by linking to the original Array, as eventually the two arrays will be in different VIs on different PCs.
A coercion dot means that the datatype is different to what the function expects and an implicit conversion is taking place. Press ctrl+h to enable the context help and then hover over the wire going to the function. See if it is really a U8 array.
russelldav wrote:
How can I clear the coercion dot on my original example (at the top of page 1)? What does it mean anyway?