07-25-2017 06:57 AM
I need to have access to program. Bellow i leave a screenshots
Solved! Go to Solution.
07-25-2017 07:06 AM - edited 07-25-2017 07:07 AM
Suggestions:
Bob Schor
07-25-2017 08:18 AM - edited 07-25-2017 08:21 AM
I did not coded the program which i want get premission. This program is an .exe created in labview. Some VI's inner this program i know, but not all. I need know names all of them.
U haven't given any solution.
The question is, how to get full premission to memory of this program.
07-25-2017 08:45 AM
Untitled 2.vi it is a VI which have to have acces.
action is an exe with included VI inner. Tell me, what is name of VI in this exe.
07-25-2017 10:59 AM
As far as I know, a compiled-to-EXE LabVIEW program does not give you "hooks" into its internal VIs (I'm happy to have some wiser heads point out that I'm wrong about this, by the way). The exception, of course, is if you build not an Application (EXE), but a Shared Library (DLL), which is designed to be callable by other independent code routines.
Bob Schor
07-25-2017 11:08 AM
Please define in a few more sentences what you mean by "access". Thanks.
07-27-2017 01:32 AM
The problem is solved.
"Bob_Schor " There is a "hooks" to VI. Every exec have got included inner all VIs which u sue to compile. There i'll write simple solution, how to haul out the VIs.
1. first step is set in ur exe or ini file the port to listening on ur system.
2. In LabView, use "Open Application Reference" (function block) and there are terminals to connect:
Machine name -> plug in 127.0.0.1 or just 'localhost'
Port number -> plug in port which one is setting to ur exe.
3. Output terminals are REF to ur app and optionaly Error wire.
4. Nex block what u need to use, is "Open VI Reference", There u have to plug in REF, name of ur VI what u want to haul out and optionaly error wire.
5. The output is a REFerence to ur VI. U can do with it waht u want.
Acces to all VIs inner exe is by property "Exported VIs in Memory" in "Property Node".
Good fun 😄
07-27-2017 07:33 AM
Thank you for proving me wrong! I'm glad to learn about "how to do things in LabVIEW that you thought were not possible". Please do all of us a favor and mark your previous Reply as the "Solution" (it is OK to give yourself credit!) -- it will help others with the same question find the answer more quickly.
Bob Schor
07-28-2017 03:40 PM - edited 07-28-2017 03:40 PM
Thank You 😄 ❤️