This is my first Xnode (not an External Node, but a true LV8 Xnode). I don't know how "revolutionary" is this, I suppose not much. I haven't found info about new Xnodes, but sure a lot of you are playing with this technique and are more advanced than myself. In fact, a couple of days have been enough to grasp the basics, so my first impression is Xnodes are far better "thought" than old External Nodes .

The purpose of this Xnode is simple, it just returns the selected string value from an enum. This was already easily done, for example with the "Format into String" function or with the "Get Strings from Enum" VI from OpenG (impressive by its own), but I think it can be an useful proof-of-concept for people who want a VI that accepts all kind of enumerations as inputs without using variants (something I've found desirable from time to time).



The function accepts all enumeration types and representations (even typedefs), or at least it should. If you find any error please tell me, I've tried to make the Xnode as light as possible.

Obviously, Xnodes can do a lot more things, but unfortunately just one example comes with LV82, so if anybody knows better, please share your wisdom .

Saludos,
Aitor

How do you manage to edit the XNode. When I open the .xnode file with my LabVIEW, a project explorer opens with a locked xnode in it. I think XNodes require a license, have you got one? Or is there an INI file setting that allows one to edit the XNode? Could you please write a short tutorial on how you created the XNode.

jimi

Hello Aitor,

same for me... here is what I get when I try to open youe xnode...

Xnodes are used as a subVI, not opened directly. From another VI's diagram -> right click -> Select a VI -> Go to "EnumToString.xnode.llb" -> Select "View all" in the bottom options -> Select "EnumToString.xnode"

I attach an example of use (put it in the same directory the EnumToString.xnode.llb is). Connect any of the enums (or other ones you create) to the input, it should adapt to it; run and get the selected string.

Tell me if it works for you .

Saludos,
Aitor

Well it's not the use people here are interested ;-). It's how you made them! As far as I know there are only two possibilies:
- You got a license from NI somehow (and have signed an NDA or someone has on your behalf) and then posting this here could get you in trouble.
- You hacked LabVIEW to not do a license check anymore or something like that and then you are also in trouble in at least certain countries on this globe who think that even thinking about circumventing anti-copy protection is a major crime.

Rolf Kalbermatter

There are also other options, which, I think, would be legal. The .xnode file is not itself copy protected (I think) but a plain text XML file. So the hard part is how to make the ability VIs (the VIs which control the behaviour of the XNode) and how to link the ability VIs so that they know they are part of the XNode library.
- There is a XNode shipping with LabVIEW or some external package, the ability VIs of which have not been password protected. Then you could propably edit the ability VIs as the license is (techically) required only to create new ability VIs.
- A. Solar has somehow been able to create ability VIs without needing to overcome technical copy protection.

This post has been edited by jimi: Jan 17 2007, 11:41 AM

Well, sorry, from the previous posts I got the impression some people was simply opening the xnode instead using it in a diagram.



Ouch, come on... Do you really think I would do something illegal? And even worse, do you really think I'd do something illegal and posting it in a public forum?

Creating an xnode is really easy and doesn't need any license. A Xnode is just a type of library and can be open, modified, etc with scripting.



And, as Jimi says, a xnode file is just a XML file. You can extract it from the llb, open it in a text editor, change what you want and returning it to the llb.

About the abilities... that's even easier . The ability VIs just need to have the correct connector pane, and you can find that connector panes in the xnode example that comes with LV82 (search for *.xnode in your LV82 installation directory). Not everything is exposed, but with some trial-and-error and knowledge of the old External Nodes is not so difficult. So you can create new ability VIs without problems (they are normal reentrant VIs).

About linking a VI to a library, it's answered in this same forum, in a question about linking VIs to a Xcontrol, IIRC. You have the library reference and use the "add item from memory" method.

So, I ask you, members of the jury, must this man go to jail for all his life?

The answer is "probably yes, but not for this"

Saludos,
Aitor

This post has been edited by Aitor Solar: Jan 17 2007, 12:09 PM

Would you Aitor Solar like to post the VI in the above image to the forum, of course assuming it doesn't contain any stuff under NDA or something that would be illegal.

This post has been edited by jimi: Jan 17 2007, 01:10 PM

I would take it easy on the condemnation. A lot of this stuff is not super protected. It just requires some one with a little sense of curiosity and the ability to use Windows file explorer. You know, it's really ok to browse inside your C:\Program Files\National Instruments\LabVIEW 8.2\resource folder...

Keep up the good work Aitor!

I think that the most interesting possibility of XNodes is to be able to create template VIs that adapt to type, similar to those that robijn suggested in this thread.

Here's a couple INI entries:
XNodeWizardMode=True (try right clicking on an XNode now!)
XTraceXNode=True (um, I forget what this did actually...it's been a couple weeks)

Of course, I personally prefer:
ExternalNodesEnabled=True

XNodes are easy to edit without any licensing (XML). There's really no security around those, and a lot of NI "examples" are given (albeit locked diagrams).

Aitor: This is very cool! great work


Adam: Thanks for these!

Michael: I think we might be getting to the point where we need an XNodes subforum, with a pinned README topic on how to get started.