Right now there is restrictions in the Custom Device API that only allow scalar values.
The only channels that do officially support more dimensional data are simulation model inports and outports.
Depending on what you want to do with the data, you could potentially represent the DBL value in its binary format and stuff four 16bit values into one DBL value.
The downside is though, that these specific channels must not be used anywhere else in the system other within your custom device.
If you try to use one of these modified channels in a calculated variable you are not gonna see the expected result.
For now, the safest way would be to create for each individual 16bit output value a separate channel in VeriStand.
Let me know if you have any questions,
Tom
