Slow cRIO Deployment in LabVIEW 2009

[Jan_HeG]

I am currently experiencing the exact same, or very similar issue.

LabView gets very unresponsive for tens of seconds after I deploy code to the cRIO. When it then resumes to normal it seems a queue of data is written to the front panel of the deployed code. 

TCP, serial and FPGA are also components in this project. 

[JackDunaway]

Jan_Heg - can you verify that the "wait" only has appeared in LV2009, but was not present in 8.6.1?

[JackDunaway]

A colleague has pinpointed at least part of the culprit of this problem. There was one property node in the boot-up sequence, and when the PN was diagram disabled, the boot-up times dropped back down to the normal 8.6.1 times. We have been using this PN in the startup sequence since 8.6.1 with no problems, until the LV2009 upgrade.

HOWEVER: I will copy part of his email to me: "BUT there is still something strange going on.  The RT top level front panel does not become active until ~80 seconds later.  During all that time the RT is working, reading inputs and writing outputs.  But there is no front panel activity.  Once the front panel eventually becomes active things behave normally.  It certainly is different in LV2009." 

Alright, so that's the latest in this saga. I hope this information helps clue you in to solving these issues, Kristen and Dev.

Best regards,

Jack

Message Edited by JackDunaway (mechelecengr) on 08-31-2009 10:34 PM

[Jan_HeG]

---

JackDunaway (mechelecengr) wrote:
Jan_Heg - can you verify that the "wait" only has appeared in LV2009, but was not present in 8.6.1?

---

Yes, there is a significantly longer unresponsive FP behaviour in 2009 than in 8.6.1.

What property node had you used that caused this?

Message Edited by Jan_HeG on 09-01-2009 01:26 AM

[devchander]

Hello Jack,

Thank you for that input.

Please do share information on the property node, which you observed to be causing this delay

It will help us to investigate this behaviour quicker 

Can you please give one additional information?

Which Windows version are you using?

Dev

[Paul@LeT]

Hey all, I work with Jack.

Dev, the property node was a red herring.  We still have a long front panel delay after nuking the property node.  Jan_HeG on 8-28 gave a good description of the behavior.  This is what I’m seeing:

1)      Click Run on the top-level vi.

2)      Watch the green progress bar advance normally.

3)      The Run Arrow goes black.

4)      The cRIO application starts immediately.

5)      WAIT, wait, wait on the Front Panel to become active (about 80 seconds).

During the wait the front panel is unresponsive.  Indicators do not update.  Controls cannot be selected.  There is constant traffic on the Ethernet port to the host.  The cRIO CPU has about 10% more “normal priority” usage according to Real-Time System Manager.

I am running W-XP with a cross-over cable to the cRIO.  Jack is using Vista.  The “bad” property node was getting the text value of an enum.  I replaced it with a Format Into String. (Thanks for post “formatting an enum into a string” by shoneill on 3-9-05.)

Paul

[devchander]

Thany you for that information Paul

I will get back to you

[George_P_Burdell]

All-

A Corrective Action Request (CAR 176549) has been created for this and is under further investigation by our R&D department.  Until a solution to fix the route of the problem has been created, a work around has been found by following these 3 steps:

1. Simply Deploy all the VIs. 
2. Disconnect from your target.
3. Reconnect to your target.

This should fix this issue until the route of this problem has been resolved.

[Paul@LeT]

Mike,  I tried your work around but the behavior was the same.  This is what I did:

1)Opened the project

2)RT/Click the top level vi

3)Select Deploy

4)Wait for the deployment (normal)

5)Rt/Click on the cRIO

6)Select Disconnect

7Rt/Click on the cRIO

8)Select Connect

9)Wait for connection deployment (as expected)

10)Click Run arrow on top level vi's front panel

11)Application starts immediately on the cRIO but the front panel on the host is inactive

12)Wait, wait, wait for the front panel to become active (97 seconds from the click on the Run arrow)

The wait still happens.  What did I miss?

Paul

[persyMG]

Hi

I have exactly the same problem with PXI 8106 RT. (I've just upgraded it from 8.6 to 2009)

After VI deployment, front panel doesn't respond for quite some time (30~40s in my case). Additionally the CPU usage on my PC is ~10% higher than normal during this wait period. Before upgrading - the same VIs and their front panels worked immediately after deployment.

So the problem may be related to Real Time software in general - not to cRIO or PXI it self.