Home > Labview Error > Labview Error 61499

Labview Error 61499

I am up against a deadline to modify this code. When you open the .txt file and look through it, you will be able to see any warnings and/or fatal errors that occurred to result in the crash. Another test: Created a very simple VI, nothing but two I16s adding, no loop. How about a big warning?I am really annoyed here. 0 Kudos Message 7 of 14 (1,193 Views) Reply 0 Kudos Re: fpga T-REX$ Active Participant ‎12-16-2013 01:01 PM Options Mark as http://jvmwriter.org/labview-error/labview-error.html

Related Links: KnowledgeBase 37BERJM9: How Do I Change the FPGA Compiler to Optimize for Area or Speed?KnowledgeBase 3U58J78T: Why Do I Get FPGA Compile Server Errors?KnowledgeBase 5VFC1LZT: Why Do I Receive The problem I found with the FPGA code was ALL of the I/O had become disconnected (red X's) inside the FPGA code. Note: Other troubleshooting steps are tocheck HKEY_LOCAL_MACHINE\SOFTWARE\National Instruments\LabVIEW\9.0\AddOns\FPGA has CompilerPath set to C:\NIFGPA2009\Xilinx\ISE . Can anyone help? http://digital.ni.com/public.nsf/allkb/0621DAF92B1731138625715E0075A702

I could understand if the PC was right on the 2Gblimit while compiling and sometimes getting nudged just over, but that isn't what's happening as a successful compile stays at 1.2Gb It's also possible to get this error while editing an FPGA VI. In order to fix the error, you can delete and re-create the affected FPGA nodes. neutronjohn Member ‎09-17-2009 07:06 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report to a Moderator Hey folks - this was not

All rights reserved. | Cart|Help KnowledgeBase Request Supportfrom an engineer NIHome > Support > KnowledgeBase English This Document is not yet Rated Why Do I In order to correct the error, replace the library with the ones attached to this KnowledgeBase.The libraryis located at LabVIEW 2010\rvi\HDL\Simulation\. Needless to say I decided to stick developing on 2011 SP1. We don't really have any way to do an "auto-notification" of potential known issues you could run into in the product (which I think is what you might be hinting at

The failure only occurs when using custom socketed Component-Level IP (CLIP) with global clock rates greater than 400MHz. Poor|Excellent Yes No Document Quality? File was not found. http://digital.ni.com/public.nsf/allkb/60CCBE0D8D6C844E862579C3006265E4 If it is possible I would like to see NI MAX technical report.

Title: * Questions: * Email id: Math question: * 9 + 5 = Solve this simple math problem and enter the result. What must i do? Showing results for  Search instead for  Did you mean:  Reply Topic Options Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark The NI AE (thanks Chris) suggested that this causes a deadlock on your RT controller when 2 VIs both try to startup.

I get the error 61499. http://digital.ni.com/public.nsf/allkb/5B8827503F7D90F386257BEA002D8E99 Cheers!TJ G 0 Kudos Message 6 of 14 (1,201 Views) Reply 0 Kudos Re: fpga Jed_Davidow Active Participant ‎12-16-2013 12:02 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Answered Your Question? 1 2 3 4 5 Document needs work? But still i cannot compile.

Attached are the error messages what I will get. weblink When I selected the master as startup, the RT starts up normally, TCPIP listeners work, and all is well.Happy developing... 0 Kudos Message 4 of 8 (1,250 Views) Reply 0 Kudos Thanks. Please see the attached file for more details.

Solution: This error has been identified to occur when using LabVIEW 2010 and NI-RIO 3.5.1. Attachments: CrioCartContResourceGetConstraints.vi Report Date: 11/12/2010 Last Updated: 03/16/2012 Document ID: 5FBCBNEQ Your Feedback! Please tell us why. http://jvmwriter.org/labview-error/labview-error-7.html Restart the computer and then re-install the: FPGA and RIO modules Xilinx tools NI-RIO driver in the above order.

Please Contact NI for all product and support inquiries. Please contact National Instruments technical support at ni.com/support.How can I prevent this error from occurring? neutronjohn Member ‎09-13-2009 01:05 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report to a Moderator Problem Description :I have a cRIO

Username: * Username Password: * Password Create new account Request new password Search this site: Primary links Home Solutions ArticlesView Articles BlogsView Blogs QuestionsView Questions Unanswered Answers not accepted Solved answers

Related Links: KnowledgeBase 3WRFDHJ4: Error -61499 in LabVIEW FPGAKnolwedgeBase 5FBCBNEQ: Error -61499 when Compiling an FPGA VI Using Hybrid Mode with CompactRIO Attachments: Report Date: 03/16/2012 Last Updated: 12/01/2012 Document ID: You can then enter that information into the LabVIEW Support: Internal Error Support Page to get some helpful information about specific internal errors if that appears to be the culprit. Please contact National Instruments technical support at ni.com/support. I have the problem fixed, at least I am able to compile the FPGA code.

Anybody have some thoughts on how to clear this? 0 Kudos Message 1 of 6 (937 Views) Reply 0 Kudos Re: error code -61499 Ray.R Knight of NI ‎06-17-2010 12:26 PM Additional Information: Traceback (most recent call last): File "./objects/lvfpga_dist/win32U/i386/msvc90/release/root\resource\RVI\TimingViolation\scripts\niFpgaTimingViolationMain.py", line 280, in NameError: name 'constraintDict' is not defined Return Code:1 0 Kudos Message 9 of 14 (1,139 Views) You can also try deleting the file perl58.dll as that is the problem that is causing the problem. http://jvmwriter.org/labview-error/labview-error-ni-488.html Please tell us why.

Has anyone else seen huge compile time increases when upgrading LV, or got any tips for reducing the compile time in LV2012 (that don't involve buying a new PC!) Cheers, Solved! It should be default be installed toC:\NIFPGA2009. I'm not getting the -61499 error any more and the FPGA code compiled and seems to be running fine BUT once out of every 3 or 4 attempts to run my

A possible solution for this issue is to: Remove the NI-RIO driver, the Xilinx tool and the FPGA and RIO modules.