LabVIEW
Can I raed and write into an array simultaniously?
Solved!
And as I already told you, you do not need the for loop. The other indicator you have seems silly.
Hi Dennis,
I think the for loop is needed as a histogram of the amplitudes is counted here. Your example just scales the amplitude values instead...
Btw. It's kind of silly to use a histogram array capable to hold 100 bins and only use the first 60 bins...
Hi Dennis,
yes, it's one more point to complain about the original VI: using DBLs to index the array...
Hi number,
have you read any of our messages?
Have you ever considered to follow our suggestions?
Why should we invest (our precious spare) time to give advice that isn't followed?
Again: Stop using locals this way and first integrate our proposed solution. Then try debugging with highlighting execution. Then spot the problems and ask for specific help. IN THAT ORDER!
OK, if you want to retain the contents of the shift register between calls of this subVI, you need to use a globally initialized feedback node instead. Also such integer histograms are most easily done using the "in place element" structure.
As others have said, your code is full of race conditions because there is no way to tell in which order the three disconnected code fragments execute.
- It does not make sense to increment the array size by one and wire it to N of the for loop. The loop should execute exactly once per element, thus it would be correct to use the unaltered array size. Of course autoindexing takes care of that automatically, so there is no need to even get the size or wire N.
- Please don't to the "array to cluster-unbudle-dance" to get the first element of an array. All you need is "index array".
- Indicators and controls should not be inside non-interactive loops. The constant updates will slow down your code.
- I have no idea why you use the absolute value. Are all values negative? If they are negative and positive, taking the absolute value would probably distort the reusult.
