“Unexpected Error” opening files

[Bilby42]

I've been experimenting creating data plugins using the Labview SDK, and have successfully got the examples shipped with the SDK to work (example loads a sample with the "lvtxt" extension). The import of these "lvtxt" files into the data portal works fine, until I attempt any analysis on the data portal data.

For instance;

Step 1: load the sample "lvtxt" file into data portal using plugin - works fine

Step 2: Clear the data portal, and reload a "lvtxt" file using plugin  - again works fine

Step 3: Perform any operation on data in the data portal (for instance min/max) - works fine

Step 4: Clear the data portal, and attempt a reload of the same "lvtxt" file - Consistently fails.

The error message that appears when I try to reload the "lvtxt" file using the plugin is "Error message from DIAdem command kernel: Unexpected error". The only option is an OK button with no other hint what's wrong. 

Annoyingly, the only way to "clear" this error is to quit and then restart DIAdem. Everything then works fine until I again modify data in the data portal, upon which the error occurs again. It appears changing the data structure (either storing results in the existing channel properties or writing the analysis to a new channel), causes a conflict with subsequent plugin loading operations. I've found no way to clear the subsequent plugin loading errors, except by doing a DIAdem restart.

What am I doing wrong here?

Labview 2015 64 bit

Labview plugin SDK 2015 64 bit

DIAdem 2017 64 bit

[Christian-P]

Hi,

I was able to reproduce the problem with the example. Here's what I found out:

DIAdem	2015 SP2 32 Bit	2015 SP2 64 Bit	2017 32 Bit	2017 64 Bit
LabVIEW 2015 64 Bit	incompatible	✓	incompatible	error
LabVIEW 2016 32 Bit	✓	incompatible	✓	incompatible
LabVIEW 2016 64 Bit	incompatible	✓	incompatible	error

The error only shows up with DIAdem 2017 64 Bit but not 32 Bit! The LabVIEW Version does not seem to make a difference.

I'm not sure about the reason. Maybe Brad or Walter have an idea.

[Brad_Turpin]

Hi Bilby,

R&D has verified that this is a bug, which they hope to address for the DIAdem 2017 SP1 update, due out early Fall of 2017.

Sorry for the inconvenience,

Brad Turpin

DIAdem Product Support Engineer

National Instruments

[Brad_Turpin · Accepted solution]

Hi Bilby,

R&D has identified a possible workaround you could try prior to DIAdem 2017 SP1 releasing.  Please contact me at the following email address if you're interested.

brad.turpin@ni.com

Brad Turpin

DIAdem Product Support Engineer

National Instruments

[usac]

 As mentioned by Brad this bug is fixed with DIAdem 2017 SP1

[Brad_Turpin]

Just to be clear, the DIAdem 2017 SP1 has been released.