Need some help with real time

[Coop]

The system I am controlling with compact Field Point consists of the chamber (initially filled with air), turbo pump (below), valve on the right of turbo pump, scroll pump below.
The I/O boards installed in FP are : DO-403, RLY-421, DI-301, DI-330.
I use:
- DO-403 to close and open the valve
- RLY-421 to start/stop turbo pump
- DI-301 to read the signal from multi-gauge (high/low) for 3 set points
- DI-330 to read signal from turbo pump (high/low) that tells me if the pump is in starting/normal operation
The process starts by turning the Scroll pump On and when the pressure in the pipe between turbo pump and scroll pump drops below setpoint 1 the Chamber2.vi will open the valve. The scroll continues to pump the air out and when
the pressure drops below set point 2 I start the turbo pump. Now both pumps are pumping the air out together and the pressure will start to decrease rapidly.
The Chamber2.vi is to automize the process of pumping the air put for this system.
I used RT Comm. Wizard and it built three VIs for me.
You can choose to do the same I believe and see what they look like.

I have few things to clear out:


-How does the VI look like from the Real Time point of view? Are there any bigger problems in a way I built it?
-My goal is to build stand-alone application that will be downloaded to FieldPoint. What would be the next step for me to do after I have made a NP VI, TC VI and Host VI? DO I download only Normal Prior. VI to the FP?
-One problem I had with RT Comm. Wizard is that the indicators: valve, pipe and scroll pump are not shown in the list of controls/indicators that you can select to be replaced with RT FIFO. Why is that?


Any suggestions, inputs, critics will be greatly app
reciated.


Thanks,
Pedja

[GValdes]

Pedja,

-If you want to build a stand-alone application, you only need to create an executable out of the Normal Priority VI and set it to load at startup. That way, every time you power-up the system, it will load your application embedded in your FieldPoint controller, and you will only need to run the Host VI in your computer to communicate to it.

-I think that you cannot see some controls/indicators when using the RT Comm Wizard because they are outside of the loop. I found a KB that talks about it:
Why Are Not All of My Controls and Indicators Listed in the RT Communication Wizard?
http://digital.ni.com/public.nsf/websearch/2478C5CCC53E460186256D63003DE388?OpenDocument
Basically, you could replace the terminals in the first sequence (scroll2, pipe, val
ve) with local variables, and use the physical terminals inside your loop.
I noticed that you are using global variables. Is there any particular reason why your are using them? Unless you are accessing those variables from another VI, I would recommend using local variables instead.

I hope this helps!

Gustavo Valdes
Applications Engineer

[Coop]

I did use local variables everywhere but when I used RT Communication Wizard it did not recognize/like them and it would just omit them.
So I replaced them with globals.
I prefer using locals too.

Thanks for your time,
Pedja