LabVIEW class

Similar Questions

• using the structure of the event in the LabVIEW classes

  Hello

  I'm new in the use of LabVIEW classes, so don't know much how I can use them.

  In my main program, I have clusters with five elements in each. The elements are controls two States and in some groups, there are three States controls. The user will press the buttons (controls), and different things will happen. In my first program were I not using classes, I had a structure of the event and the controls were cases of event in the structure.

  Is it possible to somehow use an event of cases in one of the methods that is created in the classes, so that say, that's not in the main program?

  I have attached two photos: I wanted to have a structure of the event in servoTouchEvent (in left.tri.lvclass) who is a child.

  Let me know if my explanation is not clear.

  Grateful for the help!

  Hello

  Yes, you can have a structure of the event in a Subvi rather in your main VI of top-level UI. The trick is to use the 'Save for events' and passing in references to orders that you want to have the event trigger structure for. The refnum output since the function is entered in the terminal of dynamic event of the structure of the event who could live in a Subvi. You can add instances of event where you will see these control events as dynamic events then you can do something with. These excerpts from shows all the code in a simple diagram, but the stuff in the structure of disable diagram could easily transformed into a Subvi:

   

  All this can be done without classes. What will buy classes you include the ability to encapsulate your screws and also perform different code based on what object on the hierarchy of the parent-child classes is on a wire. If the behavior of your code is different between 2-3 State and controls (which I do not know what state controls 3 you are referring), you can take advantage of the classes.

• create a definition of ownership vi in LabVIEW class

  Hello forum,.

  I am creating a VI within a property definition file in a class of LabVIEW and I always get the following for the VI error message that is created: component connector invalid accessor VI. I have a 4x2x2x4 but displays pane always error. I go in the property definition folder, right click and select new VI. The new VI is created but with the above error.

  I have now that before I was able to do it before and the VI has an icon of type box (as an icon of labview class) but can't do it anymore. Don't know what has changed.

  I'm using Labview 2013 32bits.

  Thank you for your time.

  
  

• Using gateway requirements with LabVIEW classes

  Does anyone know how to get the gateway requirements NOR read the coverage information of documentation contained in a class of LabVIEW (.lvclass)?

  Requirements gateway seems to load the content of the fine documentation of screws, controls, .llb, .lvlib, .lvproj etc., but not .lvclass? My LabVIEW crash out when I try to bridge point requirements to a project with .lvclass files!

  If this cannot be done then it is a great way to add coverage of the needs information (you know, the field "covers: ID") in the properties of the class, or something close to class perhaps, this gateway requirements can read?

  Thoric-

  I believe that gateway requirements should be able to trace of LabVIEW Classes also covers long classes are added to a LabVIEW project and requirements gateway is configured in order to study the LabVIEW project. Here is a very primitive example that I restored from files in the directories of the prescriptions and example LabVIEW gateway.

  I hope this helps.

• Data members of the object to contain LabVIEW - classes will not object accessors in CSC

  I found this weird bug with LabVIEW 2013.  I create a class that has objects as data members and I'm not able to enter in the CSC.  I can do it manually via the GUI of Perforce, but it's kind of a pain.  Here are some photos to show what I mean

  Here's a generic VI I can add

  

  Here's the accessors that I can't add

  

  Accessors that are standard labview data types (strings, tables, figures, etc.) are fine, but it does not play well with objects.  Has anyone else encountered this?

  Could this be a problem of name?

  Can see that you name as the vi name.lvclass.vi

  Have you tried to remove the name of the vi .lvclass?

• data access child LabVIEW class

  Hi all:

  I class relatives have and master as a child class...

  I'm having a problem here get data from the Create method... I can see the data at the end of the create method (see below); but at the top where I show with it does not appear... someone can he pt me where I made a mistake...

  COM and slave data are defined in the parent class and child...

  See attachment

  Thank you

  Leela.

  
  

• How to convert labview projects in the class diagram

  Hello

  I don't know if this option exsit in labview, but if she does will really help.

  How can I convert a labview in class diagram project?

  Hello

  Your windows to the Project Explorer, select the view menu and go to the "hierarchy of LabVIEW classes. This will then show you a diagram of your classes and their dependencies.

  Kind regards

