You could also package some sort of configuration file along with the bitfile that describes the data types. Veristand does something very similar with its FPGA support. However that's because all the data is coming down DMA FIFOs of type U64 array so each time cycle you need to know how all the relevant data is packed in U64s (including how many U64s to read). If I'm not mistaken, the VST Instrument Design Library also utilizes DMA FIFO for the register bus to send configuration data. It also utilizes the DMA FIFOs for sending back the multi-record acquisition data.
Anyway, my point is that if you standardize on using some sort of format for data type description, it could allow you to do some pretty interesting things and you could build a layer on top of this add-on to handle that. If you just want to convert FXP dependent upon the C Series module of interest, you could use a naming convention on your indicator that states the type of module, and then on the host you could build up logic that will appropriately cast it to the correct data type depending on the module.
Cheers,
Mike Lyons
