Quote:
Originally Posted by Mastonevich
twetherbee, I believe we had the same error at first. We found that we didn't install the LabView program/required libraries (it is required to communicate with the cRIO) and after installation the timeout error ceased.
|
Thanks for the reply. I'm more of a mechanical guy, so I'm just helping them apply basic problem solving strategies.
I'm pretty sure that they have all the software and updates loaded correctly, though. They had their laptops connected to the cRIO at one point, but couldn't get any of the code to work. Somewhere along the lines of debugging, something got corrupted or they thought to try wiping the cRIO again and start over. That is when this issue began.
Turns out that our original problem was likely due to the modules in our older cRIO not being rearranged to the new configuration for this year. (I keep telling them that documentation is your friend....)
We're all snowed in here for another day (I miss living in Wyoming and Montana where towns actually own enough snow plows that a couple inches of snow doesn't shut everything down.) so we'll have to wait and see if any of these methods work.