topic Re: Generic Configuration Editor (xCE) Reference Example in Components

Generic Configuration Editor (xCE) Reference Example

Christian_L — Tue, 28 Jul 2009 18:35:37 GMT

Please post your questions, feedback, and comments on the Generic Configuration Editor (xCE) Reference Example here.

Re: Generic Configuration Editor (xCE) Reference Example

tst — Wed, 05 Aug 2009 13:59:57 GMT

The article doesn't mention this, but it looks like you also need to have the AMC API installed to use this (at least the examples).

It would be useful if you found some ways of handling these dependencies elegantly.

I would suggest both listing the dependencies in each article and releasing all of these as VIPM packages, where you can define the dependencies.

Re: Generic Configuration Editor (xCE) Reference Example

Brian_K. — Thu, 06 Aug 2009 21:44:28 GMT

Your absolutely correct. I added the Requirements section with a link to the AMC.

Re: Generic Configuration Editor (xCE) Reference Example

Henrik_Molsen — Tue, 19 Jan 2010 10:43:45 GMT

Quote from the article:

"A walkthrough document is located in the xce_source.zip download. The walkthrough covers how to quickly get started, and the bare information on how to add onto xCE."

It does not seem that this document is in the .zip file. I really need a guide on how to use the xCE for my own project. Does anybody have such a description?

Re: Generic Configuration Editor (xCE) Reference Example

Brian_K. — Wed, 20 Jan 2010 15:56:32 GMT

Hi hmo.

You are correct I did say that and I was planning on writing that, but in the end I forgot. I apoligize, and I'll remove that comment from the article.

Are there some basic operations you would would like me to type up for you?

If you understand the concepts of LVOOP, demoEditor.zip is a very basic demo of how to add on your own objects? Take the "demoEditor(solution)" folder, place it on the same level as the xCE folder, and open the demoEditor.lvproj.

If you are learning LVOOP, then I would first suggest looking at the labVIEW help for OOP, as knowing the LVOOP is nescessary on how to use the xCE.

Thanks for looking at the xCE, I am interested to see what you are using it for.

Re: Generic Configuration Editor (xCE) Reference Example

Brian_K. — Wed, 20 Jan 2010 16:00:05 GMT

I just looked at what came in the xce_source_101.zip and it looks like the demoEditor is already in the zip. So disregard the previous zip, and just reply back with some specific questions on what you would like to achieve.

Re: Generic Configuration Editor (xCE) Reference Example

Henrik_Molsen — Thu, 21 Jan 2010 11:27:02 GMT

Hi Brian

I was just looking for some tricks on how to create my own project from the example without having to write all the example code again. Renaming and moving files in a LVOOP project seems always to end up with a lot of broken wires and error messages.

I will use the xCE as the basis for a configuration tool for a number of cRIOs on a network. Actually very much like the MAX but with other settings.

The framework is very nice and I think it will be a perfect solution for this task.

I think it would be nice with some kind of helpfile or manual that describes the possibilities already implemented in the xCE. Browsing the files it looks like there is more to it than can be seen in the examples.

Re: Generic Configuration Editor (xCE) Reference Example

Brian_K. — Thu, 21 Jan 2010 15:14:28 GMT

There is definitly a lot more possibilities then the examples show. I tried to make it so that the examples cover the up-and-running situation. That way a prototype is easy to conceive.

As for moving files, the one tricky thing to remember is that since I create LVOOP objects via their file path (like a plug-in architecture), all add on classes have to be on the file hierarchy like the examples. Althought the examples are basic, more advanced ones are:

http://zone.ni.com/devzone/cda/epd/p/id/6257

http://zone.ni.com/devzone/cda/epd/p/id/5331

They get into more of the polished look. I hope any questions you ask I can answer over this forum, as I can't work on a manual at this time. After completing this framework I learned so much that I am starting on a 2.0 that can take advantage of what I learned, and the feedback that I got. It seems to be a very common problem that many engineers face.

Re: Generic Configuration Editor (xCE) Reference Example

Henrik_Molsen — Thu, 21 Jan 2010 19:30:17 GMT

Brian

I think I have figured it out except one thing:

What I need is to change the data of the nodes during execution of the main.vi (NOT only reding XML at the beginning as is default in the examples). All I have is the name of the node and the new data (which can be of different type according to the node). What is the easiest way to do this?

(Idea: Use a function with node name as input (e.g. node17). Search for the object with the right name and return the reference. Using the reference call a method to write data to the node)

Re: Generic Configuration Editor (xCE) Reference Example

Brian_K. — Thu, 21 Jan 2010 20:44:09 GMT

So you want to change the data of a particular node from your main.

1) Take the RootNode

2) Use the getAllSubNodes method (part of xceNode class) to get all node references.

3) Go one-by-one to find the one with the correct name.

If you had the path to the node you could use goToNode.vi.

Tell me if that works.

Re: Generic Configuration Editor (xCE) Reference Example

Henrik_Molsen — Fri, 22 Jan 2010 10:45:24 GMT

