Quote:
Originally Posted by Greg McKaskle
The correct interpretation of the No Robot Code light is that no robot code is running and responding to the protocols in place. The DS has no way to know what is on the disk of the cRIO, and it doesn't try to manage that anyway.
You may want to use an ftp program or even Windows File Explorer to ftp to the cRIO and look at the info on the startup program. You can then rebuild and deploy and see if it is updated. If not, your build is failing in some way.
Another debugging technique is to use the serial cable or netconsole to see if your program starts and promptly exits -- a possibility when using C++.
Greg McKaskle
|
Thanks for the info. It was just me being stupid after all, I reflashed with this years cRIO image and it works fine. Dunno what it was 0.o. But problem solved, so all is good.
__________________
Code:
In .h
RobotDrive *ted;
RobotDrive *tedDrive;
In .cpp
DriveTrain::DriveTrain (RobotDrive *ted){
tedDrive = &*ted;
}
Yo dawg, I heard you like pointers, so I put a pointer in yo pointer, so you can de-reference your pointer while you point to yo pointer.
In the now immortal words of will.i.am, "This stuff is really good!" - neshera [more] 
Hybrid Mode
