LabVIEW FPGA Idea Exchange

About LabVIEW FPGA Idea Exchange

Have a LabVIEW FPGA Idea?

  1. Does your idea apply to LabVIEW in general? Get the best feedback by posting it on the original LabVIEW Idea Exchange.
  2. Browse by label or search in the LabVIEW FPGA Idea Exchange to see if your idea has previously been submitted. If your idea exists be sure to vote for the idea by giving it kudos to indicate your approval!
  3. If your idea has not been submitted click New Idea to submit a product idea to the LabVIEW FPGA Idea Exchange. Be sure to submit a separate post for each idea.
  4. Watch as the community gives your idea kudos and adds their input.
  5. As NI R&D considers the idea, they will change the idea status.
  6. Give kudos to other ideas that you would like to see in a future version of LabVIEW FPGA!
Top Kudoed Authors
User Kudos Count
Showing results for 
Search instead for 
Did you mean: 

Auto-Migrate to New RIO Target

I just manually transferred a fairly large LabVIEW FPGA project from one target to another (7965R to 7966R).  It would be nice to be able to click on the RIO target in the project and have an option to "Migrate to New FPGA Target" in the context menu.  The menu would open a new dialog where you could select the new RIO target and then it is automatically added to the project and populated the VIs, FIFOs, derived clocks, memory blocks, etc. from the original target.  The user can choose whether or not to delete the original RIO target.


This would also make it very easy for users to transfer sample code from the LabVIEW Example Finder to the correct FPGA target (insead of having the folder labeled "Move These Files").

Brian R.
District Sales Manager
Washington DC
National Instruments

This is a huge problem for us.  We have multiple targets running the same base code.  Right now we must use multiple FPGA projects for no reason.


Active Participant

I have a PXIe chassis with multiple 7966 modules (Multiple cameras). FPGA definitions (Memories, clocks, etc) should be able to be moved and copied to other compatible targets without having to manually redefine anything!  FPGA targets should also be able to be symlinked so that identical targets can exist in the same project.


Active Participant

This actually happens to be an issue for me as well

Please provide such a mechanism

Active Participant

We have switched over to a new cRIO platform, but still have several of the old. Need to keep two sets alive and need to copy and past across whenever a change is required.


This is not so much a feature as an essential part of the development environment.


Hope that this is being worked on as we speak.