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
Sample Exam Solutions for Review
@rk__Tinelli wrote:
Hey everyone, this is my CLA trial for the Car Wash.
I did not finish it within the 4 hours for the test, and still missing some of the requirements. I left the requirements tag file in there so you all can see what was missing.
Any feedback is more than welcome.
Thanks in advance.
If I had to pick one, the thing I'd put in a class is the timer. It's the only thing you put in a (unfinished) function global.
I'd also simply wire the stop user event to each module. Why use a buffer for that?
These decisions are not really relevant, I think for CLA you can do as you like. It's just that mixing FG and OO is a bit funky to me.
You've implemented to much stuff. The config database, the error handler. That is not required. Simply make the modules, or even put some text somewhere that a module should be made. But do not implement the module. It's a waste of time, you do not get credit for it.
You don't need to implement a stop event buffer. Simply make a VI, and put the requirements in there. "This VI will buffer the stop event. It's a function global, initialized at startup, and used by each module.". Or even, on the main: " A functional buffer will distribute the stop user event. It will be initialized at start and read by each module. Close the buffer when the program finishes".
Put more time in the tagging. Each tag [Covers: ABC] should also have a small text explaining how it should work. I think this is tested automatically. It does not need to be a lot of text.
Search LabVIEW like a graph!
@rk__Tinelli wrote:I didn't get your point about the Class timer you mentioned. Also can you explain what you meant about the use of the stop buffer?
It seems your timer is going to be a functional global. With the function enum...
FGs have downsides. For instance, if you want a 2nd timer, that's simply not possible if the timer is a FG.
If the FG has 3 functions, init, reset, and read (just as an example) a class timer would have 3 VIs: init, reset and read. But the data would not live in shift registers of a FG, but in the class's private data.
This would give you the complete re-usability of the timer. You could even make an array of timers.
Perhaps I'm wrong about your plans though.
@rk__Tinelli wrote:I didn't get your point about the Class timer you mentioned. Also can you explain what you meant about the use of the stop buffer?
I started my project using the Queue Message Handler Template, which gave me mos of the function for the user event. I wrapped it up in a API to all the modules to use.
The user event is just a reference that is created at the beginning. Not sure what the purpose of a FG is.
You get the same FG problems as mentioned before.
In stead of putting the user event in a FG, you can simply wire the user event reference to each module that you start. The module can then use it.
This saves one FG, but it also let's you see clearly which VIs use the user event. When things get more complicated, this can be a great help. With FGs, you'd always need a find all instances to give you this information.
I like my solutions to be as simple as they can be. A FG when a wire can be used is just complexity that is not needed. It's also what I don't like about frameworks\templates.
Pretty sure this is nothing to worry about for the CLA.
