Certified LabVIEW Developer (CLD) Exam Demonstration

แชร์
ฝัง
  • เผยแพร่เมื่อ 20 ม.ค. 2025

ความคิดเห็น • 19

  • @Victor-bm3ie
    @Victor-bm3ie 7 ปีที่แล้ว +2

    Thanks for sharing this great video . This is the best CLD preparation video I ever seen. I just pass CLAD last month, and would like to try CLD test as next step. This video speed up my learning curve. I might try to attend exam next month.

  • @alexgu278
    @alexgu278 6 ปีที่แล้ว +1

    Tom, thanks a lot for your demonstration; however, would you please show us more details about the subvis?

  • @tomhawkins9561
    @tomhawkins9561 9 ปีที่แล้ว +3

    Thanks for this, some good tips. I would modify the advice about leaving 'fifteen minutes at the end' for documentation - you score a quarter of the exam marks just for this, so don't risk dropping any of them because you ran out of time! Make yourself stop coding at three hours or so and devote proper time to documenting the code and any remaining gaps, before going back to tidy up any remaining functionality.

  • @JKiler1
    @JKiler1 4 ปีที่แล้ว +1

    The producer-consumer loop template is not available in LabVIEW 2017, and I admit that I largely ignored the built-in templates until I finally went for my CLAD recently. I use producer-consumer when acquiring and recording high speed data, and have for quite some time, though. This architecture looks an awful lot like what became the QMH architecture.

  • @SciHeartJourney
    @SciHeartJourney 5 ปีที่แล้ว

    Thank you Mr. Brass! Excellent work. One thing I see right away is that I myself am not yet well enough prepared to take this test. I think I'll focus on passing the CLAD first. I've heard/read that we can take the CLD without CLAD certification now. I would not recommend this unless one were as proficient as you have demonstrated yourself to be.

  • @reniam
    @reniam 12 ปีที่แล้ว +3

    Thanks - Good video. Wish it was in HD though.

  • @jimharris6036
    @jimharris6036 10 ปีที่แล้ว +1

    Thanks for sharing. Great video. I had a couple questions:
    1. Is there a disadvantage of using the relatively new Project wizard 'Queued Message Handler' to create a similar framework for CLD exam?
    2. Have you posted the source code to your ATM solution at a web location?

  • @randomstupidchicken1900
    @randomstupidchicken1900 4 ปีที่แล้ว +1

    love your explanation, do you mind share the completed file?

  • @1357lucky
    @1357lucky 9 ปีที่แล้ว

    Really good video, a lot of good stuff, great ideas to handle the UI, and an elegant way to do the ATM, I've been trying to duplicate the entire design to fully understand it all (the resolution is a little rough), and just about have it except for the subVI details which look to be straightforward. I've taken the CLD 4 times now-just a little too slow to get enough functionality in 4 hours. The last time I used a producer- consumer and got really, really close. In my opinion, unless someone has been using this 3 loop producer consumer for several years, they're not going to be able to do it in 4 hours. NI doesn't give you enough points for an elegant design versus a simple one to make it worth the trouble and risk of having a broken, incomplete design. You have to have a good portion of the functionality (maybe half) to pass and I've decided to use a simple state machine for the next attempt. If anyone can do a design similar to yours in four hours, they don't need a CLD anyway. But its a very educational video.

    • @1357lucky
      @1357lucky 9 ปีที่แล้ว

      ***** Hi Tom, Thanks for the response. I will look forward to your Simple State Machine example. The File > Create Project> Simple State Machine gives you a Template with an Event Structure in a Wait for Event case of a state machine, which I think is probably the most efficient way to create a potentially passable exam solution (that I will try next time). I tried the Producer Consumer Events and I think it becomes a bit too complex for a four hour exam. What's odd is that they give you different pattern options if you choose File>New> versus File>Create Project so you have to remember which way to access your favorite pattern assuming you don't want to create it from scratch. Anyone else has any tips, I'd love to hear.

  • @sivonparansun
    @sivonparansun 6 ปีที่แล้ว

    What is the point of the shift registers for the queues in the consumer loops?

    • @miguelsegura1794
      @miguelsegura1794 6 ปีที่แล้ว

      It is not necessary tho. So do not worry about that.

  • @javierantonioruiz
    @javierantonioruiz 12 ปีที่แล้ว +4

    Great video. It has helped me a lot.

  • @Darkxxwolf17x
    @Darkxxwolf17x 10 ปีที่แล้ว

    Hi Tom - great video. I'm studying for this exam and found the producer-consumer for events template to be a good starting point for these exams also. Do you think using the queued message handler (QMH) would have made things any easier or provided any advantage over using the template? Thanks! - Leah

  • @rsmrostov
    @rsmrostov 8 ปีที่แล้ว

    Writing down how you would approach something when running out of time I was told will NOT give you any points.
    Great work (and fast!!!), I did notice a few style violations (wonder how this would do with VI Analyzer). Very little is documented, numeric constants, algorithms etc....
    But a lot of good pointers!!!!

  • @marklevine9657
    @marklevine9657 8 ปีที่แล้ว

    Tom, BLUF: I'd like you to post the code so I can absorb at my own pace. Thanks for the video. I've been using LabVIEW since 2.0 for the MAC and my code uses polling, global variables and flags to synchronize the GUI, data collection and processing. The consumer/producer template with queuing, the event structure, Type Def and Variant data is fascinating and I'm starting to play with it.

  • @ericbrenner690
    @ericbrenner690 5 ปีที่แล้ว +4

    Seems a bit elaborate for just a ATM Machine. I would have went with a simple state machine. Much simpler to implement.

    • @jcluttrell
      @jcluttrell 4 ปีที่แล้ว

      Disagree. SSM is not modular or scalable, especially when compared to the PC Loop. Modularity, scalability, readability, and maintainability is the first grading criteria.