I made a project with a few VIs in it. Every VI had its own VI description in that project. Then I build a llb from this VIs, to use them in several other project. The llb itself works as intended, but the VI description of every VI in this library is missing. What could have caused this? How can that be fixed?
I'm using LabVIEW 2016.
Related
My question is the following:
do I need to recompile all the VxWorks O.S. libraries for the target architecture each time I switch between my projects, one for Pentium M and one for Atom?
If this is the case, is there some smart strategy to shorten the procedure?
In the case you have sources of vxworks in your distribution you can create source build projects for each BSP and build them. These projects produces the complete set of libraries. You can create VIP (vxworks image project) based on source build project and your image will be linked with the libraries you produced. One thing to remember - the source build project doesn't contain sources, but only links on them, so if you will change the source in one source build project it will be changed in all projects and the next build will change the produces library. So be aware of it. Hope this will help you.
The trick is to use SCCS (source code control system, like git, cvs, clearcase, whatever), then create two local workspaces from the same repo (one for Pentium M, and the other for Atom). When you make changes in one workspace you commit the change to the repo, and then merge those changes into the other workspace.
I have a very simple yet crucial question:
There is a labview file (VI) that it contains some VIs related to a Tektronix oscilloscope and a motor driver. I have downloaded the drivers and VIs of these hardwares from their company website and added them to the labview file. Now here is the problem; each time that I open that labview file it starts to search for all the related VIs again.How can I solve this problem so there is no need to redo this procedure every time.
thanks
Saving the VIs after the first time LabVIEW searches for dependencies should solve this. It's recreating the links, which will be saved with the VIs save, so just make sure you have write access on all files, and you're fine.
I am trying to implement a custom IPCore for the Zedboard. In my User_Logic I am including a component (My_Module) from the VHDL module (My_Module.vhd) which I wrote as part of the ISE project. But when I come to generate the bitstream for my design in PlanAhead it asks for the My_Module.ngc as if it is treating it as a blackbox. I though the NGC was only required when using CoreGen IPCores, but it seems it also wants it for any VHDL module included as I guess this is a 'black box'.
The issue is how do I create a NGC file from the VHDL for this module, which is part of an ISE project. As I can't find any function in ISE that allows you to just generate the netlist for one VHDL module. Or can I export this module out into a separate ISE project and then synthesise it to get the .ngc?
Many thanks
Sam
Are you sure you've typed the module name in exactly the same way both in your module .vhd file, and in the file using the module as a component?
Under normal circumstances, if your project includes the module as a .vhd file, it'll just be synthesized along with the rest of your sources - I did a quick test and renamed a component in one of my own projects, and got a complaint about a possibly missing .ngc file (this was in ISE, and not in PlanAhead though).
So the answer is to generate the NGC files by making the modules you want "the top module" you can then run the synthesis to generate the individual NGC. Then proceed as normal when adding IP to a PCore. So adding these NGC files to the netlist folder and modifying the BBD file and all that!
As a note for completion to get the module working you need to set the synthesis setting "Xilinx Specefic" -> and disable "add io buffers"
Are you including My_Module.vhd as a source file in your ISE Project? If you are, check to see that the ISE project doesn't have a yellow question mark next to the My_Module component. If it does, then it needs more information about that component. You should see a little icon with the letters VHD in it in your ISE Implementation Hierarchy View.
I am developing a data acquisition program in Labview that uses multiple translation stages, cameras, a high speed digitizer, and other instrumentation. I'm developing the application on one computer, and will be deploying it to another computer. The development computer has labview 2013, and computer the application will be deployed on currently has Labview 2012, but we will be upgrading it to Labview 2013 when we move the application over there. Some of the drivers need different versions of the driver to function under Labview 2012 than they do for Labview 2013.
I'm trying to keep all of the vi's, subvi's, and drivers for the instrumentation in one directory tree so that I can move the whole tree over to the computer it will be deployed on.
When I load the project in Labview I'm getting a lot of "Resolve Load Conflict" dialog boxes popping up. When I go to investigate, Labview says it can't find one of the files that is causing the conflict, but yet it popping up the dialog. An example is below:
This happens every time I load this project - saving all doesn't enter the new paths into Labview. I also tried creating a new project, and pulling these vi's in, but the new project has the same load conflicts.
Evidently Labview or these vis think that these vi's that no longer exist are still there.
How do I fix my project, vi's, or Labview so that it only uses the vi's that it should, and I don't get all of these conflicts, many of which are with nonexistent files?
I just had this same problem, but solved it like so:
In your project window, expand the Dependencies group. You should see each of the undesired subvi's listed there.
Right click on each one and select 'Replace with item found by project...'. This will bring up the familiar conflict resolution dialog box, go ahead and select the proper path and click OK.
Now, because the dependency has changed, Labview is going to change the dependency path that is saved in the calling VI. You'll see a save dialog asking if you want to save the changes to the VI(s) that is/are calling the dependency whose path you just changed. You want to save changes.
Do this for all the dependencies and you should be good to go.
I've found that when it is necessary to move driver files and libraries from the NI default locations, renaming the files prevents further confusion.
For instance if you have a "instr.vi" that you need to move to a custom directory location, renaming the file "my_instr.vi" and linking to the renamed file prevents future conflicts.
Of course, this may initially involve some amount of work in renaming all the files and then directing your calling VIs to use these newly renamed driver files, but after that initial time invest you shouldn't have any more problems.
Flash Builder 4.7 has very nice setting dialogues for AIR compilation.
Is there a way to dump/display the full command line Flash Builder using when it compiling ipa file?
The reason why I’m asking for this, is because, it is very frustrating when hand code adt compilation command line for a project with a good number of assets, as well as a couple of ANEs.
Thanks,
Flash Builder uses Java to trigger the adt.jar file to compile a project. You have to get the parameters of the Java executable process in order to find the command being executed.
You can do this on Windows through the ProcessExplorer tool. Just select the java.exe process and inspect its properties. There's a command-line text field in one of the properties tab.
It's a little more complicated on OS X. First, use the Activity Monitor to get the process ID of the java executable. Launch a new terminal window and type the following statement
ps -p PROCESS_ID | open -tf
Replace PROCESS_ID with the actual number from Activity Monitor. The result will be displayed in a new TextEdit window.
Note that there may be multiple instances of the Java executable. Just select the first one launched, i.e. the one with the lowest process ID among all the instances of java.