LabView 2012 Security System Main vi's have error 200559

The vi's give errors of 200559 in my LabView 2012 and NI application engineer "John Staskal" told me as "Another good step
is to recreate the VI in your current version of LabVIEW so that you know the error is not caused by upgrading the VI to a newer version of LabVIEW." I did all that, but not resolved.
Their application engineer John Staskal also told me as "In addition to working to resolve the error you may want to pursue is posting on our upgrade forum and asking the community to convert the VI to a current
version of LabVIEW. http://forums.ni.com/t5/Version-Conversion/bd-p/VersionConversion".
I did all trouble shooting steps such as highlight execution, probes, etc as what their application engineer told me and still having error of 200559 in LabView 2012.
I appreciate help from any one.
Ali Tariq Bhatti
Ali Tariq Bhatti
Advice: Some people talk on different issues and abusive against your post because they do not want to help and arguing with you on some other topic. You all will observe and I also observed, so also do not want to mention their name and best way is complaint them to the moderator. If anyone still wants to talk on different issues against the post, other way is to do private message.
~~~Be nice, have faith in ALLAH(God)~~~
Attachments:
NI ELVIS II Security System VIs (2).zip ‏313 KB
Error 200559.docx ‏500 KB

RavensFan,
I) Yes, I open up the front panel of the Express VI's and probe into them.
2) I use the express vi's, but if you see my attached vi's file. You will see Security System Main vi is the main vi where the program is running and where I am getting the error of 200559.
3) I also attached the word document file, so I am getting error of 200559 in probes 3, 4, and 5 using Export Key Press and Voltage vi's in this post.
4)Do you know, how to convert these my attached vi's to 2011, 2010, 2009, or LabVIEW8.5 version. May be, it fix the problem, or if you know some one to get help from or get chance to use ELVIS II board, so let me know .Your help or any one's help is appreciated.
Advice: Some people talk on different issues and abusive against your post because they do not want to help and arguing with you on some other topic. You all will observe and I also observed, so also do not want to mention their name and best way is complaint them to the moderator. If anyone still wants to talk on different issues against the post, other way is to do private message.
~~~Be nice, have faith in ALLAH(God)~~~
Attachments:
did probes for Export Press and Key vi's file.docx ‏340 KB

Similar Messages

Upgrade to LabVIEW 2012 caused Additional Installers issue

Hello again all you helpful forum-goers!
I have been using LabVIEW 2010 (SP1) for a while on my Windows XP computer, but I recently purchased and installed LabVIEW 2012 for a future project. In the meantime, my previous projects must still use LabVIEW 2010 until I use my company's formal change tracking system to upgrade them. However, when I recently opened one of my older projects in 2010 to update it and rebuild the installer, I saw in the Additional Installers tab a bunch of blank lines at the end of the list (see attached screenshot). This doesn't directly hurt me, but I have to think it is a symptom of the root problem.
More directly relevant, the NI VISA Run-Time 5.0.3 that had been checked previously was now missing, and the NI VISA Run-Time 5.2 that had replaced it was NOT checked. That seems like an upgrade oops on National Instruments' part to me. I decided it was just a quirk, and that the 2012 installer had replaced my 5.0.3 version with the 5.2 version (deleting the old version), so I checked the 5.2 version to build my installer, and after requiring my DVD to copy the software to my computer, that seemed to work ok.
Now the immediate problem: when I distributed the project file to a colleague who only has LabVIEW 2010, she was not able to build my software's installer, because it asked her for the "FADEC_Emulator" disk. "FADEC_Emulator" is the name of my software. Expanding the error dialog showed that it wanted that disk in order to get access to NI VISA Run-Time 5.0.3. Opening the properties of the installer in the project file within LabVIEW showed NI VISA Run-Time 5.0.3 checked. However, opening the project file with Wordpad showed that NI VISA Run-Time 5.2 was listed as an additional installer (and NOT 5.0.3). Maybe her system saw that I wanted NI VISA Run-Time 5.2, and automatically replaced it with the latest version it had, 5.0.3? Confusing! And if it did that, why didn't it have that version handy already? And switching versions like that seems like it would be a bad idea to do silently, in case I was relying on a feature specific to the new version.
I'm afraid that since installing LabVIEW 2012 my system has gotten into an unstable state, and I now have possibly corrupted my project's LV project file. I need to have both 2010 and 2012 on my computer for the time being.
Does anyone have any idea what is going on with my system, and/or how to fix it?
Thank you very much in advance for your suggestions and time!
-Joe
Solved!
Go to Solution.
Attachments:
Additional Installers Blank Lines.png ‏45 KB

