danielb

Alright, thanks for the info.

I knew of the AF group but generally try to avoid anything on ni.com (at least till all other resources are exhausted) since the knowledge might be there, but the page is a navigational atrocity and things are usually fragmented and hard to find.

The Launch Nested Actor.vi has the Terminal "Open Actor Core front panel? (F)". Which is pretty useful. It makes sense. It is a simple interface for me to specify whether I want to display a UI for this actor or not.

But it doesn't work in the runtime engine. The implementation of the Actor.vi includes a conditional disable structure that throws an error when an actor is to be launched with an opened front panel on a runtime system. So I can use it in development but not in production.

Is there a sensible reason for this?

What's the preferred  workaround?

Cheers,

an AF noob

Ah fantastic, I'll look into it, thank you.

My Google-Fu wasn't strong enough, it's sort of hard when you don't really know the name of the thing you want to know more about.

So thanks for that

To be honest, my understanding of XNodes is very very limited at this point. From the little information I found, the EIONode seemed to be a Hybrid XNode. It is entirely possible that I misinterpreted the information I found, but for the life of me I wasn't able to find other Information on those EIONodes.

I have found out that they don't live in the normal class hierarchy (no child of GObject, at least not documented), but can be cast to "Node". I wasn't able to completely access the nodes functionality though, and IIRC Darren mentioned in another topic that this is somehow related to them being hybrid XNodes.

So in my mind this question was at least somewhat fitting for this topic. 

If you are positive that the two topics are unrelated I will create a new thread.

Okay, I so there is some interesting information here, but it doesn't really help me solve the thing I want to do right now.

I have a cRIO + FPGA Interface project, the targets (and all c-Series modules) have already been discovered and added to the Project.

[some preprocessing not related to this topic but any pointers would still be appreciated, haven't got this one running yet either]

I also have a table of mappings from hardware resources to channel name, e.g. "Mod6/AI9" -> "p_stat_oil_01".

Now I would like to automatically rename these hardware ressources with VI Scripting to achieve something like this:

[end of the off-topic part]

Next step would be to select specific channels (defined as a list of channel names) and bundle them. Should look something like this:

All the wiring is already scripted and works reasonably well, but I can't figure out a way to expand the EIONode (on the left) and select the appropriate channels. Is this possible?

This will be a task I have to do repeatedly and I'd really like to automate it, because it is both prone to errors and very very tedious.