[CRUSH-code] controller problems - see this info from Team Update 16 if you haven't already

[Christopher H Hanson]

Bill,

I already fixed this issue in Phoenix.  We should be good.


Quis




                                                                           
             "Bill Bennett"                                                
             <bill at wizardofaz.                                             
             net>                                                       To 
             Sent by:                  "code crush" <code at crush1011.org>   
             crush-code-bounce                                          cc 
             s at wizardofaz.whsi                                             
             tes.net                                               Subject 
                                       [CRUSH-code] controller problems -  
                                       see this info from Team Update   16 
             03/28/2006 11:45          if you haven't already              
             AM                                                            
                                                                           
                                                                           
             Please respond to                                             
             code at crush1011.or                                             
                     g                                                     
                                                                           
                                                                           




IMPORTANT NOTICE FROM INNOVATION FIRST


All Teams using the FRC 2006 Robot Controller are strongly urged to update
their FRC


Code at the earliest opportunity to prevent possible Robot Controller
mis-operation.


Issue 1 - Symptom:


Teams using the 2006 Robot Controller may observe abnormal readings for the
Robot


Battery voltage on the OI while the actual voltage to the RC is 12V. In
some cases possible


unexpected behavior from the robot may occur. This results when data
packets get shifted.


When the battery voltage indication data on the OI gets shifted, the
display might well read


the OI Port 4 Aux value (where the default value (127) typically converts
to 8.2-8.3V when


Port 4 is not connected).


Fix: Add “protected” to memory area.


Issue 2 – Symptom:


Teams may observe printf statements not working and/or experience
unexpected behavior


from the robot. This occurs if your code is larger than 64K.


To verify if your code exceeds 64K:


>From the IFI Loader. When the file to download is highlighted, hit Return.
You will see ..


Flash 800 - xxxx, Mem Size yyyy (displayed in hex) in the status bar. The
xxxx hex value is


your total memory size. If this value (xxxx) is larger than FFFF (displayed
in hex), your code


is larger than the 64K boundary.


Fix: Reset the Code Model


Directions:


Follow the step-by-step instructions provided in document ► 8.2 - 8.3
Voltage Issue and


Large Code configuration (3-14-06, pdf) listed under News or Announcements
on the IFI


Web Site at http://www.ifirobotics.com/.


Note:


Be sure to get the FRC_library_8722.lib installed as recommended in Team
Update 13.


 _______________________________________________
CRUSH-code mailing list
CRUSH-code at crush1011.org
http://crush1011.org/mailman/listinfo/crush-code