Hi Joe,
I tried to reproduce your issues, and encountered mixed results. Please verify with what I've provided below that we are testing under the same conditions
jmorris wrote:
More directly relevant, the NI VISA Run-Time 5.0.3 that had been checked previously was now missing, and the NI VISA Run-Time 5.2 that had replaced it was NOT checked. That seems like an upgrade oops on National Instruments' part to me. I decided it was just a quirk, and that the 2012 installer had replaced my 5.0.3 version with the 5.2 version (deleting the old version), so I checked the 5.2 version to build my installer, and after requiring my DVD to copy the software to my computer, that seemed to work ok.
In this scenario, I built a test project with VISA RT 5.0.3 and LabVIEW 2010 configuration. I then installed LabVIEW 2012 and VISA 5.2.0 on top of the aforementioned setup. When I opened the 2010 project in 2012, VISA Run-Time 5.2 was checked (as expected, dissimilar to your configuration). As I mentioned earlier, this may have been because VISA 5.2.0 did not install properly.
jmorris wrote:
Now the immediate problem: when I distributed the project file to a colleague who only has LabVIEW 2010, she was not able to build my software's installer, because it asked her for the "FADEC_Emulator" disk. "FADEC_Emulator" is the name of my software. Expanding the error dialog showed that it wanted that disk in order to get access to NI VISA Run-Time 5.0.3. Opening the properties of the installer in the project file within LabVIEW showed NI VISA Run-Time 5.0.3 checked. However, opening the project file with Wordpad showed that NI VISA Run-Time 5.2 was listed as an additional installer (and NOT 5.0.3). Maybe her system saw that I wanted NI VISA Run-Time 5.2, and automatically replaced it with the latest version it had, 5.0.3? Confusing! And if it did that, why didn't it have that version handy already? And switching versions like that seems like it would be a bad idea to do silently, in case I was relying on a feature specific to the new version.
For this case, I built the installer on LabVIEW 2012 with VISA RT 5.2.0 then saved it for LabVIEW 2010 compatiblity. When I opened the installer in a LabVIEW 2010 with VISA 5.0.3 environment, VISA 5.0.3 was checked (as expected since LabVIEW will default to the latest version of VISA on the PC regardless of what the original installer referenced). I did, however, see three extra blank lines in the additional installers tab (more on this below) . I also tried to build the installer as you indicated, but did not get any prompts for disks and was able to build successfully.
One thing to keep in mind is that LabVIEW by default will use the version of the driver that is installed on the build PC, regardless of whether it is newer or older than the installer references. If you feel this negatively impacts your successes as a developer, please feel free to post a feature request (e.g. for a prompt when the driver version changes) in our idea exchange forum (http://forums.ni.com/t5/LabVIEW-Idea-Exchange/idb-p/labviewideas ).
Lastly, regarding the empty lines in the additional installer specifications, this problem appears to be fixed in LabVIEW 2012 and only manifests itself in 2010. During my course of testing, this did not affect building the installers and is a minor inconvenience which has been fixed in subsequent versions.
Please let me know if you have any additional questions/comments regarding these issues.
Regards
Doug W
Applications Engineer
National Instruments

System Web Server Daemon startup error

Hello,
I recently installed the electrical power management package into my LabVIEW 2012 installation. Ever since, I have been getting an error upon startup of my system that says "System Web Server Daemon has encountered a problem and needs to close. We are sorry for the inconvenience." I have since uninstalled the electrical power measurement package and done a system restore to before it was installed and the error still comes up. I don't seem to be having trouble with LabVIEW as I have used it successfully since, but this error is connected with the NI software. Anyone have similar issues?
Some more information in the error window:
AppName: systemwebserver.exe AppVer: 12.0.0.49152 ModName: systemwebserver.exe
ModVer: 12.0.0.49152 Offset: 00001715
Some system information:
Windows XP Professional Edition SP3, 2048MB RAM, LabVIEW 2012, Circuit Design Suite 11.0
Thanks in advance!

I did that after you suggested playing around with those settings. I thought manual mode would stop the service from starting, but the error still happened. I disabled the service and the error no longer happens when I restart, but only because the program doesn't try to start. But like I said, this doesn't solve the problem.
I would really like to find a real sollution to this problem, not just a band-aid for it. I am sure that this service is designed to do something, and disabling it likely causes some disfunction in LabVIEW that I am unaware of at this time.
Thanks for the help thus far. At least I don't have to see the error message every time I restart!

My daughter has loaded a security system, and has forgotten which one, and we have lost all bookmarks and history.

We cannot access any bookmarks or history since my daughter downloaded a security system to protect the computer files. She cannot remember what the file was she downloaded. How can I get the bookmarks and history back?

And does she have current backups of all her important files?
Operating a business with a computer and not keeping current backups is a very dangerous thing to do. Hard drives can fail at any time. Experienced IT people will tell you there are two kinds of hard drives - those that have failed and those that are going to fail. The only question is when.
Best of luck.

HT3775 I have a camera security system that when you save video files have either a mp4 or avi extension. Is there an application to open these files?

I have a camer security system that when you save video files have a mp4 or avi extension. Is there an application that I can open these files with?

Try VLC media player seems to play anything.
http://www.videolan.org/vlc/

I have a MacBook Air with OS X and am having trouble accessing the ADT Pulse Home Security System cameras. The mobile (iPhone and iPad) apps allow access no problem, but I can't get a picture on the MacBook. Have tried Safari and Firefox browsers.

I have a MacBook Air with OS X and am having trouble accessing the ADT Pulse Home Security System cameras. The mobile (iPhone and iPad) apps allow access no problem, but I can't get a picture on the MacBook. Have tried Safari and Firefox browsers. Anyone have any ideas? Thanks.

From a Catherine to Katherine -- Had the exact same problem!! I had to enable Java twice - both in Safari and then on the MacBookAir itself.

Only have LabVIEW 2012. Why am I asked to download LabVIEW 2011 SP1 f2 RTE Patch?

Hello,
I recently got a new machine (clean install of Windows 8), and installed LabVIEW 2012, with no other previous versions. However, when I ran the NI Update Service, it listed "LabVIEW 2011 SP1 f2 R(32-bit) Run-Time Engine Patch" as a critical update.
I'm confused; did I accidentally install LV 2011 too?
Thanks
Solved!
Go to Solution.

Also, some addons use older RunTime Engines. It is not suprising that you need the 2011 RTE patch.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Issues with windows 7 after Labview 2012 installation

Hi
I am having some issues after installing Labview 2012 on machines running Windows 7. Firstly, after installing a program on a user's machine, the machine sometimes takes 20 minutes to boot up before the user can log on. The 'Please Wait' message appears during this time. This is also the case on the development machine.
Secondly, on the development machine, I am having an issue when trying to run compiled programs created in Labview. When installing, everything works fine but when I go to open the program, it appears on the task bar for a brief period before closing. It does not appear in the task manager either. I have tried this on 2 other machines with windows 7 and Labview installed and still get the same issue.
Any help on these matters would be much appreciated. Thank you

Hi
Firstly, looking at the issue with the slow Windows 7 boot up time, as Norbert_B suggested the Windows Event Log is a good starting point to find the root of the problem. The following link describes how to launch “Event Viewer” and some common problems:
http://itexpertvoice.com/home/what%E2%80%99s-taking-so-long-how-to-fight-slow-startup-times-in-windo...
Aside from that, if your computer is part of a domain, the problem may be connected with certain Windows Services that start automatically on boot up. I recommend trying the following steps:
Open up “Control Panel” go to “System and Security” then “Administrative Tools” from here launch “Services”.
Sort the list by name and scroll down to “Network Store Interface Service” right click and select “Properties”. Under the startup type dropdown select “Automatic (Delayed Start)”.
Next scroll down to the “WebClient” service again under “Properties” this time select “Disabled” under the startup type.
As for the problem with running LabVIEW executables, I have a few questions:
Do you get any error codes when it closes automatically?
Does this occur for multiple executables or just one in particular?
Does the code run without a problem within LabVIEW?
Have you tried to update LabVIEW?
What hardware are you running?
Without this information I can only think it may be caused by the Windows Data Execution Prevention (DEP) security feature. So you can try the following steps:
Right click on “Computer” and select “Properties”.
Click on “Advanced System Settings” and select the “Advanced tab, then under the performance section click “Settings”.
Click the “Data Execution Prevention” tab.
Make sure it is activated for essential Windows programs and services only, or you have an exception for your EXE.
You may also find the following link helpful on debugging applications:
http://zone.ni.com/reference/en-XX/help/371361H-01/lvhowto/debug_apps_dlls/
Let me know if these solve the problems.
Andrew.N
Applications Engineer
National Instruments

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.

Missing vi.lib files in Run-Time LabVIEW 2012

Hi
I've got a problem executing VI's under RT in LabVIEW 2012.
Our system consist of multiple independent modules which are opened and run from a Manager VI. VI paths to the modules are read from an .ini file by the Manager VI.
We have build a single executable (RT Launcher) that takes the path of the Manager VI as argument (Attachment : RT Launcher.png).
The RT Launcher is placed in the ..\National Instruments\LabVIEW 2012 folder as the LabVIEW.exe.
The RT Launcher is called from the CLI.
"C:\Program Files\National Instruments\LabVIEW 2012\RT Launcher.exe" "C:\Workspace\Labview\Manager.vi"
This will run the Manager.vi in the RunTime Environment and the Manager.vi will open the .ini file and execute the Module VI's one by one.
By calling the RT Launcher.exe from the same folder as the LabVIEW.exe, the search paths should be the same.
The system worked fine in LabVIEW 2010.
The Manager VI is opened with broken arrow and the errors indicate that vi.lib sub VIs are missing (attachment : Manager VI errors.png)
I know there are issues regarding object cache and separated compiled code from LV2010 -> LV2011 -> LV2012, but simply can't figure out how to come around this problem.
Can anyone explain the difference and how to solve the problem ?
Thanks
Regards Kahr
Certified LabVIEW Architect
CIM A/S
Solved!
Go to Solution.
Attachments:
RT Launcher.png ‏68 KB
Manager VI errors.png ‏35 KB

Hi Kahr.
It sounds like you are making some dynamic calls to VI's, eg. by using 'Open VI Reference'. My answer is based on that assumption.
You are absolutely right. In LabVIEW2010 we introduced a function called 'Separating Compiled Code from VI'. At that time none of the VIs from VI.lib had that option enabled. In LabVIEW2011, many VI's in VI.lib have, by default, a separation of compiled code and VI. This option cannot be changed (greyed out) for these VI's as well. This feature was introduced in order to simplify source code control.
Separating Compiled Code from VIs and Other File Types
The drawback is, that it is no longer possible to call VI's dynamically from an application (executable), when this option in enabled, since the compiled code no longer exists. The method of calling a VI dynamically from an application has been (and still is) used to make some kind of a plug-and-play architecture, meaning we have one EXE-file that only gets distributed once and a set of subVI's that gets redistributed according to new versions (new features added to the subVI), meaning we can make changes in the subVI without having to redistribute the EXE-file.
With the release of LabVIEW2011 and LabVIEW2012 we can no longer distribute VI's that uses functions from vi.lib, this also include DAQmx calls even though the DAQmx driver is installed.
The simple explaining is, that it has never been intended that VI's got distributed. Eg, when Microsoft is making a new software update for Windows7, they don't send out the source code to all the users.
The solution is therefore to wrap up the source code into 'something' that includes all the compiled files. In LabVIEW we do that in a couple of different ways.
1) Include the VI's in the EXE-file.
When building the application, we have the option to include files, that normally is not included in builds. If we call a SubVI dynamically this will not automatically be included! However, the drawback of this method is, that if you need to change something in one of your SubVI's, you would need to build and distribute the entire application. Thereby, we are not making use of the plug-and-play architecture that we originally wanted. However, this method will fix the error.
Error 1003 When Using VI Server in a LabVIEW Application
2) Now, if we still want the plug-and-play architecture in LabVIEW2011+2012 (and this will properly be the same for the next many released of LabVIEW), this can still easily be achieved by making a Source Distribution. When we make a Source Distribution, we can include the VI's from VI.lib and thereby the compiled code. When using this method, two important things should be remembered:
a) Make the files into a LLB file. This will pack all the VI's into one single file, that is easy to distribute.
Go to Destinations ==> Destination Type ==> LLB.
b) Make sure not to 'Exclude files from vi.lib', as this method will then simply not work.
Go to Additional Exclusions ==> Remove checker mark in 'Exclude files from vi.lib'.
How Can I Call a VI Dynamically from an Executable Without Including Those VIs in the Build?
I have made a small example to demonstrate this:
Example: Using vi.lib
This example has two mainVIs and two EXE-applications. Build the two EXE-files, but do NOT build the source distribution yet.
1) Main(IncludeSubInExE). This version has included the subVI in the build distribution for the EXE-file. When running this EXE everything works fine, even when calling the subVI dynamically. However, since the subVI is build into the exe, we would have to redistribute the exe for every new version of the subVI. This breaks the hole idea.
2) Main. The subVI is no longer included in the build. When running and trying to call the subVI, you will get this error (on both your developer and run-time machine):
Now, build the Source Distribution and run this EXE again. The exe is running perfectly with no errors.
I hope this answers your question.
Best Regards
Alex E. Petersen
Certified LabVIEW Developer (CLD)
Application Engineer
Image House PantoInspect
Attachments:
Using vi.lib.zip ‏83 KB

