The majority of off repairs for the ACD215 R9 Keyboard are for the orange dots on the screen. - Shops / Techs should never press on the LCD screen when removing and installing the ACD215 Keyboard, as this may result in the orange or black spots on the LCD. This is considered customer induced. Pilots - repeated tapping on the screen will also cause the spots. 

- Orange or black dots on the LCD screen on the R9 ACD215 Keyboard - Flat rate repair cost will apply

- Controlling the brightness on the R-9 Keyboard - See attached R-9_Keyboard_Contrast.pdf

- R9 Warranty - Avidyne Corporation made the decision to end the R9 Warranty New and Renewal. The R9 System is still services and supported by Avidyne corporation. All request for repairs requires an Avidyne Dealer to submit a repair request. 

- The ACD215 keyboard is intermittently not powering up with the system.  When this happens, there is no faint Avidyne splash or backlight cycles visible and the COM1 button does not illuminate.  The "No Comm with Keyboard" CAS messages does not display on the IFD's.  - Possible broken wire between the R9 Keyboard and IFD5000i - See an Avidyne dealer to check wiring.

- R9 pilots with an ADS-B failed - Check the Flight ID in Setup to make sure your tail number is displayed - Goto Setup and scroll to Aircraft Flight ID. 

- ACD215 powers on, but screen is black/dark. When ACD shuts off there is a 'No Comm" message on the IFD - See an Avidyne dealer - ACD215 may require repair.

- Range on the RIFD will intermittently change uncommanded - possible joystick encoder. - See an Avidyne dealer, unit requires repair.

- Joystick stuck in one position - See an Avidyne dealer - unit requires repair.

- USB port flap will not spring back to closed position - See an Avidyne Dealer, unit requires repair.

- ALT SEL knob not able to change by 100' increments when being pushed in. - See an Avidyne Dealer - unit requires repair.

- ACD215 shows RAM test failed - see and Avidyne dealer - unit requires repair. Photos are required showing the error. Did the error occur after an update? Does it remain at all times, even after power cycling the R9 system?