Errors in the "Getting Started with the FPGA Module" examples

[afd-2000]

We have LabView 8.0, the NI-5640R, and the LabView FPGA module installed on a computer with the IF-RIO board, and we are trying to compile the provided NI examples (NI-5640R documentation), but we receive errors that say "sub VI is not executable" and "you have connected terminals of two different types"  Why are the existing NI VI's not compiling properly?  We are guessing that we have some configuration error, though we aren't sure.

[JerryAL]

Hi - Where specifically are you getting this error?  During the compilation process?  Or after when you try to run the example?

I'm assuming the FPGA VIs have good run arrows (vs broken run arrows) before you start to compile.  If they are broken before you start to compile, LabVIEW shoudl highlight where the mismatch is.

Jerry

J

[afd-2000]

The run error is broken and gives the option to list and locate errors, though these errors are found everywhere in the files that are provided in the NI-5640R.  Several wires have red x's that say that different types are attempting to be wired, and multiple blocks are highlighted that list errors that say that the blocks cannot be activated.  It seems like there is a problem with how the software and board has been installed.  The group that used the board before us had a functioning project, although they but the IF-RIO in their own computers, so they might not have put everything back together properly.  Their old VI's produce the same errors on our computer.  Do you have any suggestions on what to do? 

[JerryAL]

Hi

Is the broken run arrow on the Host VI or the FPGA VI?

If it is on the Host VI, it may be that the FPGA Refernce has not been binded.  Go to the diagram and find the Open FPGA VI Reference VI.  Right click on the VI and select "Bind to Typedef..." from the pop up menu.  This should bind the references in all the subVIs to the same control.  This varies depending what FPGA VI is used with the Open FPGA VI Reference VI.

If it is on the FPGA VI, there might be something common missing, such as a subVI.  Other wise each reason that a wire is broken must be identidfied and fixed before the FPGA VI can be compiled.

Jerry

[JerryAL]

Hi

As another suggestion to check, check to make sure that the VI that has the broken Run arrow is actually set to run in the correct target?

A VI programmed to run on the Host will have a lot of errors when targeted to the FPGA, and vice versa.

You can check by looking in the bottom left hand part of the VI Window.  It will either say something like “My Computer”(Host) or “FPGA Target.

Jerry