Jump to content

Chris Davis

Members
  • Posts

    423
  • Joined

  • Last visited

Posts posted by Chris Davis

  1. Neville and Ton,

    Thanks, I had looked at the OpenG toolkits in the past once or twice, though recently I haven't installed them in the project that I'm presently "embedded" in. I may be remembering incorrectly, but it seemed that it was easiest to install OpenG if you had a direct link to the internet, and often our developmental lab computers are specifically left OFF of the internet, for a variety of reasons.

    BTW, the example code I "snipped out" was from some older code I had from Labview 5.1.1, well before I had heard of OpenG. It was the quickest and easiest example I could think of to illustrate my point.

    I'll have to look into installing OpenG toolkits on one of my connected machines and see what makes sense in the long run for the machines off of the internet.

    Best regards,

    -Pete Liiva

    I'm in the same situation. I've found that there is a (fairly) easy way to move OpenG Packages to off-line computers. Simply copy the "cache" directory of commander or VIPM to a keyfob. You can then add these packages and install them as you need to.

    BTW, this topic came up in the beta stage of VIPM, and JKI has stated that they are working on an easier way to move the packages to non-Internet computers.

  2. If your user info is true and you are using 8.2 you may be out of luck. I think parts of scripting were closed after 7.1.x. I'm still using 7.0. You might try copying the create constant or control out of my example and pasting it in your code to see if it works.

    BTW, don't feel dumb. I wanted to know more, and so I had to devote some more time and effort. This is not a casually learned topic. Althought with my examples, I hope to make it easier to get started learning the basics.

  3. One last note, your tutorial is great, but lets all keep the real goal in mind, which many of us have stated over and over: we want to end up with something that can eventually convert a VI to text and then recreate it from that text.

    I'd like to see this happen too, but I know it will take a long time to get right. It led me to start this thread and create the examples. Before a text->VI parser could be written, I thought some scripting examples would be needed, since those who might be good at the parsing might not be good at understanding the scripting side of LV.

  4. The machine I'm on only has 7.1 so I'll convert to 7.0 and 8.x later and substitute & add.

    Fine by me if you want to combine, but might I suggest that we consider moving/copying all this into the code repository later.

    One last note, your tutorial is great, but lets all keep the real goal in mind, which many of us have stated over and over: we want to end up with something that can eventually convert a VI to text and then recreate it from that text.

    Then again, I'm not sure how much work we want to put into this, I'd be pretty surprised if NI doesn't already have this in-house. Be a bummer to put in all the work and then have NI release it. Then again, NI might not release ...

    What do the rest of you think?

    I'm thinking that a code repository entry is needed with entries in the knowledge base referencing these examples for dicussion.

  5. :worship: Hey Chris, great examples! I heartily agree with the kudos others have been giving as well as the ideas for more.

    Both VIs are in LabVIEW 7.1

    Mike,

    Thanks for the addition, I'd like to add it to my VI's, but I need them saved as LV 7.0. I'm doing this work on a machine that only has LV 7 installed. I'll add them to my post and zip everything up to make it easier to download.

    Thanks,

    Chris

  6. Look at the pattern matching example. Its located in the following location

    <LabView Directory>\examples\Vision\2. Functions\Pattern Matching

    With this example you will see how to match a pattern. You will have to snap one image, learn that pattern, then snap another image and look for that pattern in the new image.

  7. I have an IMAQ 1411 card, and I tried do make some thing but without result, I can snap, grab ou acquire image but I can not track ROI in motion!!!

    Thanks for the screenshot. I can see that you captured the image, and setup an roi.

    Do you have the Vision Development Module (IMAQ)? The pattern matching functions will be installed with that toolkit. There are also examples of how to do pattern matching over time.

  8. I'd like to make more examples, and posting them to a single place would be helpful in the future when we want to point someone to a complete consise example of how to get started with scripting. I know the code repository has methods to source code control. What about the knowledge base?

  9. Nice idea. I guess time remaining has to be an estimate based on how long it took to execute a certain amount of work? Also a built in tally of time elapsed would be nice.

    Is this the same dialog that shows up in OpenG Builder and the JKI LV 8.0.1 mass compile tool? That dialog has an elapsed time indicator, which I somehow find more helpful than a time until complete indicator. Guess I've been fooled to many times by the windows time until complete calculation to put any merit in this type of indicator.

  10. Thanks David, I was hoping someone would get something out of this VI (now these VIs). It took me a couple of nights to get them right, and understand what was going on, so I thought I would document everything thus far, just to make it easier to pick it up, if I have to lay it down for a while.

    p.s. Yes, I know. Very droll.

    Took me a minute but, :D

  11. I got interested in Labview scripting recently, but had lots of trouble getting started. After reading the FAQ and activating scripting on my LV 7 install, I was at a loss on what to do, and how to do it. I started figuring things out and thought that I would share my simple examples so that others might have an easier time getting started with scripting. I have attached one example (LV 7.0) of a VI that creates a new VI with a control and an indicator on it. This new VI simply passes through the connection from control to indicator. It also connects the control to the upper left (input) side of the (4x2x2x4) connector pane, and the indicator to the upper right (output) side of the (4x2x2x4) connector pane. I know this example may seem pretty simple (and it is), but it does gather some basics that one needs to get started in scripting.

    Warning, this VI's diagram is long (left to right), but I wanted to make it look good and document it as best I could. Teaching others is the best way to reinforce what you have learned.

    Enjoy :thumbup:

    EDIT: Added second example showing how to create a VI to multiply two numeric controls together and produce the result in a numeric indicator. In this case the two inputs (X and Y) are connected to the two upper left connectors of the (4x2x2x4) connector pane and the product is connected to the upper right connector of the (4x2x2x4) connector pane.

    Download File:post-2547-1161747922.vi

    Download File:post-2547-1161750384.vi

  12. You might also consider a different prize for the winner. I'm sure that a NI-6008 works for some people. But I'd hazard a guess that a $150 Amazon gift card would go over with more people...

    BTW, I didn't participate in this coding challenge, mostly because of time constraints. So a quick coding challenge would be nice. But a quick coding challenge could also mean that the prize was less costly. I too would like to see a challenge with the picture control. In fact, when I read the previous post from Mike Ashe, I thought of this post, which was done to prove that with enough time and effort or experience (in this case), any UI can be done in the picture control.

×
×
  • Create New...

Important Information

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