Sample Exam Solutions for Review

[CFrias]

These are the operation steps from the pdf

1) Run Interlock set to close

2) Press Reset

3) Press Start Sequence

4) Time Count, counts to 10

5) Press Pilot once 10 is reached

6) Set Flame Sensor to over 50%

7) Turn on Forced Draft Fan

😎 Set Fuel Control Valve Position to over 30%

9) Press Shutdown, set interlock to open, or reduce fuel to less than 30% any of these will start time count

10) Time Count, counts to 10

At this point all the controls are set back to their default values but the main vi has not been stopped so the while loop is still running and we can go through the steps again.  If I try to run it at this point step 4 and 10 get skipped and the Time count never changes for 0.  So I can run it once but the second time around it doesn't count.

[wiebe@CARYA]

The elapsed time express VI (and most express VIs) are very limited in their applicability.

It's often harder to use it than it is to make your own timer.

Might as well make it by wire (as LV is supposed to be 😎).

See attached class. Now don't be scared, it's probably a nice intro to OO if it's your first contact.

I practiced making such a timer for my CLD, so I could make one in 5 minutes, while letting the first read of the exam sink in.

[wiebe@CARYA]

---

@CFrias wrote:

7) Turn on Forced Draft Fan

😎 Set Fuel Control Valve Position to over 30%

9) Press Shutdown, set interlock to open, or reduce fuel to less than 30% any of these will start time count

---

Step 8 is cool 😎.

[CFrias]

I am taking the exam at the end of the month.  Anyone one have any thoughts on how I made the sprinkler system.  I appreciate the feedback

[CFrias]

We did it boys.  Thanks to everyone who helped out.  Just got my CLD today

[JoGra]

Hi, 

I have also prepared a solution for the ATM. 

My approach for simpler programs is usually to keep the main data in a cluster and mange complexcity through multiple states/cases with with JKI state machine.

For this CLD sample exam was keeping i similarly flat in structure with only few subvis to organise the blockdiagram. 

I saw in the other solutions for the ATM that many make the "account" handler self contained subsystem. How value is given in the evaluation that the code has a hierarchical structure with subsystems (even if its not really necessary imo)?

Thank you!

[rdeka]

Hi all,

Here are one of the many types of solution I created for the CLD Sample Exam papers.

Please have a look and let me know what areas I can work on to improve.

(I was suppose to give my online exam on 8th of March but after waiting 2 hours of "troubleshooting" my exam did not happened. I emailed ni certification and waiting to hear back).

Cheers,

Rahul

[wiebe@CARYA]

---

@rdeka wrote:

Here are one of the many types of solution I created for the CLD Sample Exam papers.

Please have a look and let me know what areas I can work on to improve.

---

EDIT: Not sure if I looked at the right code here. There are 2 car wash solutions in your zip. Seems like a bad idea...

After just a quick glance at the car wash...

The uninitialized shift register (esp. the error) could be problematic. If there is an error, the program will not run properly the 2nd run. Either initialize it before the state machine or in the init. Not a problem in the car wash (there won't be errors), but in general a red flag.

The cases  "Underbody Wash", "Bug Remover", "Presoak", "HP Wash", "LP Wax", "Spot Free Rinse", "Tire Shine", "Air Dry" are almost entirely duplicates of each other. Put the differences in a for loop and index on the case (for instance) so you don't have all this duplicate code. You might not loose points on the CLD (you might, and should, but maybe not), but think about what happens if you forgot something before duplicating. You have to change it 9 times, losing time, risking mistakes.

Determine Wash Cycle is just a lot of repetitive code too:

Try to do this in a for loop (not tested):

Less work, less code, less wires to straighten, less room for mistakes.

So mostly things to save you time...

Duplicate (and repetitive) code isn't as innocent as it seems though. It takes time to make, more time to work with, and time to refactor. That's 3X the time to do it right the 1st time 😁 .In CLD's and in real project.

Be lazy: don't duplicate code!

[rdeka]

Hi @wiebe@CARYA,

Thank you for looking into it. And I should've been clearer.

My code is in "USB Template (LV 8.6)" folders. The ones in Solution folder are actually provided by NI.

My solutions are the ones with QMH.

Kind Regards,

Rahul

[wiebe@CARYA]

---

@rdeka wrote:

My code is in "USB Template (LV 8.6)" folders. The ones in Solution folder are actually provided by NI.

My solutions are the ones with QMH.

---

Well, their solution is only 3 VIs and 4 controls. 😂