Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by jcarmody

  1. QUOTE (hariprasad @ Jan 10 2009, 03:50 AM) NI published a piece yesterday that describes Software-Defined instrumentation; it may give you a better idea of virtual instrumentation. This will give you an idea of what LabVIEW can do, and this will tell you how much it costs. Good luck with your interview! Jim
  2. QUOTE (mic_k86 @ Jan 9 2009, 10:19 AM) I like doing http://tinyurl.com/9wl6yb' rel='nofollow' target="_blank">this j
  3. QUOTE (Gilligan.Mark @ Jan 6 2009, 11:01 AM) Hi Mark, welcome to LAVA. Don't feel at all bad about asking questions; folks around here love to help (just try to search for the answers before asking the forum). You're welcome to think of this as your island in a sea of information. Kind of like a Gilligan's island... Now that that's out of the way...
  4. QUOTE (neB @ Dec 29 2008, 02:02 PM) Yep .
  5. QUOTE (hanady @ Dec 29 2008, 12:12 PM) http://lavag.org/old_files/monthly_12_2008/post-7534-1230576120.gif' target="_blank"> :laugh: Give me your code, Horsemaster, and I shall give you mine. :laugh:
  6. QUOTE (crelf @ Dec 23 2008, 11:10 AM) Thanks for the link. He's fantastic! It's wonderful to find an extroverted engineer. Jim PS - How do you tell an extroverted engineer from an introverted one? The extroverted engineer looks at your shoes when he's talking to you.
  7. QUOTE (El Tipo @ Dec 22 2008, 12:35 AM) Ask any time. Have fun learning LabVIEW; this forum is full of folks that will help.
  8. QUOTE (El Tipo @ Dec 21 2008, 02:00 AM) version 8.0 Download File:post-7534-1229864301.viQUOTE when you said u didnt like the subicon u meant that it could have been done for example pasting a picture instead of actually write something on it? or u meant something else? I included a link to an icon editor written by one of the LAVA contributors. It's a really neat way to identify your VIs by using colors, categories and text. A bit like you did, but on steroids. QUOTE I did not fully understand when you stated that I was planning to get the password from an external source. Am planning to make a final program and make an executable and have some sort of security on it. I was just suggesting that hard-coding the password into your program means that you'd need to build a new executable in order to change the password. That's fine if you're working on your desktop, but some folks need to release software through their Quality department and can't be modifying software every time a password is compromised (like when a user writes it on the monitor...). QUOTE The reson why I used the stop function was because I've never used that function and I can't recall ever seeing it used. LabVIEW help says this about it: "Before you call this function with a TRUE input, be sure to complete all final tasks for the VI first, such as closing files, setting safe values for devices being controlled, and so on." I brought this up because you probably don't need it. Are you familiar with State Machines? They have advantages over the stacked sequence structure; they're worth learning. (I like the , myself.) Jim
  9. QUOTE (El Tipo @ Dec 20 2008, 02:41 PM) I don't know about this...QUOTE what i want is that if the password is not right the first 2 times it closes the main program, as well as the subvi (i dont like it on top of the main VI) and if the password is right then close the subVI or take it from the top of the main VI and be able to run the main normally. I would like to know if my aproach is the correct one. thaks for any help. regards : Pedro E. There are many ways to crack a nut. There's probably not a correct way, only a better way. QUOTE otherwise give me some advice on how can I do this. My way may not be better, FWIW... Let me know if I misunderstood what you were going for. I've never used the Stop function, perhaps someone else could tell us why to use it. I didn't use it in my solution. You made your subVI a little more complicated than it needs to be. Take a look at the attached VI. You didn't need any code in the False case of your main VI; it would have closed anyway. I don't love local variables, but they're easy when you need to do what you did. I didn't like your subVI icon. There's a better way. :thumbup: You may have already planned to get the real password from an external source. It's better than hard-coding it. I'll wait for others to chime in with a BETTER way. LAVA is a good place to be. Here's what I did. Download File:post-7534-1229821372.vi Regards, Jim
  10. QUOTE (ASTDan @ Dec 20 2008, 12:02 AM) I agree with Dan; the books are great. I learned LabVIEW by reading those books, reading other people's code, studying the practice exams and asking a lot of questions. LAVA is the right place to come if you want to ask lots of questions while you're going through the books :thumbup: .
  11. I have only one on YouTube, and it's fits in this category. My smoke wasn't caused by an electrical fire; you can see a burning pine cone on the vacuum's exhaust for a few seconds in the beginning.
  12. Try here first, and if that doesn't help try here. Glad to help!
  13. jcarmody

    Alfa String

    QUOTE (alfa @ Dec 15 2008, 03:01 AM) How did he know it was the last year of his life?
  14. Not everybody searches the LAVA (or NI) forum before asking a question. Here's a gentle way to demonstrate how easy it is to find an answer to a question that's already been asked.
  15. QUOTE (Michael_Aivaliotis @ Dec 9 2008, 01:01 AM) I was hoping he could explain my signature first...
  16. QUOTE (crelf @ Dec 8 2008, 07:13 PM) ... for very small values of R!
  17. An anagram: "Charles Andrew Ososami" = "Now as melodic harasser" Charles, do you sing? From: "Joy! Mad scream."
  18. Is it because this is a bot not a real person that you came to me?
  19. I understand that the Lava Lounge allows us to "Enter the lounge and discuss anything and everything." and that "Nothing is off-topic and all discussions are encouraged." but this is ridiculous. Charlie is offensive and his bad grammar makes me [sic]. :thumbdown: :headbang: PS - my member number is not a palindrome, but if you write it forwards and then backwards it inexplicably becomes one. Additionally, the prime factors of 7534 are 2 and 3767 - both of these prime factors are prime. Can you believe it? Finally, divide my member number by pi (my avatar shows my affinity for pi) and you get (approximately) 2398.146682508678919365540546497. This is freaking me out; I'm going to stop writing now...
  20. QUOTE (Pollux @ Dec 4 2008, 04:25 AM) You could bundle all of your controls and carry them around in a shift register to get rid of the local variables. Adding error in/out terminals to your subVIs will let you enforce data flow without flat sequences. you can replace the select statements that return a 1 or 0 with a Boolean To (0,1) use another state to sync the front panel indicators to the data cluster when necessary http://lavag.org/old_files/monthly_12_2008/post-7534-1228391339.png' target="_blank">
  21. QUOTE (mballa @ Nov 28 2008, 02:17 AM) Thanks, Mark. I watched the video and have since had no trouble getting the connections I want. The method seemed familiar; the information must have been in another post but it didn't stick until now.
  22. QUOTE (matthike @ Nov 26 2008, 12:32 PM) This has been done before. http://www.google.com/search?hl=en&client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&hs=yrO&q=site%3Aforums.ni.com+tetris&btnG=Search' target="_blank">Search the LabVIEW forum and you'll find a plethora of information. Jim
  23. QUOTE (asbo @ Nov 24 2008, 11:11 AM) That was my first thought, too. I can't imagine why anyone would need that; I'm hoping there's something more to it.
  24. QUOTE (miab2234 @ Nov 24 2008, 09:54 AM) I don't know what you mean by "make an LED showing EX:ABC". I looked at the VI you attached and found it strangely familiar ... All you did was replace the boolean indicator and translate the comments. Jim
  25. QUOTE (miab2234 @ Nov 23 2008, 03:30 PM) Miab, It stops at 2 because you're comparing the value in the shift register (initialized at 1) with a constant 1 inside the loop. This loop will only execute one time and, even if you changed this comparison, it will never become a 2-D array of LEDs that go on and off one by one. I'm not sure where you were going with your VI so I wrote my own! The code is commented so you might be able to see what I had in mind (I have good days, and I have bad days ). This approach is limited, but I don't know what your requirements are so I didn't spend too much time on it. Let me know if you need more than 64 elements in your 2-D array and I'll try to help you figure it out. Jim
  • Create New...

Important Information

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