Brian

OK - it worked except for data access.

I created a new Public function in the RootClass: "get Node ref.vi" which has NodeName as input and returns the DataNode*. Code is as you described above.

Now how do I change the data of that object when I receive new data in the main.vi (assuming it happend at a time when the node UI is not runnning)?

In the examples it seems that data is only accesible during execution of the UI in the subpanel.

Re: Generic Configuration Editor (xCE) Reference Example

Henrik_Molsen — Fri, 22 Jan 2010 12:30:48 GMT

Brian - again

Forget about my last post!

The data are encapsulated by the object (and should be) so I figured out how to update these during run of the UI.

Re: Generic Configuration Editor (xCE) Reference Example

Henrik_Molsen — Tue, 16 Feb 2010 14:01:38 GMT

Did anybody figure out how to use tree glyph in the xCE framework?

Can you help Brian?

Re: Generic Configuration Editor (xCE) Reference Example

Henrik_Molsen — Tue, 16 Feb 2010 14:13:34 GMT

Figured it out:

On the main.vi -> Initialize there is a call to Initialize root. The InitRoot input should ALSO bundle the glyphs folder. F.eks. C:\Program Files\National Instruments\LabVIEW 2009\examples\general\controls\treecontrol\max_symbols.

For the lvclass override the GetGlyphFile.vi and return only the name of the file in the glyph folder. For example: max_mysystem_max_remotesystems.png.

It works 🙂

Re: Generic Configuration Editor (xCE) Reference Example

Brian_K. — Tue, 16 Feb 2010 15:31:39 GMT

That is correct. When you initialize the root you can set the glyph folder. Then every class that overrides GetGlyphFolder.vi can output the exact string that relates to the glyph that they want. Awesome job figuring that out. Sorry about not posting back on the 1-22, I guess I did not see the response in my inbox.

Re: Generic Configuration Editor (xCE) Reference Example

Jorge_Amaral — Wed, 26 Jan 2011 14:41:33 GMT

Hello guys,

I'm really interested in this subject. Because I believe that since labview allows us to do things in a quick way we fall in a stupid situation where we are always doing the same code. And the configuration system it's a good example.

OOP it's a new thing for me but I already read some tutorials.

But a very nice way to understand, would be by modifying the the example posted here. I was pretending to add a new class. But I can't understand the procedure for that... The Object init should be something that all got to have. And there must be a way to do a "copy-paste". Can someone illuminate me?

Thanks to all!

Re: Generic Configuration Editor (xCE) Reference Example

Brian_K. — Wed, 26 Jan 2011 15:49:57 GMT

LVOOP can take a little while to understand. To create a new class I would follow this

http://zone.ni.com/reference/en-XX/help/371361F-01/lvconcepts/creating_classes/

If you need to see examples on how the xCE works I would look at the LCE:

http://zone.ni.com/devzone/cda/epd/p/id/6257

Re: Generic Configuration Editor (xCE) Reference Example

Jorge_Amaral — Thu, 27 Jan 2011 09:47:01 GMT

Hello again and thanks for the reply...

In the first link that Brian sent ("To create a new class") I can see the generic procedure to create class.

Probably I expressed myself in a bad way. I was trying to know a way of creating a new in the posted example. So, I would want to know the procedure to create a new class using the "channel" class.

I created a new class named "TCPDevices" where the object will be the IP string. The next step that i tried was the "Initialize.vi". That I supposed that should be a good way for copy that. Making this example more easy to grow. And that was my first problem. But it's not possible to copy-paste that vi.

A solution for my problem was by using "Clone Class" option. But is this the correct way?

Another strange thing that i saw was the following.... I made the next steps:

1. Create TCP class

2. create "new... vi from static dispatch template"

3. Named "Initialize.vi" (because I wanna something similar to Initialize.vi of the ChannelClass)

4. Placed the "Set UiViName.vi" on this

5. Tried to connect my object to the input... But it returns an error. And I can see that the width of my object wire it's larger than the one in the Channel example.

So... What's the basic error that I'm making here??

I'm really trying to jump to OOP but it's not very easy.

Re: Generic Configuration Editor (xCE) Reference Example

Brian_K. — Thu, 27 Jan 2011 14:03:14 GMT

I believe the concept you are missing is Inheritance. If you want to create a new class that builds off another class then your "Child" class need to inherit from your "parent" class. In your example I would say the "TCPDevices" class would inherit from the "channel" class. Then you could create a dynamic dispatch method for TCPDevices that overrides Inialize OR the TCPDevice class could just use the channel classes Initialize. I would suggest looking up LVOOP Inheritance, as well as looking at the example Dynamic Dispatching.lvoop in the LabVIEW Example finder. Am I correct in what I am suggesting?

Re: Generic Configuration Editor (xCE) Reference Example

Jorge_Amaral — Thu, 27 Jan 2011 14:38:13 GMT

yes you are.

I will take your suggestion and think a little on that.

Thanks for the help