Front Panel Property Node Errors with Real-Time

[John_Neutron]

Hello Everyone

I appear to be experiencing some strange errors when trying to access the FP.* property nodes on my Real-Time PXI system.

The nodes that I specifically care about are;

Write FP.Title which gives an error 53

Read FP.State which gives error 1043.

I was under the impression that these were avaliable in the Real-Time environment from the help.

I have also tested other FP. properties whichshould be avaliable and these appear to give errors aswell.

I have checked that the appropriate VI Server "accessible server resources" options are all checked under my target's properties and other VI class property nodes work as expected.

I have created a VI which demonstrates the issue (see attached) and I am using Version 12.0.1f2  (proffesional development system).

Any help would be much appreciated.

Cheers

John

[crossrulz]

RT doesn't have a front panel.  So property nodes dealing with front panels will not work.

[Texas_Diaz]

I'll second that notion.  RT doesn't have a front panel, should never be used to create pop-ups / user interfaces / dialogs.  Real-Time systems are the same as regular systems, except everything dealing with the user interface is compiled/stubbed out (almost).

-Danny

[John_Neutron]

Thank you for your responses.

I was aware that real-time deployments do something different with the front panel.

I am developing an application around the remote panel features in LabVIEW which do work well in real-time. It appears that even with a client connected to the panel (so it is definately loaded somewhere on the real-time machine) that these property nodes still produce errors.

Oh well. I want the code to run on both normal and real-time targets so I will just have to use the conditional disable structure and accept that the user experience will be slightly different when connecting to real-time panel hosts.

I guess that means that my real question is why does the help list these feature as being avaliable in real-time if all it will do is cause an error?

Cheers

John