Error code 30155002 Labview 7.1 PDA

Hello everyone,
    I had a problem with my PDA.
    I developped a little programe and stored my datas in an array. Then I showed these datas in a 'PDA XY Graph'. After about 2 hours of mesurement, my PDA had an error messager : "Application failed. Error code 30155002. Unable to allocate the memory..." at that moment, I have stored 1574 points in my array.
    I think that maybe the memery of PDA is limited. But I am not sure of that. So I would like to know what dose this error message mean?
And what exactely the tail of the memory of PDA.
     Thanks a lot for your answers!
     Sincerely!
     Zhang An

Hello Zhang An,
What is your OS ?
The considerations to take into account are different if you are working with Palm OS or Pocket PC:
Palm OS Considerations
The following considerations can affect the way you design a PDA VI for
Palm OS devices, emulators, and simulators.
• Palm OS is not multithreaded and has limited memory for programs.
• Palm OS does not use a traditional file system. It stores data in memory
chunks called records that are grouped into databases. Expansion cards
use a traditional file system.
• Palm OS implements all files as databases and can have a maximum of
64,000 records in each database. Each record can be a maximum of
64 KB in size.
• Each VI within a PDA VI cannot be larger than 64 KB because of the
way Palm OS links the applications together. However, a top-level
PDA VI can contain several subVIs whose total file size is greater than
64 KB.
The size of a PDA VI on the host computer is not an accurate indication
of how large it will be when you build it as a PDA application. When
you build a PDA VI into a PDA application, LabVIEW notifies you if
the file size is too large. Break up the VI into smaller subVIs to reduce
the file size.
• There is a total limit of 64 KB on all front panel array data.
• Applications are limited to approximately 160 KB of heap, or dynamic
memory space, for everything except code. The application uses some
of this space to maintain state, so not all of it is available for data.
PDAVIs immediately terminate if they run out of memory. You can
use the PDA Memory VIs to manage the dynamic memory space.
Pocket PC 2003 Considerations
PDA applications are limited to about 32 MB of space for everything
except code. The application uses some of this space to maintain state, so
not all of it is available for data. PDA applications immediately terminate
if they run out of memory.
hope this helps
Best Regards
Alexandre D
NIF

