10-31-2011 11:23 AM
Hi
I also got this off agilent
Looking at the error message, It seems that the problem might not be with the interfacing of Dasylab with the 34972A. I have looked for information about the error message that you get, and were able to find something from The IVI Compliance Package release notes (please find attached).
This is the part you might consider useful:
“Prior versions of the IVI Engine exposed several functions for creating and persisting configuration data at runtime. The functions are no longer supported and now return the following error: IVI_ERROR_FUNCTION_NOT_SUPPORTED. If you want to design programs to create configuration data at runtime, use the new IVI Engine function, Ivi_GetConfigServerHandle. You can use the handle that this function returns with the IVI Foundation-defined Configuration Server C API to edit the configuration data that the IVI Engine is using
10-31-2011 02:30 PM
I believe this information may be outdated (the only reference to this was in IVI Compliance Package 2.0). The most current version available is 4.4.0. Do you have any other programming environment to try this in, like LabVIEW or CVI? The reason I ask is this function still exists, so that statement doesn't seem to make sense to me. In one of your screenshots, you had the Ag34970 highlighted under IVI Drivers>>Advanced>>Instrument Driver Software Module, can you post screenshots of the Support Modules and Physical Names tabs that show in the center pane when Ag34970 is highlighted?
Thanks,
Sean
11-01-2011 02:15 AM
Hi
Could the problem be because i changed the name of the published API from IviDriver to IviDmm in instrument driver software module. I only did this so that Dasylab would pick up the driver as the 34072A didnt have a IviDmm driver on the agilent web site. When the driver is called IviDriver does this mean that the driver is instrument specific and may not have all the IviDmm functions ?
11-01-2011 05:24 PM
This is definitely a possibility. As you can tell from the error description, that error number is referencing the fact that it is not a supported function. Did you just download the drivers for the 34072A and then browse to the folder IviDriver and rename it IviDmm?
Thanks,
Sean
11-02-2011 02:59 AM
Hi
Ive since had an Email from agilent and they are now telling me that this is the issue. Iam looking at using LABVIEW now. Ive downloaded the Evaluation version of LABVIEW 2011 and every thing seems to work fine with the example VIs from the agilent plug and play drivers. Thankyou for your assistance. The only issue that i will have now is migrating an extensive Dasylab program into LabView test sequences and all.
11-03-2011 02:10 PM
I'm glad you were able to establish the cause of your issue. Good luck with your migration, and if you have questions, I hope you are able to find assistance!
Thanks,
Sean