Jump to content

Wire Warrior

Members
 View Profile  See their activity

  • Posts

    226

  • Joined

  • Last visited

  • Days Won

    3

 Content Type 

Everything posted by Wire Warrior

  1. Wire Warrior

    Cool! RT @mballa Just met a 14 year old that just passed his clad. That made my day. #NIweek

  2. Wire Warrior

    The #NIWeek session "Advanced Error Handling In LabVIEW" was very informative. Take it later this week if you can!

  3. Wire Warrior

    Hanging at The Ginger Man with @crelf and Justin G. #niweek

  4. Wire Warrior

    #niweek RT @WireWarrior http://yfrog.com/kioddmlj Just checked in!

  5. Wire Warrior

    Just passed the state line headed to Austin for #NIWeek!

  6. Wire Warrior

    The bags are packed for #NIWeek ready to leave tomorrow morning. Now to join some kebabs with friends.

  7. Wire Warrior

    What a great prize! RT @vishots This is pure awesomeness: http://bit.ly/nX7j9U LabVIEW 1.0 Emulator LAVA door prize.

  8. Wire Warrior

    Heading to pickup the rental car for #NIWeek. This looks like a great trip.

  9. Wire Warrior
    Hard to say what might be happening without seeing some code. Can you post your code for us to look at ? Jason
  10. Wire Warrior
    I like some of the new features! Jason
  11. Wire Warrior
    One thing I have noticed on my MAC at home is that there is limited support for some of the DAQmx features. Might be worth a call to your NI rep to ask if you are running into some kind of limitation because the evaulation/MAC combo. Jason
  12. Wire Warrior
    I believe that LV2011 will be released next week during NIWeek. Keep an eye out then for the details. Jason
  13. Wire Warrior
    Sharon, Check your connection there. I think you need to initialize the task and then connect the task reference to the acquisition VI. Jason
  14. Wire Warrior
    Excellent! Thanks for the map. Jason
  15. Wire Warrior
    jkuehn, You can do what your wanting by using dynamic events. If you search for that in the example finder I believe you will find some examples. Basically you need to pass the reference for the control of the subVI to the 'control' VI where you will register the specific type of event you want to process, mouse over, value change, etc. Jason
  16. Wire Warrior

    #NIWeek thought "Wear Pants!"

  17. Wire Warrior

    Grilling some steaks and just relaxing. It's a nice day.

  18. Wire Warrior

    Only 3 weeks to go 'til #NIWeek. I am really looking forward to it!

  19. Wire Warrior
    Oh this sounds SOOO much like conversation at my house with my two boys (17 yo and 16 yo). The other day I looked at one of them and said "You know....you're going to be amazed at how much smarter I get over the next 5 years. Do what you got to do." Though lately letting the older one get the 1969 Ford F100 truck has taught some valuable lessons. Turns out I knew more than he thought about the amount of work and cost in such a project. LOL KIds....I wouldn't get rid of them for money. Usually...;-) Jason
  20. Wire Warrior
    Just purchased a LAVA T-shirt and a coffee mug. Thanks for the coupon! Jason
  21. Wire Warrior
    Christina's blog EyesOnVIs has a great post detailing the steps in control customization here http://blog.eyesonvi...bview-buttons/. I recommend you check that out Jason
  22. Wire Warrior
    It sounds like you also have a good case for the use of a Hardware Abstraction Layer (HAL) as discussed in the 2011 Developer Day presentation here. This covers some concepts regarding removal/substitution/inclusion of instrumentation components using LVOOP techniques. I found it quite educational and informative. All of the example code slides and scripts are there for download. The situation you are coding for sounds like the conceptual "ideal" poster child for OOP techniques. The architecture you use needs to handle the variability of hardware, tested units, operators, etc. that occur from maintenance/growth of long time use. Jason
  23. Wire Warrior
    You should also check the instrument driver network on the NI site. Might be something available there that supports your device. Jason
  24. Wire Warrior
    Well.....beef is a primary ingredient in BBQ. Jason
  25. Wire Warrior
    I think she's making a reference to the "Keep Austin Weird" logo/saying that is part of the Austin, TX local culture.
×
×
  • Create New...

Important Information

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

  I accept