Doug,
There are several ways that you could go about this.
The best method is dependant upon just how much flexibility the system is required to have. You mention 16 signals, with the possibility of current, voltage, or RTD inputs. How much variablity is there on the composition of the signals, is it possible that one test will require 16 RTD inputs and the next 16 voltage inputs, then a third requiring a mix of all type of signals?
The first option would be to create a multiplexer that dynamically re-routes the signals based upon the configuration chosed by the user. I have built test systems in this manner that use several large relay multiplexers to provide flexible system testing that allows me to test or generate the signals for every type of FieldPoint IO module. However, FieldPoint itself does not offer any large density relay multiplexer options although other NI products such as PXI and SCXI do. One type of solution would be a PXI chassis, a PXI controller (why not build the entire computer system in at once), an NI PXI-4070 DMM (offers current, voltage, resistance, diode, and other readings) and an NI PXI-2503 multiplexer (with RTD's you would operate it in the 12x1 (4 wire modue). THis would allow you to route 12 different front panel signals to the DMM, one at a time. Use 2 PXI-2503's and wire them together to get a 24 input system.
A second option, and one that is less complicated, is to simply design and wire the system in such a way that you can provide any type of signal to the measurement system which is capable of reading every type of device. For example, consider a FieldPoint Network module and a FP-TB-10 Dual Channel Terminal base. The FP-TB-10 can mount 6 Dual Channel modules. You could place a FP-AI-V10 for 2 input channels of 0-10 Volts,a FP-AI-C020 for 2 channels fo 0-20 mA inputs, a FP-RTD-PT100 for two channels of RTD inputs, etc... On your front panel, you can wire several input connectors, you can use one set of connectors for current inputs, another set of connectors for voltage inputs, etc... From a software perspective, you can simply display the appropriate channel based upon the user defined configuration.
The two approaches really boil down to how much flexibility the customer requires.
Regards,
Aaron
LabVIEW Champion, CLA, CPI