Jump to content

Search the Community

Showing results for tags 'executable'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Software & Hardware Discussions
    • LabVIEW Community Edition
    • LabVIEW General
    • LabVIEW (By Category)
    • Hardware
  • Resources
    • LabVIEW Getting Started
    • GCentral
    • Code Repository (Certified)
    • LAVA Code on LabVIEW Tools Network
    • Code In-Development
    • OpenG
  • Community
    • LAVA Lounge
    • LabVIEW Feedback for NI
    • LabVIEW Ecosystem
  • LAVA Site Related
    • Site Feedback & Support
    • Wiki Help

Categories

  • *Uncertified*
  • LabVIEW Tools Network Certified
  • LabVIEW API
    • VI Scripting
    • JKI Right-Click Framework Plugins
    • Quick Drop Plugins
    • XNodes
  • General
  • User Interface
    • X-Controls
  • LabVIEW IDE
    • Custom Probes
  • LabVIEW OOP
  • Database & File IO
  • Machine Vision & Imaging
  • Remote Control, Monitoring and the Internet
  • Hardware

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Personal Website


Company Website


Twitter Name


LinkedIn Profile


Facebook Page


Location


Interests

Found 18 results

  1. Hello all, I am looking for a way to find controls on an executable LV program. I need this function because I want to automate a series of tests (user mouse clicks for example) on an executable LV program. The normal tools who does it with windows objects are not able to recognize LV controls individually. My idea is to find a way to recognize LV controls so I can interact with them individually. If anyone knows any third party programs to do automation tests for a LV exe that would also be highly appreciated. Best Regards, Vlad
  2. 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
  3. 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 t
  4. So, according to this NI document http://zone.ni.com/reference/en-XX/help/371361L-01/lvhowto/linking_vis_to_help_files/ It should be possible to link a .chm file into your executable so that a user can choose Help > Help for This VI. Well, I followed the advice, and no dice. Here is my LV2017-64bit attempt. In the development environment, it works fine, but in the executable Help for This VI is grayed out. The .chm file is a poor excuse, and unrelated to this VI, but never mind that, it's not the problem here. LV17helpEx.chm html_help_VI.vi test_help_html.aliases test_
  5. Bonjour, I use Labview 2015 32-bit on a 64-bit Win& pro computer. My application connects to Hardware using NI-VISA and NI-DAQmx only (Two RS232 communications via a VCOM port and one NI DIO card using DAQmx). Until today, I was building an executable which I was copying through the network on another win7 pro machine in the lab next to the hardware. It was working fine with Labview Runtime 2015 installed on this machine along with NI-VISA and NI-DAQmx. I never used an installer, I installed those 3 components seperatly. Yesterday I added some features to the applicati
  6. Hi, I would like to associate icons with file types that are handled by a LabVIEW built application. To do so, "defaultIcon" key has to take a value of executable path with parameter "resource ID". The question is how to build in more than one icon with executable? Examples of LabVIEW keys: -library: ..\LabVIEW.exe,-8 -llb: ..\LabVIEW.exe,-3 Is it even possible with app builder? Any workaround?
  7. Hello to all. First I explain my environment and then I will ask the question. PC 1 (development PC): intel i5, windows10 64bits, 8GB Ram, Labview 2015 SP1 (32 bits), Vision Adquisition Software 2015, Module Vision 2015, DSC 2015, ni OPC Server. PC 2 (deployment PC) : intel celeron 1.99 GHz, windows 7 64bits 8GB Ram, Labview 2015 SP1 (32 bits), VIsion Adquisition Software 2015, Module Vision 2015, DSC 2015, ni OPC Server, Run Time Engine 2015, VIsion Run Time 2015. PC 3 (deployment PC) intel Atom CPU N2600 1.40GHz, windows 7 64bits, 4GB Ram, Labview 2015 SP1 (32 bits), VIsi
  8. 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): ** 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: Debug
  9. I use SVN for version control in my project and am often faced with many conflicted VIs that must be dealt with. I have found that frequently, the changes causing these conflicts are not "real" changes (for example, a wire was moved or a typedef for a cluster control was changed). So, I am trying to create a tool that queries my project directory for any VIs that have conflicts, and running the VI Comparison tool with only non-cosmetic changes enabled to automatically find VIs that don't have any "real" changes and marked the conflicts as resolved. I would like to build the tool into a .exe be
  10. Hi all, Have you see these Windows PCs on sticks?? http://www.amazon.com/gp/product/B00RVCGNEC/sr=8-1/qid=1422529141/ref=olp_product_details?ie=UTF8&me=&qid=1422529141&sr=8-1 http://liliputing.com/2015/01/intel-compute-stick-149-pc-stick.html I would love to know if anyone has tried running Labview Executables on them and if they have ran into success or trouble? Of high interest to me would be serial communications using serial adaptors. Im still not sure if this is possible with this class of PCs. cheers Puya
  11. Hi, I have some applications (executables) made by several VIs and when they start, users see "loading in progress" window which displays VI's names. This is a typical behavior of LabVIEW, that other languages don't have. Is there a setting to hide/disable that window? Thanks, Claudio
  12. Hypothetically, if one created a LabVIEW executable that used a remote application reference to interact with the LabVIEW IDE, how much of the scripting function set would work? I've already discovered "New VI" doesn't work, but what about the non-creative functions, such as programmatically showing a block diagram, traversing the block diagram, inspecting nodes and other objects etc.? It seems to me that it should be ok to perform inspection, just not manufacture, right? So why are a load (if not all) of the scripting methods denied when attempted from a remote interface?
  13. This topic has come up a few times, mainly http://lavag.org/topic/13990-1502-error/?hl=1502 and http://lavag.org/topic/12461-strange-error-in-application-generating/?hl=1502. I just got hit with this issue today and will post what I found in case it will help somebody else. I recently upgraded to LV2013, and converted a large project I'm working on. Upon attempting to compile the executable, I was hit with the 1502 error with a particular VI. This had not ever happened with 2012, and the offending VI had no errors and ran fine in the development environment. Like others had reported, enabl
  14. Have a look to this brand new toolkit for LabVIEW if you are interested to distribute LabVIEW executable with advanced licensing, automatic update capabilities and a lot more amazing features. BLT for LabVIEW (Building, Licensing and Tracking) http://sine.ni.com/nips/cds/view/p/lang/en/nid/211731 BLT for LabVIEW is a stand-alone program you can use to distribute LabVIEW applications for commercial use in a few clicks. License your own LabVIEW application in a few clicks - no coding required Automatically (and remotely) update your applications when you make changes in your LabVIEW co
  15. Hi All, This is my first post on LAVA, so here it goes: I am creating an application that involves reading data on two RS-422 serial ports. Everything was going just dandy until it was time to build my application into an executable. I've spent time debugging my issue and have been able to narror down where the source of the error is coming from, but I can't figure out why it's happening or how to fixt it. I created a simple VI that clearly demonstrates the error. The VI first configures two serial ports using VISA. It then gets the number of bytes at the port and reads from VISA
  16. I try to build an executable out of a program that is fully functional under the development environment (LabVIEW 2011, Linux). The executable complains that one of asynchronously launched VIs is bad because one of its components cannot be found. The VI does not invoke any sub-VI dynamically. To identify the problematic sub-VI, I use the following code: A new executable was build including this code and the VI under investigation. A run results in the following error: Possible reason(s): LabVIEW: File not found. The file might have been moved or deleted, or the file path might be incorr
  17. Shortly: We desperately need a good hint on principles describing how an Application (EXE) build interacts with Source Distribution build(s). Descriptions found in ni.com and generally in Internet mostly advise “use Source Distribution” not saying “why”. It works perfectly with simple test projects but is not sufficient for our real needs. Please advice where the general principles can be read. Details: There is a framework code (GOOP4 that means that all problems should be the same with build-in LVOOP). The framework dynamically invokes VIs. The dynamically invoked code also has OOP architec
  18. Anyone seen this before? Please explain what is in the red circle. Im having a problem: webserver can not start after running my exe After many builds I found that It is come down to one little vi that i used: Inverse matrix as shown in the attachments. If i open this vi for the first time it shows: localhost as shown then i close it, reopen the vi again and it is now changed to: my project/My Computer as shown I dont understand, can you explain? This is the main cause of the error that i have as attached. (i know this because if i remove this vi, my exe runs fine!)
×
×
  • Create New...

Important Information

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