Assigned myself Challenge 1 (Timer) - personally i think this should change to incorporate some form of pause functionality as most CLD exams require pausing of a time (car wash for example), this would bring it more into line with the exams and take it away from using the timer express vi which lets say has its limitations....
Let me know your thoughts.
Assigned myself Challenge 1 (Timer) - personally i think this should change to incorporate some form of pause functionality as most CLD exams require pausing of a time (car wash for example),
I agree, knowing how to do an elapsed time with a pause ability is very useful for the CLD.
I'll be happy to take #15
Hi all. Happy to see some movement here!
On adding Pause to CLD 1: Careful -- the exercises are intended to build. Exercise 1 is an introduction to timing. Exercise 2 introduces using an FGV for the timer, and Pause is added in Exercise 3.
If the consensus is that it would be helpful to add Pause to the non-FGV timer using the Elapsed Time Express VI, perhaps it could be added as an "Extension" section, and the Extension solution saved separately. Or perhaps you could take a look at CLD 3, verify that Pause is introduced & handled well.
|1 Elapsed Time Express||Simple Timer using Express VI, Elapsed Time & Reset|
|2 Elapsed Time Express Caller||Timer FGV using Express VI, Elapsed Time & Auto Reset|
|3 FGV Timer||Timer FGV using Get Date/Time in Seconds, Elapsed Time, Auto Reset & Pause|
|4 Event Structure Time Out|
|5 Parse Config Data File||Read .ini, parse to Cluster|
|6 CSV file utility||Read/Write .csv, parse to Cluster Array|
|7 Time Stamp Parsing||Parse Time Stamp to Strings|
|8 CSV file commands utility||Read/Write .csv, parse to Cluster Array|
|9 Step Sequencer with Express Timer|
|10 Elapsed Time Express VI Step Sequencer|
|11 Producer Consumer|
|12 Sequencer State Machine||Sequence steps based on data loaded from a file.|
|13 Flow Rates|
|14 Timer Application||State machine, loads time targets from file, runs timer for durations, with pause and cancel|
|15 Text String Parsing||Reads .csv then parse, processes, formats, and save data in a new .csv file|
|16 State Machine with Enables and Disables|
|17 GUI keypad||Read keypad GUI, output in string and numeric format.|
I had a look at CLD Success Package solution #1, and revamped it. (Somehow I cannot create a new thread on the Certifications sub-forum, therefore I post in this thread.)
I implemented only two minor changes:
Note: Currently, there is a flaw in the Exercise VI: The Front Panel provided contains an "Elapsed Time" String Indicator, however the Solution contains an "Elapsed Time (s)" Numeric Indicator (which is also shown in the Exercise 1 instructions PDF)! The Numeric Indicator makes much more sense, so in my eyes the Exercise VI needs to be changed as well.
Hi ikaiser. Thank you. This looks pretty straightforward.
Other opinions & comments please?
Thanks, all. I'll be looking at other submissions next, realize there's a backlog.
Thank you for your quick reply.
- I would like a little community input on removing the Close Reference.
I agree that commenting it to explain would be a good solution. Both possible versions (closing + "explanation comment" or not closing + "explanation comment") tell the learning programmer why exactly happens there.
Not closing and not explaining why can lead to false conclusions, closing although it is not needed as well.
I worked through Exercise 2 and found some things I'd like to improve.
Regarding the instructions pdf:
Also, "CLD 2 Elapsed Time Express FGV Solution.vi" does not match the requirements give in the instructions pdf:
I changed the solution FGV vi to match the instructions pdf, also introducing some other changes:
I attached the solution FGV VI only, the tester VI and .ctls I left unchanged.