Hello, community
Since some years I'm using LabVIEW now (currently 2010). I'm working in the automation business branch and I see, that there are many HMI visualization softwares around. Nearly all of then support the inclusion of ActiveX plugins into the HMI surface. We are using LabVIEW, among other software, to control our machines. The HMI software we have to use is normally decided by our customers, so not always the same HMI software. Mostly we use Wonderware-InTouch or Siemens-WinCC. Using LabVIEW as HMI host system is not an option, as customers want to stick to their favorite tools and want to be able to manipulate the HMI by themselves.
We would like to replace certain parts of our HMI by LabVIEW-VIs.
This can currently be done by
-
Compiling the VIs we want to display as standalone programs with HTML server included.
-
Installing a runtime LV on the HMI-PC (Windows based)
-
Including a WindowsExplorer.ocx into the HMI project and displaying the VIs via Web connection.
This is very sub-optimal because it includes many superfluous things and induces a
more than necessary amount of problem-sources.
What I would like to be able to directly build an .ocx file out of our VIs and so include our VIs directly as AvtiveX objects into the HMI (instead of Windows Explorer as wrap around).
What do you thing about an application builder able to produce ".ocx" output?
Regards,
Ralf
Any idea that has received less than 4 kudos within 4 years after posting will be automatically declined.