Quote:
Originally Posted by Kevin Watson
BTW, when you say it only happens when EEPROM is being written, is it my code that's doing the writing? Is my camera code running too?
|
Yes to both. I've only noticed it when writing camera configuration, so it could be an issue with how the pan/tilt control software changes menu modes and might turn out not be related to EEPROM at all. Or it could be that the camera EEPROM data structure is long enough for it to show an effect where a shorter EEPROM structure does not.
In our software, we've generalized the EEPROM and menuing support and added several additional menus (drivebase PID tuning, arm PID tuning, sensor and navigation status, and automode targeting setup). To keep from rewriting what's already provided to us, there is a small bit of "wrapper" code around the calls to the camera and tracking menuing functions. However, those functions do still get called just as often as they do in the unmodified camera code.