FPGA LabVIEW 2011 Compilation Crash - I/O Node

When I try to compile this FPGA LabVIEW code then LabVIEW crash every during" Generating Intermediate Files"
It don't like these "FPGA I/O in" variables in FPGA I/O Node.
Constants "POT_net_1_x" are same standard DIOs.
Hardware: PXI-7841R
Solved!
Go to Solution.

Hi JCC,
Glad you got it to compile, it may have been that LabVIEW got a corrupted file somewhere in the project that was causing an issue and by rewriting the code you bypassed this problem.
If the further problems relate to a problem with FPGA compilation then you could post them here, otherwise it is probably best to create a new thread with a title that relates to that problem, that way other people will know what the thread is about and it they know the answers or have suggestions they will help.
Kind regards,
James W
Controls Systems Engineer
STFC

Similar Messages

Bug (LabVIEW 2011 sp1 crash)

Bug (LabVIEW 2011 sp1 crash)
1) Open LabVIEW
2) Blank VI
3) Front Panel / View / Class Browser
follow exactly this :
Class Browser / Object library ---> select "LabVIEW Classes" ---> and then clic "Search"
result : The window "Class Browser Search" opens ----> do nothing ... just "Cancel"
back to the window Class Browser ...
Class Browser / Object library ----> now select "DAQmx"
result : in the window Class Browser : Objet library = DAQmx
Class = DAQmx buffer
don't touch anything else (!)
and now clic "Search" ... LV CRASH

When you meet your colleagues, could you ask them, of course when they have time, to create this number.
This will make me happy, and this would be a small reward for this bug report.
Thank you very much in advance ThiCop

LabVIEW 2011 compiled application icon missing

Previously when I built an application the VI Icon would appear in the top right corner exactly the same in the compiled executable as it did in the VI.
Since upgrading to LabVIEW 2011SP1 all I get is a blank/question mark, icon missing indicator.
This happens for all of my compiled applications regardless of what icon I specify, even if I leave it as the default.
VI icon looks like this Application icon looks like this.
Just to be extra clear, there is no problem with how the exe icon appears in windows explorer and shortcuts.
I am ONLY talking about how the front panel icon in the top right corner appears.
The application works, it just looks ugly/unprofessional.
Is this a bug? Do I have something configured incorrectly? Is there a workaround? Has anyone else noticed this?
Troy
CLDEach snowflake in an avalanche pleads not guilty. - Stanislaw J. Lec
I haven't failed, I've found 10,000 ways that don't work - Thomas Edison
Beware of the man who won't be bothered with details. - William Feather
The greatest of faults is to be conscious of none. - Thomas Carlyle
Solved!
Go to Solution.

I tried building on another computer. It works properly.
My usual development machine is running Windows XP SP3.
The other computer I just tried a build on is running Windows 7 and that works fine.
I'm trying a repair of the XP installation now (I'll get back to you in a couple of hours!).
One other possible difference is that on the XP machine I installed the LabVIEW 2011 SP1 f1 patch.
Now I can't remember if I uninstalled it again afterwards. How can you tell if the patch has been applied or not?
I can't remember if I did it on the Windows 7 machine too???
Troy
CLDEach snowflake in an avalanche pleads not guilty. - Stanislaw J. Lec
I haven't failed, I've found 10,000 ways that don't work - Thomas Edison
Beware of the man who won't be bothered with details. - William Feather
The greatest of faults is to be conscious of none. - Thomas Carlyle

Labview 2011 application crashes from time to time

Hi together,
from time to time my LV application crashes. This happens in different stages of the program.
I use some ext. DLLs written in C, some simple IO hardware and some serial communications with ext. hardware.
My feeling is that it has s.th. to do with the upgrade from LV 851 to LV 2011, but I'm not sure.
On target PC and on develpment PC we're using WXP Pro. SP3.
Many Thanks.

The crash dialog from LV indicates (most common reason) an unhandled exception thrown by a component used in your application. Therefore, the OS shuts down the process of this exception, in your case LV.
From experience, external code is a prominent source for such exceptions. You should try removing all DLL calls as a first step for pin-pointing the source of the crash. If the crash is not occuring anymore, it is most likely that a call has invalid parameters (e.g. empty array instead of a predefined buffer).
Try to boil down the issue as much as possible. To be honest, this could be a very time consuming issue, but you have little to no choice i assume.
Sidenote: Do you have the Desktop Execution Trace Toolkit? If yes, run it and observe memroy allocations, reference leaks and unhandled errors as primary parameters.
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Labview 2011 FPGA Compile Error

