Academic Company Events NI Developer Zone Support Solutions Products & Services Contact NI MyNI
This Document is not yet Rated  Rate this Document

VI Server Call Causes LabVIEW Embedded Application to Crash

Primary Software: LabVIEW Modules>>Embedded Development Module
Primary Software Version: 2.0
Primary Software Fixed Version: N/A
Secondary Software: N/A

Problem: Inside the LabVIEW Generic Error Handler VI there is an Open VI Server call. This VI Server call gets the name of the VI being called. My LabVIEW Embedded application seems to crash when I have the Generic Error Handler VI in it. Can I use the VI Server functionality in my LabVIEW Embedded application? How do I confirm that the VI Server is the cause of the application crashing?

Solution: When a LabVIEW Embedded application crashes, a possible reason could be a VI Server call. The VI Server functionality of getting the name of the VI being called is currently not supported in LabVIEW Embedded. In order to get your LabVIEW Embedded application to run correctly, you should remove these VI Server calls.

Take the following steps to confirm that the VI Server is the cause of the crash:
  1. Pass the following preprocessor definition to the compiler: DEBUG_LOG=2

    2. Note: The exact method for passing the preprocessor definition will depend on the specific embedded target.
  2. Rebuild your application and then run the executable. Watch for the following pattern towards the end of the output:

    3. Begin VI
    Alloc VI heap
    Run block diagram
  3. It is important that the VI has not been run up until this point. Make sure that the line Initialize front panel terminals does not appear between "Alloc VI heap" and "Run block diagram" in the output.


Related Links:

Attachments:





Report Date: 09/18/2006
Last Updated: 10/04/2006
Document ID: 41685T00

Your Feedback! poor Poor  |  Excellent excellent   Yes No
 Document Quality? 
 Answered Your Question? 
  1 2 3 4 5
Please Contact NI for all product and support inquiries.submit