Understanding RT remote panel ideosynchrosies

[Grub]

Hello,

I'm just starting to feel comfortable in programming with Labview (Just got my CLAD cert)  However, I'm strating to dabble in RT programming I from what I've read there are some pitfalls.  Can anyone point me to literature or give me alternatives to these problems?

1.  I have previously used a lot of local variables, property nodes, and vi references (in combination with invoke method nodes) in my programs.  All of my real time applications require user input from time to time.  This makes it very hard for me to avoid using remote front panels.  In the past, I have used the web server on the Fieldpoint module and made a user interface that way.  I've read on this board that I must use a property node (value) and a local variable to update a value from the remote panel into the running vi.  Is this true? 

2.  DO event structures work on RT?

3.  Do VI references work in RT? If so, how does LabVIEW RT resolve the vi pathname when it gets compiled and downloaded to the RT target?  In other words, do I have to specify the VI pathname that it WILL BE once downloaded, or do I specify the pathname of the VI while it is still on the PC?

[tst]

There are no control references, but I think you can get VI references. Look here for some more details.

All VIs are built into the startup.exe file. I am not sure if RT allows for dynamic loading of VIs (it may), but in any case, the file structure on the FP is similar to that which is on the hard drive.

Event structures will probably work, but what's the point.

To pass data to and from the computer, you should write your own communication protocol. You can try using the RT Comm Wizard (tools menu) or search for TCP in the example finder to see examples of this.

[Khalid]

Couple of comments:

1.  Event structures do not work in RT when embedded.  As a general rule of thumb, anything to do with the front-panel (property nodes, etc., for example) is a suspect on RT. 

2.  RT does allow for dynamic loading of VIs.  You will have to however load the called VI into memory beforehand so that it gets bundled up in the EXE. 

Regards,

-Khalid