Jump to content

jcarmody

Members
  • Posts

    947
  • Joined

  • Last visited

  • Days Won

    39

Posts posted by jcarmody

  1. 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: :angry::nono::(:unsure: :headbang: :lightbulb::throwpc::wacko:

    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...

  2. QUOTE (mballa @ Nov 28 2008, 02:17 AM)

    I started a series of http://forums.lavag.org/Auto-wire-FP-to-Connector-Pane-Tool-and-more-t9366.html&view=findpost&p=54874' target="_blank">videos to hopefully clear up any confusion.

    The first video covers the wire by arrangement function.

    Let me know what you think.

    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.

  3. QUOTE (miab2234 @ Nov 24 2008, 09:54 AM)

    Hi Guys,

    I want to go further with the programm and i want to make an LED showing EX:ABC and continous still i press Stop

    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 :unsure: ... All you did was replace the boolean indicator and translate the comments.

    Jim

  4. QUOTE (miab2234 @ Nov 23 2008, 03:30 PM)

    It do but the 2. Problem is it stops at 2. LED.But i want that it continuous.How can i do that ?

    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! :D 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 :wacko: ). 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

  5. I don't trust Google... :ninja: ... but I like it. I wonder what they're trying to replace with this; my first thought was that I could use it like I use Delicious. If they'd only add LabVIEW to Google Docs I'd never have to leave (oh, yeah, they'd need to add Emacs, too. I gotta have my Emacs! :wub: )

    post-7534-1227361159.gif?width=400

  6. QUOTE (mballa @ Nov 21 2008, 01:00 PM)

    I use it.

    Feedback:

    post-7534-1227308544.gif?width=400

    This example has an enum that I'd like to wire to the top/left terminal as show, but I never want the DBL in/out to be in the bottom row. (I'd only like this arrangement if those were error clusters.) I got this using "By Arrangement".

    When I used "By Pairs" I got this:

    post-7534-1227308549.gif?width=400

    This is closer, but it took the pairing concept too far (IMO) by putting the DBL in/out on top.

    I want the "By Arrangement" front panel with the "By Pairs" terminal selection, like this:

    post-7534-1227309806.gif?width=400

    Jim

    PS - I just noticed that the boolean indicator and DBL control were renamed.

    PPS - In another "BTW", I use (and like) your icon editor...

  7. QUOTE (asbo @ Nov 20 2008, 09:55 AM)

    I've seen this before - it's downright epic. What I can't wrap my head around though is why it was ever considered a good idea to move a semi with the trailer still open.

    That trailer has barn doors, not a roll-up door; you have to pull it away from the dock to close them. It would have been a good idea to block the carts in, though.

  8. I'd like to add one word of caution. Although these are all good questions to prepare you for the CLAD exam, they only scratch the surface of what you may face on the actual exam. I took the CLAD last year after practicing the online test many times; I even took screen shots of each question so I could go back and wire up every block diagram and study every conceptual question. In the end, when I sat down in front of the testing computer the first question didn't look like anything I saw during practice. That's fine, I thought, there are 39 more questions to go. Then, the second one was unfamiliar too. And the third... That how it went; I think that only a one or two questions were similar to ones I had seen during practice.

    So, I say to take the practice exams as many times as you can. Study the questions off-line (asking for discussion here is a good idea) but go through the Basics I & II material until you're very familiar with it. Also, when you're taking the actual test, take advantage of the testing software's ability to "mark" a question to review later. The actual CLAD isn't like the practice tests; you can keep going back to a question until you're satisfied with the answer (or, until your time runs out). I kept going through the questions until I had un-marked all of them. Keep in mind the way folks here are answering the questions; you can often dissect the grammar for clues to what the questioner has in mind as the correct answer.

    Good luck and happy wiring! :D

    Jim

    Here's a list of things that I wasn't prepared for:

    . Order of events - vi mouse down, boolean mouse down, boolean value change?

    . disadvantage of saving data in ASCII file

    . coercion dot means?

    . expression nodes (I didn't even know what this was!)

    . sub-vi remains in memory, even when not displayed, if there are...?

    . things auto-indexing does

    . default auto-indexing behavior of for & while loops

    . date/time formatting (that pesky %d%M stuff)

    . weakly-typed vi reference definition (this one threw me for a loop)

    . ring controls accept vs. enumerated list

    . 1000/0 into for-loop 'N' results in how many iterations? (wire it for yourself)

    . stacked sequence advice

    . multiple X & Y axes on graphs & charts

    . when 'wait until next ms multiple' begins counting

  9. QUOTE (shoneill @ Nov 3 2008, 04:38 PM)

    No, thanks. I get cut on sharp things.

    QUOTE (jzoller @ Nov 3 2008, 10:55 AM)

    I had the attached laying around, hopefully it's helpful.

    Thanks. There's sure an awful lot going on in there.

    I'm going go forward with Python. I'm not sure what would be easier, but I'm more interested in learning Python than how to use .net in LabVIEW. I played around at lunch today and wrote open, query and close VIs so I have enough to get started and a clearer vision of where I want to go.

    Thanks to both of you for your suggestions.

    Jim

  10. Hello,

    I've read a few posts about using SQLite in LabVIEW and haven't found the library to replace the broken link I mentioned here. My former employer had some useful VIs, but they are proprietary (and, being that they're my former employer, I no longer have a right to use them). So... I've wanted to write some wrapper VIs to use SQLite without ODBC and the NI DB toolkit (it works fine) and have made some initial progress. I first tried to use a Call Library Function node to access the functions inside SQLite3.dll directly, but got lost right away. I had seen a post where some work was started using CVI, but I didn't understand why a C wrapper was needed around the dll to use it in LabVIEW. What I got out of this, and a few hours of Googling, was that it was needed and I was missing something fundamental.

    Anyway, in a moment of inspiration I decided to use a Python Script node to access the database and was able to execute a SELECT query and also divine some schema information. I haven't tested it extensively yet (it's very much preliminary work and a bit sloppy), but I've just begun and would like some feedback as to whether I'm way off base or if this would be useful. I'm very interested in doing this, especially if others would be able to use it. I'll appreciate any suggestions you make.

    Thank you,

    Jim

    Download File:post-7534-1225677106.zip

  11. QUOTE (Omar Mussa @ Oct 31 2008, 05:49 PM)

    I reviewed what you did. I have a few comments for various states in your state machine

    Omar,

    Thanks for your help. Would you mind if I asked a question re: Sequence: Wait? I did this in the other program I mentioned because it requires the operator to perform a timed operation not controlled by my software. I didn't want to wait in a state without handling UI events. The sequence needs to continue once the operation completes; how could I handle this without going through Idle? Am I misapplying the JKI State Machine?

    I appreciate the time you spent on your response and I'll definitely refer back to your suggestions and take the advice.

    Jim

    Ashwin,

    I hope I didn't hijack your post. Perhaps I misunderstood your original post and you won't need a state machine.

    Jim

  12. QUOTE (kmc @ Oct 31 2008, 01:49 PM)

    Ashwin,

    You were about ten minutes too early! I just got back to this thread after spending some time in LabVIEW to see your latest post.

    Anyway, I think I understand your assignment but don't think that your approach is adequate. I think this is a perfect application for a JKI State Machine (I love the JKI State Machine!!! :worship: ). The only thing that would make me deviate from a JKI State Machine would be the DAQ part; I'd probably need to make some sort of a Producer and use the JKI State Machine as the consumer. Regardless, you have a lot going on and it would be akward to stuff it all into a Sequence Structure (never use 'em myself, 'cept to give myself something to wire to when I'm enforcing data flow on objects w/o inputs). So...

    I've made a start at this but don't want to go too far. First of all because it's your assignment and I don't want to either do too much of it for you or lead you down a bad path (more likely?). Secondly, I don't think I have enough information to continue. Please take a look at what I've done and see if it could be developed into a solution to your problem. The "Macro: Initialize" state is where I put the sequence; you can tell what I have in mind by looking there. If you haven't seen the JKI State Machine yet (why not!?!?!?), take a look at the tutorials on their web site. (I think I have the link around here, somewhere... ;) )

    There's a bunch left to do; for example, you'd probably want an indicator to prompt the operator on what's expected. The point I left off was simulating the DAQ so I could evaluate the inputs at each station, but that's not too difficult. Let me know if this helps and if I can help further.

    Best wishes,

    Jim

    :question: To the JKI folks & others that are familiar with the JKI State Machine, would you comment on what I've done? I've read the discussions here and on JKI's site, and I've (nearly) finished an application at work based on this (just working on getting Software Quality Assurance approval). I've gotten my feet wet and would like to learn more.

    I've added some states to let me sequence through test steps. I've added a "Sequence: Wait" step that causes the program to loop for a specified time so other operations can continue ("Sequence: Wait >> 10" will loop for ten seconds before continuing to the next step). I've added a "Sequence: Wait for button" that will wait until a named button is pressed during a particular test step. "Sequence: Wait for button >> pbx" will loop, holding this place in the sequence, until a button labeled "pbx" is pressed. I'll probably add the option to specify a final state using a command argument. It doesn't handle the event; it just waits until it's pressed. I've put a cluster of control references outside the main loop (so I can set indicators w/o resorting to local variables) and I've added target & elapsed time indicators to the Front Panel.

    Do you think I'm OK with these approaches?

    Thanks,

    Jim

    Download File:post-7534-1225478032.zip

  13. Hi Anthony,

    First of all QUOTE

    They often contain at least one moron that inevitably gets his turn to waste everyone's time with nonsense
    We fired him in September.

    Seriously, though. My experience with functional specs tends to make me agree with the first article, but specifically with this point: QUOTE

    Functional specs only lead to an illusion of agreement

    My situation has me building test equipment that must meet a customer-approved ATP, which is written in stone and the basis for a functional spec. The trouble begins when we start to get requests from our internal customer (the Design Engineering group) for features beyond the ATP requirements.

    I've seen success with a "Statement of work" - "Statement of understanding" process where the customer writes what they want (the SOW), we read it and respond with our understanding of what they wrote (the SOU). They read our SOU and modify their SOW and we go 'round and 'round until we're sure that we have an understanding (as sure as we can be, anyway).

    I can't see how to build test equipment without a good document at the beginning, whether it's called a 'functional spec' or 'requirements document'. I began a thread here looking for help (got some good pointers, too). I'd need to learn to manage the process at the beginning of the project so I can satisfy all my customers (ATE delivered on-time, within budget and slick).

    Thanks for the link.

    Jim

×
×
  • Create New...

Important Information

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