09-04-2012 10:59 AM - edited 09-04-2012 11:01 AM
Here's some specific practice items you might work on in preparation for the CLD.
and the most important thing in my opinion, which has been said a lot but I'll say it again ....
09-04-2012 11:34 AM
These are really good tips.
I can't over emphasize the practice using a state machine. If you are not using a state machine, you are likely doing it wrong.
The hardest part of the exam is the time constaint. If you haven't practiced coding efficiently, get to it. Make sure your shortcuts and settings are setup before the exam starts (you are supposed to be allowed to set up the environment before starting the exam). Practice the exams. If you are not getting them done in the allotted time, you need to study up on your techniques. Most of all, do not second guess yourself. You do not have time to rearchitect your project. Choose an architecture and run with it. Simple state machines will work for 99% of the exams (I'm sure there's an exception somewhere out there).
One more key point: Document, document, document! Explain what you are doing with comments. If something doesn't seem right, document what you did. If you are running out of time, document what you still need to do in order to meet your requirements (you might get some mercy points). Documentation is by far the easiest points to get. So document as you go (especially the VI and control documentation).
09-13-2012 08:23 AM
If I would add just one tip; Run your code!
Don't wait until the last hour to run your code for the first time. If you run out of time and have no functionality then you will fail the exam regardless of your style or how well you documented your code. You don't have to complete all of the requirements to pass. But your functionality mark comes only from what works. Remember, you get no functionality points for things that "almost" work or things that would have worked if you had more time.
My advice is to get the most basic functionality coded, then get that working. As time starts to run out, make sure you test every time you add a new function. It's a shame to add that last feature and fail the exam because a little bug broke all your functionality.
09-17-2012 01:00 AM
In terms of time efficiency, a few thoughts. I haven't passed the CLD yet (1 week away for me), but this helped me improve my speed on the practice exams:
Good luck everyone!
09-21-2012 03:35 PM
Oh, in addition to Patrick's remark about making sure your code runs:
Before the test ends, you should close the entire project / exit LabVIEW, and re-open. Then try running your application again. This will catch any problems with uninitialized shift registers, default control/indicator values, etc. Leave enough time so you can debug from here if needed.
09-21-2012 06:19 PM
one more from me..
09-26-2012 08:21 PM - edited 09-26-2012 08:34 PM
what helped me most was...
btw, I was able to code the whole exam in just a while loop( a SIMPLE state machine is all you really need for it, so stop worrying about which architectural design to use)...
09-27-2012 12:02 AM
I took the exam today. With about 45 minutes left, I quit LabVIEW and tried reopening the project. The project file was corrupt and wouldn't open! I showed the proctor. Luckily all the VIs were still working, but this underlines the importance of shutting things down and opening up from scratch. I had to throw together a new project file.
When I turned in the test, the proctor checked it on his computer before sealing the USB stick into the envelope.
MAKE SURE YOU CHECK BEFORE YOU TURN IT IN!
09-27-2012 08:23 AM
@apok wrote:
[...]
btw, I was able to code the whole exam in just a while loop( a SIMPLE state machine is all you really need for it, so stop worrying about which architectural design to use)...
While I agree with that statement, it's a bit dangerous. We (the test takers) don't know what's in store for us. I'm not advocating to worry about architecture, but at least be familiar with the Producer Consumer and well as a good State Machine. By the time someone is to the level of taking the CLD (and having a chance of passing it), you should be comfortable with all of the architectures that are represented in the templates.
09-27-2012 09:09 AM
@Broken_Arrow wrote:
@apok wrote:
[...]
btw, I was able to code the whole exam in just a while loop( a SIMPLE state machine is all you really need for it, so stop worrying about which architectural design to use)...
While I agree with that statement, it's a bit dangerous. We (the test takers) don't know what's in store for us. I'm not advocating to worry about architecture, but at least be familiar with the Producer Consumer and well as a good State Machine. By the time someone is to the level of taking the CLD (and having a chance of passing it), you should be comfortable with all of the architectures that are represented in the templates.
ohhhhh! I agree...by the time you are ready,you should be comfortable with all the different various design architectures. I was just stating the fact that I was able to do it that way and in no way am I endorsing main vi w/sub vi's coding with a single while loop , it's just some members here get stuck with the idea of using the more complex style, when all that is really needed is the "simple state machine."