LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Commanding Opus with labview and ActiveX

Hi.

 

I'm trying to command Opus, a software for spectroscopy. With the old installation we were using DDE, but it seems that it doesn't work with newer versions of labview, and that ActiveX is what we're supposed to use now. So I tried that, using this old thread. But when I get to the Opus dll's, the list is said to be empty.

 

Has anyone have encountered this problem before and could help me ?

 

Thanks a lot.

0 Kudos
Message 1 of 12
(2,695 Views)

DDE should still work.  Just copy the DDE.llb from the old version and paste into the new LabVIEW folder.

 

George Zou
0 Kudos
Message 2 of 12
(2,675 Views)

Thanks for the idea, I had already tried that, but the VIs in this DLL are not supported by labview 2017.

0 Kudos
Message 3 of 12
(2,670 Views)

but the VIs in this DLL are not supported by labview 2017.

Could you give more information ?

 

DDE doesn't use DLL, it uses CIN.

I just tried open DDE master VI in LabVIEW 2017.  It's not broken.

 

George Zou
0 Kudos
Message 4 of 12
(2,663 Views)

I'm not at work so i can't show you right now, but the VI was using a kind of node that isn't supported by labview anymore. I can show it to you tomorrow morning.

0 Kudos
Message 5 of 12
(2,661 Views)

ut the VI was using a kind of node that isn't supported by labview anymore.

Yes.  DDE master uses CIN.  You can no longer find CIN on the function palette.

But it should be backward compatible. i.e. existing CIN should still works.

I used DDE last year in LabVIEW 2015.  Works OK.

CIN obsolete a few years before 2015.

 

George Zou
0 Kudos
Message 6 of 12
(2,658 Views)

Here is what i get with the problematic VI.

 

Thanks for helping me ^^

0 Kudos
Message 7 of 12
(2,640 Views)

Hi Hyouryu,

 

which LabVIEW version are you working with? 32bit or 64bit?

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 8 of 12
(2,636 Views)

64bits

 

Thanks for helping.

0 Kudos
Message 9 of 12
(2,633 Views)

Hi Hyo,

 

(with more than 99% probability) that CIN is made for a 32bit environment.

As the context help message in your image explaines: when calling the CIN for a new target system (like your 64bit environment!) you must supply a new code object for that environment.

 

Simple solution: use LabVIEW 32bit instead…

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 10 of 12
(2,628 Views)