09-01-2012 03:42 PM
This is somewhat of a planning question regarding indexing and possible future utilization of spare inputs on CompactDAQ modules. What do you folks typically do when you are designing an application with a certain number of defined inputs and a number of spare hardware channels that may or may not be used in the future? Do you include and index the spares in the original application, or do you deal with them down the road if and when those channels are ever put into use? Is it better to have the spares integrated into the application scheme, or it it just as effective to tack them on at the end later? What are some of the pros and cons of both methods?
09-01-2012 04:11 PM
Good Question. I normally won't include the un used channels into the application.
Facts
Hope this helps
09-01-2012 05:15 PM
I think P Anand has listed several key points.
Only you can answer how likely the addition of channels will be. If you feel that the extra work to add channels later will be greater than the work to include them in the original version, then it may be worth including them now. Also consider whether the uused channels would be confusing to the end users.
Since you are considering the possiblity of adding channels, I think you should design the program so that doing so will be relatively straightforward. For example keeping the list of channels as an array and the data in multidimensional arrays (where one dimension is channels) simplifies adding channels. The data structures do not change, only the number of elements. Make typedefs of controls (especially clusters and enums) which might need to be changed as channels are added.
Lynn