'Clone' of the project library (.lvlib)

We have a study on sound localization - move us a speaker with a robotic arm, play sound through the speaker, ask our subjects to point a laser where they perceive the location of the sound and press a button. We can also turn on LEDs and lasers, adjust sync settings, even to move the sound source. The various tests are "programmed" by entries into an Excel workbook with columns for the timing, healthy situation, sound settings, etc. In addition to the Excel workbook, we generate 3 output files - a header file XML that describes the configuration of the recording (analog and digital channel names and scales) and saves the settings of each trial as it is executed, an XML event which records all of the events of "point-in-time", such as Messages, status changes, or modifies the digital I/o, and a file of examples that contains N (usually 16) sampled analog and digital channels sampled at 1 kHz. We control all of this a LabVIEW Real-time project, which also includes routines to study, manipulate and analyze data of output files.

The project evolves (slowly) - we are currently at Version 2.0 (Version 1.x was developed in LabVIEW 7.0, this is the complete rewrite 2012/2014, "start from scratch and do it right, or at least better"). We are contemplating adding the ability to study the sounds delivered via stereo headphones (vary the volume from left to right or by adding a small time gap between channels) and calls this Version 2.1.

To try and prevent "Version hell", we intend to do "backward compatibility" Versions - we will Add some new columns to the workbook Excel for new parameters in headphones, but put in place LabVIEW code to simply "do nothing" (with headphones) if he reads a Version 2.0 workbook where these parameters are lacking. This allows us to code of Version 2.1 allows to make a Version 2.0 experience.

We are faced with one of the problems are to know how read and analyze or manipulate data files resulting. For example, the header file contains specific sets the version of the data, which are analyzed by the XML parser and converted directly into a Cluster of LabVIEW. Thus a Version 2.0 file must be read by the code who "knows" a Cluster of Trial Version 2.0, whereas a 2.1 file needs a trial 2.1 Cluster.

When I read the header file, the first thing I encounter is the Version number (2.0 or 2.1). Knowing this, I could, in principle, use a Case statement to call a Version 2.0 or Version 2.1 analysis routine. But I am trying to 'avoid a mess', and libraries in the project seems a good way to do so, if I understand how to use them properly.

[For now, I have to say that I tried a little experiment: I have created a new project, built Library1 in a folder with a 'Hello' and 'Test' Library1, built the library 2 (inside the folder library 2) with 'Hello' and 'Test' (different) and called the high-level.] Worked well. I then "took a shortcut" and copied the folder Library1 (outside of LabVIEW) on the menaces3. When I said that the project to add 3 library, I had a mess of conflicts, which I couldn't resolve. And I "broke" LabVIEW - even after removing all the .lvlib and the .lvproj files, I couldn't create a project and make a folder to add (Snapshot) without a missing file error to appear. I did the experiment using LabVIEW 2012 - this problem has affected not only LabVIEW 2012, but also 2013 LabVIEW and LabVIEW 2014, but not LabVIEW 2011. I spoke with the support of OR, which are also puzzled. I am currently working in a new virtual machine until I can get LabVIEW "repaired"].

