Jump to content
ASalcedo

can .ini file be changed to "enable debugging" and then user can get my block diagram?

Recommended Posts

Hello to all.

I am deploying an executable (not installer) in a target PC with the same programs (labview and toolkits) installed than the development machine.

When I create executable I uncheck the option "enable debugging" (see image below):

Application%20Builder.PNGApplication%20Builder.PNG

** In the image "enable debugging" is checked but I uncheck in my application.

Then I am trying to debug in run time and of course I can not.

I do this to make me sure that the user can not get my block diagram.

But now I realized that in .ini file that Labview creates with executable there are these options:

DebugServerEnabled=False
DebugServerWaitOnLaunch=False

 

So if user writes "true" in these options, can they debug in real time and because of that get my block diagram?

 

Thanks a lot!

 

 

Edited by ASalcedo

Share this post


Link to post
Share on other sites
5 hours ago, ASalcedo said:

So if user writes "true" in these options, can they debug in real time and because of that get my block diagram?

No. If you do not check "Enable Debugging" in the build specification, and do not explicitly uncheck the "Remove Block Diagram" option for a VI within the build specification, then the block diagram is removed during the build process and cannot be recovered from the executable. Setting the INI file option might allow the user to connect with the debugger, but they will not actually be able to debug anything because the block diagrams aren't there.

  • Like 1

Share this post


Link to post
Share on other sites
16 hours ago, ned said:

No. If you do not check "Enable Debugging" in the build specification, and do not explicitly uncheck the "Remove Block Diagram" option for a VI within the build specification, then the block diagram is removed during the build process and cannot be recovered from the executable. Setting the INI file option might allow the user to connect with the debugger, but they will not actually be able to debug anything because the block diagrams aren't there.

Thanks a lot! I tried yesterday and you are right :) !

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Similar Content

    • By DARTHWOD
      Hi Friends,
      I am facing issue in labview programming. My vi read csv file in a folder and plot it in waveform graph. Initially i have twenty csv file in that folder, while runnning my vi some more csv files will be added to that folder. The problem is only twenty csv file initially placed got read, later added csv files were not read by labview. 
      Condition: Once my vi starts running, the files will be automatically added to that folder. Because i am running an experiment which stores data in the form of csv file to that folder. How to keep on read the csv files continuosly while my experiments stores series of csv files.

    • By Dawid
      I'm trying to execute LPR.exe command to print some labels on a printer. However as its normal, problems occur. I could not find answer on any topic conneced with "sytem exec". I already tried all described methods (I think so). That's why I'm asking very kindly for any help.
      When trying to execute or call the LPR.exe from System exec VI, I'm receiving error:
      "'C:\Windows\System32\lpr.exe' is not recognized as an internal or external command, operable program or batch file."
      Generally I would like to call function: "lpr -S 192.168.1.5 -P lp C:\test\do_druku.txt" which works from command window without any problem.
       

      print.vi

    • By daoudi
      Hi,

      Can I put a vi labview application on a web server on html 5 for exemple?

      if we can do that, it can be done just in local network(with several machines TCP/IP) or can be connected with a web server ?

      Thank you 
       
    • By John2787
      Reposting this here in an effort to gain some traction because it's absolutely killing me. 
      I'm trying to build a standalone .exe with a VI that contains a Scilab script using the Scilab gateway. On the actual program I created I get an error message stating that the front panel cannot be loaded on the SubVI that contains the Scilab script node. If I delete the node the program runs fine. 
      I decided to create a very basic VI containing a Scilab script to troubleshoot, and I get the following error: "This VI is not executable, The full development version of Labview is required to fix the errors". I don't understand this at all, since I do have the full development version of labview. Also, the code runs fine as a native VI, and this error is occuring on my development machine, so all required files should already be in the correct locations. Additionally, I've added "ScriptScilab.dll" as an always included source file and it's in the correct folder for the runtime engine. In fact, I've tried it in multiple different locations (app data directory, app root directory, LV2017 root directory, etc...) and still nothing. 
      What am I missing here? .Zip of may sample application attached. 
      My Application.zip
    • By ensegre
      I wonder if someone ran into this and has a good suggestion about. I have a DSC project, in which it looks just right to organize hierarchically my shared variables. Like, e.g.

      Now this is easy to do programmatically, see the attached project. The problem arises when building an application. It would look as if the plain way to do it, would be to create a build specification which includes the additional libraries, and select their deployment in the "Shared Variable Deployment" tab. However, this doesn't seem to work for nested libraries as in my example. The only possibility seems to add in "Always included" each of the contained libraries. But by doing like this the hierarchy is flattened.
      If I include like this,

      then the variables within the container library are not deployed at runtime.
      In my example project:
      open the project in the IDE, run DeployAllSharedVariables.vi, then CheckDeployed, and see the result (all four variables found with their nested paths) build and run DeployFlatLibraries and see the result: four variables, but flattened paths build and run DeployHierarchicalLibraries: only the two variables in the unnested SimpleVariableLibrary are there. I've searched a bit, and only came up with this document, which (for >2009) says "just check the checkbox". Nor the help page says much either.
      I wonder if I can do what I'd like only compiling separately the libraries, and loading them programmatically afterwards, both in the IDE and in the exe. Which probably is sane, but inconvenient for the first attempts.
      TestDeploy.zip
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.