View Single Post
  #9   Spotlight this post!  
Unread 01-02-2005, 08:09
ldeffenb ldeffenb is offline
Registered User
AKA: Lynn Deffenbaugh (Mr)
None #0386 (Team Voltage 386)
Team Role: Mentor
 
Join Date: Jan 2005
Rookie Year: 2003
Location: Florida
Posts: 75
ldeffenb has a spectacular aura aboutldeffenb has a spectacular aura aboutldeffenb has a spectacular aura about
Send a message via ICQ to ldeffenb Send a message via AIM to ldeffenb Send a message via Yahoo to ldeffenb
Re: Default code problem

Actually, the 2.4 default code can be compiled without the camera support and then you can later turn the camera on. Just go to Project/Build Options/Project and click the MPLAB C18 tab. If you remove _USE_CMU_CAMERA, the camera code will be ignored by the compiler.

Alternatively, you can edit user_camera.h and comment out the #define FREEZE_ON_ERROR. This define causes the blinking Red lights and the controller errors if there is any communication problem with the camera.

On a separate note, has anyone seen the tracking packets from the camera quit after some time when Kevin's gyro code is integrated into the 2.4 default code? I'm suspecting an interrupt conflict or corruption between the gyro's 400hz interrupt and the camera's serial port for receiving the T packet data. Anyone seen anything similar?

Lynn (D) - Team Voltage 386 - www.teamvoltage.org