Hi,
I'm new to FPGA. I want to use Labview 2011 SP1 with the Spartan 3E starter kit from Xilinx (Spartan 3E driver available from NI labview website).
I'm trying to work my way through the examples that came with the driver. I've run into the same compiler error with a number of the examples. The error is attached.
Error 7 occurred at Read from Text File in niFpgaCompileWorker_CheckForErrors.vi->niFpgaCompileWorker_JobComplete.vi->niFpgaCompile_Worker.vi:1
Possible reason(s):
LabVIEW: File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS X, and / on Linux. Verify that the path is correct using the command prompt or file explorer.
C:\NIFPGA\compilation\Shift_FPGATarget_Shift_87E8371C\Spartan3EStarter.bld
I've checked the registry to ensure that the path to the compiler is correct.
Any assistance would be welcome.
Regards,
James.
Attachments:
Labview2011_FPGA_CompileError.JPG ‏96 KB

Hi,
I don't have any Xilinx tools installed - other than the ones that installed with the Labview FPGA module.
I have attached the compilation logs and output results from my attempt.
I have renamed the extension on the following files from .lvtxt to .txt
BuildResults.txt
CodeGenerationResults.txt
Regards,
James
Attachments:
BuildResults.txt ‏5 KB
XilinxLog.txt ‏42 KB

Labview 2011 save for previous version crashes

Hello,
I am trying to save an existing Labview 2011 project to any previous version. I have tried 2010 all the way down to 8.0. I have a clean project, all files are LV 2011, it builds and runs correctly. I have mass compiled. It did call 2 dynamic vi's but I have removed those. The project did contain conditional compilation, but that is removed. It did contain disabled diagrams, but they are removed. I did a save hierarchy to a seperate folder, just to make sure the standard save works. It does. There are 1196 vi's and controls in the project.
If I save to LV 2010, quite a number of sub vi's are saved (909 including controls), but none of the top level ones. The crash is manifested by Labview leaving memory (task manager doesn't see it any more) and the Labview window dissapearing.
Attached is the save dialog at the instance before crashing.
I have not been able to locate a log to let me know the last loaded vi. If you know of such a log, please let me know.
Has anyone experienced similar problems? If so, any clues on how to fix this?
Thanks,
Bart Schroder
Attachments:
LV2011 save crash.jpg ‏17 KB

BartSchroder wrote:
I have not been able to locate a log to let me know the last loaded vi. If you know of such a log, please let me know.
In the advanced build configuration, check "generate build log file". See if you get more information. Good luck.
Quote from the help:
Generate build log file—Specifies whether to create a log file for the build. The build log file lists all files contained in the build, including subVIs you do not specify as Startup VIs or Always Included. The log file also contains general build information such as build start and end time, the build specification and project name, and any errors that occurred during the build.
LabVIEW Champion . Do more with less code and in less time .

Application crashes when calling DLL built with LabVIEW 2011

Hello everybody,
Our application calls DLLs built with LabVIEW 2010 SP1. We installed LabVIEW 2011 and built some DLLs. So far so good. If we start our application and run 2010 DLLs it still works fine. If we run a 2011 DLL just once no error happens, but if we try to run the same 2011 DLL our application crashes reporting the error below. I saved the code for 2010 version and built a DLL and it works fine. Does anyone know why?
Thank you in advance.
#Date: Fr, 16. Sep 2011 16:25:25
#OSName: Microsoft Windows XP Service Pack 3
#OSVers: 5.1
#OSBuild: 2600
#AppName: PasTA
#Version: 11.0f2 32-bit
#AppKind: AppLib
#LabVIEW Base Address: 0x30000000
16.09.2011 16:25:26.181
Crash 0x0: Crash caught by NIER
File Unknown(0) : Crash: Crash caught by NIER
minidump id: 8a779b3f-51d7-4864-8e4d-6ab0195cd158
ExceptionCode: 0xC0000005
N
0x3072C804 - lvrt <unknown> + 0
0x3072CBB8 - lvrt <unknown> + 0
0x7C864191 - KERNEL32 <unknown> + 0
0x7C83AB50 - KERNEL32 <unknown> + 0
0x00000000 - PasTA <unknown> + 0
Attachments:
error.PNG ‏11 KB

