DIAdem

cancel
Showing results for 
Search instead for 
Did you mean: 

write Diadem 9.1 plugin

I have a plugin that was written in version 10 that I can't load into version 9.1.  Can I convert or re-write the plugin so it will load into 9.1?
0 Kudos
Message 1 of 5
(3,960 Views)

Perhaps,

 

I the DataPlugin in question is not encrypted, and if it uses only functions that were available in the USI 1.1 version that ships with DIAdem 9.1, then yes, we can convert it to a DIAdem 9.1-friendly DataPlugin.

 

In that case, you just need to go to the DataPlugin management dialog, open the configuration for that DataPlugin, and change the assigned USI version from whatever it is now to 1.1.  Thereafter, it should work.

 

If you have trouble with this, let us know,

Brad Turpin
DIAdem Product Support Engineer
National Instruments

0 Kudos
Message 2 of 5
(3,947 Views)

Hi Brad:

 

Thanks for the reply.  Unfortunately the "Compatible with" field was already set to USI 1.1.  I had to do this in Diadem 10 because I don't know how to do it in version 9.  The plugin was developed in version 10.  I called the NI service desk before Christmas and worked with a support person to troubleshoot.  We re-installed diadem from the GM MSI script.

 

I get the following error when trying to load the plugin after verifying

 

This action is only valid for products that are currently installed.

 

We get this error on 3 laptops.  In addition, Windows explorer does not display the NI icon for the file.  Do you think it is an installation problem?

 

Tom Jackson

0 Kudos
Message 3 of 5
(3,938 Views)

Hi Tom,

 

If the *.URI file does not show up with an NI Eagle icon in Windows Explorer, then that mans that the usireg service is not active on that computer.  The usireg service is automatically installed with DIAdem 9.1 and later (the versions of DIAdem which support DataPlugins), as well as with modern versions of LabVIEW.  If you have DIAdem 9.1 on that computer and do not see the NI Eagle icon on the *.URI file, then that suggests that there is an issue with the installation of DIAdem 9.1 on that computer.  I do recognize that this has occurred on 3 separate computers now, so it does appear there is a systematic issue here, not a one-off problem with a specific computer.  Would it be possible to test this on a computer that has had DIAdem installed "nomally", that is, from the MSI installer (setup.exe) as opposed to the installation script approach?

 

Bad Tupin
DIAdem Product Support Engineer
National Instruments

0 Kudos
Message 4 of 5
(3,920 Views)
Thanks Brad.  I'll let you know the results once completed.
0 Kudos
Message 5 of 5
(3,910 Views)