Leaderboard

You don't have to choose between classes and polymorphic VIs. You can get the inheritance you want, automatic function selection, and you can make it an edit-time error you choose the wrong read and task creation combination. Check out this example of dummy classes. Open example.vi attached here (saved in LV 2012) to get an idea of what I mean. We have done this in our classes before with great success. In fact this can work better than doing Dynamic Dispatch for your reads, because there is no run-time overhead for LabVIEW to determine what Read VI to call. But you still have the flexibility to define your OOP hierarchy. daq classes.zip

The first attempt I made was not good and is more of an example of what not to do than what to do. And honestly, I'm not sure if I have it anymore but I'll check later if I can dig it up. I will say, before the test I never felt completely comfortable. I was always in a serious time crunch, and I don't know if I ever finished the practice exam in the 4 hours allotted. I was crammed for time at the end of the actual exam also. So, if you're waiting for that "ok, I'm ready" feeling, you probably aren't going to ever get it! What I found helped the most was practice as best you can and realize that in your day-to-day job you have most likely done things far more complex and those things will prepare you better than any amount of practice can. If, through your code, you can get across to the graders the point that you know how to architect, I am sure you'll be good to go. Again, I'll see if I can dig up some of the practice stuff I did, but later attempts were purely regurgitation of the solution, so they probably won't help you too much, if I even still have them.

I agree -- the design is not something I would ever use in the real world. I forget which CLA example I looked at (is there only one?) but I do remember it is very consistent/misleading as far as what is important. They implemented an entire error handler if I remember correctly! I would suggest not doing this on the test. IMO an error handler "shell" with comments will suffice. You may find actor oriented solutions to be the best solution for the problem, but is it the best solution for passing the test? These two things are inherently different (especially when there is a time limit) and as engineers we always want the best solution to the problem. But, now we find ourselves thrown in a situation (just make it "good enough") that completely contradicts what we have been molded to do! It's a difficult balance, but I trust you'll find it.

A kind soul at ni.com as built the executable; all is well http://forums.ni.com/t5/LabVIEW/built-it-for-me/m-p/2469268 weld3li, good luck for your project. I'm just curious; how come your supervisor wants you to build an .exe if he/she knows it's hard to get Application Builder in your country?