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.
Related
I'm a hardware/software developer and prefer to keep my source files on an external USB drive or thumbdrive. The problem I've been facing for years it seems is when I try to save these files. When I save a file and then compile I occasionally get syntax errors on lines that don't even exist in my source. For example it will complain about line 83 when my source file is only 80 lines long. Lets say I have the file open in a particular editor (I prefer Programmers Notepad or Notepad++) and see only 80 lines... I can save but then if I pop open the same file in parallel using something like Wordpad sure enough... I see the extra lines and it looks like the last few lines of real code got munged and then appended to the end of the file.
At first I thought it was the editor but have found that no matter what editor I use it happens fairly frequently. I recently upgraded to a new laptop and OS (From Win7 to Win10) and lo and behold the same problem exists here. Tried different USB drives/sticks.... same deal. Am I missing something??? This problem has been driving me bonkers! :P
How to use labview real-time module to catch .txt file in D disk ?
I would like to use myRIO project.
In case you are trying to open a file on your PC, as suggested by #Khachik,
I'd recommend reading this white paper: Best Practices for Target File IO with LabVIEW Real-Time. The best solution to your problem depends on what you are trying to achieve.
An option could be to transfer your file to the target using FTP and then read it from your code, taking care of properly formattig the path depending on the Real Time operating system you have.
Years ago I began scanning my "important" documents using Pagis, software that came with my HP Scanner. Eventually I began to scan to PDF (as the scanner software became able), but I still had many old XIF file. The Pagis software would run only on 32 bit OS (Windows) which is now becoming less and less common. In fact I have a Win32 system I've kept alive just to retain access to the XIF files.
I can convert these files using Adobe Acrobat (or equivalent) "simply" by opening the XIF viewer, then printing the doc to the Adobe PDF "printer". Unfortunately I have enough files that this manual process would take many years.
So, what's the best way to convert a large number of XIF files to PDF?
I recently found SikuliX, a scripting tool intended mainly for testing GUI. It is different from most such tools I have seen (e.g., Selenium) in that it is purely image based and cares not what the underlying technology is (HTML, XAML, etc.)
It took me about an hour to learn enough to write a script to open the XIF viewer, select the PDF "printer", click the button to print, fill in the desired output file name (XIF viewer truncated to short name if left alone), and then wait for the print to complete. The script then moved to the next XIF file. (I fed the script a file listing all of the XIF file paths on the drive.) I was using Nitro PDF rather than Adobe.
The script ran for a couple of days (I didn't say it was fast!), but converted all but a few of the files. From time to time it would stall and I'd have to modify the script a bit (increase wait time for UI to change, etc.)
There are probably not many folks facing this particular conversion problem, but I've been looking for a good solution literally for years. So, if you're in the same boat then this is a way to get to shore!
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.
I am facing problem while generating CAB file. I want to customize the INF file generation depending upon what components I choose to package. At present, we need to modify the INF file manually to include/exclude the components. I would just like to know, is there any programmatic interface where I will give the paths of the components to be packaged and it will give me INF file. This file I will provide to cabwiz.exe to generate the CAB archive. I am searching this type of solution because I want to avoid VS installation on non-developer's machine.
Thanks,
Omky
I'm not aware of any "programmatic interface for INF generation", but that said, it would be pretty trivial to create one. The INF format is pretty straightforward with not a lot of sections or options, and many of which you can safely ignore.
I created a tool some time back that generated an INF that would parse a desktop file/directory tree and generate an INFo that would replicate the same tree on the device with the same files. Basically you'd build the tree on the PC that you wanted on the device and the tool would read what you had, build an INF and then package it (I'd actually post the code, but I can't find it offhand). It took maybe an hour to write.