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

Similar Messages

  • FPGA An internal software error has occurred. memory write

    Hi everybody
    We are encountering an error during compilation of an FPGA VI. It is probably related to our use of FPGA block memory. We have a non-timed while loop that is reading from an FPGA host-to-target FIFO and writing into block memory (inside a sub-VI called z_scan_write.vi). In another loop (this one is timed-loop), there is a subVI called we z_scan_read.vi, inside which we read from the block memory.
    Does anybody have an idea what is going wrong and how we could avoid this problem? Thank you very much in advance for any hint!
    The full error message is as follows. Note that it refers to the above-mentioned two subVIs z_scan_write.vi and z_scan_read.vi...
    An internal software error has occurred. Please contact National Instruments technical support at ni.com/support with the following information:
    nirviUIDToObject.vi<ERR>
    Error getting object reference for UID.
    All text parsed:
    <CodeGenErr>
    <ErrorCode>-61060</ErrorCode>
    <DynamicText><TreeLineInfo><LineInfo><ErrorInfoCallback><VIPath>C:\Program Files (x86)\National Instruments\LabVIEW 2010\vi.lib\rvi\ClientSDK\Core\ErrorReporting\Private\nirviPersistentNameToProjectItemLineInfoCallback.vi</VIPath>
    <Data>zIntensityTuples/{29C03A58-DC8D-4BC7-BAFA-66AFAE4E42D1}/%s</Data>
    </ErrorInfoCallback>
    </LineInfo>
    <TreeInfo><TreeID>ProjItem</TreeID>
    </TreeInfo>
    </TreeLineInfo>
    <TreeLineInfo><LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.z_scan_write.vi_FPGACompileCopy00000021.vi</VIPath>
    <UID>2747</UID>
    <ObjectName>Memory Write &apos;Memory Method Node&apos;</ObjectName>
    </DiagramObject>
    </LineInfo>
    <TreeInfo><ParentID>ProjItem</ParentID>
    </TreeInfo>
    </TreeLineInfo>
    <TreeLineInfo><LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.z_scan_read.vi_FPGACompileCopy00000001.vi</VIPath>
    <UID>194</UID>
    <ObjectName>Memory Read &apos;Memory Method Node&apos;</ObjectName>
    </DiagramObject>
    </LineInfo>
    <TreeInfo><ParentID>ProjItem</ParentID>
    </TreeInfo>
    </TreeLineInfo>
    </DynamicText>
    </CodeGenErr>
    <CodeGenErr>
    <ErrorCode>-61060</ErrorCode>
    <DynamicText><TreeLineInfo><LineInfo><ErrorInfoCallback><VIPath>C:\Program Files (x86)\National Instruments\LabVIEW 2010\vi.lib\rvi\ClientSDK\Core\ErrorReporting\Private\nirviPersistentNameToProjectItemLineInfoCallback.vi</VIPath>
    <Data>zIntensityTuples/{29C03A58-DC8D-4BC7-BAFA-66AFAE4E42D1}/%s</Data>
    </ErrorInfoCallback>
    </LineInfo>
    <TreeInfo><TreeID>ProjItem</TreeID>
    </TreeInfo>
    </TreeLineInfo>
    <TreeLineInfo><LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.z_scan_write.vi_FPGACompileCopy00000021.vi</VIPath>
    <UID>2747</UID>
    <ObjectName>Memory Write &apos;Memory Method Node&apos;</ObjectName>
    </DiagramObject>
    </LineInfo>
    <TreeInfo><ParentID>ProjItem</ParentID>
    </TreeInfo>
    </TreeLineInfo>
    <TreeLineInfo><LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.z_scan_read.vi_FPGACompileCopy00000001.vi</VIPath>
    <UID>194</UID>
    <ObjectName>Memory Read &apos;Memory Method Node&apos;</ObjectName>
    </DiagramObject>
    </LineInfo>
    <TreeInfo><ParentID>ProjItem</ParentID>
    </TreeInfo>
    </TreeLineInfo>
    </DynamicText>
    </CodeGenErr>
    <CodeGenErr>
    <ErrorCode>-61106</ErrorCode>
    <DynamicText><TreeLineInfo><TreeInfo><TreeID>1</TreeID>
    </TreeInfo>
    <LineInfo><VI><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</VIPath>
    <Name>NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</Name>
    </VI>
    </LineInfo>
    </TreeLineInfo>
    <TreeLineInfo><TreeInfo><TreeID>2</TreeID>
    <ParentID>1</ParentID>
    </TreeInfo>
    <LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
    <UID>2803</UID>
    <ObjectName>SubVI: &apos;NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi&apos;</ObjectName>
    </DiagramObject>
    </LineInfo>
    </TreeLineInfo>
    <TreeLineInfo><TreeInfo><TreeID>3</TreeID>
    <ParentID>1</ParentID>
    </TreeInfo>
    <LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
    <UID>2816</UID>
    <ObjectName>SubVI: &apos;NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi&apos;</ObjectName>
    </DiagramObject>
    </LineInfo>
    </TreeLineInfo>
    </DynamicText>
    </CodeGenErr>
    <CodeGenErr>
    <ErrorCode>-61106</ErrorCode>
    <DynamicText><TreeLineInfo><TreeInfo><TreeID>1</TreeID>
    </TreeInfo>
    <LineInfo><VI><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</VIPath>
    <Name>NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</Name>
    </VI>
    </LineInfo>
    </TreeLineInfo>
    <TreeLineInfo><TreeInfo><TreeID>2</TreeID>
    <ParentID>1</ParentID>
    </TreeInfo>
    <LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
    <UID>2803</UID>
    <ObjectName>SubVI: &apos;NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi&apos;</ObjectName>
    </DiagramObject>
    </LineInfo>
    </TreeLineInfo>
    <TreeLineInfo><TreeInfo><TreeID>3</TreeID>
    <ParentID>1</ParentID>
    </TreeInfo>
    <LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
    <UID>2816</UID>
    <ObjectName>SubVI: &apos;NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi&apos;</ObjectName>
    </DiagramObject>
    </LineInfo>
    </TreeLineInfo>
    </DynamicText>
    </CodeGenErr>
    <CodeGenErr>
    <ErrorCode>-61106</ErrorCode>
    <DynamicText><TreeLineInfo><TreeInfo><TreeID>1</TreeID>
    </TreeInfo>
    <LineInfo><VI><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</VIPath>
    <Name>NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</Name>
    </VI>
    </LineInfo>
    </TreeLineInfo>
    <TreeLineInfo><TreeInfo><TreeID>2</TreeID>
    <ParentID>1</ParentID>
    </TreeInfo>
    <LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
    <UID>2803</UID>
    <ObjectName>SubVI: &apos;NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi&apos;</ObjectName>
    </DiagramObject>
    </LineInfo>
    </TreeLineInfo>
    <TreeLineInfo><TreeInfo><TreeID>3</TreeID>
    <ParentID>1</ParentID>
    </TreeInfo>
    <LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
    <UID>2816</UID>
    <ObjectName>SubVI: &apos;NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi&apos;</ObjectName>
    </DiagramObject>
    </LineInfo>
    </TreeLineInfo>
    </DynamicText>
    </CodeGenErr>
    <CodeGenErr>
    <ErrorCode>-61106</ErrorCode>
    <DynamicText><TreeLineInfo><TreeInfo><TreeID>1</TreeID>
    </TreeInfo>
    <LineInfo><VI><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</VIPath>
    <Name>NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</Name>
    </VI>
    </LineInfo>
    </TreeLineInfo>
    <TreeLineInfo><TreeInfo><TreeID>2</TreeID>
    <ParentID>1</ParentID>
    </TreeInfo>
    <LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
    <UID>2803</UID>
    <ObjectName>SubVI: &apos;NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi&apos;</ObjectName>
    </DiagramObject>
    </LineInfo>
    </TreeLineInfo>
    <TreeLineInfo><TreeInfo><TreeID>3</TreeID>
    <ParentID>1</ParentID>
    </TreeInfo>
    <LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
    <UID>2816</UID>
    <ObjectName>SubVI: &apos;NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi&apos;</ObjectName>
    </DiagramObject>
    </LineInfo>
    </TreeLineInfo>
    </DynamicText>
    </CodeGenErr>
    Solved!
    Go to Solution.

    Removing the two subVIs that read from/write to the block memory doesn't avoid the error showing up during compilation. The error details are obviously different now; they don't refer to the two subVIs (mentioned in the previous post) anymore...
    An internal software error has occurred. Please contact National Instruments technical support at ni.com/support with the following information:
    nirviUIDToObject.vi<ERR>
    Error getting object reference for UID.
    All text parsed:
    <CodeGenErr>
    <ErrorCode>-61106</ErrorCode>
    <DynamicText><TreeLineInfo><TreeInfo><TreeID>1</TreeID>
    </TreeInfo>
    <LineInfo><VI><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</VIPath>
    <Name>NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</Name>
    </VI>
    </LineInfo>
    </TreeLineInfo>
    <TreeLineInfo><TreeInfo><TreeID>2</TreeID>
    <ParentID>1</ParentID>
    </TreeInfo>
    <LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
    <UID>2735</UID>
    <ObjectName>SubVI: &apos;NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi&apos;</ObjectName>
    </DiagramObject>
    </LineInfo>
    </TreeLineInfo>
    <TreeLineInfo><TreeInfo><TreeID>3</TreeID>
    <ParentID>1</ParentID>
    </TreeInfo>
    <LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
    <UID>2748</UID>
    <ObjectName>SubVI: &apos;NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi&apos;</ObjectName>
    </DiagramObject>
    </LineInfo>
    </TreeLineInfo>
    </DynamicText>
    </CodeGenErr>
    <CodeGenErr>
    <ErrorCode>-61106</ErrorCode>
    <DynamicText><TreeLineInfo><TreeInfo><TreeID>1</TreeID>
    </TreeInfo>
    <LineInfo><VI><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</VIPath>
    <Name>NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</Name>
    </VI>
    </LineInfo>
    </TreeLineInfo>
    <TreeLineInfo><TreeInfo><TreeID>2</TreeID>
    <ParentID>1</ParentID>
    </TreeInfo>
    <LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
    <UID>2735</UID>
    <ObjectName>SubVI: &apos;NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi&apos;</ObjectName>
    </DiagramObject>
    </LineInfo>
    </TreeLineInfo>
    <TreeLineInfo><TreeInfo><TreeID>3</TreeID>
    <ParentID>1</ParentID>
    </TreeInfo>
    <LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
    <UID>2748</UID>
    <ObjectName>SubVI: &apos;NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi&apos;</ObjectName>
    </DiagramObject>
    </LineInfo>
    </TreeLineInfo>
    </DynamicText>
    </CodeGenErr>
    <CodeGenErr>
    <ErrorCode>-61106</ErrorCode>
    <DynamicText><TreeLineInfo><TreeInfo><TreeID>1</TreeID>
    </TreeInfo>
    <LineInfo><VI><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</VIPath>
    <Name>NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</Name>
    </VI>
    </LineInfo>
    </TreeLineInfo>
    <TreeLineInfo><TreeInfo><TreeID>2</TreeID>
    <ParentID>1</ParentID>
    </TreeInfo>
    <LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
    <UID>2735</UID>
    <ObjectName>SubVI: &apos;NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi&apos;</ObjectName>
    </DiagramObject>
    </LineInfo>
    </TreeLineInfo>
    <TreeLineInfo><TreeInfo><TreeID>3</TreeID>
    <ParentID>1</ParentID>
    </TreeInfo>
    <LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
    <UID>2748</UID>
    <ObjectName>SubVI: &apos;NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi&apos;</ObjectName>
    </DiagramObject>
    </LineInfo>
    </TreeLineInfo>
    </DynamicText>
    </CodeGenErr>
    <CodeGenErr>
    <ErrorCode>-61106</ErrorCode>
    <DynamicText><TreeLineInfo><TreeInfo><TreeID>1</TreeID>
    </TreeInfo>
    <LineInfo><VI><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</VIPath>
    <Name>NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</Name>
    </VI>
    </LineInfo>
    </TreeLineInfo>
    <TreeLineInfo><TreeInfo><TreeID>2</TreeID>
    <ParentID>1</ParentID>
    </TreeInfo>
    <LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
    <UID>2735</UID>
    <ObjectName>SubVI: &apos;NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi&apos;</ObjectName>
    </DiagramObject>
    </LineInfo>
    </TreeLineInfo>
    <TreeLineInfo><TreeInfo><TreeID>3</TreeID>
    <ParentID>1</ParentID>
    </TreeInfo>
    <LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
    <UID>2748</UID>
    <ObjectName>SubVI: &apos;NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi&apos;</ObjectName>
    </DiagramObject>
    </LineInfo>
    </TreeLineInfo>
    </DynamicText>
    </CodeGenErr>

  • FPGA Internal software error

    Hi,
    I'm using labview 2009. When I compile the fpga target vi, i got the following message:
    " An internal software error has occurred. Please contact National Instruments technical support at ni.com/support with the following information:#,910x,907x,911x,783x;781x,785x;784x,9​10x,907x,911x,783x;781x,785x;784x,9101;9102;9103;9​104,9072;9073;9074;9144;9601;9602;9611;9612;9631;9​632;9641;9642,9111;9112;9113;9114;9116;9118,7830;7​831;7833;7811;7813,7851;7852;7853;7854;7841;7842,9​101;9102;9103;9104,9072;9073;9074;9144;9601;9602;9​611;9612;9631;9632;9641;9642,9111;9112;9113;9114;9​116;9118,7830;7831;7833;7811;7813,7851;7852;7853;7​854;7841;7842,Onboard,Onboard,Onboard,Onboard,Onbo​ard,Derived,Derived,Derived,Derived,Derived#,,,,,,​,,,,CONST_TCO_SPI,12.5,13.5,11.25,14.5,12.25,9.25,​13.5,7.5,11.25,8.5CONST_TSU_SPI,2,4,3,2,4,4,4,4,4,​4CONST_TH_SPI,4,4,4,4,4,4,4,4,4,4CONST_TSU_PLUS_TH​_SPI,6,8,7,6,8,8,8,8,8,8#,,,,,,,,,,CONST_TSU_SSMIS​O,6,6,6,6,6,6,6,6,6,6CONST_TH_SSMISO,4,4,4,4,4,4,4​,4,4,4CONST_TSU_PLUS_TH_SSMISO,10,10,10,10,10,10,1​0,10,10,10#,,,,,,,,,,CONST_9201_TCO_SPI,10,10,10,1​4.5,12.25,9.25,10,7.5,11.25,8.5
    Method Name: <b>Compile For Target</b>"
    Does anyone know what caused this problem? Thanks in advance.

    Hello Kb1126,
    To better be able to answer your question could you please share what RIO device you are working with, the RIO device software and any relevent Xilinix tools versions, as well as the possible version installed on your RT target (assuming you are using a RT controller to interface with your FPGA). 
    Thanks,
    Blayne Kettlewell

  • Why Do I Receive Internal Software Error(s): Terminal Index Out of Bounds. Error code -61350,When Compiling my FPGA VI for an cRIO-9118 using NI 9223 ?

    I am receiving the following error (in a pop-up window) when compiling my VI FPGA code in chassis NI 9118 using NI 9223 module.  This error occur while compiling process (generating intermediate files , stage 7 of 7). how do I resolve this error ?
    thank you
    additional information :
    Original error message: 
    Errors : 
    Internal Software Error(s): Terminal Index Out of Bounds.
    Error code: -61350
    Details : 
    A terminal with this index does not exist on this block diagram node.
    NiFpgaHandleCallbackError.vi<APPEND>
    <b>Complete call chain:</b>
    NiFpgaHandleCallbackError.vi
    niFpgaNodeInformation.lvclass:Get Const Variant.vi
    DfirModGen.lvclass:GetConstant.vi
    niLvFpgaMungerBrainwashIONodeCommon_Dfir.vi
    niLvFpgaMungerBrainwashSingleIOGrowableMethod_DFIR.vi
    nirviEIOMethodImplementation_SpecifyDFIR.vi
    nirviEIOMethodImplementation_SpecifyDFIR.vi.ProxyCaller
    Solved!
    Go to Solution.

    Hi tesa,
    This is a bug which was fixed in LabVIEW 2012 SP1. The CAR number created for this bug is 332811 and as you can see in this link, it is already in the bug fixes list.
    Carmen C.

  • An internal software error has occurred. Error code: 1003

    Dear, I am working on a FPGA programming. When I use the VI: "High Throughput Add Function". Some error occur.
    Internal software error(s):
        Error code: 1003 (refer to details)
    Details:
    An internal software error has occurred. Please contact National Instruments technical support at ni.com/support with the following information:
    Error 1003 occurred at E:\Program Files (x86)\National Instruments\LabVIEW 2012\vi.lib\rvi\FXPMathLib\FxpAdd\modGen\nifxpmath_Add_EmitCode.vi: There's a broken VI

    Hello Yjin,
    Can you show me a VI in which this error occurs?
    Which software versions are you using?
    An easy way to find this information is as follows:
    http://digital.ni.com/public.nsf/allkb/271F252B4EF0A2E0862570E70056A1E4?OpenDocument
    Kind Regards,
    Thierry C - Applications Engineering Specialist Northern European Region - National Instruments
    CLD, CTA
    If someone helped you, let them know. Mark as solved and/or give a kudo.

  • Internal Software Error occurred in MIG software DAQmx

    Hi All, I have a very disturbing problem. Ever since upgrading to Labview 2011 and NIDAQ951f1 I get errors like the following in code that uses DAQmx:
    Error -229771 occurred at DAQmx Create Channel (AO-Voltage-Basic).vi:1
    Possible reason(s):
    Internal Software Error occurred in MIG software. Please contact National Instruments Support.
    The strangest thing is that this  happen only when I run the VI while a LV project is open! It does not matter wether the  VI is part of the project or not. As soon as I open any project (or create a new empty project) the error occurs when I run any DAQmx code. To test I am using one of the DAQmx example files: Cont Gen Voltage Wfm-Int Clk-On-Board Regeneration.vi for now, but the problem occurs with the other examples as well.
    I tried to resolve the issue by removing all NI software and doing a clean install, but the problem persists. Needless to say I cannot do any development this way.
    Any idea what's going on? Please advice.
    Best regards,
    Dixie

    Hello Dixie,
    There is a knowledge base topic treating this issue --> http://digital.ni.com/public.nsf/allkb/03123D0E8A36C48E862577A4005B6BAA?OpenDocument
    Have you already had a look at it?
    The problem you have can also be somewhere network-related. As some networking feature are handled by the Project Explorer, this can explain why you encounter the issue only when it is open. I propose that you first check the knowledge base and then keep me updated. I will give you further info if that does not solve the issue.
    Cédric | NI Belgium

  • Internal Software Error in MIG

    Running Windows XP SP 3
    Labview 8.2
    Error: 
    Error -229665 occurred at DAQmx Create Channel (DO-Digital Output).vi:1
    Internal Software Error occurred in MIG software. Please contact National Instruments Support.
    No new devices installed. 
    When opening MAX no devices listed in Device & Interface category. Same error with other VIs.

    Did not work for me as the tool returns an error.
    Instead I used MAX : Tool>>Reset Configuration Data after making sure I first exported all my configuration (devices, tasks, channels, scales...)  as described here. Then the Max config was imported back in.
    L.
    PS: The issue manifests itself with DAQ Device control drop downs not seeing/finding any device: the drop down does not drop at all.
    Some VIs using Daqmx open with many GUI object not showing up at all, and LV stops responding. (LV 2011).  This issue appeared first after installing daqmx on a Win 7-64 laptop...

  • Internal Software error

    Hi, 
    When I compile my fpga target vi i got an internal software error shown in the attached picture.
    The program I'm working on is somehow complicated and the target file size is about 801KB and I also used 15 target-scoped FIFOs to transfer data within the target. I've also attached the log file. Does anyone know what caused this problem? Thanks in advance.
    Attachments:
    Untitled.png ‏40 KB
    lvlog2011-10-06-13-05-10.txt ‏4 KB

    It is an internal error generated by the application. I think the disc is still ok since the application is still preparing the data for burning to the disc and the actual burning has not yet started. Try running the program again and see if the error is still the same. If it displays a constant error every time you try burning the project, it is either the application can’t handle the size of the data that is going to be burned or there is an error in your system.
    Run a disk check on your computer to see if there is any error that is preventing the application from working properly.
    Right click on drive C and then select Properties.
    Click Tools tab.
    Click Check Now button.
    Check Automatically fix file system errors and then click Start.
    If no error was found try launching the application again. If it’s the same, use other video editing application where you can burn a video also.
    http://www.techyv.com/

  • Internal Software error PGC  for encore CS3 !!! solved  !!!

    Almost everybody here knows the next error:
    PGC "timeline name" has an error at xx:xx:xx:xy internal software error : %0, line timeline name - PGCINFO: name= timeline name, ref=BPGC, time=xx:xx:xx:xy
    Where the y in time stands for the length of the timeline minus 2 frames. The BPGC error can also be FPGC or DPGC dependant on how many menu's there are in the project.
    It kept me awake for weeks and after reading this forum several times and comparing encore CS3 with encore 2.0 filenames I found the solution.
    This Error is a bug in encore witch has nothing to do with blank filename spots and sonic coding or codecs or planning your workflow with a pencil but pure with the combination Adobe Premiere Pro CS3 and Encore CS3.
    This is what generates the problem:
    In Adobe Premiere Pro CS3 you build project with video, sound and chapters. Then you export the project via the Media Encoder not Multplexed.
    Premiere CS3 then creates the following files:
    filename.M2V (video file mpg)
    filename.AC3 (audio file ac3)
    filename.M2V.XMPSES (an adobe file with preview info and chapter pointers)
    filname.XMP (??)
    It is the .M2V.XMPSES file witch creates the PGC error. If you use the MULTIPLEX DVD option then ADOBE will not create the .M2V.XMPSES file so there will not be an error. This trick mentioned by ADOBE and many others is just to go around the bug instead of solving it. Also with multiplex you have just one sound track. I use two sound tracks like 5.1 and a 2.0 track witch you can choose in a menu.
    Some people say it is the blank spots. Also not true. They have probably just erased the blank spots of the M2V file and forgot the .M2V.XMPSES file.
    When you just delete the .M2V.XMPSES file and then open the M2V and AC3 file in Encore as a new asset, make a timeline and menu's and the project will built and burn. Only if you delete this .M2V.XMPSES file Encore takes a longer time to import the M2V file and will be without the chapter points.
    Almost everything else will work like menu with sound and even a movie background (use M2V files). Only the motion buttons in a menu still wont work unless you use a black background !?!. Haven't figured this out yet. Only solution for this is use Encore 2.0. In this older version also the motion buttons will work without error's (everything else also so why buy CS3??)
    Here is what you must do create a DVD without errors:
    -Create a project in Premiere Pro, even with chapters.
    -Write down all chapter points (minutes:seconds:frames)
    -Create two new unique maps in explorer for example D:DVD1 and D:DVD2
    -Export in Premiere with Media Encoder without the Multiplex:DVD but with NON to the D:DVD1 map
    -Copy from D:DVD1 only the M2V and AC3 files to D:DVD2
    -Start up Encore DVD CS3 or 2.0
    -Create a new unique project in Encore for example "DVD" and save this in the map D:DVD2\
    -Then use Save-as (under file) and pinpoint to D:DVD2\dvd to be sure that all Encore's files are placed in this folder.
    -Select M2V file and make new timeline.
    -Make chapter points (you wrote down the points, did you?)
    -Create menu's, even with sound (AC3) and movie background (M2V)
    -Then render project if you have used a video for menu background
    -Finally Built and burnnnnnn!!
    -If you like to use motion buttons in a menu then use Encore 2.0
    I have double checked my work flow and it really works. I have built a project and burned with success Then I deleted the timeline and the M2V file. Copied the .M2V.XMPSES file in the used folder. Re loaded the M2V file in encore (this time much faster! and with chapter points). Tried to built and burn and back was the error. Also this happened in in Encore 2.0!!
    Hope that this will solve the PGC error once and for all !!!
    Marcel W
    system:
    acer aspire AMD 64 3800+
    2 GB
    250 GB hard drive for system
    750 GB hard drive for movie
    software Adobe Encore 3.0.1.008, Premiere PRO 3.2.0, Photoshop CS3 10.0, All upgraded
    NERO 7
    No Internet

    > Where the y in time stands for the length of the timeline minus 2 frames.
    This can actually vary, and so far at least, I don't think we've seen a pattern as to type of pgc error based on how many frames from the end it reports.
    > The BPGC error can also be FPGC or DPGC dependant on how many menu's there are in the project.
    Number of menus is not relevant; the iteration of the first letter is more related to subsequent occurrences of the error. In my current tests it did not always update; they may have been too similar.
    > This is what generates the problem...
    Well, the problem does not occur every time you do what you describe, any more than it occurs every time spaces are left in the file names. What you have is, as some other suggestions, a workaround. Thats not bad, and I wonder if you are onto something as to what is contributing to the problem.
    So, on to the interesting part whether the xmpses file, or at least what Encore is doing with it, is contributing something. I took an old test project that throws the PGC error and did some experiments.
    Background. I am a user who does get the pgc errors regularly, but not always. Creative Suite Production Premium, with PPro CS3 3.2.0 (374) and Encore 3.0.1.008. Pentium 4 2.8GHz 2G RAM, XP SP3, Multiple drives, Nvidia GEforce4 MX440 i.e. an older system. I have lots of stuff loaded and running, including virus protection and firewall, so there are any number of potential conflicts. But I get no crashes, and only one problem other than the pgc. (PPro and Encore monitor windows do this diagonal thing I suspect the display card, but the drivers are up to date. Maxing and then back to fit fixes it.)
    If you want to attempt to replicate my studies, here is a link to my problem clip and the first Encore project I describe.
    http://www.videoandcomputer.com/test/pgc_test.htm
    This project involves a very short AVI export from PPro CS3 - just over 8 seconds - called pgcbad_clip1.avi. Just to answer any question, the source is dv camera capture, and the source and avi export I use are dv avi type 2. There were no effects added on the timeline.
    Test 1: Create a project in Encore CS3. Use the sunset menu and delete all the buttons except "play all." Import the avi as a timeline. Set the timeline end action as "return to last menu" and set the button link to the timeline. Auto transcode. (Project settings are 8mbps max and a3c.) Check project shows okay; there is never a problem with that. Build to a DVD folder in a new folder. This project throws the pgc error.
    Test 2: Now create a new Encore project in a new folder. Use the same process, except import as timeline the m2v and a3c files from the first run. (I.e. if the clip is pgcbad_clip1.avi, in the test1 project folders, there is a folder called pgcbad_clip1.avi that has 6 files.) Note that in the folder they are imported from is an xmpses file from the first project's encore transcode. The build again fails with the pgc error - same frame, etc, but I really think the frame number doesn't matter.
    Test 3: Now create another new Encore project in a new folder. Use same process, but before importing the m2v and a3c as timeline, delete the xmpses file. Drumroll...... Build succeeds!
    Go figure.
    This is not the repeatable bug option weve been looking for, but based on a clip that always fails, it does demonstrate the odd event of deleting the xmpses file as a workaround. I wonder if that will give adobe something to work with.
    Can anyone else get my clip to work/not work in a straight project?
    Test 4: Just to answer the question since the avi file fails here, will the elemental option succeed? I exported elemental m2v and wav from PPro, used the same project process, and transcoded the wav. That build also works! I have seen this work both ways. I have had projects where the elemental failed, and an avi export worked. I do believe the elemental options work more consistently. But my project that I completed yesterday used all avi exports, animated buttons in the submenu, - no pgc error.

  • When I try to burn a DVD in Premiere Elements 12 I get an Internal software error%0, line %

    When I try to burn a DVD in Premiere Elements 12, I get an Internal software error %0, line %1. This is the first time that I have tried to use this program.

    As suggested in the original reply in January, you will find best advice over on the video forum. Most of us here are photographers.
    Click on the link below and copy and paste your question again. Good luck.
    Video questions: Click here for Premiere Elements Forum

  • How do you get Encore to work? Internal software error.

    I've made a new project with Encore CS4 consisting of mainly slideshows and about 2 movie timelines. I've created menus to be how i want them.
    When i go to build the project about 9/10 it doesn;t work. Sometimes it just crashes and gives a crash report. other times it does all the building slideshows and motion menus then starts the prepare build and comes up with internal software error, and build stops.
    This is extremely frustrating as it takes serveral hours to get to this stage every time because it has to re build all the slideshows.
    It has only worked once, and it wasn;t quite what i wanted so i made some minor adjustments (added a pic in a slideshow, or music to a menu) and since have tried twice to rebuild it and it hasnt worked.
    Encore seems like it could be really good but all its bugs make it a piece of crap.

    I don't remember the dimensions, but I have read messages that pictures that are too large will cause problems... maybe someone will come along who knows the actual size and can tell you
    Also... This is aimed a Premiere Pro, but may help
    First, work through all of the steps here http://ppro.wikia.com/wiki/Troubleshooting
    If your problem isn't fixed after you follow all of the steps, report back with the DETAILS asked for in the questions at the end of that link

  • Error -20023 internal software error

    Hola a todos. Soy un nuevo usuario del labview y mientras intento aprender algo me he topado con un error que no entiendo a la salida de un filtro:
    Software error ocurred in no asociated comand id on axis control error -20023 internal software error please contact ni for suppor
    Lo que hace el programa no es problema. La cosa es que si quito el filtro funciona bien.
    Para hacerlo funcionar utilizamos una señal simulada de una 9239 creada con MAX.
    Si alguien puede darme alguna idea, se lo agradeceré un monton.
    Attachments:
    prueba3.vi ‏291 KB

    Hola Gonzalo el código de error es de un filtro y el VI que estas utilizando para interpretar los errores no te da una descripción adecuada porque ese es para Motion, y en este caso no lo estas usando por eso la descripción del error no tiene sentido.
    Aquí el erro puede ser por poner rangos inválidos en la frecuencia de muestre, o corte, o debido a que no hay información en el waveform. La siguiente liga tiene mas información:
    http://digital.ni.com/public.nsf/allkb/ABBD3A7BC25E17C8862561270058A4A0?OpenDocument
    Saludos
    Benjamin C
    Senior Systems Engineer // CLA // CLED // CTD

  • PPro6 to Encore "internal software" error

    I encoded in PPro6 and then imported an mpeg2 project as a timeline from PPro6 into Encore.  When I try to burn a DVD, I get an error message: PGC "" has an error at 00;00;00;00.  Internal software error: 50, line "" Info: name = "", ref= Bpgc, time = 00;00;00;00;00.
    The project was fully rendered in PPro.  I've re-exported 3 times, and it happens every time. 
    I did a search on the Forum, and found one other person who had this problem, but their problem turned out to be with their audio.  My project has no audio at all.  Just video.
    Thank you for any help/ideas/suggestions you may have! I'm totally flummoxed.

    Stan Jones wrote:
    The .xmpses file is an xml (type) file.
    Rename the file .xmpses.old and the .xmp renamed as .xmp.old (I don't recall for sure whether there was ever any benefit to renaming the .xmp file. We want to maximize the chances that it works, so rename both.)
    Can I just say Stan I am so so grateful for this post. So easy to do and solved my problem!!! I was beyond fed up with the whole thing. After having such problems with Dynamic Link causing slight flickering in my videos I have tried to go back to Exporting with my own settings for Encore in CS6 but found it caused so many more problems than it ever did in previous versions of the programmes. I tried exporting the sequences in so many different ways, different bit rates, including Encore chaptering before Encore and even nesting. Had so many different errors like 52102, line 332 and this PGC error was the final one and my biggest problem. Cannot believe how simple it was. I normally chapter within Encore anyway so changing a little file name of the other 2 connected files of my sequence really was no bother at all.
    I honestly think this is the answer to many of the problems that I have had in Encore as the errors although in different forms, more often than not, seem to be chapter related.
    it is now 1.45am and because of you I can now go to bed to get up and film another event in the morning. CHEERS! (don't worry I'm a girl lol)

  • Internal software error: .\PGCStreamInfo.cpp, line 1413

    Im designing a DVD teaching project within Encore DVD 2.0.0.48678 from the Creative Suite 2 Production Premium software system. The project is very large and complex. As of now there are only 2 separate timelines. 1st time line has 50 chapters. 2nd time line is not finished but currently has 15 chapters. Because its a teaching DVD, there are also chapter play list created for each individual chapter. I also have a countless number of menus and links to sub menus and additional video links from the chapter play list. All of my links are set and operational with all functions in the individual menus working properly. This is an ongoing project for 3 months now, with perfect results prior to today. I have used the "preview from here" function with no problems to test the links and verify the menu structures with flawless results for the past 3 months. Today I was giving a demo of my progress, when I selected the "preview from here" I received this new error message, "internal software error: .\PGCStreamInfo.cpp. line 1413". I have checked and rechecked links, buttons, playlists, chapters, end actions, timelines, basically everything I could imagine and have even tried a computer restore point from 5 days back, at this time still have not resolved this issue.
    AMD Athlon 64 3000+
    2.01 GHz 1.00 GB of RAM
    Microsoft Windows XP Home Edition Version 2002 SP2
    Gigabyte GeForce 7300 GT videocard
    Thanks for any suggestion, if more info is needed to solve this, i can provide it.

    There are a couple of other threads about a similar error which seem to point to a possible chapter playlist problem:
    Internal Software error ..... When 'preview from here' or Build
    Chapter Playlist play order bug?

  • Internal Software Error: %0

    I get the following error message after Encore 2.0 prepares the slideshows and goes to the next step. All of the video material is prepared and, the progress window is in the middle of "Planning Audio for movie". Any suggestions for a fix?
    Adobe Encore DVD
    PGC "Yosemite Valley" has an error at 00;00;20;04.
    internal software error: %0, line Yosemite Valley - PGC Info: name = Yosemite Valley, ref = Ipgc, time = 00:00:20:04
    OK
    Thanks.

    So, finally I've found the source of the problem and a workaround!
    First the source:
    when Encore has to transcode a video it must corrupt the file, because it's the transcoded file that causes the problem, I tried this by importing a transcoded file into Encore 1.5 there it came with the same error.
    Now the workaround, ok maybe it isn't quite a workaround but it's a way to go:
    What I did was: I built my project new in Encore 1.5, because Encore 2.0 has a problem importing the videos by me, but if you would just import the videos in 1.5 and let 1.5 transcode them so that all of them would fit on a DVD you should be able to import the transcoded files in CS3 and it should work, no guarantee.
    Other possibility: try opening your project in encore 2.0 and re import your videos there and let 2.0 do all of the transcoding, that might work too!
    But for certain: don't let encore CS3 do all the transcoding!
    I'm working with PAL files I don't know if it will be the same by NTSC, but it's worth a try!
    If anybody feels like reproducing the bug, here is the way to do it:
    Make a project in Encore CS3 and import Videos encoded by premiere as MPG2-DVD (I think: .m2v .wav) and set the transcoding options to automatic, encore should have to transcode the files. Then let encore make the DVD, at some point you should get that nice PGC error!

Maybe you are looking for

  • What causes redirection to another page on pageflow action?

    Hi, we are developing an enterprise web application on WLP 10.3 using Page Flow portlets. There's a requirement that users should be able to run the application simultaneously in multiple browser windows sharing the same session and we have noticed s

  • Doubt in MOVE statement

    what is the arrtibute value of this hex1 type .. in CL_ABAP_CHAR_UTILITIES. hex1 TYPE x VALUE '0D', my req is this value is in structure n data: begin of itab_input          c1(40) type c value 'hgfsdhfjsdf'.          hex1 type x value '0D',      end

  • Unwanted startup of Adobe Photoshop Album Starter Edition 3.0

    How do I stop Adobe Photoshop from instantly opening a CD of Pics. that I put into my drive. What I want is to be able to choose how & by what method I open that CD! Photoshop opens up the CD BEFORE I can even run a virus scan on the CD & by then it

  • How Iphone theft can be stopped (Apple please read this)

    Its good to hear all the time that apple has come up with an anti theft feature which has reduced theft of this lovely device by so much of percentage, but its still happening. Lets understand, if your iphone is stolen you put it on the lost mode and

  • Can you send mail at later time

    can I compose an email and set it to send at a later time?