What I want to do is identify all Version-specific routines in my folder of analysis and include data in this case TypeDefs for the Version-specific parts. I would then "wrap" all this in a project library Version 2.0. The code "on the outside" would have its own copy of TypeDefs (she could use the "Latest Version", as external routines are supposed to be 'backward compatibility'.

So here are my questions.

Suppose that I restructured my project so that I have a record, both "Real" and "Virtual" (in the project) parsing, and it contains a subfolder called Version 2.0 that contains the Version-specific TypeDefs and most of parsing code. Is there an easy way to transform the Version 2.0 to Version 2.0 Library folder so that when I call functions in this library, they use Version 2.0 of the TypeDefs of the library, regardless of the TypeDefs declared in the main routine?

Assuming that I have a folder of Version 2.0 of work and the library, is there an easy way to "clone" to make a folder of Version 2.1 and the library? If so, all I would need to do the "work" for Version 2.1 of the code would replace TypeDefs of Version 2.0 in the file of Version 2.1 with the "correct" TypeDefs, and (b) add any additional analysis code is required for the new features in the new Version.

I apologize for the long-winded nature of this issue. I look for tutorials on libraries of the project (there are), but none covered this topic. To pay for your patience, I am happy to write and submit to the OR for a future white paper on libraries of the project - which would speak?

Bob Schor

PS - Moderator - if it belongs to another Forum, feel free to move it.

On the money Bob! Save under... Duplicate the hierarchy to the new location (requires that the new library offers a new name)

To convert a virtual folder to a lvlib just to create a new lvlib in the project and move the project members want in the new lvlib Project Explorer does the rest of the book nitty gritty on registration of the members of the lvlib with the new property information. (You will be prompted to save the members when the composition is changed)

And Yes, it's the kind of mistake you don't do twice. And, believe it or not, I had this type of issue used to justify not using projects! "they are too much hassle when you mud round in windows Explorer ' then I asked them if the never borrowed the car of their father and did not him tell you parked above on the next Street. They now use projects.

Tags: NI Software

Similar Questions

Problem with icons of the LV2012 library (.lvlib)

Hello

Using LabVIEW 2012 Full version (32-bit) on Windows 7 (64-bit).

I create a project library (.lvlib) and add a bunch of screws.
I create a banner library icon and apply icon library of all the screws in the library.
I then change the icons of all the screws in the library, add additional layers, so that each VI icon has a layer called "NI_Library" (the banner library icon) and a bunch of other layers.
So far so good.

I have then change the library icon and apply the change to all the icons in the library.
I open to the top of the screw in the library and find that all the extra layers that I added to each icon previously were wiped out. All my cancelled work.
Now each VI has 3 layers: NI_Library, NI_IconNumber and VI icon and none of my other layers.

I am sure that this has not happened in LabVIEW 2011. IN LabVIEW 2011, if I changed the icon libray and apply the change to all the screws in the library, only the layer of "NI_Library" has changed, all other layers remained intact.

Is this a known issue? Surely this can't be the way it is supposed to work? Or I'm things misunderstanding?

It's a bug that has been fixed in 2012SP1. My apologies for the great inconvenience.

How to see the Images in the project of addiction?

Hi all

I have two projects, one dependent on the other, I did a project in the project library, and the other as a CLDC Application. I have some images stored in the library project, and I want to access that images of the CLDC Application. I don't know how to access the images by hint which way. Any body know the solution please help me.

Thank you and best regards,

Rajapandian.K

I had to help someone with something similar to this:

http://supportforums.BlackBerry.com/T5/Java-development/how-can-I-place-resources-in-a-separate-cod/...

You can add an extra function so that she gets the EncodedImage and returns.

In fact, I just realized that EncodedImage.getEncodedImageResource has support for the specification of the module that contains the resource.

RTE de LV cannot open the project files that include references .lvlib in dependencies

I am writing a DLL LabVIEW to inspect the LabVIEW project files, and I noticed that if a project has a .lvlib reference in its dependencies, then the Run-Time Engine is contradictory on whether or not he can find the project file:
- Project.Open returns error 7 (file not found)
- Project.GetFileLVVersion is a success
Here are some excerpts from my code of G and C engaged in this behavior:
```
   int openStatus = StatusSuccess;

   char * projectVersion = createStringWithLength (VersionStringLength);
printf ("Analysis %s\n", pathchaine);

   OpenProject (pathchaine & openStatus, projectVersion, VersionStringLength);

   printf ("  project written in LabVIEW %s\n", projectVersion);
If (openStatus is StatusSuccess)

   {

      printf ("  Open the project file.") \n") ;

   }

   on the other

   {

      printf("Error: could not find Project file, or file was not a Project file (Error code %i).\n», openStatus);")

   }
```
However, when running in the development environment, the two methods are successful.

Is this a bug, and if so, is it fixed in 2014 of LabVIEW?

Here's how you can reproduce:

Prerequisites:
reference .lvlib to break dependencies Project.Open in LV RTE
```
$ make

patch the file "builds/platdefines.h.

GCC - std = c99 g OpenProject.c o OpenProject.exe - lOpenProject - Lbuilds
```
6. type "c:\xtra\temp\OpenProject.lvproj" OpenProject
```
OpenProject $ 'c:\xtra\temp\OpenProject.lvproj '.

Analysis c:\xtra\temp\OpenProject.lvproj

  Project written in LabVIEW 13.0

  Open the project file.
```
7. the opinion that both call nodes execute correctly.

8. type "c:\xtra\temp\OpenProjectWithLvlibDep.lvproj" OpenProject
```
OpenProject $ 'c:\xtra\temp\OpenProjectWithLvlibDep.lvproj '.

Analysis c:\xtra\temp\OpenProjectWithLvlibDep.lvproj

  Project written in LabVIEW 13.0

Error: Could not find the project file or file was not a project file (error code 7).
```
9. notice that the node version managed while the open failure.

10 type diff OpenProject.lvproj OpenProjectWithLvlibDep.lvproj
```
$ diff-u OpenProject.lvproj OpenProjectWithLvlibDep.lvproj

-OpenProject.lvproj  kills Nov  4 11:28:28 2014

+++ OpenProjectWithLvlibDep.lvproj      kills Nov  4 11:32:37 2014

@@-13,7 + 13.11 @.

       true

       fake

       

-      

+      

+          

+              

+          

+      

       

          

             true
```
Here's another way to trigger this behavior, which shows that LabVIEW occasionally Range the element dependencies:
Add to the project a new VI and place the constant path of file "Application Directory" his block diagram.

Select ""leader "Save All (this project)" and use the default name for the new VI.

Type 'c:\xtra\temp\OpenProject.lvproj' OpenProject

Notice that there is a mistake once again, as is expected.

Remove the "Application Directory" path of file constant

Select ""leader "Save All (this project)"

Type 'c:\xtra\temp\OpenProject.lvproj' OpenProject

Note that the problem has disappeared, as is expected.

Add the "Application Directory" path of file constant in the block diagram.

Select ""leader "Save All (this project)"

Type 'c:\xtra\temp\OpenProject.lvproj' OpenProject

Notice there is no problem, which is surprising, because that there should be a mistake because the dependencies item was not tidy.

Close the new VI and pull out of the project.

Select ""leader "Save All (this project)"

Open "OpenProject.lvproj" in a text editor.

Note that the dependencies item was put away.

Add VI back to the project.

Select ""leader "Save All (this project)"

Type 'c:\xtra\temp\OpenProject.lvproj' OpenProject

Notice that there is a mistake once again, as is expected.

NInjaneer_wow wrote:

The same behavior occurs in LabVIEW RTE: a new project with a constant of the Application in an empty vi directory will return an error 7 - file not found, but still return the correct version of LabVIEW in which the project was created.

I did experiment with workarounds for this problem, and I found a.

When I used to get the path of LabVIEW libdir in the ini of the executable file, execution is able to load and inspect the project file.

LIBDIR = 'C:\Program NIUninstaller Instruments\LabVIEW 2013'

While it is expected that a stand-alone executable can be placed on a system that does not have the LabVIEW IDE, it is still surprising to me that the execution engine cannot find standard library of LabVIEW without some explicit guidance. What other factors contribute to this behavior?

References:

Configuration of LabVIEW files and paths- http://labviewwiki.org/LabVIEW_configuration_file/Paths

What is the right way to specify the location of the shared library in an a .lvlib function call library function node?

I'll have a bit of a problem with how to specify the location of library shared in a call library function node it is a VI that is part of a library of LV. Here's a little background which may help.

I do a lot of measures using spectrometers photo from several manufacturers. Someone in my company developed a C DLL library, which provides a simple API for all the different spectrometers. To facilitate this DLL to use in LabVIEW, I wrote a .lvlib that wraps all the functions. When I want to use the API, I simply include the .lvlib file in my project that allows me to drag and drop the wrapper s VI on my block diagram. When I created the .lvlib of VI, I specified the path in the call library node. /. * so it will always look in the local application to the DLL directory when I run.

The problem is, when I load demand, LabVIEW you asks for the location of the DLL even if it's just there in the local directory! I tried to put copies of the DLL in the directory with the .lvlib, but he still refuses to find the DLL loading. What I am doing wrong?

You should in this simple case enter the full path to the DLL by navigating to it. If the DLL is on the same volume/drive that the VI containing the call library node LabVIEW will be internally store the relative path from the VI to the DLL (but still show the absolute path). If you move the DLL and screw together (so the relative location of the DLL to the VI remains the same) LabVIEW will always find the DLL.

I don't think that the lvlib would add nothing to that.

How to access a global variable that is common between the different baskets project library

My project consist of several libraries, after generation the library project packed for each library, I find it cannot share data in a global variable between different packaged project library file. For example: packed project library #1 contains VI variables global wirte 'position' and give it a value '400 '. Library #2 present another VI project try to read this global variable, but he gave reading of is NULL not "400". Why has this happened? Is it possible to solve, welcome any help, I wll appreciate for this!

If you understand what is happening here...

When you build a PPL, it takes in the .lvlib and also all the dependencies of the .lvlib.

In your case, when you generate the Test Task.lvlib in a .lvlibp, she also pulls on a copy of the DataProcess.lvlib:GlobalsVariable.vi because it's addictive to read GlobalVar.vi.

When your application runs, you end up with two copies of GlobalsVariable.vi in memory:

DataProcess.lvlibp:GlobalsVariable.vi

AND

Test Task.lvlibp:: GlobalsVariable.vi (I don't know how PPLs namespace dependencies... If there is still the DataProcess.lvlibp)

Because they are different screws (i.e. in a different namespace), they have their own memory and that's why you can't access the data.

Your Test Task.lvlibp calls the version of GlobalsVariable.vi, he pulled the dependencies.

To solve this problem - you must ensure that Task.lvlibp of Test calls the version of GlobalsVariable.vi of the DataProcess.lvlibp - you'll need to replace all instances with the version of the PPL. Of course, if you run DataProcess in the development environment, then it will always be bad namespaced, hence the suggestion to put your global variable VI in is own PPL that you then use in the process of data and Test tasks.

Get the dependencies of VI in a packaged project library

I'm building a test sequencer which uses packaged libraries to the project. I want to be able to get the path to a VI that is part of the packed but not explicitly part of the lvlib the PPL has been built since. If I'm trying to get dependencies VI library or any VI in the library by using the method of getting the dead VI, I get only the dependencies that are explicitly part of the lvlib, even though I see clearly that there are screws that are part of the packed library, I can open them , and I can view the code.

Background:

My test of libraries have an entrance variant on which I set a global variable used byt the sequencer of test. While the tests can have access to these global variables, I want to decompress values of type variant and write them on local copy (namespaced) of the test of the global step. This function works, but to use it, I need the way access to the copy of the lvlibp global. I tried wiring, the name of VI, because I know it's in memory, but it returns an error. I also tried wiring the VI name prefixed by the name of the lblibp, following the format used in the title bar of the global open in the packed library.

I do not want to include the global in the library explicitly, because it will be used by other libraries. I could deploy the global library packed own ots, but I wanted to see if I could make this work, a s it seem elegant and transparent for the other people in my group try to use (just use this world!) and it requires less files to deploy.

In addition to experimentation, I found that you can open a reference to any VI in a packed using the string library name:

error-5093 "the analysis library is not found" in the 64-bit project. But the analysis library is located in the 32-bit project

Hello

I use the system of Labwindows/CVI 2010 full development in a Windows 7 Professional 64-bit computer. Thus, the analysis library is installed (see the attached file) and the analysis of the options to customize menu library is selected.

I use several function analysis library (WhiteNoise, MaxMin1D, LinFit, etc.). 32-bit projects work very well. 64-bit project there is not link error, the exe file is created, but there are errors like this:

Function WhiteNoise: (return value is 5093 [0xffffffffffffec1b]). The analysis DLL library is not found or cannot be loaded.

Ditto for the other functions of analysis library.

How to use the analysis in 64-bit projects library, is the library of analysis 64 bit compatible?

Thanks in advance

Hi DansatB,

Thank you for posting on this forum!

Yes, the advanced analysis library is 64-bit capable. I can do the test on my computer the CVI 2013.

I think it'll be great correctly uninstall your version CVI all ANS reinstall.

Concerning

Impossible to include the static library containing the QObject class in Cascades project

I'm working on the new platform BB10 based on Qt.

I have a static library project that defines a QObject class (essentially the class sends signals and a few locations). The project compiles fine and gives me a file libwhathever.a nice

When I try to include this library in my project of stunts I get these errors during construction:
- undefined references to com::vasco:digipass:sdk:utils:qrcodescanner:MyClass:staticMetaObject
- undefined reference to com::vasco:digipass:sdk:utils:qrcodescanner:MyClass:newQRCodeDetected (QString)
- location reference external com::vasco:digipass:sdk:utils:qrcodescanner:MyClass:staticMetaObject undefined: c:\Developer\bbndk\target_10_1_0_2342\qnx6\usr\include\qt4\QtCore\qobject.h
- location reference external com::vasco:digipass:sdk:utils:qrcodescanner:MyClass:staticMetaObject undefined: c:\Developer\bbndk\target_10_1_0_2342\qnx6\usr\include\qt4\QtDeclarative\qdeclarative.h
- location reference external com::vasco:digipass:sdk:utils:qrcodescanner:MyClass:staticMetaObject undefined: c:\Developer\bbndk\target_10_1_0_2342\qnx6\usr\include\qt4\QtDeclarative\qdeclarative.h
- no reference to vtable for com::vasco:digipass:sdk:utils:qrcodescanner:MyClass
- no reference to vtable for com::vasco:digipass:sdk:utils:qrcodescanner:MyClass
I think that I miss the compilation step where the Q_OBJECT macro is run. I'm on the right track? I've heard talk about moc and qmake, but I don't know how or when to use in my build process.

In fact, I solved my problem simply by running the moc on the header file defining the Q_OBJECT. It generated the file moc, that I needed. Then my ant script does the rest of the compilation with qcc and my indefinite references have disappeared.

Can AE copy a good imported from the library of cloud in the folder that the file of the project resides in?

Currently, it seems any assets that you import from the library is saved in your user and not side by side with the project file. First will create a folder "CC libraries downloads" which makes much more sense...
Or am I wrong?
Thank you
Ryan

In a future update, we intend to make the location to which the library assets are recorded an option defined by the user.

How to consume the data model library adf for the project?
Hello

I use Jdev 11.1.1.6.

I have a workspace Jdev containing the business component (entity objects, view and application module objects exposing the your). This workspace is deployed to a library of the ADF. This library is packed with DB connection details.

I have a different workspace Jdev which needs to consume this library of ADF data model. This workspace is actually just the layer view (no business at all components).
I added the data library ADF model to his draft opinion and it is showing application module and your sub of the data controls.

My question is: how will this project view to connect to DB when running?
It allows the connection of packaged data model ADF Libabry? If so, how?
or should I create a business under this workspace view, just the purpose of connection project? If Yes, then what is the use of connections, including creating the library of the ADF?

Thank you
JAI
Hello

It uses the connection in the library of the ADF. However, I recommend that not save you the database connect information in the library of the ADF. Instead:

-set the ADF BC model to use JDBC data sources
-In the library of the ADF, configure it to contain only the name of data source
-In the view project (the workspace) set up the database connection that is exposed by the library

When the library is imported, verify the Application resources--> connections and right click on the name of the connection that is imported to configure

Frank

What is the ADF_Library_Dependencies.library in each project for example xModel?
Hello
(1) what is the ADF_Library_Dependencies.library in each project for example xModel?
(2) the url for the namespace of the file is inaccessible, how can I get it? http://xmlns.Oracle.com/JDeveloper/110000jlibrarynode
(3) we foud does include all the dependent libraries are there?
(4) a few times, it causes the failure of the deployment of applications and bring it after deletling it, y?

Thank you first of all.
# 2 the URL to the XML namespace is not intended to be a URL to access a resource, it is just a way to make the namespace unique. Often companies will use URL as a matter of convenience, but it is not a URL that you would ever type in the browser to get a resource from.

John

Add the project to remote portlets as a shared library in another project
Hello

We are working on WSRP. We have producer such as Websphere and Weblogic (ver 10.2) consumer.

We created a portal (WsrpEar) EAR & portal (WsrpWeb) Web project and then consumed all the remote portlets for Websphere. The "producer" created during this process is 'MyProducer '. This project has no other all local portlets. In this "WsrpWeb" project we do not have a file ".portal. The reason is that we want to EXPORT this project "Web portal" alone as a '. '. WAR"file (WsrpWeb.war), and then add it as a shared library in our application MAIN WEBLOGIC PORTAL (MyProjectEar & MyProjectWeb).

We could do all this stuff. Once the war (WsrpWeb.war) is added as a shared library in the main application, we could see the remote portlets under "Available Portlets" from the main application. We could even drag it and drop it on the main ".portal' of application file. But when I ran, he throwed an error like below:
-----
{color: #ff0000} The source of this error is:
com.bea.wsrp.consumer.management.producer.ProducerManagerException: producer with handle {color} [{color: #ff0000} MyProducer {color} | http://forums.oracle.com/forums/] {color: #ff0000} in webapp {color} [{color: #ff0000} MyProjectWeb {color} | http://forums.oracle.com/forums/] {color: #ff0000} does not exist. {color}
-----

He is looking for the handful of producer in ' wsrp producer - registry.xml "of the main application (MyProjectWeb). But here we do not have an entry because we are consuming remote portlets directly from shared library and the shared library has a file of "wsrp producer - registry.xml" who did the handful of producer entry.

When I manually added the entry handle producer in the ' wsrp producer - registry.xml ' main, as application below, remote portlet executed successfully.

& lt; wsrp producer handle = "MyProducer" & gt;
& lt; Description / & gt;
& lt; seller / & gt;
& lt; initCookie requires & gt; perGroup & lt; / initCookie requires & gt;
& lt; requires registration & gt; false & lt; / requires registration & gt;
& lt; - service URL & gt;
& lt; WSDL url & gt; [http://xxx:yyy/wsdl/myservice.wsdl] & lt; / wsdl-url & gt;
& lt; / service-URL & gt;
& lt; / wsrp-producer & gt;

(xxx and yyy here are the host name and port # producer websphere).

Anyone can guide us on this? Is he referring to also make an entry in the ' wsrp producer - registry.xml ' main application or is there any way?

Thank you
ANU

Published by: user10826720 on January 29, 2009 06:36

Published by: user10826720 on January 29, 2009 06:38
Hello Anu,

The file WEB-INF/wsrp-producer - registry.xml (normally created by the IDE) and the database tables (normally created through construction Administration Tools) are the only two places where WSRP producer is stored for a consumer WSRP WLP.

So, yes - you can add this file (or an entry in this file) in your web application, or the other possibility would be to create your own code that calls the ProducerManager API to implement the producer when the webapp deploys first of all to a new server to boot. You could make this code look in what that are the configuration files you wanted to, but I don't think it would be easier to just put information in wsrp producer - registry.xml.

Thomas

How to build the project with library error in adf adf

Hello
IM using jdev 11.1.2.3
in my project I module 2 so we need to build the project with adf dependency libraries...

Two copies of the way to build the project with trial and error in adf adf

Timo

Do a right click in the Project Explorer is sometimes slow

I have a big project of the AF with a lot of classes and libraries. I only really use these two (lvclass and lvlib) to structure and organize the project. Right click on VI sometimes takes a terribly long time to load, say up to 10 seconds, depending on the library/class. It appears to be vaguely related to how many things the owners have libraries/classes. What exactly is causing this loading time? Any ideas how I could get rid of this significant disadvantage?

Here is more information and a few thoughts:
- Windows 8.1
- LabVIEW 2015 / 32 bit (I can't say for sure, but I think that I had no such problem on earlier versions 2014 and 2013)
- Mass of compilation of all of the project (taken as 2 hours) had no effect
Thanks for all the ideas and resources. I'm very, very happy to announce that this particular fix https://decibel.ni.com/content/docs/DOC-44159 (fix for the issue of AF project provider performance) made my problem disappear. Time has been reduced from ~ 7 sec less than a half second. Wonderful! That, to me, proves false the idea that the mere fact of having hundreds of classes or a large AF would make your current IDE experience terrible.

'Clone' of the project library (.lvlib)

Similar Questions

Maybe you are looking for