There are various techniques used when creating a driver that supports multiple models or models with different installed options, where there are slight functional differences between the models and options. <br>
If there are VIs that only pertain to a specific model or option, then modify the VI prefix to associate that VI with the particular model/option. For example, a function general family driver might use "ag33xxx" as the general prefix, but VIs that only operate on the ag33250 might use the prefix "ag33250". <br> It sounds as if you need to remember this model/option to modify functionality within a common VI. For example, the commands might differ between two different models. To handle this situation, you store model information in the User Data VISA property. At initialization time, you can detect which model you are connected with and either store the model number directly or some ID to represent the model.<br> Both these techniques are used in the <a href = http://zone.ni.com/idnet97.nsf/9b2b33e1993d877786256436006ec498/0027109f3d6e32dd86256d6d0068a5bd?OpenDocument> Agilent 33xxx function generator driver </a>. You will see how User Data is set in the Initialize VI and the retrieved in the Configure Burst Modulation VI.