• Problem with the combination of LabVIEW (dynamic distribution) classes, statechart module and module FPGA

  LOCATION:

  -I am developing a software plugin based on plug-ins based on LabVIEW classes that are instantiated in running. Plugin real classes come from the plug in generic classes that define interfaces to the VI instantiation and can provide basic functionality. This means that many of the methods of the class are dynamic distribution and even methods of child classes can call the parent method.

  -Plugins top level (the ones directly accessible by the main VI) each have a run method that animates a plug-in specific state transitions.

  -Transitions of the plug-in data acquisition (DAQ class) class calls a method of the DAQ class that reads data from an FPGA card OR and transmits to another component via a queue.

  PROBLEM:

  -Higher sampling rate, a FPGA-to-host FIFO overflow occurs after some time. When I "weigh" the system just by moving a window of Firefox browser on the screen, the overflow is triggered immediately. I did not have this kind of problem in older software, where I was also reading a FIFO of FPGA, but made no use of LabVIEW classes or diagrams.

  SOLUTIONS I'VE TRIED (WITHOUT SUCCESS):

  -J' put the transitions in a timed (instead of a simple while loop) loop that I assigned specifically to an own kernel (I have a quad-core processor), while I left all the other loops of my app (there many of them) in any simple loops. FIFO overflow still occurs, however.

  QUESTION:

  -Does anyone have a tip how I could fix this problem? What could be the cause: dynamic distribution methods, the acquisition of data of state transitions or just the fact that I have a large number of loops? However, I cannot change the fact that I have dynamic distribution methods because it is the essence of my architecture...

  Tips are greatly appreciated!

  I've now changed the execution priority of all the screws involved in reading of the FPGA FIFO '(highest) priority critical time '. This seems to be improving the situation much: so far I have not a FIFO overflow, even when I move around the windows on the screen. I hope it stays like that...

• By comparing the LabVIEW OOP class hierarchies

  Hi all

  The Question

  Does anyone know of a tool for comparing the hierarchies of LabVIEW classes?  (As 'Compare VI hierarchies' for .lvclass hiearchies?)

  For example

  Let's say I have foo.lvclass in both projects, and I want to compare the two instances, and their respective members.  One instance has methods that the other is not?  Is a method or differ from private data?

  Why?

  I have several applications with dozens of classes, which many must be interchangeable, and I want to quickly determine what classes are later, perhaps to consolidate some common code base.

  I thought about this announcement as a suggestion on the exchange of ideas, but I didn't know if I just don't see a feature that is already there.

  Thank you very much

  Jim

  Hi Jim,.

  It doesn't seem to be a way to do this. The nearest feature of you, that I could find was to use hierarchies of VI screw/compare compare to compare files .ctl for two classes. The LabVIEW help topic documents how to proceed:

  http://zone.NI.com/reference/en-XX/help/371361L-01/lvhowto/comparing_vis/

  However, this does not really reach the feature you're looking for. Thank you for posting this idea to the exchange of ideas!

• How can I unit test screws with classes?

  I have my first VI using an oriented object approach I want to unit test. How in the world I have configure Unit Test infrastructure to accept a specific class? See the attached excerpt.

  Hi elrathia,.

  Here is a link that should help you:

  http://zone.NI.com/reference/en-XX/help/372584D-01/lvutfconcepts/utfc_tests_cases/

  Below, you can see an example location:

  labview\examples\Unit Test Framework\LabVIEW Class\LV Class.lvproj

  (Note this is for 2012)

  DylanC

