From 04:00 PM CDT – 08:00 PM CDT (09:00 PM UTC – 01:00 AM UTC) Tuesday, April 16, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
Certification
Finally!
I have finally passed the CLD!
My tips:
Before the exam:
Do all four of the practice exams at least once.
Have someone else review your practice exams. ( Post them on this board )
Day of the exam:
Get a good night's sleep.
Eat something before the exam.
Use the washroom before the exam.
Bring water.
Ask your exam proctor if you can customize the LabVIEW settings prior to starting the exam. ( I have read that this is allowed, but you'll need to remember to ask before you get your exam )
Read the entire specification before starting any code.
Divide the tasks up into logical steps. Remember, you might not have time to implement all of the program's features. But the program will still have to run to get points for functionality.
Be prepared for the curve ball! The creators of the exams were pretty crafty. Every exam I wrote had what I would consider to be a "curve ball" in it. A little twist that could make you stumble if your architecture is too rigid.
Run your code often! Especially when you start running out of time. I have failed this exam in the last five minutes by adding a feature that broke major functionality.
If you have time, close LabVIEW completely. Then re-open and run your code. ( Although if you're giving a very old PC to do your exam on I would advise against this. On my last exam, this was a very long five minutes )
Next, the CLA.
@pallen wrote:
Every exam I wrote had what I would consider to be a "curve ball" in it. A little twist that could make you stumble if your architecture is too rigid.
This is a great piece of advice from pallen. Keep it simple, especially early on. Plan ahead for things in the requirements that you might miss. Although you might have a concrete plan after reading the requirements through the first time, there's always something! You might forget to reset a counter, or clear an indicator, etc.
For example, say you initialize everything when the program starts (which is common with any program). What about re-initializing once the program has started? Maybe you should plan to access that initialize code again, passing slightly different parameters to it. This is just one example.
