Mike Ashe

Interesting way to walk down the tree. I'm going to try this, and then disconnect the bottom most unbundle and rewire it to the top cluster and see if it maintains the low level unbundle. If so, then we can then delete the intermediate unbundles.

Ditto here. Sometimes I was able to get to a subcluster directly, but mostly only at the same time as resizing. After a short while it doesn't seem to work except for the main cluster elements. Oh well, at least we have some part working. I might try to add all the elements with a resize next, then selectively delete the ones I don't want to try to arrive at the final desired configuration.

If the name of Keats was writ in water, then the name of Castenada was writ in smoke... and from alfa's "writtings" I'd say he's still passing his smoke through the waters and writs with a psychedelic pen(rose)

Nice example. I've wanted to integrate more picture control into some scripting. This little snippet will come in handy for that, thanks!

Oh sweet. I missed this one during beta, but was wishing for a way to do this for a while now. That and things like the "bundle cluster in error wire insertion" is really making the LabVIEW editing feel a lot more intelligent these days.

My current avatar is actually my 9 year old son in his Jedi halloween outfit. As a former BTB fan, even HE would say that last one was droll ... Bye the way, welcome aboard Santosh! What kind of things do you use LabVIEW for in the IT department?

Welcome aboard Bob, so what type of "fire" have you been thrown into, what are you using LabVIEW for? Good luck!

The example of unrolling given above is trivial, not hard to unroll and distribute. But I imagine that with complex contents in the loop that the difficulty of unrolling/atomizing goes up exponentially. I would think that, eventually, to make coding with this efficient that we would need some type of on-the-fly syntax warning that the code (fragment) we just created/connected is not unrollable and that if we wanted to take advantage of the parallel capability we would have to edit. Interesting CS/compiler problems. I can see where more parallel distribution would be highly advantageous if we were distributing to, say, an array of processing cards each with one or more CPUs running LabVIEW Embedded and we were trying to create an MxN matrix processor for something like image processing of video streams.

Okay, this looks like yet another Homework Hustle, but at least you showed us what you tried. One quick, simple, thing to do is not to write the data out every time through the loop. In your first design above, take all the stuff that you tried to transfer into the second loop, and instead, put a CASE structure around them, then divide the loop counter by 2 or 4 or 42 (the answer to everything ...) and when the remainder from your counter division is zero then post that set of data. You can decimate your user data rate that way and still log all your data to disk.

Well, you started out your first post by saying that this was a Senior Project, that usually means some type of schoolwork in most languages. Still, since you are persistent: do you have access to Google? In the time after I made my last post and while you were posting your reply I made a quick Google query on the "STA 300 analog ports" The very first link on the first page (for me at least, in english, Firefox browser) is a link to a PDF of the screw terminal assignments on the STA 300. Seems that should give you what you asked for. I need to go find my second cup of coffee this morning. Hmm, too bad we can't Instant Send physical objects like we can files or messages. Brazil has great coffee. I'd charge a fresh cup for that last answer.

Alnaimi, A project is the same as homework, it is schoolwork. Still, did you read the two posts I pointed you to, especially the first one? The first thing that it said was that "Google is your friend" If you do a google search on Google: KPCI 3100 LabVIEW The very first page will give you links to example code, several different VIs and also Visual Basic code (if you are new to LabVIEW) that you should be able to use both to help you understand and then modify to use in your project. Get some of these, try to make them work and then if you have problems, post one of your VIs and ask a specific question, and you will probably get help.

FF is now at about 15% in worldwide use, so I would expect it to be higher here. I'm going to guess: FF 35% IE 60% And the person who guesses closest wins .... A Free copy of FF 2.0 !

Hi, and welcome aboard! There is lots of stuff applicable to manufacturing here on the forum and a lot of us work (or have worked) in that area. To start, might I suggest you read: How To Use the LAVA Website Then you might want to tell us a little more about the specifics of what you do with LabVIEW and what type of manufacturing problems you are trying to solve. The more specific you can be the more response you usually get here. Good luck :thumbup:

In general, we do not do that here. For a typical response to questions like your's see This Post ... That was actually one of the kinder answers. We do not do homework for engineering students. Lastly, if you want to get help here, we have occasionally been known to give it, even to engineering students, but only if they ask the questions the right way and if they post VIs they have already written to try to solve the problem. Show us that you have made some real effort, then ask specific questions and maybe someone will help here. I have and so have others. But not usually with questions posed like the one you did above. You might also want to read: How To Use The LAVA Website

Works fine for me, but that probably does not qualify as a reason for SOME people to make the obvious switch ...

This is the second time I typed this, LAVA barfed the first time, oh well ... Randy, you don't have to have a drop in toolkit for it to be useful in the C.R. Note that Chris Davis recently added several examples into the VI Scripting subtopic of the C.R. and they are not toolkits, yet I think they are fine examples. Your code, with a little more commenting and formatting would probably help some people out.

