Jump to content

NI 9213 not working in FPGA with other modules


Recommended Posts

Hello everyone,

Note: I have tried to post this on the NI Discussion Forums but it is "under review"...

I am trying to get my FPGA program working. I have been able to get the first three modules working (at least not throwing an error when the FPGA starts I haven't actually tested data though put yet) but no matter what I do I can't get the 9213 to work except an empty example project. If I diagram disable the loop with the NI 9213 (Module 4) calls in it the FPGA will run with no errors.

Here is the error I keep getting :

Error -61017 occurred at Open FPGA VI Reference in NI 9213 Getting Started (Host)ud.vi
Possible reason(s):
LabVIEW FPGA: You must recompile the VI for the selected target.
=========================
LabVIEW FPGA: You must recompile the VI for the selected target.

Here is my setup: 
LabVIEW 2024 Q1
cRIO-9064 (Firmware: 24.0.04129, OS: NI Linux Real-Time ARMv7-A 4.14.146-rt67)
Slot 1, NI 9203
Slot 2, NI 9265
Slot 3, NI 9474
Slot 4, NI 9213

As a test I used the NI 9213 Getting Started.lvproj from the example finder to verify that the module by it self would work. And it does. 

To make the example work with my system;
* Create a copy of the example
* Right click the Project name -> Add Target and Devices
* Select Existing target or devices -> Discover an existing target(s) or devices(s) -> Real-Time CompactRIO -> Select my cRIO
* Click OK
* Select LabVIEW FPGA Interface
* Click Continue
* Click Discover
* Copy the NI 9213 Getting Started (Host).vi from the sample cRIO to my cRIO
* Copy the NI 9213 Getting Started (FPGA).vi from the sample cRIO/FPGA Target to my cRIO/FPGA Target 
* Create and Build a Build Specification for the NI 9213 Getting Started (FPGA).vi 
* Open the NI 9213 Getting Started (Host).vi and right click the Open FPGA VI Reference select Configure Open FPGA VI Reference
* Select the Build Specification created above
* Click OK 
* (optional) Add an probe on the Error wire between the Open FPGA VI Reference and the Reset (Invoke Method) 
* Click Run at the top

Next I added a second loop in the NI 9213 Getting Started (FPGA).vi and added in the channels for the other modules. It will compile just fine but as soon as I try to run it it, the Open FPGA VI Reference throws the above error... again (See the NI 9213 Getting Started (FPGA) - w other modules.vi, The top loop is the added modules and the bottom loop is the untouched loop from the example)

Next I disabled the new loop and recompile and it still throws the same error. You can see the diagram disable statement around the top loop. 

Next I deleted the new loop and recompile and it still throws the same error. (saved the NI 9213 Getting Started (FPGA).vi as a new vi so I could keep the previous one as a sample and created a new build specification)

Next, in the project I disconnected from the cRIO, changed it's IP address to 0.0.0.0 and re-added my cRIO again (same steps above to add my cRIO to the sample project). This time I added the re-named NI 9213 Getting Started (FPGA).vi to my FPGA and recompiled again, and it works. 

So a few comments / observations,
1. In the attached vi, in the bottom loop, the case structure that is connected to the error wire, I can't use that in the top loop. I tried to reproduce this in my original project and I had to use Error State boolean from the unbundle by name in both loops. This seems odd to me.
2. I am not worried about the timing right now. The only thing I really want the FPGA for is to create a PWM output from one of the DO channels. If I can't figure this out by Monday I am going to try to switch to Mixed Mode and put everything except the DO module on the Scan interface. 

I have done similar things to this in the past but I can't figure this out. 

Any help would be appreciated.

Thanks, Ryan

NI 9213 Getting Started (FPGA) - w other modules.jpg

NI 9213 Getting Started.zip

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.