Quote:
Originally Posted by Kevin Sevcik
Firstly, what on earth do you mean by stuck/stick code?
|
Stuck code is basically a description for the process of building/compiling the code, and then setting it to run as startup on the cRIO (the communications issue seems to pop up less often when we run the code that's already on the cRIO whenever we start, when compared to deploying/running code from a computer to the cRIO).
Netconsole seems useful, I will look into it, thanks.
Another issue that may factor into this is possible concurrent modifications to the Jaguars, as we are looping reading inputs and setting outputs in different loops. I don't exactly know what the Jaguar is doing on lower layers of software, so to what extent this may affect our issues is unknown.