While we're on the subject of LabVIEW, has anyone noticed that when you are typing in a post, the automatic spell checker here on LAVA underlines LabVIEW as if it is miss spelled? LAVA, however, is not. I hear rasberries in the background...

Nice example Randy, thanks for sharing this! I can see good uses for this in reporting on tests.

The key here is to get in front of that senior engineer in the interview. And the key to getting past the HR department when you have any disadvantage, such as lack of some specified credential, is to find and make contact with some person in the company and convince them to interview you *before you submit to HR*. Let your contact know that you do not meet "requirement XYZ" but that you more than make up for it with LMOP, etc, and have that person inform their HR dept ahead of time that they are expecting your resume and that they want it forwarded to them anyway. This "pull" from the inside is what it takes. You cannot push a rope, but if you can get someone inside (with pull) to "pull" then you can stand or fall on your interview skills and experience. How do you do that? Well, it looks like you've already found one way (see post #4 above) in making contacts on forums like this. Or another good way can be meetings at trade shows or conferences. The best meetings at those are usually the meetings outside the meetings. Good luck!

You have to move them individually. You can: 1. get an array of all the references that are members of the same group as your "key" object. 2. get the positions of all the objects. 3. "Defer Panel Updates" for your VI. 4. Set the updated positions of all objects (same offset to all of them) 5. "Enable Panel Updates" to get everything to move at once. Be happy ... Last step, make a suggestion to NI to allow group moves. :thumbup: Hmm, the coffee is good today ... so .... Here is a quick VI to do group moves and a demo Download File:post-45-1162847143.vi Download File:post-45-1162847203.vi The variant is the "key", but you could use any of the upper controls, in the group, which is all the upper controls on the front panel. NOTE: The demo & move VI moves the group position, relative, not absolute. It should be pretty obvious how to modify this to make an absolute, or centered move if you so desire.

Another chunk of wood: FF 2.0 releases mere days after IE7, "catching up" as you point out. How long was it after FF introduced tabs that IE made them an add-on?

I'm really disappointed ... Perhaps this slip can be attributed to your down under roots. The fact is, the harbour tasted terrible, and terribly weak. That was the real problem. Any true subject of the Crown (or any other true tea drinker) knows that to make a proper pot of tea the water MUST be boiling vigorously when it first makes contact with the tea. Ask Jean-Luc about his Earl Grey (although I prefer House of Jackson's Breakfast Tea). This is the real reason behind the American Revolutionary War, it had nothing to do with taxes or freedom. We insulted England and all tea drinkers everywhere by trying to use cold water ....

I'd believe another honest engineer from your own company if they said you had had them on your desk previously, but I would have a hard time believing you, even if I saw them myself during a visit to VIE in MI. I would suspect you had put them on the day before just to mess with someone. Not from the New England colonies, we dumped all our a couple of centuries back ...

You can use the Microsoft XML Parser 4.0 as an ActiveX Automation control to read and parse the file for you. It takes a little bit of work, but you learn a lot in the process and end up with some usefull tools. The parser ships and installs with LabVIEW now. 1. Drop an Automation Ref control on your front panel 2. Select Microsoft XML 4.0 Class and IXMLDOMDocument2 object A. wire an Automation Open node to that and then into ... 3. Drop an invoke method on your diagram, wire to the Ref and select "load" as the method 4. xmlSource needs a variant of a path as input 5. next wire in a property node set to "childNodes" 6. Check for parse errors, then A. Property: length B. loop through the child nodes getting the item , nodetype, data, etc The rest you can work through yourself, have fun :thumbup: Okay, I'm about to go get my second cup of coffee, so I'll also point you to: Microsoft: Introduction to DOM - Document Object Model Which will give you a bit more guidance (and save me from having to answer a lot more of the initial questions). As you work through this remember that it is from the perspective of the text world, so in the "Working With DOM" subtopic you can search on "childNodes" and see the function for getting the nodes. The equivalent in LabVIEW is just the initial Reference wire with a property node (item 5 above). Etc, etc. Like I said, some work, but lets you use much more flexible tools and a much more compact and readable XML that with NI's built in stuff. YMMV

Obviously spoken by a member (at least still in heart) of the Commonwealth. Said members being overly interested in maintaining "The Queen's English", etc. But, considering the peremptory tone of the original tea-deprived rant, I feel you missed the proper pronoun, which should not have been, "I" or "My", but rather, "We" or "Our" ... Hmmm, green tea, and tea in general is a subject worth exposition. Perhaps in the lounge instead of LabVIEW General. Maybe we need a tea icon to go with the recent coffee icon.