Jump to content

Fab

Members
  • Posts

    193
  • Joined

  • Last visited

  • Days Won

    15

Everything posted by Fab

  1. RT @crelfpro: Code in LabVIEW? You're going to want to watch one of my favorite sessions from #NIWeek by @delacorllc -> https://t.co/PbvLsg…

  2. Excited to be presenting at the San Antonio #LabVIEW Users Group Meeting - Thursday Nov 5 at 11:30 AM County Line https://t.co/0ZMHrtWNaO

  3. #LabVIEW NI Unit Test Framework falsely passing test expecting NaNs array? Use User Defined Tests @NIglobal @LabVIEW https://t.co/OMvwgt9ASj

  4. RT @RahmanNow: If you are in peace with yourself it will express itself in kindness, compassion, love and life will flow with ease🌻 https:/…

  5. RT @DesruelleLuc: Un tutoriel français "comment apprendre à utiliser LabVIEW" sur https://t.co/hX0uA9ppZm https://t.co/kt4zKKHH1Q

  6. We finally got around to recording the presentation given at NI Week 2015. https://t.co/U9V2WKtXzj https://t.co/YOHDr0cAAK

  7. Awesome forgotten #LabVIEW feature, available since 1.2 !! Thanks @swatzyssdc for sharing https://t.co/5C1SLactDQ

  8. RT @delacorllc: @RoebuckChris teaching "5 tips to bring order to your development chaos" at the CLD Summit #LabVIEW @niukie http://t.co/L4Y…

  9. Enjoyed being virtually there, thanks for calling guys! Enjoy CLD Summit :) Congrats on the award again. @RoebuckChris @swatzyssdc @niukie

  10. RT @delacorllc: Amped to see DQMH mentioned in the keynote at the European CLD Summit #LabVIEW @niukie http://t.co/nRUkVhuX6W

  11. I think this could apply to software/hardware consulting as well ;)https://t.co/KgdkDPjsYa

  12. Revisiting Source Code Control and couple of videos on how to setup #LabVIEW with SVN, Hg & Git @NIglobal @labview https://t.co/11NzQUGyI2

  13. We are also fighting the problem via the scripting tools. Automating the busy work and abstracting that away from junior developers. In our experience, explaining the concept of user events and how the information is transmitted from DQMH module to module has never been the problem. The problem is when the junior developer has to remember all the steps needed to create a user event. With the scripting tools we automate most of the busy work and let the junior developer do the final connection of editing the event structure case to handle the specific event, but they don't have to worry about remembering to add the new event to the typedef, to the destroy events, to the create event, etc, etc. standardization was a big part for the Delacor team deciding to use the NI QMH as our springboard. The producer/consumer and QMH templates were the ones we realized most of the junior developers we encountered were familiar with. This is one of the reasons the Main module looks a lot like the NI QMH template, with minor exceptions. Glad to know that DQMH is one of your options for your future projects. Let us know if you decide to go with it. Also good to know that you find both the videos and the scripting tools useful. This inspires us to continue to create such tools for the community.
  14. "Team formation for Success" on @LinkedIn Ideas to guide #FIRST teams and perhaps some other teams as well https://t.co/Aq4YaHgR0M

  15. RT @jamesmc86: Great article, also a good way to think about hiring consultants - http://t.co/5rJlpTzANS

  16. We address this via the Cloneable DQMH Module. It already comes with clone management and at run time the N number of instances to launch can be selected. We have an example of this in the shipping example. The DUT is a cloneable module. When a DQMH module is created, the tester comes with a button that shows the block diagram of the DQMH Module Main. If the DQMH module is cloneable, then it will show the block diagram for all instances if the ring is set to "All" or it shows the block diagram for the requested instance. This feature was not included in the shipping example, but you can see it in a project created via the DQMH Project template or by adding a DQMH module to your project. In our experience, junior developers get around via the DQMH API Tester to know what is running or pressing the "Show block diagram" button on the tester to see what is going on in the DQMH Main. Most of the time they do not need to go that deep and having a simple API with simple API calls: Start, Show Panel, Hide Panel, Stop, etc means they can do simple VIs that just call a chain of these calls. If they need to debug, they just need to run the tester and use it as a sniffer.
  17. RT @NathanTippy: #ProgrammingTime spent thinking about code to be written is much more important than time spent writing code. Re-Tweet i…

  18. And so it begins the post #NIweek blues. Safe travels to all our #LabVIEW friends, see you next year!!

  19. RT @delacorllc: Don't miss Chris' Don't Panic: #LabVIEW Developer's Guide to #TestStand Thursday, August 6     2:00 PM  Room 16B #NIweek #D…

  20. RT @mickeymcmanus: Happy birthday to Dave Wilson! Today he's offered himself as science guinea pig for #niweek keynotes! http://t.co/6gmCfF…

  21. RT @delacorllc: Don't miss TS6421 - Chris' Don't Panic: #LabVIEW Developer's Guide to #TestStand Thursday, August 6     2:00 PM  Room 16B #…

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.