Quote:
Originally Posted by Alan Anderson
It's so strange that I suspect you either have a broken Digital Sidecar or a faulty cable connecting it to the DIO module in the cRIO. Do you have access to any others to try swapping them out?
|
Unfortunately I do not. There is one little mark on the cable that looks funny so it isn't impossible that the erratic behavior is caused by the cable however I have gotten it to run with another example program so if it is a problem it is a problem it should stop working if I run it a few times and wiggle the cable around. I will make sure to check that as well.
EDIT:
Simple robot does indeed do those things at least the code suggests it should but the last time I ran it absolutely nothing happened. I will try again. The main difference I have spotted between the example code that I ran and worked and simple robot is the working code use the "new" c++ keyword to allocate memory for a "RobotDrive" object instead of the way the simple robot and my code have it done. I should definitely see if that fixes it although it should not have any effect unless the code is doing something really weird behind the scenes.