On that note, you should be able to create DLLs in 2010 and run them with 2011, correct?? In my case, I have a 2010 built DLL (talking to sbRIO), most of the functions work when run in 2011, but a couple of them lock up LabVIEW on the desktop (but not the sbRIO), no lock ups happen with 2010 on the desktop.

LabVIEW 2013 Fpga will not compile tutorial solutions

Y'all
I am working to get the CRIO evaluation software to compile the tutorial solutions. so far it will not and complains about missing XILINX_EDK (warning.) Attached is the xilinx log. (Do I need to reinstall? or what)
Thanks for help!
Sincerely,
Paul
Attachments:
XilinxLog.txt ‏130 KB

Hi Paul,
What version of LabVIEW (2013/2013 SP1), LabVIEW FPGA and Xilinx Compile Tools do you have (or are you compiling on an external server)?
Which example specifically are you trying to compile? You mentioned tutorials, but I'm not sure exactly what example you are referring to.
Thanks!
Xavier
Applications Engineering Specialist
National Instruments

Fpga DMA FIFO compilation error

Hello,
I have a cRIO 9074 with FPGA. I am trying a simple piece of code to learn how to aquire data that is generated on the FPGA at a rate of 10 KHz and transfer it to the Host VI for processing it later offline. However, I encounter this compilation error when compiling this basic FPGA VI containing a FIFO
write node (picture of the VI attached below). In the Compilation Report, it says that there were 256 Block RAMs used (the
total number is 40), therefore an error was produced. The exact compilation error
notification from the Xilinx report is reproduced below:
# Starting program map
# map -o toplevel_gen_map.ncd -intstyle xflow -timing toplevel_gen.ngd
toplevel_gen.pcf
Using target part "3s2000fg456-4".
Mapping design into LUTs...
Running directed packing...
Running delay-based LUT packing...
ERRORack:2310 - Too many comps of type "RAMB16" found to fit
this device.
ERROR:Map:115 - The design is too large to fit the device. Please check the Design Summary section to
see which resource requirement for your design exceeds the resources available
in the device. Note that the number of slices reported may not be reflected
accurately as their packing might not have been completed.
NOTE: An NCD file will still be
generated to allow you to examine the mapped design. This file is intended for evaluation use only,
and will not process successfully through PAR.
Mapping completed.
See MAP report file "toplevel_gen_map.mrp" for details.
Problem encountered during the packing phase.
Design Summary
Number of errors : 2
Number of warnings : 125
ERROR:Xflow - Program map returned error code 2. Aborting flow
execution...
Bitstream Not Created
Timing Analysis Passed
What does this mean? How can I fix this error?
Thank you,
Bogdan
Solved!
Go to Solution.
Attachments:
FPGA.png ‏16 KB

Sorry, I forgot to mention that...LAbVIEW 2009. And yes, this is the only loop on the FPGA.vi. I just made up this code to understand how exactly I would save some data on the host for subsequent processing, but I didn't get to that point because the VI on the FPGA does not compile successfully. Do you know of any example of the most basic code for DMA FIFOs between the FPGA and Host Computer? This should be pretty straight forward, but for some reason it's not.
Thanks,
Bogdan

Cannot execute a library created with Labview 2011 in visual C++

I created a very simple DLL in Labview 2011, then, I try to call this DLL from a Visual C++ 2005 application.
I have tried to load the DLL at compilation time with the .LIB and .H files, and also dynamically with AfxLoadLibrary.
When I try to call the library function, it works fine, but the second time i call the library freezes the app.
all the library does is to show a simple dialog box and that's it, no params, no returns, no nothing,
but it freezes the app, why the VI works in Labview, but in DLL doesn't?

Hi Alveru,
What might be happening is that the process never ends and when you try to re call it, it fails and that it is why your app freezes, what you can do to probe is that is what is happening is to test your DLL directlly in LabVIEW with the Call Library Function Node so you can import the DLL and test it. If it also freezes or not work as expected the problem is with the DLL.
The proceses are automatically closed by LabVIEW at the moment the VI stops running; however, when you deploy the vi, you need to close them manually.
Try this out!!
Regards,
Luis Fernando
National Instruments Cono Sur
Ingeniería de Campo y Consultoría
http://chile.ni.com/

