09-22-2015 11:32 AM
Here's the question:
Q30: While running a VI interactively from the development environment on a LabVIEW Real-Time target you get this dialog. What is NOT a possible cause of this dialog?
Waiting for Real-Time target (myRT-Target) to respond.
Stop Waiting and Disconnect
A Real-Time target rebooted
B Real-Time OS network thread starvation
C Network cable disconnection
D Real-Time application allocated too much memory
It seems like A and D would be the same because D would cause a reboot right?
B and C also seem similar because that would disable network comm.
Solved! Go to Solution.
09-24-2015 06:44 AM
A is not the same as D, as there will be no automatic reboot, if memory is full
(only the application will stop, but system will be able to communicate)
So, D is the desired answer.
Hint for the exam:
The Compact RIO Developer Guide will be extremely helpful (more than other course content) for passing the theoretical part
http://www.ni.com/compactriodevguide/
09-25-2015 12:19 PM
Interesting!
I'm thinking on my past projects, I've had a watchdog and that's what was doing the reboot when memory was full.
Thanks for the info.
09-25-2015 12:50 PM
@AbandoningCausality wrote:
Interesting!
I'm thinking on my past projects, I've had a watchdog and that's what was doing the reboot when memory was full.
Thanks for the info.
Simple test case:
Drop in a "Data Queue PtByPt.vi" with "Sample Length" wired to +Inf.
Trust me, you won't see the
Waiting for Real-Time target (myRT-Target) to respond.
Stop Waiting and Disconnect
Dialog I know from experience