• The difficulty for the reorganization of elements in the DataSet class

  I have a LabVIEW class whose private data cluster includes a cluster of small clusters.  (It is not as bad as it sounds).  I order the elements of one of the smaller clusters in the control of the class.  When I check the order (by selecting 'arrange the controls in the group... ") I can verify that the order has indeed changed.  However, when I unbundle the cluster of data of a member of the VI, the order has not been changed.  I re-recorded the control, the class and the project, rebooted LabVIEW and created a new Member VI after the order of cluster and unbundle nodes are always in the wrong order.  Is there somewhere else I need to change the order of cluster and more just in control?

  Any help/suggestions would be greatly appreciated!

  
  

• Several files palette in a library/class file problems

  All developing a labview class, I wanted to put the default palette, so I added the relevant dir.mnu file to the class. Unfortunately, the class had a dir.mnu in her file. On the addition of the file, I received an error message on a dependency change * (which makes no sesne, how a palette file can have dependencies!). On the recording of the class and any attempt to reopen it, LabVIEW argues that it is corrupt. Inspect the .lvclass xml files reveals that when I added the new file paletee, LabVIEW actually just added a second reference to the file already in the project palette, he then considered a problem when it tries to load the class. This is clearly a bug on several levels:

  1. It should not possible for the user to induce LabVIEW to create files xml corrupted through such simple attempts to use the documented features.
  2. The underlying problem is that LabVIEW seems to use the classic search/link rules to load the library items, be they a vi (which must have a unique name) or another file (which might well be legitimately not unique).
  3. Almost impossible to rename a palette file without breaking the links palette this bug in particular is very annoying.

  I was able to reproduce the behavior described.

  This was reported to R & D (AUTO ID: 181638) for further investigations.

  Thanks for the comments!

• Classes: Component child connector does not match

  Hello

  I use LabVIEW classes in one of my projects and I sometimes run into this:

  When I create a vi child by creating a vi the appropriate name for the class of the child rather than use the built in 'create vi to replace' connector of the child component is reported as part of the parent is not - even if it seems to me that it does not.

  Note I do only because I want to keep the FP of this child specific vi.

  This makes me think that I don't really understand what needs to be exactly the same.

  Sending dynamic input/output are of the class that the vi belongs to. Which shouldn't be a problem though, huh?

  All other entries are appropriate types (simple stuff: cluster error, U8, I32, boolean, DBL).

  They need to have the names and labels even?

  They are in the right position too.

  Connector components share the same model (standard 4x2x2x4).

  Anything not listed here that I don't even know?

  Any advice would be appreciated.

  Best regards

  Florian

  The dynamic send screws must exactly match the component connector - dynamic distribution of input/output terminal, data types, as well as the State required or recommended/optional connection - maybe it's the last one you haven't checked? (search for "BOLD" / normal text in contextual aid of the screws).

  I'm sure the names/labels do not matter.

• Cannot control the color sensor in LabView for Mindstorms

  Hello!  New here.

  I'm currently boning on LabView via 'LabView for Lego Mindstorms' for a possible job in the near future, and I encountered a problem from the beginning.

  I am programming my brick Lego of LabView to simply activate the color sensor which is quite easy: I'm building a while loop and inside I have a block of color sensor attached to a block of text that displays the light intensity of the probe in the text on the brick.  I compile and run the detector turns on and I can read the intensity constantly updated on the brick.  This part works fine.  I would now like to control the light sensor (that doubles as a light source with color LEDs) on the front of the LV Panel.  The book I'm using (LabView for Lego Minstorms) says I should block sensor on the entry "generate light' do right click and choose"Create--> Control"in the menu that appears.  A Boolean command button should appear connected to the sensor block in the block Panel and a push button should appear in the front panel.  This is not what is happening.  Here, the two things are different.

  (1) I have no port "generate light" click on right-click.  This is probably using a version more day of Mindstorms that uses of the book.  It's a matter of book/Mindstorms, which probably cannot be resolved here but I hope that the next issue of problems will make it irrelevant.

  (2) I right click and create the control, but rather than create a Boolean command button as the book predicts, it creates an icon "BrickReference.lvclass".  He connects very well with the light sensor and a corresponding block is created in the front panel, but it is a paper weight that I can tell.  I can't do anything with it.  There are no buttons to push, no slider, button, button radio etc and I can't seem to change into something that somehow work.  I have delete and don't create a no kidding Boolean button from the library, but it does not connect to the photoelectric cell and so I can not compile.  So now, I'm a little stuck.

  I searched "Reference of the brick" online in the context of LabView class and have found little or nothing that talks about its definition or how I can use it to control the light via the front panel sensor.  Help with the software section is not much help, and yet I'm sure there must be a way to control a simple Lego light sensor of the façade for debugging purposes and others.

  If you know what I'm doing wrong or if you know a finish around this issue that will allow me to control a Mindstorms brick from the front in this way, please let me know.

  Thank you!

  Try to post in the forum of Lego.

  http://forums.NI.com/T5/LabVIEW-for-LEGO-MINDSTORMS-and/BD-p/460

• How can I probe wire values within a class?

  Hi all

  I use a Modbus Library built using classes. I need to view the data inside a VI that is part of a class in a tree inheritance. I can't set a breakpoint in this class, or the sons of the probe or retain the yarn values. I looked into creating a custom probe, but the option is not available. I have read in several documents on LabVIEW classes and tried the built-in help also, but I don't know I'm missing something obvious. Please could someone point me to the right resource to use, or tell me what I'm doing wrong.

  Thank you

  Ray

  Tarsel wrote:

  Hi Gregory

  If the program or running or not, I can normally do a right-click on a wire and probe option is available. In this case, the option is grayed out or non-visible (even for breaking points). [...]
  Ray

  This indicates that the VI is set to "Enable debugging" = False (disabled).

  Norbert