Similar Messages

  • An error occurred loading VI. LabView load error code 1: LabView load error code %ld: %p"

    I have been developing a VI file that has
    been working fine, until now. I am using 8.6.
    Every time I attempt to open this file
    I keep getting:
    How do I fix the error code:
    Labview: Memory is
    full.
    An error occurred loading VI. LabView load error code 1:
    LabView load error code %ld: %p”
    On a separate dialog:
    “Not enough memory to complete this
    operation.”
    I ran VI analyzer which told that the
    VI:
    One or more errors occurred during
    analysis.
    Testing errors tab – Vi not loadable
    and my file name. At the bottom in the error description I got:
    “Error 74. Memory or data structure
    corrupt. <my file path> and <file name>.”
    Could not be opened.
    Is there anything I can do to recover
    the file?

    Hi kevin_khan,
    I went ahead and tried to open it and got the error attached.
    Peter T
    Applications Engineer
    National Instruments
    Attachments:
    test.png ‏14 KB

  • LabVIEW load error code 1: LabVIEW load error code %Id: %p

    One of my VI crashed while trying to save some data to file, I then tried to save the VI afterwards, but message with Out of Memory popped up again and the IV closed down. So now I can´t open my VI, then I try I get the "LabVIEW load error code 1: LabVIEW load error code %Id: %p" message and I have been given no opportunity to recover an older version of the VI then I close down and open LabVIEW again!!! So my VI is lost or what?
    This is a huge problem for me, hope someone can help...
    Regards
    Jesper

    Hi Jesper
    For the future you should be good with LabVIEW 2012 (Normally realeased after NI Week in Austin in beginning of August). From what I know about this problem it have not been mentioned to be solved in a fixpack before release of LabVIEW 2012.
    If you are reading in large files that uses more memory than avaliable and do wan't to avoid LabVIEW from crashing then you could add more RAM to your PC. If you are using Windows 32-bit you could try to edit the boot.ini file for Windows to allow Windows to allocate more memory to LabVIEW as explained in the following article:
    Extending Virtual Memory Usage for 32-bit Windows
     http://zone.ni.com/reference/en-XX/help/371361H-01/lvhowto/enable_lrg_ad_aware/
    You could also try upgrading to Windows 64-bit this will allow much larger memory operations, and Windows 64-bit will let LabVIEW allocate more memory.
    To use Source Code Control on your computer you will need:
    1) A Source Code Control server with space to store the backup VI's and previous versions on (this can be your own PC). All Source Code Control providers that follow the Microsoft Source Code Control API. We have a list of tools that we have been tested that can be found here (note that some is free and other is not):
    Which Third-Party Source Control Providers Can I Use with LabVIEW 8.0 and later?
    http://digital.ni.com/public.nsf/websearch/26EC5904169430CE8625706E00743997?OpenDocument
    2) After installing the server you need to configure LabVIEW to communicate with this server. In the article below under the section "Configuring LabVIEW to Call the Microsoft SCC API" you can see how to do this:
    Software Configuration Management and LabVIEW
    http://zone.ni.com/devzone/cda/tut/p/id/4114
    3) You are good to go. Source Code Control uses the two most know functions "Commit / Check out." When you Check out a document you will be able to edit it, and when you then commit the changes then it will be saved with a new version number on the server. For each commit you will be able to select "Revert to previous version" to go back and restore a previous commited VI. You can use these functions on the VI it self or as I prefer from the Project Explorer.
    Bisides the advantage of being able  to restore previous versions, Source Code Control is also a great tool if your are multiple users working on the same project. You will i.e. be able to be 2 or more developers working on the same VI at the same time and then merging your changes to one VI when you are finished.
    Best Regards
    Anders Rohde
    Applications Engineer
    National Instruments Denmark 

  • Installer build error code-21 Labview 8.6.1

    While attempting to build an installer I get an error code -21. What is the error and how do I correct it?

    I also have this problem.  The executable build itself works correctly, but the installer fails to build.  There are a number of DLL dependencies, but they are all included and present in the build and in the installer Source Files.  I put CDK.EnableLog=True in my LabVIEW.ini and logged the error from the installer build process.  Here is an excerpt from the relevant section:
        [LOG ON]  Fri Apr 30 13:46:02 2010
    <<<MDFConfig_SetDeveloperLanguage>>> Language id: 9
    <<<MDFConfig_SetDistributionLanguage>>> Language id: 9
    <<<MDFConfig_SetBuildDir>>> Build directory: C:\MyPrograms\MyApp_Working\Install
    <<<MDFConfig_SetBuildMode>>> Build mode: 1
        [NMDK BEGIN]  Fri Apr 30 13:46:02 2010
         Building developer part
    > Adding files to installer
    <<<MDFBuildDevPart_SetFileNames>>>
    <<<MDFBuildDevPart_SetDefaultInstallDir>>>
    <<<MDFBuildDevPart_SetUpgradeInfo>>>
    <<<MDFBuildDevPart_SetOtherProperties>>>
    >  
    > **************
    > *** Error: An internal tool or library returned an error. (Error code -21)
    Error in MDF API function: _MDFBuildDevPart_SetOtherProperties
    nmdkSetInformationalProperties returned error code 26024
    > *** End Error Report
    > **************
    >  
    Adding product dependencies to developer part
    >  
    > **************
    > *** Error: Windows SDK function returned an error. (Error code -12)
    Closing dist kit
    ***** About to begin MAXImportConfig:oMAXPartModifications...
    No MAX import files specified - nothing to do - returning.
    Error in MDF API function: _MDFBuildDevPart_Close
    Error in MDF::BuildDeveloperPart::Close.
    ERROR: Caught MSI Exception:
    <Unable to format error record.>
    MSI error code: 6
    > *** End Error Report
    > **************
    >  
        [LOG OFF]  Fri Apr 30 13:46:02 2010
        [MDF END]  Fri Apr 30 13:46:02 2010
         Closing MDF.
     I've also tried the same with a simple test application and it build/installs correctly, so I know it is my project somehow.  One notable difference is that I previously had namespace conflicts in the executable build that were resolved by the following these instructions:
    http://digital.ni.com/public.nsf/allkb/47272B69E2C​167DB862574AC006A258B?OpenDocument
    I hope someone can help.  I need to deploy this application soon.
    Regards,
    - Ray

  • Error Code 0xC0000025 (labview 2014)

    Hello Everyone,
    My labview program is communicating with a function generator (Agilent 33521A) and a frequency counter (Agilent 53230A) using the standard device drivers available on NI's website. I have recently upgraded from 2012 version and my labview program is consistently crashing. I get the same error code each time but the crash is random. Moreover if I run the code for function generator separately it completes the required number of iterations. But crashes if both instruments are used simultaneously. I have attached the screen shots of  front panel/block diagram along with the VI.
    I will be grateful if anyone can help me.
    Hamza
    Solved!
    Go to Solution.
    Attachments:
    Front_Panel.png ‏80 KB
    LabView_Code.png ‏62 KB
    Frequency Sweep + Counting.vi ‏50 KB

    Driver specific questions are hard to get answers from: but here are a few things to try.
    [before you start: I do not have these drivers installed, these are just things I noticed poking the Block Diagram]
    Are you intending to close the generator duding each for loop run? On the next loop, the ref to that address has been destroyed.
    You are using error mannaged drivers, Do you want the system to handle errors from previous loops?
    This is a pictrure of how I would restructure
    Remember you can add a contitional terminal to a for loop (right click border) to have the For loop end early on boolean or (more usefully) error. 

  • Error code 28 LabVIEW Null menu

    The error cluster of my VI indicate that the error 28 : LabVIEW Null
    menu occur in it, but when I open the block diagram  of this VI to
    see which subVI cause the error, the error doesn't reappears anymore
    and everything is OK.
    Afterward, if I close my erroneous VI and run it again. The error
    Reappears. I try a MASS COMPILE but I still have the same problem. So I
    have 2 questions.
    1) What can cause the apparition of the error when I run my application normally and not when I open the VI block diagram.
    2) What can cause the Error: 28 : LabVIEW Null menu.
    Thank you for your answer
    Gpaito

    Hi,
    This is over 1 year old ?!?!  
    What i mean is that you can add your VI to a meesage so we can have a look at it
    Message Edited by K C on 02-26-2007 09:31 PM

  • LabVIEW load error cod %ld: %p

    All of the sudden, when I tried to open a VI, I got an error message that said, "LabVIEW: Resource not found.  An error occured loading VI 'VI name.vi".  LabVIEW load error code 1: LabVIEW load error code %ld: %p".  I tried to revert that particular VI to the previous version through source control, but that didn't help.  Does anyone know what I need to do to fix this?  Thanks!
    Kudos and Accepted as Solution are welcome!

    It was fine, and now I can't open the VI.  It is possible that I forcefully closed the VI a few times with ctrl+alt+del.  The name.vi is the host vi for an fpga application.  It interacts with user, calls .NET DLL to communite with a DUT, pass data to/from FPGA, etc.
    I had already looked at the link that you posted.  Not sure does it apply to me.  
    Kudos and Accepted as Solution are welcome!

  • User defined Error Codes

    Hello,
      I am using the "Bundle by Name" VI to insert error info into the Labview Error Cluster.   I am doing calculations and have assigned a -23096 to the error code and during program execution a dialog box pops up stating the following
    Possible reason(s):
    Analysis:  Too many decimal points.
    I am assuming the dialog box is being generated by the system because the -23096 is defined to in the the range for Math errors. So how do I defined my own error codes that Labview will not use and cause unexpected dialog boxes to appear. My approach to handing the errors is the I will check the error status flag and if the error is one of mine I will handle it.
    Regards,
    Kaspar
    Regards,
    Kaspar

    After rereading your last post I think I know what you are getting at. Here is how I create a custom error cluster.
    1.On your front panel lay down a "error in" control cluster found in 8.2.1 at Array Matrix and Cluster.
    2.Switch to your block diagram and right click this control and change it to a constant.
    3.Wire this constant into the top of a bundle by name function. Expand the bundle by name to show the 3 elements. For each element create a constant and enter your information. You can feed the output of this function to any error input of the following vi's or create an indicator and hook it to your front panel connector pane.
    Hope this helps
    Using LabVIEW 2010SP1 and TestStand 4.5

  • Error code 15 with pda program

    Dear All
    I get error code 15 when I run a program using daqmx base on a pda through daq card E 6024. Previously I was able to run these programs but after removing and inserting the card into the pda, I get error 15. I am using Labview 7.1 on operating system 2000 to create the programs.
    Any ideas?
    Many Thanks
    Rupa

    Hi, some of the common issues are listed below :
    Error code 15 is “Unable to Locate Device”, which means that the DAQmx Base driver is unable to find the device on the PDA. Here are some common issues to check.
    Is the expansion pack fully connected? Be sure that connection is secure.
    If the expansion pack is connected and still the DAQCard is not detected, try re-powering the PDA.
    If you have a dual slot expansion pack, sometimes the power schemes can keep DAQmx Base from detecting the DAQCard. Try changing the following settings. Go Start>>Settings>>System>>Power>>”Uncheck Options Boxes to Not Turn Off Device if Not Used For” PDA Battery. Also change Start>>Settings>>System>>Power>>”Uncheck Options Boxes to Not Turn Off Device if not Used for” Expansion Pack Battery Power.
    After changing this, the board should be detected by DAQmx Base.
    Try reinstalling the DAQmx Base Driver for the PocketPC device.
    Please let me know if any of these option work.
    If not - is the card ok in a laptop?
    Thanks Sacha Emery National Instruments (UK)
    // it takes almost no time to rate an answer

  • Spartan 3E with Labview 2012 (32 bit) on WIndows 7 64-bit - Error Code: -310602 NI-COBS: Unable to communicate with device over communication cable.

    Thanks for the info, Kyle.  I will probably try to find an older 32-bit XP machine.  VM is just not an option for me right now.

    Hello everybody,
    I am trying to use the DIgilent Spartan 3E board with Labvew 2012 SP1 32 bit.  I am able to compile the example code for LED shift.  I am however unable to transfer code to the FPGA.  I get the following error message:
    Error Code: -310602 
    NI-COBS:  Unable to communicate with device over communication cable. 
    Please verify that the cable is connected to a supported device and that the appropriate drivers are installed.
    My system configuration is as follows:
    Windows 7 (64 bit) on Dell XPS laptop.
    Labview 2012 SP1 (32 bit)
    Labview FPGA 2012 SP1
    Labview 2012 FPGA support for Spartan3E
    Xilinx 13.4 tools
    DEFB LV FPGA 2012sp1 support installer
    Xilinx USB cable driver v1.3 installed.
    I took all the precautions mentioned by others on this forum and others, mainly that the cable must be disconnected before installing the Xilinx cable driver. All software and drivers were installed correctly.  I even uninstalled and reinstalled the entire Labview software set I had.  I still get the same error.
    A few other questions:
    1.  Is the Xilinx cable different from a regular USB cable of the same configuration ?
    2.  When I program the FPGA I only have the USB cable connected between my computer and the Spartan 3e board.  Should any other cable be connected ?
    3.  What should be the correct jumper settings for J1 - JP30 (especially J30, J11, JP9, JP6, JP7, etc) ?
    I have been at this or over 3 days trying to figure it out.  Any help will be greatly appreciated.
     

  • When Trying to Install Labview 8.6.1 on Windows 7 Get Error Code -12

    When Trying to Install Labview Deveopment Suite 8.6.1 on Windows 7 Get " *** Error: Windows SDK Function Returned an Error (Error Code -12)"
    I assume a compatability issue will Labview installer and Windows 7.  Is there a work arround?

    I figured as much, but maybe if enough peole are interested NI will be pushed to a solution.
    It's not that the programm won't run, it's that the installer fails before it even gets installed.
    I am using Windows 7 RC Build 7100.  It installs and runs just fine in Virtual XP Mode on Virtual PC for windows 7 (http://www.microsoft.com/windows/virtual-pc/download.aspx) which I find works better than compatability mode.
    Thanks for your help.

  • What can I do about "LabVIEW load error code 38: Failed to uncompress part of the VI."

    While attempting to load an executable LabVIEW application for LabVIEW 2009 SP1 on a Windows-XP machine when the following pop-up message occurs. "LabVIEW: Memory or data structure corrupt. An error occurs in loading VI 'NI_Gmath.lblib: Backward Bracket Search.VI'. LabVIEW load error code 38: Failed to uncompress part of the VI. The VI is most likely corrupt." What seems odd is that the same LabVIEW application loads fine when logged on as a privileged user account, but fails to load on a private user account.
    Attachments:
    2012-07-18 LabVIEW Load error code 38.jpg ‏1314 KB

    Here's a thought:
    So when something is decompressed, a temp folder is often used. 
    I have no idea why LabVIEW would be decompressing anything, but I suspect it is trying to put the decompressed file into a temp folder where the user does not have write permissions.
    In the .ini file for your executable, you can add a line that specified the location of the temp folder to use:
    tmpdir=C:\Temp
    On my Win7 machine, the location is:
    C:\Users\MyUserName\AppData\Local\Temp
    On WinXP, it is probably:
    C:\Documents And Settings\YourUserName\local settings\temp
     Try changing the tmpdir key in your ini file to something to C:\Temp and see if that helps.
    - john

  • Labview: resource not found error code 24 when building executable using 8.20 and dsc module

    I am trying to build an executable and I keep getting and error and cannot seem to figure out what is wring.  The whole error is "LabVIEW: resource not found.  An error occured loading "interface 3.vi"  Labview load error code 24:  this vi cannot be loaded because it is broken and has no block diagram."
    I am using LV 8.20 and DSC 8.2.  I am trying to create an executable that has the web server running for using remote panels, i have netowrk published shared variables, connecting to a fieldpoint unit, and I am using the NI system tray icon vis to load the program to the system tray.
    I have my shared variable library added as a support file, as well as the lvdsc.ini, and the tray icon files.  I have sleected "Enable Enhacned DSC run time support" in the app builder, did not remove any type def,etc.
    I cannot get the .exe to run on my development machine or another machine, I get the same error.  I tried creating an installer that installed the 8.2 runtime, dsc,fieldpoint, variable engine and manager and MAX.
    I could not find anything in the help files on the dsc, maybe someone else has some hints.  thanks
    Kenny

    Hi Kenny,
    I hope you are doing well today! What is interface 3.vi? Is it possible for you to post your project over here? Also, I would recommend creating a simple DSC application; and would like you to build it. Do you still get errors?
    Adnan Zafar
    Certified LabVIEW Architect
    Coleman Technologies

  • Installer LV7.1 - LabVIEW load error code 21: An external subroutine required for execution could not be found.

    Bonjour,
    Je cherche à créer un installer portatif utilisant les drivers NI-DAQmx 8.7.1 et NI-CAN 2.6.0.
    Je dispose d'un code LV 7.1 et j'ai installé l'application builder 7.1.
    Mais une fois l'application installé sur un PC vierge de Labview, j'obtiens le message suivant:
    load error code 21: An external subroutine required for execution could not be found.
    Ce message est répété plusieurs fois (pour différents VIs) puis le programme ne se lance pas.
    J'ai bien veillé à installer les drivers NI-CAN et NI-DAQmx correspondant au préalable sur la machine cible.
    En chercant sur le forum, plusieurs pistes m'ont été proposé:
    La version NI-DAQ
    L'intégration du Run time Engine
    Un problème de DLL
    J'ai vérifié ces 3 points mais cela n'a pas règlé mon problème.
    Résolu !
    Accéder à la solution.

    Bonjour,
    Merci de ta réponse.
    En fait, j'ai bien inclu le runtime engine de Labview qui était effectivement la source de l'erreur.
    L'installation de NI-DAQmx v 8.7.1 provoque la mise à jour de la version du runtime engine (passage de 7.1 à 7.1.1).
    J'ai donc désinstallé Le runtime engine 7.1.1 (ce qui a provoqué la désinstallation de labview et NI-DAQ).
    Puis je suis passé par une version plus ancienne de NI-DAQ (7.2) que j'ai adapté (inclusions de DLL et de VIs).
    Les messages d'erreurs ont alors tout simplement disparus!

  • Is there a LabView example in the use of user defined error codes?

    Specifically, I have a VI that tests four arrays of data against various high/low limits. I have pass/fail outputs for 18 tests. I'd like to combine these into an 'error out' cluster with appropriate error codes and messages, for which I've created an x-errors.txt file.
    My first question must be trival - how do I just set the 'status' bit of the error stream to let the general error handler then look up the error desription from the file?
    Secondly - I can't find an example of this in the technical resourses, amI missing something?
    Thanks,
    Mike
    Mike Evans
    TRW Conekt
    N.I. Alliance Member, UK
    http://www.Conekt.net

    There is no example program. There is extensive help on how to do this. Here's the basics.
    1) There are two ways to define user error codes in LV6.1. If you are using LV6.0 or earlier, only one method is possible.
    2) The 6.0 method involves wiring arrays of error codes and arrays of error code strings to the General Error Handler.vi. These codes will be used to explain any error code which is undefined in LV's internal error code database. Error codes reserved for users which are guaranteed not to be used by NI are from 5000 to 9999.
    3) The 6.1 method allows you to create a specially formatted error code file on disk that will be merged with the LV error code database each time LabVIEW launches. For help on this, go to LV's online help, and in t
    he Index tab, type
    "user-defined error codes, in text files"
    (without the quote marks)
    4) If you want to set an error into the error cluster, use the General Error Handler.vi again. Wire your error code value to the Error Code terminal (the leftmost-topmost corner terminal). Wire the name of your VI to the Error Source terminal, and wire "No Dialog" to the Type of Dialog terminal (left-side, near the bottom). The error code cluster that comes out of this VI will either be the error in (if one was set) or a new error code cluster with your error and the status bit set to TRUE.
    5) The attached demo is written in LV6.0.
    Attachments:
    Error_Demo.vi ‏37 KB

