@Bob_Schor wrote:
It's either the Hardware or the Software. Let's assume the Hardware is basically OK, and let's also assume that most of the Software (Windows, LabVIEW) is also OK. That leaves the code that you are running, which is 99% sure to be the problem. Fix your code.
If you need help with this, attach your code to your reply (attach the actual VI, don't waste our time with a picture of it that we cannot inspect or execute) and we'll try to help. [Eventually, we'll get the Forum's Telepathy Module working so we can "see your code" through your eyes, but that's a few years off ...].
Bob Schor
So, just the Hardware or the Software then? Phew! I thought it could be something else! Either way, like I mentioned in the opening post, the issue comes up with the basic example of analog input for the device, i.e. known good code that NI provides and that is directly downloaded from their site, and publicily available here: http://www.ni.com/example/31213/en/
But also found attached here. Either way I did some backtracking and Alex was on to it, the issue was caused by plugging the USB into a 3.0 port. I switched it to a 2.0 one and it works fine now, 32 or 64 bit version had nothing to do with it, it crashes in either if I use a 3.0 port, and works in either when using a 2.0 one. It amazes me that NI hasn't stepped up their game yet, when 3.0 has been around for so long, but well, at least finder will get something if someone else stumbles upon this bug.
