Issues using Diadem connectivity VIs in LV 2017: Porperty or invoke node is corrupt

[User002]

I am trying to get this example to work with my own data and custom layout using the Diadem connectivity VIs in LV 2017.

https://forums.ni.com/t5/Example-Programs/Automating-Report-Generation-with-LabVIEW-and-DIAdem/ta-p/...

But I get the following error:

When I open Diadem Integer Variable Get.vi and look at the invoke node I see this:

I am trying to automate report generation with a layout I've made. Are the connectivity VIs so old that they won't work with newer LabVIEW versions anymore? And if so what is the best way to automate report generation? I have also looked through the example finder and it only mentions controlling LabVIEW from Diadem, not the other way as far as I can tell. I also found the following page, but can't find the actual example, it is from Diadem 2015.

http://zone.ni.com/reference/en-XX/help/370858M-01/exploff/examples/expl_interfaces_vi/ 

Thanks for any guidance from anyone who has a good way to do this!

[Gaheel17]

Hello samhh1,

Is there any particular reason why you want to automatize this process using LabVIEW?

You can use DIAdem scripting to automatize the report generation process. Take a look at this document.

Best,

Gaheel17

[User002]

Thanks for the link Gaheel17,

No particular reason. This is a new endeavor for me and the old connectivity VIs were the first thing I came across when exploring automated report generation. Since posting I've started working with scripts and will definitely peruse the document you linked to as I keep researching.

Thanks again!

[User002]

Following up on this post, does anyone know of how I could generate DIAdem reports from Labview? I have a template and I can automate it within DIAdem, but I want to run my Labview programs, then have the reports without needing to open DIAdem. Seems like the old connectivity VIs would do this but don't seem to work.

Thanks!

[BG103]

Dear Aheel17,

Your response did not seem particularly helpful. You ask why someone would want to automate from LabVIEW? I ask why did LabVIEW make these VIs? Clearly there are many answers. I have very good reasons to automate from LabVIEW instead of DIAdem and am curious why you didnt even try to answer the question that I also am stuck on?

This particular issue showed up previously on one machine vs another so I suspected it was version issue. I am now having issue show up again on 2019 LabVIEW/DIAdem versions

BG103

[Brad_Turpin]

Hi All,

The LabVIEW DIAdem Connectivity VIs are indeed very old-- I believe they released first with LabVIEW 6.  They also have not been actively maintained by NI for almost a decade now.  However, they still work in all LabVIEW versions (up to 2020 so far), though of course they require a mass compile to the correct version you want to use them in.

The LabVIEW DIAdem Connectivity VIs use LabVIEW ActiveX invoke nodes to call the DIAdem application.  If you encounter problems, please check the compiled version of the VIs.  Additionally, you should match the LabVIEW bitness with the called DIAdem bitness, i.e. 32bit/32bit or 64bit/64bit.

All that said, about half of the LabVIEW DIAdem Connectivity VIs have been secretly shipping with LabVIEW for something like a decade as well-- tucked away in the vi.lib folder that houses the VIs to export a front panel graph to Excel (or DIAdem).  I recommend that you see if you can get by with the half of the LabVIEW DIAdem Connectivity VIs that secretly ship with every LabVIEW version-- they're guaranteed to automatically be shipped in the correct mass-compiled version, and theoretically LabVIEW has to support them.  Here's my favorite-- note that you can wire in either a REPORT layout file (*.TDR) or a SCRIPT file (*.VBS) into that second input.

"C:\Program Files\National Instruments\LabVIEW 2020\vi.lib\ExportToExcel\DIAdem Report Wizard Start CSC.vi"

Brad Turpin

Principal Technical Support Engineer

NI