Unsupported VIs for the cRIO-9030

[LJHerskowitz]

Is there a list of unsupported VIs on the new 9030s and 9033s?

[neil_before_zod]

This KnowledgeBase Article covers unsupported features for NI Linux Real-Time Targets:

http://digital.ni.com/public.nsf/allkb/1C16BFEA5262E33E86257A46006FC92B

[LJHerskowitz]

Is this knowledgebase correct?

It says, 

RT targets support the Event Structure only with dynamic events

That isn't true. I just made a quick VI that reacts to value change of a button.

It also says, 

When a VI or stand-alone application runs on an RT target, you cannot execute VIs that modify a front panel. For example, you cannot change or read the properties of front panel objects with property nodes because there is no front panel for VIs that run on the RT target.

But there is a front panel. That was a major upgrade here. I have found some property nodes that work and some that don't. Is there a list of supported functions or am I just exploring bugs here?

[nathand]

Some of these things will only work in the development environment. Have you tried compiling your code? Does it still work? Although some functions that involve front-panel interaction will work in the development environment, they won't work (or won't work the same way) when you compile to an executable.

[LJHerskowitz]

It is not working in the development environment.  nathand, do you have experience with the 9030? It seems like you are describing how property nodes will work on a VXWorks cRIO where property nodes do work in the development environment but not compiled. In the development environment there is a front panel. But on the 9030 there is a displayport so the RT has a front panel.

[nathand]

No, I don't have specific experience with the 9030.

[natasftw]

Be careful when bringing up VxWorks versus Linux.  You're erroneously suggesting the 903x series are the only Linux based RT systems when you make the comparison you made.  You shouldn't do this. 

If you're putting a button onto the RT code, you're using bad practice.  You don't want to include the user interface with something RT.  I haven't tested to see if it works on the 903x.  But, it certainly causes errors on every other Linux RT RIO I've tried.

The KB you read lists 2013 as the primary version.  The 903x was introduced with 2014.  It's possible it behaves slightly different.  I don't see any documentation with a quick search that would confirm expected behavior one way or the other.

[smithd]

That KB should never have been written unless I'm missing something. The information you want should be here:

http://zone.ni.com/reference/en-XX/help/370622M-01/lvrtconcepts/rt_rtlinux/

and here: http://zone.ni.com/reference/en-XX/help/370622M-01/lvrtconcepts/rt_osnotes/

Those documents are maintained by R&D and are thus up-to-date with newer features like embedded UI

[LJHerskowitz]

Thank you smithd for the links. That at least mentions that the property node won't work without a front panel (if the embedded UI is disabled). I have a front panel, but I am seeing errors. Is this a bug?

I am passing a splitter reference into a sub.vi that checks to see if the splitter is vertical. That is throwing an error. It doesn't throw an error if I just create a splitter property node, but if I pass a reference into a sub.vi I get an error. It seems like a bug.

natasftw, I did not mean to infer that Linux was only on the 903x RIOs. I was just being specific with which hardware I was using. But with the new Linux RIOs, it is not bad practice to use a UI. That was a major improvement that NI was touting.

[smithd]

---

@LJHerskowitz wrote:

Thank you smithd for the links. That at least mentions that the property node won't work without a front panel (if the embedded UI is disabled). I have a front panel, but I am seeing errors. Is this a bug?

I am passing a splitter reference into a sub.vi that checks to see if the splitter is vertical. That is throwing an error. It doesn't throw an error if I just create a splitter property node, but if I pass a reference into a sub.vi I get an error. It seems like a bug.

---

Good question, I'm not sure. Sounds like a bug. You might see what happens if you have both the linked property node and the by-reference property node in the code at the same time. The code itself might also help -- it could be something to do with splitters, as an example.