LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

activeX example can't find objects

Solved!
Go to solution

I'm trying to make a 4d intensity plot and unfortunately the examples appear to be non-functional.

Part of the process involves adding a Wvector for amplitude control across a 3d plot, and the Labview example "Plotting X, Y, and Z Data on an ActiveX 3D Surface Graph" can't find the necessary objects to work.

Screenshot attached, Labview Professional development system 2015 service pack 1. The internal help file can't find the necessary object.

 

Thanks for help on this issue.

 

David Schriebman

Ultraviewcorp.com

0 Kudos
Message 1 of 4
(247 Views)

Hi David,

 

the message box tells some possible reasons: does one apply to your case?

 

Anyway: we cannot debug images of parts of a frontpanel with LabVIEW. Please attach your VI!

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 2 of 4
(201 Views)
Solution
Accepted by topic author DavidUltraview

Your LabVIEW version seems to be 64-bit (white background of the LabVIEW icon). Those ActiveX controls are almost pre-historic from like millennium change or even a little before and were 32-bit only. While it is principally possible to invoke ActiveX components out of process through a proxy server so that calling of 32-bit ActiveX components from a 64-bit process is possible there are a number of difficulties with it.

1) The component has to be programmed to support out of process invocation. Considering when the 3D plot component was developed this might never have been a design criteria and most likely never has been tested in any way.

2) Given that 1) is true, the component needs to be registered to be callable from 64-bit processes. That for sure won't happen for this component as when it was designed, 64-bit Windows was not even a pipe dream.

 

ActiveX was at the time 64-bit Windows got fashionable and common (Windows 7 was the first Windows version that got really installed as 64-bit version in more than very specific incidental cases) already long a legacy technology and the 3D Graph based on ActiveX was the same. There was no incentive to spend even one single hour in making such a legacy technology work at that point. Microsoft had already for years tried to downplay and marginalize ActiveX at that point in favor of .Net. 

Rolf Kalbermatter
My Blog
Message 3 of 4
(193 Views)

Thank you very much Rolf, 32 bit vs 64 bit does make sense for this and the examples I was trying to work from were indeed quite old.

0 Kudos
Message 4 of 4
(176 Views)