Can I get MJD (date and time) in LabVIEW 2012 SP1?

I need to time stamp my data before sending it to the file. I have been doing this with the standard calendar date and time but MJD is what we prefer to use. How can I get an MJD timestamp in LabVIEW 2012 SP1?
Solved!
Go to Solution.

Hello Brad_Henry,
The Format Date/Time String will return the day of the year when the %j argument is used, as per this help document:
LabVIEW Help: Format Codes for the Time Format String
http://zone.ni.com/reference/en-XX/help/371361J-01/glang/codes_for_time_format_str/
If you're looking for the actual MJD, I'm not aware of a built-in function that generates this so you'll probably need to create or find a function to calculate it manually. This should pretty basic arithmetic, and it looks like people have already made a few public examples, the first two search results here look to be just about what you need:
ni.com search:
http://search.ni.com/nisearch/app/main/p/bot/no/ap/tech/lang/en/pg/1/sn/catnav:ex/q/julian/
Regards,
Tom L.

MY LVOOP solution to CLD- Security System

Hi All,
Today , I gave a shot at the security system example from CLD. I did it using LVOOP. Do leave your comments on the code. (I havent done much documentation. Also, I have given the flexibility to the program to log file in any format, as per extension entered by user. The code has been written in a hurry, so pls ignore any cleanups of BD remaining ).
Thanks in advance!
-FraggerFox!
Certified LabVIEW Architect, Certified TestStand Developer
"What you think today is what you live tomorrow"
Attachments:
Test_Security.zip ‏100 KB

