LabVIEW.ex​e - applicatio​n error

Hi.
I'm trying to use CIN to up-down flip a two dimensional array passed from LabVIEW.  Everything seems to work fine when I run the .vi (flipper.vi).  However, when I run another .vi (save_data.vi) that uses the flipper subroutine, it crashes LabVIEW.
Specifically, I recieve a LabVIEW.exe - Application Error:
The instruction at x-location referenced memory at y-location. The memory could not be "read".
Now I understand that somewhere along the lines LabVIEW accesses corrupt memory, due to a lack of array initialization or something. Unfortunately, that's about all I understand.
I'm using LabVIEW 8.0. Here is my flipper CIN code:
/* CIN source file */
#include <extcode.h>
/* stubs for advanced CIN functions */
UseDefaultCINInit
UseDefaultCINDispose
UseDefaultCINAbort
UseDefaultCINLoad
UseDefaultCINUnload
UseDefaultCINSave
/* Typedefs */
typedef struct {
    int32 dimSizes[2];
    int16 Numeric[1];
    } TD1;
typedef TD1 **TD1Hdl;
extern "C"{
MgErr CINRun(TD1Hdl dataIn, TD1Hdl dataOut);
MgErr CINRun(TD1Hdl dataIn, TD1Hdl dataOut)
        int32 rowSize = (**dataIn).dimSizes[0]; // number of rows of data
        int32 colSize = (**dataIn).dimSizes[1];    // number of columns of data
        (**dataOut).dimSizes[0] = rowSize;
        (**dataOut).dimSizes[1] = colSize;
        // up-down flip of data
        int32 i, j, arrayIndex;
        for(i = 0; i < rowSize; i++)
            for(j = 0; j < colSize; j++)
                arrayIndex = colSize*i + j;
                (**dataOut).Numeric[arrayIndex] = (**dataIn).Numeric[arrayIndex];
    return noErr;
Let me know if you have any ideas on how to possibly initialize the data that I'm passing into the CIN.
Hopefully this makes some sense. Thanks,

Hi, mrod,
The destination array should be resized before writing values with NumericArrayResize function:
The code above should work without troubles (hopefully).
best regards,
Andrey.

Similar Messages

  • I get an labview.ex​e applicatio​n error when i use the driver of 4395A spectrum analyzer

    i have the message:unhandled exception in labview.exe(HP4395A_32.dll):0xc00000005:access violation.
    could you help me?

    This error can be caused by many things. The first step in getting an instrument driver to function is the "Getting Started.VI"
    Be sure the GPIB controller can establish communication to the device. Also, capturing with NI-Spy will help isolate any VISA errors.
    Randy Solomonson
    Application Engineer
    National Instruments

  • Can not open 7.1 program in labview 8.5.1 -- handler error

    I made a program in labview 7.1
    And I wanted to open it in labview 8.5.1, but it opens with errors, and I can not run it.
    In every sub vi, till the lowest level, I got the error "handler error".
    Can somebody help me? 

    Hi Sven,
    Due to data dependencies within the *.LLB your 8.5.1 version of your vi was still opening the 7.1-version of the 'General error handler.vi'. Because these two version are no longer identical, LabVIEW concluded that the wiring you made was no longer correct.
    Replacing the 'General error handler.vi' under the data dependencies with the one at: C:\Program Files\National Instruments\LabVIEW xxxx\vi.lib\Utility\error.llb
    should resolve the problem as we discussed on the phone.
    Kind Regards,
    Wouter
    NI Applications Engineering
    Northern Region

  • I am trying to make a Shell call to Firefox in the C:\Program Files (x86)\Mozilla FireFox\ directory and LabView shell call gives an error.

    I am trying to make a Shell call to Firefox in the C:\Program Files (x86)\Mozilla FireFox\ directory and LabView shell call gives an errors. I can go to the DOS shell and make the call fine, but Labview Shell gives several errors. Anyone know how to get around the directory issue with Program Files (x86) directory name having the space in it and the (x86) that DOS does not seem to like?
    Solved!
    Go to Solution.

    You need to use quotes.

  • LabVIEW FPGA: An internal software error in the LabVIEW FPGA Module has occurred

    Hi,
    I am trying to build a LabView FPGA VI. During compilation, I always get error stating "LabVIEW FPGA:  An internal software error in the LabVIEW FPGA Module has occurred.  Please contact National Instruments technical support at ni.com/support".  At the time, comiplation process is almost at the end.  "Final Timing (place and route)" shows as completed. When Checked the Xilinx log session, at the end it states that "  Process "Generate Programming File" completed successfully". However, I do not see any generated bitfile.
    When clicked on error details, it shows following: 
    LabVIEW: An unknown error occurred.
    Error -2629 occurred at Error occurred while loading XML string. Invoke Node in niFpgaXml_PrettyPrint.vi->niFpgaWriteBitfileXml_Core.vi->niFpgaCompileWorker_CreateBitfile.vi->niFpgaCompileWorker_JobComplete.vi->niFpgaCompile_Worker.vi:6460001
    Possible reason(s):
    LabVIEW: An unknown error occurred.
    I tried multiple times but so far no luck to generate bitfile for this VI.  What could be wrong here?
    I am using Labview 2013

    Hi Mark,
    Here is the device utilization Summary. My development system is running with Windows-7 (32 bit) with 3GB RAM and Labview 2013. 
    Device Utilization
    Total Slices: 90.0% (11970 out of 13300)
    Slice Registers: 40.7% (43258 out of 106400)
    Slice LUTs: 71.6% (38103 out of 53200)
    DSP48s: 1.4% (3 out of 220)
    Block RAMs: 22.1% (31 out of 140)
    Timing
    40 MHz Onboard Clock
    : 40.00 MHz (57.90 MHz maximum)
    80MHz (Used by non-diagram components)
    : 80.00 MHz (100.19 MHz maximum)
    --WillsG

  • A full development version of labview required to fix the errors.

    When i tried to run my exe file, it gives following error.
    "A subvi is not executeable.A full development version of labview required to fix the errors."
    i do have full version of 6.02.
    Am i missing something something when i built exe?
    any Help will be appreciated.

    Well, here we go again...
    I have seen this error way too many times in my day.
    The problem is you have a bad linkage, or unsaved or compiled VI in your hierarchy when you built the application.
    Open your main, or otherwise open (into memory) ALL VIs in your hierarchy. Then, do a save all from the file menu. This should solve the issue.
    The other reason I have seen this is if you have bad linkage. As there is no real way to tell what your linkage is, you need to go into the hierarchy, select View Full Path in Title and make sure everything is where you think it is. I have often seen this occur even when the application I was building from was in perfect condition. Often times, when the app builder is used, VIs will be called from locations you
    don't expect.
    You have to be VERY careful about developing in a hierarchy. I actually got to a point where I had to even place all the NI VIs into my directory structure.
    Take a careful look at the hierarchy. Chances are the executable is calling the wrong code, or is compiling with the wrong version.
    If in doubt, go to a fresh machine, and move all of your VIs (individually if you have to, or as a .llb preferably) to the new machine and build it from there. Alternatively, you can try doing a save as from your main and select "application distribution" this will resolve any issue with VI locations, except where Dynamic VIs are being used.
    Good luck, 'cause you are going to need it.

  • Please help suggestions for solving built-only compiler error: 'The VI is not executable. The full development version of LabView is required tofix this error.'

    We have develoepd a software tool and build it on regular basis. It currently runs error free when compiled in the editor, but when we built it and run the executable stand alone we get the error.
    'The VI is not executable. The full development version of LabView is required tofix this error.' plus a broeken error.
    This menas an compiler error that is not present in the editor but in the stand alone version. We tried to identify errors as suggested in several posts in this forum, but so far unsuccesfull.
    As the editor and its compiler do not see the error  and are running fine and the stand alone version just syas 'find the error in the editor' in this case LabView is of no help.
    Can anyone suggest a sensible or 'good practice ' way of searching for the source of this error?
    Our project  comprises hundreds of Vis over several libraries.
    Thanks,
    Chris

    Thanks Craig for all your suggestions.
    We seem to have located the problem in a new vi just added to the package causing conflicts by using the same vi names as other vis already present in the package. Excluding this vi removed the error.
    It seems related to a conflict by having two vis with the same name, which was mentioned by LabView and interactively resolved when running the main vi from the editor. When successfully building the main vi the builder did not mention this conflict and reported a successful build, but when trying to run the executable it gave the cryptic error. The error caused us problems because there was no hint for the cause, just the suggestion to solve this in the editor, while at the same time in the editor the VI was running fine.
    We will post about this in detail after we have positively proven that this actually was the case.
    The .net version issue was already checked.
    Performance was the same on all machines we tested on including the dev machine.
    Debugging was tried nut did not help as the vi could not run (broken arrow). We assumed that debugging only helps in running faulty functioning vi''s. We did not check for broken arrows in sub-vis (after connecting), that could have helped, although our application has hundreds of our own vis.
    In relation to your remark: 
    'Are you using many classes? Have you verified that the proper access scopes are set for functions calling those vis?'
    Could you elaborate on setting access scopes. We were not aware of this option in LabView, although we realize this is a basic element of the underlying c code.
    Ragrds,
    Chris

  • Como hacer que labview envie un mensaje de error si no se cumple una condicion

    como hacer que labview envie un mensaje de error si no se cumple una determinada condicion

    Hola,
    Aquí anexo un VI de ejemplo en el cual, cuando se cumple cierta condición booleana (que el valor de un control numérico sea mayor a 3) se genera un error personalizado. Puedes correr el programa e ir aumentando el control hasta que aparezca el error.
    Hay una forma de añadir códigos de error personalizados de manera permanente a LabVIEW. Los códigos 5000 al 9999 están reservados para errores personalizados de usuario. Estos se pueden crear en LabVIEW en el menú de Tools >> Advanced >> Edit Error Codes...  Los códigos de error con sus descripciones personalizadas se quedarán guardados en el archivo :   C:\Program Files\National Instruments\LabVIEW X\user.lib\errors\-errors.txt
    Asi ya guardado puedes utilizar simplemente el VI de Simple Error Handler en lugar del General Error Handler, y no tienes que definir cada vez el código de error y la descripción.
    Espero que esta información te sea útil. Que tengas muy buen día.
    Pablo Bernal | NI México
    Adjuntos:
    Custom error.vi ‏16 KB

  • I get a nimax.exe- Applicatio​n Error every time I start labview

    every time I start a vi either by double clicking or by opening labview first I get an application error... "the instruction at "0x1ca12b96" referenced at "0x00000000", The memory could not be "read", click ok to terminate the program". when I click ok the program does not terminate and as long as I don't close labview completely I can close it and reopen the vi. I am unsure if the program malfuncions after that point but it is certainly an annoyance. Have you seen this problem before? Is there something that I should do to the vi to correct the problem? Thanks,
    David Long
    K.H. Controls

    I talked to NI about this issue, and tried the following WITH success (note that I am running W2k and Labview 6.0.2):
    1. Uninstall all NI components in the reverse order you installed them. For me, this was Ni-Daq, Ni-488.2, and finally Labview 6.0. If you have to, look at the modified or created dates of the folders to see what order you did it in.
    2. After this, I decided to go a bit further and delete the registry key for Ni-Daq under HKEY_LOCAL_MACHINE\SOFTWARE\National Instruments\NI-DAQ. Make sure you Export your registry key beforehand in case something goes wrong.
    3. Install Labview 6.0, custom installation. For this installation, DO NOT INSTALL the drivers, just Labview.
    4. After that, I installed the upgrade patch for Labview 6i -> 6.0.2, downloaded at ni.com.
    5. Next I downloaded the 2 files for NI-DAQ 6.9.3, uncompressed the files, and ran the setup. When the installation was done, I chose to not reboot now, but let me do it later. At one of these points, you can also Mass compile the VI's. I don't think it's necessary at this point, but I did it anyway.
    6. Finally, I downloaded NI-488.2 version 2.2 (which has a new version of MAX than NI-DAQ 6.9.3), uncompressed it and installed it.
    7. After this last step, I rebooted the computer and was able to finally get into MAX to configure my DAQ card.
    So far, this method has worked. Perhaps it can work for you.

  • LabVIEW 7.1 reports an applicatio​n error 'instructi​on adresses memory at 0x00000000 - ... could not be written' when finishing LabVIEW, even when not running any private code

    Hi there,
    I have found similar Qs here, but this one is _somehow_ different.
    My quite large app (>600 VIs) uses some DLL calls to communicate with medical devices. It runs OK, AFAIK, even when started several times. BUT I get an error message each time I when finishing LabVIEW 7.1 (even when just having loaded the app!!!). The error message states that "The instruction at 0x778cca36 adresses memory at 0x00000000. The process 'written' could not be done on that memory. Click to close the app".
    Any clues?
    My system: Athlon64 3000+ with 1GB of RAM running W2k German with all availabel SPs, LabVIEW 7.1 English with all support files from the devellopr suite May05 edition. System was set up 2 days ago on a fresh PC. The old system showed the very same behavior.
    My opinion is, that simply loading an app and than removing it should not cause such an error??!!
    Greetings from Germany!
    Uwe
    Attachments:
    Application_Error_LabVIEW_when_finishing.jpg ‏20 KB

    I can't look at your code because I don't have LV 7.1, but I would recommend searching on the side of the DLL.
    Do you have the source for the DLL? Can you be sure that the DLL doesn't somehow have a memory addressing bug? The DLL will be loadsd as soon as the program is loaded AFAIK, so maybe when unloading the DLL an error occurs because something isn't initialised properly. I've never programmed a DLL, so I may be way wrong, but my instinct tells me that the problem will most likely be with the DLL.
    Hope this helps
    Shane.
    Using LV 6.1 and 8.2.1 on W2k (SP4) and WXP (SP2)

  • More than 1 ms MOMO digital IO 7358 in LabView Real-Time 8.5, error downloading EPOS dll file into RT

    Hi all,
    I have several problems here, I tried to google but still I could not solve the problem.
    Here are my questions:
    1. I tried to download an example program of EPOS which require to download a DLL file into the RT, but it failed, here's the error (I attached the picture) 01/02/2008 13:29:50.511 [error] LabVIEW:
    Failed to load shared library EposCmd.dll:_VCS_GetProtocolStackName@16:C on RT target device.
    From the NI.com forum,
    I found a similar problem and it said by installing Network Variable Engine and Variable Client Support into the LV-RT, and I did, but still failed. Any one can help me about this?
    2. I posted a question also in lavag, I think this section is more appropriate. "I
    am trying to use the digital IO of the motion controller of 7358, but then I realized the delay is more that 1 ms (I checked using the oscilloscope), I attached the code (MOMO = Must On Must Off). Is this real, I mean the hardware delay between on-off is as big as this? Anyone knows the solution for this?"
    Note: I am using LV-RT 8.5, PXI-7358 Motion Controller, EPOS 70/10
    Thank you for any help
    Message Edited by bono02 on 01-02-2008 05:47 AM
    Attachments:
    maxon-rt3.JPG ‏120 KB
    momo1.JPG ‏55 KB

    Hello bono,
    1.  From what I have seen, this error is usually caused by one of two things.  The first is the Shared Variable software components not being installed, which is covered in this Knowledgebase.  The other is due to a corruption of the ni-rt.ini file on the Real-Time controller.  You can follow the steps layed out in this Knowledgebase, which gives three possible remedies.  You could also try reinstalling the software (firmware) or create a PXI Uninstall disk from Measurement & Automation Explorer by selecting Tools»Remote Systems»RT PXI Disk Utilities»Create PXI Uninstall Disk.  Boot the PXI Controller from the PXI Uninstall Disk, which will erase the ni-rt.ini and ph_exec.exe on the target.  However, you will need to reconfigure the controller after doing this.
    2.  Due to the nature of the digital I/O on motion controllers, it is not surprising that you are seeing around a 1ms delay.  It deals with the fact that it must update the motion controller with the new value on each control loop.  This Knowledgebase gives a little more clarification regarding the 7350 specs.
    Carlton
    CLD

  • Problems with Labview and Windows XP with error -214721786​5

    Hello. Im a new beginner in Labview and am having a problem with a error message
    I dont understand. Im running Labview on a pc-logger with windows XP.
    The program is written by a guy on my university, and logs voltage from
    a solar cell panel. He doesnt have the time to check in to it, so Im supposed to
    find out what's wrong.
    The error message is as follows :
    Error -2147217865 occured at Cmd Execute.vi->DB Tools Insert
    Data.vi->Solcelle.vi
    Possible reasons :
    Exception occured in Microsoft OLE DB Provider for ODBC Drivers,
    [MySQL][ODBC 3.51 Driver][mysqld-3.23.38-log]Can't open file :
    'solcelledata.MYD'. (errno: 145). in Rec Create - Command.vi-
    >Cmd Execute.vi->DB Tools Insert Data.vi->Solcelle.vi
    I really hope someone can tell me what's wrong and specifically what to do
    with it, or possibly guide me to someone who could suggest a solution to this
    problem.
    Reguards
    chrisdee

    Hi Chrisdee,
          (.. not to discount what TimoS has suggested, however...) 
    Embedded in the error information you provided:
    ... Can't open file : 'solcelledata.MYD'.
    Sounds like the program needs this file?  Has the program been moved to a new location?
    just a wild guess!
    Cheers
    Message Edited by Dynamik on 10-06-2005 04:53 AM
    When they give imbeciles handicap-parking, I won't have so far to walk!

  • Labview 8.0.1 installer error

    hello all,
    I am having an issue with building an installer package in labview 8.0.1.  I can build an executable every time, but when i try to build an installer I get the error message in the attatched txt file (its to lengthy to paste here) .  this error happens no matter what switch settings i use in properties, including with and without run-time engine.  I have tried reloading the 8.0.1 upgrade and the same results.  For a variety of reasons I can not goto 8.2 right now to try that...
    Any and all suggestions will be appreciated
    thanks
    Chris 
    Attachments:
    Document.rtf ‏128 KB

    Hi Chris,
    Have you tried building a new installer from scratch with new VIs?  Furthermore have you tried to build the installer from another computer? 
    Regards,
    Nadim
    Applications Engineering
    National Instruments

  • LabView Crashing and compile server error.

    Hi,
    I'm having some errors when I compile code for my FPGA (PXI-7831R). I am using LabView 8.2.1.
    Sometimes labView crashes completely and sometimes it comes up with a compile server error.
    My code contains 3 VI's. The first send sends digital output and reads digital input 10 times and then called another VI to save these results. The second VI repeats the first VI 10 times.
    When the first VI is compiled on its own it works (including the saving data VI which saves it to a FIFO) but when the second VI is compiled, that is when it errors.
    I have attached the compile server errors and the screen dumps of when labView crashes.
    Can anyone suggest what I am doing wrong?
    Thanks.

      ok. Let me try and make my problem a little clearer....
    I have now combined all the VI's into one.
    It is supposed to write to the digital output and read from the digital outputs 10times at a rate of 10us and store the data to the FIFO. This process is then repeated at a rate of 80ms for 8 times.
    I have attached a word document with an explanation on the error. 
    Attachments:
    lvlog07-26-07-12-04-50.txt ‏3 KB
    Problem Explaination.doc ‏61 KB
    f623_appcompat.txt ‏93 KB

  • I am using datasocket in seperate vi, with error catching, but network slowdown causes labview to crash without any error message ...

    I have a master computer setup as a datasocket server with several vi's that publish. I have about 5 other computers each with a vi that reads the data socket publisher. The interval at which the 5 vi's read is every 15 minutes, concurrently. It seems that when ever there is a network slow down, LabVIEW crashes catastrophically, even though I have timeouts in the datasocket readers. Is this error related to the datasockets not being able to handle the slow down or something else? Should I use another technique - if so - which is more reliable (FTP, TCP/IP?). This bug has been hounding me for several MONTHS.

    One thing I forgot to mention - the 5 datasocket readers are also web servers, serving out the front panels to the web after getting updated. Well, after weeks of trial and error, would you believe that if I turn off the web server logging, everything works fine. I have had it off for a week now and no crashes. I first discovered this by realizing that if I turned off the web server everything ran fine (which would be totally useless for my application), so then I searched this site and found an off the cuff remark about the web server logging function causing crashes for an unrelated problem. I figured what the heck, I'll disable it and see what happens. So far so good, I am still keeping my fingers crossed ...

Maybe you are looking for

  • Startworkflow : method not implemented error

    Hi, I am using the following code to run a stored procedure. But every time the stored procedure is called, I get a message that the Startworkflow method is not implemented. But still the procedure is called and everything works fine. Can you please

  • Unable to use the stars in My Rating in Smart Playlist

    For the last few weeks, I am unable to see or select the stars when I pick "my rating" as a criteria in smart playlists. My older playlists that used this criteria work well, but when I enter one of them toedit it, I don't see the starts eitther. I a

  • I have lost the sound to my ipad. How do i get it back?

    I have lost my sound. I tried to get it back in the settings app but I was not successful. Has anyone had a similar experience? If so can you help me to get my sound back?

  • Accessing Oracle DB at multiple location(long distance)

    Hi guys, I have a situation where i need to connect to oracle database which are at long distance(say singapore and UAE). Structure of database is same. Which is the better way to implement. 1. Using seperate connection for database Connection conSin

  • Iphone4S email attachment and jpeg problem - Cant open

    Hello, I hope someone can help me as I'm a bit rubbish and the problem is driving me nuts!  I've tried searching the support forums but I can't find an answer. For some reason, I'm unable to open email attachments or RTF files and even Jpegs that are