Thank You Tien
I suspected that would be the answer. I feel this is a much needed addition to greatly enhance useability. Of course, semiconductors are the focus. As an instructor, the lab manuals often use components not in the db. I typically use a distributor site to find components with similar specs, then back to Msim to see if it exists. If it does, the simulation may not be what is expected and the cycle repeats to find another similar part. This can take a long time.
For the actual component to be purchased, it ultimately comes down to price since students will have to pay for the parts. But for the simulation, a similar part is usually good enough IF one can be identified. That is the crux of the problem It would be very nice if one could take the opposite approach whereby the useable Msim parts are identified parametrically first, then simulations run, then go to the distributors for the most cost effective solution.
In our preliminary circuit design approach, general part values are spec'd, distributor sources are compared for suitable components, possible part numbers are identified, then the lookup cycle between Msim/vendors begins. I would note here that it is preferred that your proven models be the basis for simulations rather than creating new models for parts not in the db and that prototype/test resolves the final part values.....
I have to believe that NI has a db with commercial Msim part numbers being used along with their key electrical specs already, yes? And if not, your tight integration with certain vendors should permit an exchange of information (a text dump). This may be overload for the function window. A db/spreadsheet view similar to the vendors seems a better fit for such information display. I will keep my fingers crossed for a future version of Msim.