Pretty good all in all, some comments though.
They like comments and descriptions in controls and indicators, points are deducted for not having this.
They also like block diagram constants to be labelled (again points off for not doing this).
Your error cluster is not handled too well, if there is an error in any of the states it will just propogate through continuously, probably not what you want. I think the app is supposed to stop on error (cant remember exactly).
The Array local variable in the "get status" state is unnecessary, you could just move the control outside, into the while loop. Locals are generally discouraged.
In the "get status" I would not recommend hiding the index display of the string array you are passing on. At first glance it seems the same state is being queued regardless!
You are not closing the file reference.
One thing to note, my CLD was a lot longer than the pratice examples (a lot!, and I code quite quickly).
Good effort though!
nrp
CLA

What files do I send to be upgraded from LabVIEW 5.1.1 to LabVIEW 2012?

OK. Just to be clear. I am a complete newb to ANYTHING LabVIEW or LabWindows related. I am a programmer, but I have never used any version ever. That said, I am responsible for the upgrade process of getting our old LabVIEW 5.1.1 system up to date. The old system (still running and doing it's job everyday), is an old Windows NT v4.0 SP6 system running LabVIEW 5.1.1. You can just imagine how ancient this is by today's standard.
Have I set the stage properly? I hope so. Newb, Ancient LabVIEW version 5.1.1, Windows NT 4.0, upgrading from 5.1.1 to 2012.
Now here is what I "think" I know about what is required. Because LabVIEW 2012 will not directly read in, process and /or compile LabVIEW 5.1.1 files, I must first open and save the files using an intermediate version of LabVIEW (specifically 8.2.1) to bring the files up to a version that 2012 can handle. I have noticed in reading the Version Conversion forum, that I can attach a zip file of my LabVIEW files and one of the resident Gurus will convert it for me and give them back - quite nice I think.
Now, I have what I think are all of the required LabVIEW vi and llb files that make up this system we have in place, but I want to be sure before I just post a bunch of stuff.
What exactly do I need to zip up and what can I leave out?
Are there LabVIEW vi and llb files in a "project" that are not needed?
Are there any setup/configuration/project specific files I need to include?
Are there any limitatations to this conversion process that I need to be concerned with - such as various toolkits/suites/modules that may have been used but are no longer supported?
Secondly, I am not really comfortable with posting my vi and llb files for the world to see (and possibly use) as I am not the owner of said modules, just the user/future developer who will be responsible for insuring they stay up to date. Is there any way I can send my files to a specific NI guru via email instead of just posting them?
Solved!
Go to Solution.

So if I understand you correctly, all I really need to do is to get LabVIEW 8.2.1, and update my .vi, .lib, and any .ctl files to that version.
Is it a simple matter of just opening the files and hitting something like SAVE AS, or just SAVE and it will do this? Once done, LabVIEW 2012 will then allow me to open them and do what I need to do? Do I have to save them into LabVIEW 2012 first, or is that automatic when I try to recompile them?
When I get a copy of LabVIEW 8.2.1 (eval version), do I have to get all of the pieces (modules, toolkits, etc.) in order to update the 5.1.1 files? Based on what is installed on that NT v4.0 system, we have the following items installed:
NI VISA
NI ComponentWorks 3D Graph
NI DataSocket
NI LabVIEW 5.1.1 Advanced Analysis Library
NI LabVIEW RTE 5.1.1
NI LabVIEW v5.1.1
NI Measurement and Auto Explorer 1.1
NI-488 2.1.60
NI-DAQ 6.6
NI-PAL 1.3.110
NI-Reports
NI-VXI/VISA
You mention DAQ. Our program uses NI DAQ v6.6 now. I have LabVIEW Developer 2012, so I just download the DAQ files for it and it will replace the NI DAQ v6.6 library files we use now?
Thanks for your help so far. If we had a support contract in place, this wouldn't be an issue. However, as I stated, I am not the owner of the files, just the currently assigned caretaker, and part of my task is to get from where we are now on this ancient hardware/software platform, to the latest and greatest. However, I am specifically not allowed to just place the files on a public forum for all to see. It just isn't done. We can send them to a known location and a known entity, but not to just anyone/anywhere as a public forum is by its very nature.
I know there is nothing you guys can do if I cannot give you the files, but thanks for helping me to do it myself. Getting an eval copy of 8.2.1, et. al is probably what I have to do here.

Installing both Vision Builder 2012 and LabView 2012 on same Computer

am new to NI Vision Builder Automation Inspection 2012 (Which I am supposed to learn and use for part inspection) as well as LabView (Which I need not know at this time)
When I was presented (to work with) a 1722 Camera and the computer, Labview 2012 was already installed but not Vision Builder.
The IT folks installed the Vision builder without uninstalling LabView.
I have my problems getting upto speed with my inspection work, but is any of it attributed to both systems being on the computer?
Can I (Must I) uninstall LaView??
Thanks

LabVIEW and Vision Builder run fine on the same computer. I have several versions of each on mine with no problems.
Bruce
Bruce Ammons
Ammons Engineering

Labview 2012 Runtime Application Crash: Access Violation Error

hi All,
my rather large app that I been develping over teh last few years has recently been crashing.
I do not know if it is since I began compiling it in LV2012 SP1 that the problem occurred or I have some programming error
that I cannot track down.
It use to run with uptimes over months, even with some memory leaks.
If I monitor using Task Manager there is no decernable increase in memory usage.
It crashes on two different systems - both running Windows XP.
The developer version running in LabVIEW 2012 f5 ( Windows XP ) does not crash. Only the runtime version crashes.
It also crashes either if the program sits idle for a few days - 5 or so ( memeory footprint stable ), or if it is used extensively to actively gather and control several instruements ( memory increase matches data size increase )
It does call several external API via ActiveX to spawn off processes, however from the lvlog.txt it seems the crashing is a simple open file that uses the NI supplied String to Config.vi.
I have double/triple check my code and I close any refernces open by the calling vi.
I am sure how to read teh mini-dump files so if someone can look at these it would be apreciated
thanks
Michael
Here are two crash logs:
Attachments:
fde86f7f-a024-417d-ac1c-d38b2e9a41e3.zip ‏61 KB
4f75c413-793d-46db-b66c-889a2f2daf69.zip ‏59 KB
00660fb7-749d-4af5-bcb1-ac5cad73a5cb.zip ‏56 KB

Hi Michael,
It's tough to tell what's going on, especially since it seems like you've really covered your bases! I'm curious about the fact that you don't see the crashes in LabVIEW (LV), just in the Run-Time Engine (RTE). Have you ever tried running it in LV for an extended period of time?
Also, do you have any loops in your program? Perhaps shrinking any waits that might be present and allowing your program to run faster would decrease the amount of time to see these errors from days to shorter.
In the future, when you get a dump file, submit it to our R&D department. It then pops up on a website that allows me to read them. I can also use win debug but that will take me a bit, so I'll have to get back to you on that.
Also, if you could take a picture of the error, that would help as well.
Julian R.
Applications Engineer
National Instruments

LabView 2012 Security System Main vi's have error 200559

Similar Messages

Maybe you are looking for