04-01-2016 09:13 AM
I have a Labview 8.6.1 application that has been running for a long time now.
I replaced the workstation, after a period of time the Pickering PCI switch stops working. I created a utility to find out what the issue is and to recreate.
I recreate by just initializing the card and closing it. It will work 100 times every time, then at 101, it can't find my switch any longer.
It doesn't matter if I access it 50 times IVI method and then 50 times VISA method, it is 100 times.
Any help would be greatly appreciated.
See attached images
04-01-2016 09:37 AM
Additionally, I do have a USB GPIB that a Solartron is attached to that continues to work even though the switch does not. Exactly 100 times it will work. 😞
04-01-2016 10:40 AM
Sounds like a Pickering issue, not LabVIEW. I would go bug them.
04-01-2016 10:45 AM
Why is there a coercion dot on your resource name? Maybe add a short "wait" before closing the resource. What is in your false state? I assume it's not nothing because you are using a property node for the resource name.
Just some general tips that may not be related to your problem. Add a wait into the while loop, it will still be plenty responsive. Don't use property nodes to retrieve values, use a shift register. Change your boolean to "latch when released" and it will automatically reset to false once its value is read.
04-01-2016 11:17 AM
False is a 200 ms wait.
04-01-2016 11:18 AM
I think you are right about it being a Pickering issue. I am bugging them bigtime also 🙂
04-01-2016 11:30 AM
Do you still have the old workstation? Some common pit-falls with upgrade are differences in:
Do you have a modern LabVIEW version you could try?
04-01-2016 11:36 AM
It was the Pickering driver. On the machine where it worked, I had 3.52.007. I had downloaded a newer 4.x driver that was causing all of the headaches. I am now able to go over 100. Pretty crazy. Thanks for all the feedback.
04-01-2016 11:49 AM
@tartar813 wrote:It was the Pickering driver. On the machine where it worked, I had 3.52.007. I had downloaded a newer 4.x driver that was causing all of the headaches. I am now able to go over 100. Pretty crazy. Thanks for all the feedback.
Now, Go back and stick a Zip of the right driver in with the source code and add the ReadMe.txt file explaining the dependancy! (And, if possible, Slap the original developer for not having documented the dependany~!)
04-01-2016 12:06 PM
I have put all of the software in specific folder 🙂 I would slap the original developer, but that would be me. Ugh!