LabVIEW Access Violation Crashes

We've been seeing numerous LabVIEW crashes when calling VIs through the LabVIEW adapter in TestStand. I've searched the knowledge base and discussion forums without success and figured I would post here before opening a help request.
The actual error we see is:
Exception: Access violation (0xC0000005) at EIP=0x012B60E6 Version: 11.0.1f1
We see these crashes several times a day, but while calling no specific VI. They happen mostly on 2 PCs that are running Windows 7 - 64 bit, but I think we've seen them in the past on PCs running the 32 bit version of Windows 7. Here is the data related to those 2 problematic PCs.
OS: Windows 7 Professional SP1 64 bit
LabVIEW: 2011 SP1 (11.0.1f1) 32 bit
TestStand: 2010 SP1 (4.5.1.134) 32 bit
PC: Dell Optiplex 790 with Intel Core i5
Other significant information.
We see these crashes when we're running the batch model in TestStand with multiple threads open. Some VIs are reentrant, and some are not.
The 2 PCs that run the batch model (with multiple threads) have the 64 bit version of Win 7 Pro, and crash most often.
The 3 PCs that run the sequential model or the batch model with a single thread have the 32 bit version of Win 7 Pro and rarely if ever have crashed.
Not sure if it's related to the OS version or the multi-thread usage and switching the PCs/OS versions to isolate that isn't easy.
Has anyone else seen similar issues? Does Windows 7 Pro 64 bit work reliably with LabVIEW 2011 32 bit?
Any information would be appreciated.
John Morrissey

Hi Amezam, thanks for your reply.
We appear to be having different access violations each time (or they are one of a large group of them, we cannot tell).
The crashes appear to be at random, we cannot connect the crashes to any specific sequences of events and we cannot reprocude the crash consistently on the same piece of code! One pattern I have noticed, however, is that the violations appear to coincide with a peak in program activity - very frequent indicator updates for instance*.
I am unable to disable antivirus protection at will, but I will raise it with our IT Support to see if we can try that.
I believe that we are intearacting with external code - 3rd party device drivers which include packed libraries. I have no control over these and, furthermore, if I were to remove them the code would not be able to function at all. However, if you think it is a good idea I can attempt to create a separate piece of code which calls the same driver function very rapidly to see if that is the problem.
As for error handling - those nodes which use them only return error codes from the base 3rd party libraries, which according to the documentation only return custom error codes (these are not related to the error/crash that we are seeing). If you think it's still possible that they will return an Access Violaton error and crash, I will link them up.**
* - sidenote: I implemented a method of reducing the number of updates to a graph indicator (from several times a second to several times a minute) - this has reduced the problem significantly.
** sidenote 2: Some of the nodes which return custom errors are linked properly, and they are not returning errors; these ones are the most likely to return errors since they are called extremely frequently. I am not seeing anything except the documented custom error codes from them.

LabVIEW Access Violation Crashes from TestStand

We've been seeing numerous LabVIEW crashes when calling VIs through the LabVIEW adapter in TestStand. I've searched the knowledge base and discussion forums without success and figured I would post here before opening a help request.
The actual error we see is:
Exception: Access violation (0xC0000005) at EIP=0x012B60E6 Version: 11.0.1f1
We see these crashes several times a day, but while calling no specific VI. They happen mostly on 2 PCs that are running Windows 7 - 64 bit, but we've seen them in the past on PCs running the 32 bit version of Windows 7. Here is the data related to those 2 problematic PCs.
OS: Windows 7 Professional SP1 64 bit
LabVIEW: 2011 SP1 (11.0.1f1) 32 bit
TestStand: 2010 SP1 (4.5.1.134) 32 bit
PC: Dell Optiplex 790 with Intel Core i5
Other significant information.
We see these crashes when we're running the batch model in TestStand with multiple threads open. Some VIs are reentrant, and some are not.
The 2 PCs that run the batch model (with multiple threads) have the 64 bit version of Win 7 Pro, and crash most often.
The 3 PCs that run the sequential model or the batch model with a single thread have the 32 bit version of Win 7 Pro and rarely if ever have crashed.
Not sure if it's related to the OS version or the multi-thread usage and switching the PCs/OS versions to isolate that isn't easy.
Has anyone else seen similar issues? Does Windows 7 Pro 64 bit work reliably with TestStand and LabVIEW 2011 32 bit versions? I posted this question in the LabVIEW discussion forum, but I don't know where the issue resides, I'm posting in the TestStand forum also.
Any information would be appreciated.
John Morrissey

