06-13-2018 11:50 AM
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.
06-13-2018 01:12 PM
DDE should still work. Just copy the DDE.llb from the old version and paste into the new LabVIEW folder.
06-13-2018 01:21 PM - edited 06-13-2018 01:33 PM
Thanks for the idea, I had already tried that, but the VIs in this DLL are not supported by labview 2017.
06-13-2018 01:35 PM
> 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.
06-13-2018 01:38 PM
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.
06-13-2018 01:51 PM
> 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.
06-14-2018 03:29 AM
Here is what i get with the problematic VI.
Thanks for helping me ^^
06-14-2018 03:47 AM
06-14-2018 03:56 AM - edited 06-14-2018 03:57 AM
64bits
Thanks for helping.
06-14-2018 04:04 AM - edited 06-14-2018 04:05 AM
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…