I am sure that this is far from a 'new idea'. I have been using DiAdem 11.1, and have not looked at the new features of 2010 yet. The new idea...use LabVIEW code to make scripts. I know LabVIEW very well, that is how I make the TDMS files; but the idea of data analysis or automation comes to a standstill when you tell me I need to learn VB to manipulate or work with the data I just gathered beyond the canned toolsets already in DiAdem. DiAdem needs to be like Teststand in this regard. You can use different code types with Teststand, and it works. And this needs to work in all the different categories of scripting or automation (Navigator, View, Analysis, etc.) Any software package NI creates should have LabVIEW as the center point, and always require seamless integration of LabVIEW code. I think that comes down to plain-jane good marketing strategy.
Hi biographie,
Switching out the VBScript scripting language in DIAdem for a similar scripting language may eventually happen, but switching to a compiler such as LabVIEW would require so much work that it never gets serious consideration from version to version. Now that there is a shift toward server side processing with the Analysis Server, NI would be much more likely to create a native LabVIEW task option in the Analysis Server, like just happened for Python with the 2018 release.
Brad Turpin
DIAdem Product Support Engineer
National Instruments