02-22-2005 08:52 AM
02-23-2005 09:37 AM
02-28-2005 09:19 AM
03-01-2005 08:17 AM
03-02-2005 05:57 AM
02-25-2011 09:50 AM
Well its time to dust off an old thread I started. Brad's solution worked way back when this thread was created (using Diadem 9.1) but now I am upgrading to Diadem 2010 and some of my scripts no longer work. I traced it down to the ScriptCMDreset() function. In Diadem 2010 I get an error stating this command cannot execute because other user commands are running and cannot be reset. I don't call any user commands in my scripts. Is there something in DIAdem 2010 that has changed from 9.1 that the ScriptCMDreset() will no longer work properly?
Has anyone else run across this?
Thanks in advance
AJL
02-28-2011 08:57 AM
Hi AJL,
I just tested running ScriptCmdReset in DIAdem 2010, and it executed without error on my computer, so there must be SOMETHING different going on at your end. It is possible to dynamically create and declare UserCommands, so maybe a script is running that creates a UserCommand that you're not aware of.
If you choose the menu "Settings>>Options>>Extensions>User Commands...", what do you see in that dialog?
Brad Turpin
DIAdem Product Support Engineer
National Instruments
02-28-2011 09:18 AM
Thanks Brad. I have looked at the mentioned location and a "usercommandexample" is running on startup. I deleted this but still have the same problem. I will do some more digging and see if any other user command is running.
On another note, will the diadem connectivity toolkit 3.0 for LabVIEW 7.1 work with Diadem 2010 (11.2)? When I tried this I get a Diadem connectivity open VI reference error.
Thanks,
AJL
02-28-2011 01:23 PM
Hi AJL,
I would have expected the LabVIEW Connectivity VIs for LC 7.0 to work with DIAdem 2010, mainly because very little has changed in the DIAdem ActiveX server. There are newer versions of the LabVIEW Connectivity VIs that you might be able to use which were tested against DIAdem 2010. What is the newest version of LabVIEW that you can use?
Brad Turpin
DIAdem Product Support Engineer
National Instruments
03-01-2011 07:57 AM
The newest version I can use is LV7.1. I am trying to get the LV developers to upgrade though. An interesting thing I discovered yesterday was that if I call the LV VI from DIAdem the VI gets parameters from DIAdem but I cannot return any data. The error I get when called from DIAdem is an 8088 DIAdem Interface connection fail. However, if I have DIAdem open but run the VI from LV everything works fine.
Next calling LV from DIAdem and if I don't pass my errors from VI to VI I get the error message for the 8088 but everything works and returns the correct data to DIAdem.