Jump to content

XNode and ExternalNode help


Recommended Posts

Posted

Hey... at least you guys have gotten me to the point of admitting that XNodes even exist. Time was I would have accused you of hallucinations and swamp gas reflecting the light of Venus for believing in XNodes.

lordexod: The XNode tech is reserved to National Instruments for a long list of reasons, not the least of which is that it requires some significant contortions to avoid the traps and pitfalls of working with them. XNodes invoke G code to do their work. There are various operations that are not stable to do while LV is doing certain operations (loading a VI is not always safe, for example, depending on what else LV is doing at the time). As a matter of fact, XNodes have been mostly abandoned by NI for further development ourselves because of their issues. They work great for some things, but poorly (or crashily) for others, and it is very hard to tell in advance whether a given use case will turn out to be the former or the latter. We'd like to have a more complete "G written in G" solution, one that we could release to customers, but XNodes aren't it.

Posted

Does anyone have specific documents about "XNode" and "ExternalNode" for LabVIEW FPGA? (hdlnode.jpg, createxnode.jpg)

Look at this

How did you enable the creation of a Xnode and selection of abilities in your Project ?

Posted

I usually buy the "it is too complicated for the masses" argument until I try using XControls. Compared to those XNodes are a walk in the park.

Ah, but XControls don't have the potential to corrupt your VI if you do them wrong. There's a big difference between "complex" -- which is a reason to put a good UI on something but not a reason to never release it -- and "flakey around the edges" -- which is a reason to keep it in house.
Posted
Ah, but XControls don't have the potential to corrupt your VI if you do them wrong. There's a big difference between "complex" -- which is a reason to put a good UI on something but not a reason to never release it -- and "flakey around the edges" -- which is a reason to keep it in house.

XControls can lock you out of classes in rather unfriendly ways (and yes this is documented I know but I still think it's not great that the IDE lets one create uneditable items without a bit more effort to stop you...). Still XNodes are fun to play with and a pain in the backside to work with. It's a shame that that is apparently an unsurmountable hurdle, but hey third (or more ? - External Nodes, XNodes, ...) time lucky :shifty:

Posted

Aristos Queue: "The XNode tech is reserved to National Instruments for a long list of reasons...." - Not anymore, but for one reason only. I enabled XNode on LabVIEW, as you can see the screenshots.

"Yes. I do. No, I won't share. " - If you do not want to share or exchange,you will not admit publicly that you have something.

Darin: With this "MathNode" a good job. A little bit I know already what is going on with this XNode.

Posted

lordexod, when AQ says he won't share the information, that in itself is useful information. Since the implied intent was not clear (that XNodes can corrupt a VI), he was then more explicit.

Posted

todd: "XNodes can corrupt a VI..." - In LabVIEW is a vi file recovery option. And as LabVIEW or computer the crashes, you can always reset.

Darin: This XNode's is a very interesting.

  • 1 month later...
Posted

Aristos Queue: If you want something for knowledge of the "xnode, externalnode",it write on priv.

Anyone know what is "LabVIEW_LabVIEWInternalTag_PKG"?

  • Like 1
Posted

AQ's not trying to be mean in denying you internal information on xnodes. First, such documentation was written for internal purposes and as such contains "classified" information. Second, xnodes were not designed as a feature for customers but as an internal tool. As such, believe me!, they are buggy, under documented, flaky, dangerous and unfinished. They are nowhere near a feature we can support and we are not allowed to talk about them. This is not really a "protecting you from yourself" but rather not publishing an unfinished, buggy feature. Maybe someday we'll have the resources to finish and productize the feature. But for now, we are supposed to answer "No comment" according to the lawyers. =)

Posted

Djed:

Second, xnodes were not designed as a feature for customers but as an internal tool. - I am not a customer.

As such, believe me!, they are buggy, under documented, flaky, dangerous and unfinished. - I did not bother me.

They are nowhere near a feature we can support and we are not allowed to talk about them. - This is the forum, you do not have to speak.

You know what it is "LabVIEW_LabVIEWInternalTag_PKG"?

  • Like 1
  • 2 weeks later...
Posted

How bad works XNode's Interface in LabVIEW, you can write such an interface to the WebUIBuilder software.

From what I saw, there are several types of XNode (CXNode, GXNode, HybridXNode).

  • 1 month later...
  • 2 months later...
  • 4 months later...
Posted
How to enable xnode properties in Labview? I downloaded your vi and when i try to explore on available properties for xnode i couldn't. Is there any keys to be added to LabVIEW.ini?

priv

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.