Arrays, sub VIs

[Dennis_Knutson]

You really need to learn to start a new thread when you ask a new question. This question (as the last several ones) are off-topic. You'll get more attention if you start a new thread with an appropriate topic.

[Mbdeck]

Dennis,

It would have been nice if you said something about the question I posed. Fact of the matter is that I've tried to start new threads before when some people made similar comments like you did above. I hardly get enough reponses to address the the problem as much as I get on this particular thread. In any  case, I've started a thread on the topic and you can reply to it here if want to assist. Thanks

new thread : http://forums.ni.com/ni/board/message?board.id=280&thread.id=4916

[Dennis_Knutson]

The fact is, according to your profile, you have started only two threads prior to this new one (unless you are posting under a different user name). You might think about posting to a more appropriate board as well. It does not sound like you are using either NI''s real-time hardware or LabVIEW Real-Time. Either the Multifunction DAQ or LabVIEW board would work better.

I have no experience with microphones but you should provide a few more details than just 'I am having  trouble'. That is kind of a generic description.

[Mbdeck]

Ok Dennis,

Thanks for the correction. I've now posted it to the labview board with a little more detail. Please help if you can.

[Mbdeck]

Hi,

I'm trying to make sense of a code in a tutorial and I would like someone explain. I don't quite understand why the minimum array size output of the max and min vi was used to set the number of loop iterations.  please see attached picture of vi.

Also, does an auto-indexed input tunnel of a while/For loop function differently from the auto-indexed output?

Thanks

[RavensFan]

That is so the loop doesn't run forever in the event there are no matches.  It uses the the smaller of the two arrays to determine how many times to run.  It would work OK if you used the larger of the two arrays, but it would just run longer while it compared the smaller array to a default of an empty string.

If you are using a newer version of LabVIEW (8.5 or newer?), the conditional For Loop was introduced.  You could just autoindex on both arrays, and also use the stop terminal (which didn't exist in For Loops in earlier versions) to stop the loop early in the case of a match.

PS.  Please just attach your image to the message as a .png or jpeg file rather than embedding it in a Word document.  There are some people who aren't using MS Word, or who would just not prefer to have Word open up just to see your picture.

Message Edited by Ravens Fan on 05-18-2009 10:13 PM

[Dennis_Knutson]

And you also still fail to understand the need to create a new thread for a new question. Is it really that difficult?

[Mbdeck]

Dennis,

I considered starting a new thread but decided to post this under the topic "arrays". Why start a new thread on similar topic?. Before I post I search the ni website and if there is a forum dealing with the question I post it there. I don't know what your problem is really or do you just feel like chastizing somebody?.  Can you tell me why this particular post is inappropriate?. I've been postng quite often recently at differently forums as long as the questions are related. Please I don't this sort of hostility here. Thanks for your input anyways.

[Dennis_Knutson]

For one, the subject 'Arrays, subVIs' is just too generic to start with. You might as well just use the subject 'LabVIEW' (just joking, don't ever be that generic).

Second, by burying several barely relatated questions in a single thread, you've just made it harder for someone else to find a solution.

Third, new and unanswered questions get more attention from readers of the boards.

Keep the threads small and specific. When your question is answered, mark the answer as solving the problem.