Jump to content

jcarmody

Members
  • Posts

    947
  • Joined

  • Last visited

  • Days Won

    39

Everything posted by jcarmody

  1. QUOTE (Vidula S @ Sep 18 2008, 12:54 PM) I'd do it like this: http://lavag.org/old_files/post-7534-1221834955.vi'>Download File:post-7534-1221834955.vi Perhaps there's a way to use property nodes for the indicator? I don't know. Maybe somebody else will comment on this. (I hope ) This VI uses a boolean 'enable' control and a boolean 'last enabled state' shift register, and another String shift register to store the data while the indicator is disabled. The key is to catch when the enabled state changes and then put the current data (either from the indicator or the shift register) into the appropriate container. These are the 'enable' states & transitions I was interested in: start/stay TRUE - append data to string indicator start/stay FALSE - append data to shift register TRUE - FALSE - put string indicator value into shift register and append data there FALSE - TRUE - put shift register value into string indicator and append data there I hope this helps! Jm I finally have a LabVIEW icon under my name!!! :laugh: Yippee!
  2. QUOTE (Antoine Châlons @ Sep 18 2008, 10:27 AM) I've been using it recently on a project I inherited. I'd never make a VI that didn't fit on one screen! NI had their mobile expo in our parking lot a few weeks ago (very cool) and I mentioned that students in a few LabVIEW Basics classes had asked me about a zoom feature. His answer was that NI has resisted doing that so as not to encourage large block diagrams. I wonder why they even have the navigation window. Jm
  3. jcarmody

    Alfa String

    QUOTE (alfa @ Sep 9 2008, 04:10 AM) In communist (Soviet) Russia, forums watch YOU! Yakov
  4. I've inherited a bunch of spaghetti code, some of the most tangled bunches of wire you've ever seen. But, as bad as they are, I was able to understand & extend them. I've attached my favorite example of horrible code. The best thing about it is that I can point to the spaghetti code (written by coworkers) and honestly say it's not the worst I've seen.
  5. QUOTE (PJM_labview @ Sep 6 2008, 09:02 PM) I went from the VIC20 to the C64. I still have it in the garage.
  6. Let us know who you are My name is Jim Carmody. I'm a Mechanical Engineer/CLD/CPI with (almost) two whole years of LabVIEW experience. where you’re from I'm from Connecticut, but I've been living in North Carolina for the last four years. what you do I've been working as a Test Engineer for in the aerospace/defense industry for the past four months. whatever I've been programming forever (I began with BASIC on a Commodore VIC20). I've solved some interesting problems over the years but I've never been anything more than a pretty good amateur. I started using LabVIEW when I took a position as a Software Engineer, learning the language on-the-job, and becoming very fond of it along the way. I lurk around lavag.org because I want to become an excellent LabVIEW programmer and I'm hoping that spending time in this community will help me grow.
  7. QUOTE (Darren @ Aug 27 2008, 11:01 AM) Thanks. I thought you were referring to a pre-8.6 trick. I'd have know if I had installed 8.6. Jm
  8. QUOTE (Darren @ Aug 26 2008, 03:58 PM) How do you make shortcuts? Jim
  9. There's an interesting article on the NI Developers Zone about this - http://zone.ni.com/devzone/cda/tut/p/id/5313
  10. CPI was easier to get than CLD. I spent about 5 hours in a TX NI classroom, made a short presentation (about while loops) and went home. I've taught two LabVIEW Basics (I & II) classes. Teaching is fun, not at all like working! The preparation beforehand is a lot of work, though. Jim CLD/CPI
×
×
  • Create New...

Important Information

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