jdeas
09-08-2013, 03:09 PM
The manual only shows hooking up the AFpilot to the 430/530 devices. There is no direct correlation to 300XL port settings.
After working through the EFIS troubleshooting guide, and updating the AF-AIRINC firmware I was able to see the AIRINC version info on the EFIS but there were some unexpected results.
1) Setting the 300XL COM1 to 'aviation' out I still had to set the EFIS to NMEA@4800 before I could see any GPS data.
2) Forcing the AP to 4800 baud and rebooting it also had to be done to the AP before the GPS data could be seen.
While everything can now see the 300XL, when I engage the FD, the AP displays 'EXT TS VS' instead of 'EFIS GPSV'. Is this correct for the 300XL (non wass) system?
It currently appears that the AIRINC module is only functioning as the AP to EFIS interface. Is there any combination of 300XL setting that will allow it to interact with the EFIS?
After working through the EFIS troubleshooting guide, and updating the AF-AIRINC firmware I was able to see the AIRINC version info on the EFIS but there were some unexpected results.
1) Setting the 300XL COM1 to 'aviation' out I still had to set the EFIS to NMEA@4800 before I could see any GPS data.
2) Forcing the AP to 4800 baud and rebooting it also had to be done to the AP before the GPS data could be seen.
While everything can now see the 300XL, when I engage the FD, the AP displays 'EXT TS VS' instead of 'EFIS GPSV'. Is this correct for the 300XL (non wass) system?
It currently appears that the AIRINC module is only functioning as the AP to EFIS interface. Is there any combination of 300XL setting that will allow it to interact with the EFIS?