I just had the same error in a LVOOP Project. First I got a crash (something with out of memory). The I got subsequent Access Violations. Could trace it down to one VI that:
a) had been working just fine before
b) wasn't changed after test mentioned in a) but got (even just running on its own) subsequent access violations every time I ran it
c) VI used a class konstant, property node (to set 2 class attributes); Inputs were a string and an integer and an error cluster; outputs: one instance of the class (initialized with string an integer) and the error cluster
d) Problem could be solved by deleting the class constant used in the VI and put the same in again (an just rewired the thing); I assume this caused a recompile that solved the prob
Maybe this helps narrowing the general problem down.
P.S: I dont have a still non working version of that VI, since I was happy to have solved this and just saved the VI before thinking about making a copy.

Labview 2011 32-bit, Tescom ER3000, Windows 7 64-bit

I currently have Labview 2011 32-bit installed on a Windows 7- 64-bit machine. I am trying to run the VIs found in the attachment below, but I get the error that function called in the DLL has failed and that TESCOM.DLL may be in use. Any thoughts as to why this is happening? I've already checked to make sure the path referenced in the VIs' function call nodes is correct... any and all help is appreciated!!
~Avi
Solved!
Go to Solution.
Attachments:
ER3000.llb ‏139 KB

Greetings;
I have been reading up a bit on the company and the DLL itself, and are we sure it is supposed to work well with Win7? Would it be possible to try booting up LabVIEW in compatibility mode (XP) to try it out?
http://www.documentation.emersonprocess.com/groups/public/documents/data_sheets/der301767x012.pdf
Only mentions up to XP, hence the question.
National Instruments
Applications Engineer

Install labview 6.1 (or compatible) run-time engine with labview 2011

I have installed a trial period version of Labveiw 2011 in order to check for possible upgrade issues I may have if I decide to upgrade from labveiw 6.1. Well, needless to say there have been alot. That is as expected since I have not updated labview in many years. I am still not under any pressure to update; however, I would like to in order to get support and make sure I do not have any compatibility issues with new equipment purchases. I have been able to resolve most of my compatibility issues with simple code fixes and such. However, twice now I have run into an error when launching labview executeables compiled by two different equipment manufacturers. The equipment I am using is not even old...maybe a year or so. When I launch the labview executables to control this equipment on a PC that has the trial period labview 2011 installed, I get an error message stating something like " This requires a Labview 6.1 (or compatible) run time engine." I have tried to download and install the 6.1 labivew engine but I can't install this engine on a PC which has labview 2011 installed. Can someone explain how I am to run these executables under labview 2011. I can't imagine these executables were developed using 6.1 since this equipment is not even a year old now.
Solved!
Go to Solution.

Im not for sure I am on the same page with you here. Im not trying to develop any code myself. I have some labview executables that came with hardware we purchased in order to control it. We used to have labview 6.1 installed; so everything was working ok. But now that I have installed 2011, I get an error message when trying to run these executables. The error message states that this executable requires a labview 6.1 or compatible run-time engine. I have seen this error on both XP and Windows 7 machines. I did not develop the executable, it was developed by the hardware manufacturer. But since this hardware is only about 1 year old, I an assuming they used a newer version of Labview to develop this code. Certianly newer than 6.1.
So I guess my question is..is there a way for me to get this executable to work on a PC that has labview 2011 installed. I have tried to install a labview 6.1 run time engine but it will not install. Any other options?

How to add a time delay of microsecond in labview 2011

can you please help me, how to add a time delay of microseconds in labview 2011 version . I expect a helpful replies

A delay between what and what?
Is this plain LabVIEW, LabVIEW RT, or LabVIEW FPGA? What kind of data acquisition hardware are you using?
What is your OS? An accurate "software only" delay of microsseconds is not possible on windows or any other general purpose OS.
perumpadapu wrote:
... I expect a helpful replies
To get a helpful reply, you need to provide much more detail on what you are trying to do!
LabVIEW Champion . Do more with less code and in less time .

FPGA LabVIEW 2011 Compilation Crash - I/O Node

Similar Messages

Maybe you are looking for