Scan Engine Initialization, when does it occur?

[viScience]

Looking at the cRIO console output it appears that the Scan Engine gets initialized well after my startup.exe start running.

I have also confirmed this by turning on the user led when my app starts running and it is many seconds later that the console output

show the Scan Engine Init.

My question and problem is:

1.  Would it not be better to first launch the scan engine and then the startup app

2.  As it is, by what mechansim can our app's determine when the scan engine is transactional?

This may explain some of the weird timeout 56 and 66030 errors that I have been getting.

[Greg G.]

Hi,

I agree that this is not an ideal situation that the Scan Engine starts after the startup application starts.  However, there is a relatively easy way to find out when the Scan Engine has finished starting.  Do any of the following:

• Read or write any I/O Variable
• Execute the VI "Synchronize to Scan Engine.vi"
• Run a timed loop using the Scan Engine timing source

These operations will all wait for Scan Engine initialization before they complete executing. 

greg

[mallyaprs]

Hi,

The usual way how it works is,

Running startup app: some startup.rtexe

Welcome to LabVIEW realtime.

NI scan engine initialized.

Sync to IO scan done ( if you are using synchronize to scan engine)