Hi Andy,
I appreciate your reply! We spent some more time working on this last night. We were able to see the cRIO in MAX after adding it by IP address. We could set the IP address of the cRIO using the FRC cRIO Imaging Tool, and then connect to it with MAX to remove the gateway setting. An interesting observation was that every time we ran the FRC cRIO Imaging Tool and then connected with MAX, MAX always saw a gateway setting of 10.xx.yy.1 and a controller name of "temp." We'd overwrite these and could read back our new settings, until the next time we ran the FRC cRIO Imaging Tool. It would invariably crash and leave us with the same settings visible in MAX. The LED would change to a two flash pattern after this.
We've also observed LED activity on the cRIO shortly after the error 56 is reported. We couldn't help but wonder if the cRIO isn't responding late. We're going to try the same process on a different cRIO tonight and see if it behaves any differently. Hopefully we can isolate the cRIO from our programming process as we try to figure out what's going wrong. I'll also add that I've successfully used my same laptop and same software to program cRIOs before, and I've never had any trouble.
Our cRIO is nominally drawing about 150 mA at 24 V. I've never measureed any of our others so I don't know if that's normal or not.
Ultimately we're back to the point of seeing the cRIO in MAX, seeing it with the FRC cRIO Imaging Tool, and unable to successfully program due to any number of errors. Error 56 is repeatable on one of our laptops. The other will generate a different error every time but all of the other symptoms including observations in MAX will be identical.
Does this sound like any known condition? If it doesn't sound familiar, we'll continue by trying a different cRIO and report back what we find.
Thanks!
Nick
