01-22-2004 03:01 PM
07-03-2010 05:01 PM
All I can do is to provide some generic process where you analyze the instrument commands in the one driver versus the instrument commands in the manual for the other instrument. Change as needed. You should really have a good understanding of the instrument functions before modifying any code. You should also have a basic understanding of an instrument driver itself. Information on that can be found here though the driver you are using as a template is old and not written to any current standard. It might be just as simple to start from scratch. Drivers are not really that hard to write.
07-03-2010 05:09 PM
Thank you for your reply, Dennis.
I have some more questions. How, if its possible, one can transfer the known SMU connections to the labview program? and also if one knows the commands, for performing tasks for the particular instrument, then is there any standard procedure to transfer them to the LabVIEW environment?
07-03-2010 05:23 PM
Don't know what you mean by connections. If you mean setting up an instrument manually and creating the commands to recreate that setup, then that is instrument dependent and if you are familiar with the instrument manual, you would know whether such a feature exists or not.
Yes, there are standard procedures for using commands in LabVIEW. As already mentioned, you can create a driver per the linked instructions above, use the Instrument I/O Assistant, or just use VISA Wrtes and VISA Reads for just the commands you need. Have you gone through the fundamentals tutorial?