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
1
1
cancel
Showing results for 
Search instead for 
Did you mean: 

Make Bitfile Paths Relative, Not Absolute

Currently when you build a VI the bit file path is stored as relative (you can see it in the project XML). This means if you change the project location either:

 

  • Moving machines.
  • Checking in and out of source code control on different machines

You have to recompile the FPGA to use VI mode or run interactively. It seems the bitfile could be stored as a relative path like all VIs in the projects.

 

Cheers,

James

James Mc
========
CLA and cRIO Fanatic
My writings on LabVIEW Development are at devs.wiresmithtech.com
6 Comments
Active Participant

I believe this is already addressed in 2013. Check out the new Open Dynamic Bitfile Reference function to reference an FPGA bitfile by path at run time when communicating with an FPGA target. Using this new function should entirely mitigate the problem... If I understand your idea correctly. Just use the Application Directory node (or whichever node is relevant) and build the path at runtime.

 

 - TJ

Cheers!

TJ G
Active Participant

That certainly helps but I am also thinking about the project link so that it would still be able to run interactively or using the VI option in FPGA Open Reference even after moving computers.

James Mc
========
CLA and cRIO Fanatic
My writings on LabVIEW Development are at devs.wiresmithtech.com
Active Participant

I agree that this can be a very annoying problem.  The bitfile path seems to be the only type of item in the project file that gets stored as an absolute path, which doesn't make much sense.  Accessing the bitfile programmatically isn't really a problem, even prior to LabVIEW 2013.  The problem is with having to recompile after moving a folder in order to run in interactive mode.

Member

We run into this problem every day (using LV2012) and the way we get around it is to use a PC layer and reference the bitfile.  It does require duplicating the FPGA VI's front panel on the PC layer and wiring the controls and indicators up to an FPGA Read/Write Control node, but that is a thousand times faster than waiting for a recompile!

Member D*
Member

CMal, How do you do "Accessing the bitfile programmatically isn't really a problem, even prior to LabVIEW 2013"?

 

I'm using LV 2012, but the "Open Dynamic Bitfile Reference" appears to be LV2013?

Member PBP
Member

I have also faced this problem but now What I do is I go to FPGA build specification properties and change bitfile name to previous complile name. This works if you have just moved your code from one location to another without changing in FPGA VI.

 

Second problem is host VI shows error. For this I right click to "Open FPGA VI Reference" VI and Configure Open FPGA VI Reference option and repoint to build specification.

 

Above steps always solves my problem incase of source code is transffered from on PC to other PC or change source code location.

PBP (CLAD)
Labview 6.1 - 2014
KUDOS ARE WELCOMED.
If your problem get solved then mark as solution.