i am trying to translate the labview program to a real time labview programming....i wan to know what te the main isse that i need to focus on

[YH_Goh]

currently i am doing a lift monitoring system which made use of labview. Due to time constraint, i have decided to use the real time labview program. However i have no prior experience on the real time programmng, can i be enlighten on the main issue and what are the thing i ned to look out for. is thre any documentation that i can use?

[Chad_H]

Derek,

Programming for LabVIEW Real-Time is very similar to programming for LabVIEW for Windows. Many VIs do not need to be changed in order to run in LabVIEW Real-Time RT Engines. However, here are some issues to consider:
1) Drivers
2) File I/O
3) Dialog Boxes
4) Shared resources

1) Drivers. If you application was written in LabVIEW for Windows, and then ported to run on an RT Engine on RT Series Hardware, you need to be sure that the drivers you are using are supported on your platform. See KB 28G97MZ8: http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/aad11f924e5b5fd086256a310053a094?OpenDocument

2) File I/O: If you are running your programs on an RT Series DAQ Device, it has no storage device, so file I/O operations will crash. See KB 26FBO0KN:
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/3c35f5e85476579d862569f50067462e?OpenDocument
File I/O on RT PXI Controllers is supported in 8.3 filename format (no spaces in the filename allowed).

3) When your application is deployed, (Operate>Download Application, Operate>Run, then File>Exit without closing RT Engine VIs), you VIs continue to run. However, the RT Engine runs headless with no keyboard, monitor (limited information displayed), or mouse, so any user interaction previously required by your VIs, such as Dialog boxes, will hang or crash your program. For user interaction with a deployed application, communicate to the Host PC using shared memory, VI Server, TCP/IP, DataSocket, or UDP. See ~\labview\examples\rt\rt communication.llb for examples.

4) Even though your programs now run in a real-time operating system, you need to follow good real-time programming techniques. These include: using multithreading with critical tasks set to time critical priority. One time critical VI with no parallel loops. Avoid accessing or using shared resources in time crital VI (shared resources cause jitter). Shared resources include the memory manager (preallocate arrays used in time critical loops), global variables for interthread communcation (use RT Queues). For more information, visit the LabVIEW Real-Time Resource Library in the Developer Zone: http://zone.ni.com/devzone/devzone.nsf/webproducts/c25f8c664230613a862567df006abb06?opendocument