Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bitfile path on target is hard to work with. #321

Open
theSloopJohnB opened this issue Jun 7, 2017 · 2 comments
Open

Bitfile path on target is hard to work with. #321

theSloopJohnB opened this issue Jun 7, 2017 · 2 comments
Labels

Comments

@theSloopJohnB
Copy link
Contributor

I've been having some trouble with the 'bitfile path on target relative to root' field that's on the cRIO configuration.

It says 'relative to /home/lvuser' but when I put the file name in the error message indicates that it tries to load it from the root directory.

Here's a snippet to illustrate the problem:

image

I also can't really edit the bitfile path on target field because LabVIEW 'helpfully' converts my path to windows style. Maybe we should use a string here.

@pollockm
Copy link
Contributor

pollockm commented Jun 7, 2017

Yeah, the utter worthlessness of the path control when working on a cross-target application is a sore spot with us. We've done some work on other modules (TDMS included) to swap in a string or a path control depending on which target is being used. There is also some ugly string parsing work put in previously to "de-correct" the path. @becega might be able to comment as to where that lived.

@jacobson3
Copy link
Member

Two users running into same problem on our forums.

https://forums.ni.com/t5/Distributed-Control-Automation/Problem-with-FPGA-configuration-in-DCAF/gpm-p/3808768

@becega , maybe we should add this to the ToDo list.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants