LabVIEW
VISA resource name
@77hybbr wrote:
How it is different to use shift register with visa resource name and not using shift register with visa resource name when using VISA read inside while loop? I am asking with respect to data acquisition, would it cause the incomplete data acquisition missing packets ?
If the resource cannot change, then I tend to use tunnels. If all you have is a VISA Ready inside of the loop, it doesn't really make a difference if you use the shift register. If you have case structures or event structures, then it makes it easier to use tunnels (forget to wire the reference through a case and your reference could be gone).
@77hybbr wrote:
Another question is what If we don't close the visa outside the while loop for each data acquisition, would it cause visa read to take more or less bytes than specified byte number during next data acquisition?
If the resource is not closed, then the buffer will keep filling up with anything that comes through. So you could be dealing with old data. But the way you worded this question throws up a red flag in my brain. Maybe you could show an example (ie code) with the exact situation you are facing?
Nothing to add to what crossrulz said other than to say I prefer to use a shift register just because it's more of a habit to me, and the downsides are minimal (probably a small speed loss in very high speed loops). Basically, if I always use a shift register, I don't have to think about it 😄
The only thing I'd like to bring up regards For loops, which the OP didn't ask about but it may be relevant...
A resource wire is basically the same as a shift register for a While loop but it may behave differently for a For loop in edge cases. A While loop is guaranteed to run at least once. A For loop may run zero times (if, for example, it's autoindexing and something upstream generated an empty array). A For loop that runs zero times will output the wire's default value on an output tunnel, but it will pass a value through with a shift register. Usually you're using a While loop with a VISA reference (and is in fact what the question is asking) but it's a good thing to keep in mind.
For something like a VISA reference, this means that upstream errors may cause you to hang a port. Take the following code:
The For loop runs a number of times equal to the number of commands read from a file. If that function errors (like if the file doesn't exist, or is configured improperly), then the For loop will run zero times, meaning the VISA Close function gets an empty VISA reference at its input. Thus, running this code will open your port, but will not close it in the case of an error, and your port will be stuck open until you fully exit the program. Switching to a shift register ensures that you'll always pass the VISA ref through the loop, even if it errors, and your port won't hang open:
It's almost certainly an issue with your code, so we can't help until you show it.
I doubt it is opening and closing the port that may cause an issue, though it certainly COULD be.
Are you reading in two bytes at a time? If so, you may not be reading fast enough to keep the Read buffers empty. Try to read about 1/10th of a second worth of data at a time and process it that way.