Maybe you are looking for

  • K8N Neo2 Platinum 54G BIOS problem

    I recently bought a MSI K8N Neo2 Platinum-54G mainboard with W7025NMS v1.3  092204 revision of BIOS. AMD Athlon64 3000+ 939 is installed on the mainboard, with 2x512 GEIL PC3200 memory modules in dual channel configuration working on default frequenc

  • OAS 8.0.4.20a installation problem

    Discussion Groups JDeveloper OAS 4.0.8 installation problem profile | register | preferences | faq | search next newest topic | next oldest topic Author Topic: OAS 4.0.8 installation problem mchow911 unregistered posted December 17, 1999 05:58 PM I t

  • My calendars were erased today

    I have not upgraded to Lion.  When I opened up my iCal this morning AFTER I synced my iPad all the calendars were gone.  I had about 7 calendars, months of appointments, critical accounts to keep up with, etc. Can I get any of this back?  I still hav

  • DHCP and ACL Problem

    Hi, Why the clients in vlan 30 cannot get ip from DHCP (192.168.1.3 and 4) when the ACL is applied to the vlan 30? When the ACL is removed clients can get ip from dhcp. Thanks 10 permit ip 192.168.3.0 0.0.0.255 host 192.168.1.3 20 permit ip 192.168.3

  • HT204266 prompted to contact itunes support

    I'm trying to purchase an app and during the buying process it prompts me to "contact itunes support". Where do I call to speak to a live agent and  not a computer. I can't seem to find any information on the FAQs either.