AFS 4500 Serial Port Configuration Questions

[Bill Rogers]

I am preparing to wire the serial ports for my AFS4500. I would like to use a seperate GPS for the Lat/Long input so I can cross check the GNS-480 position. The following is the configuration I was thinking of using.

Serial Port # Device Data Format Label (GNAVx GPSx NAVx)
Serial Port #1 ARINC (480) ARINC GNAV 1
Serial Port #2 GTX-330 TFC/ICARUS
Serial Port #3 SL-30 SL-30 NAV 2
Serial Port #4 AFS GPS AFS GPS GPS 2

A couple question with this setup.
1. Will all of the information (except Lat / Long) from the GNS 480 come in over the ARINC? In other words will any navigation functions be lost from the GNS480 interface without the RS232 connection?

2. It is convienient to run the GPS 18X to serial port 4 because the +5VDC and ground are there to power it. Is it acceptable to run the ARINC to Serial port 1 or do I have to swap it with another component?

Bill Rogers

[Trevor Conroy]

Bill, your configuration looks great! The GNS-480 doesn't output GPS altitude over RS-232 anyway so you aren't loosing anything by not having the RS-232 interface.

[chuckwn2]

The GNS-480 doesn't output GPS altitude over RS-232 anyway so you aren't loosing anything by not having the RS-232 interface.

Trevor,

Is an RS-232 connection between the GPS and EFIS not required because the navigation information is being passed to the EFIS through the ARINC module?

Thanks,

Chuck

[Trevor Conroy]

That is correct. However with an Garmin GNS-430/530/650/750, GPS altitude is only provided over RS-232, which is why we utilize that connection. The GNS-430/CNX-80 doesn't output GPS altitude over RS-232 or ARINC.

[Bill Rogers]

Thanks Trevor. Does the 480 send LAT/LONG across the ARINC to use as the primary source, or will the 4500 be using the AFS GPS for the primary LAT/LONG with this config? Any internal cross checking of position if the two sources disagree?

[Bill Rogers]

I have finally installed the AFS4500. It gets a GPS position from the GNS480 (GNAV 1) and the VDI works on the startup check from the 480 (haven't noticed the CDI yet). I also haven't verified that the 480 is getting any information from the AFS4500. Today I tried to check the ARINC adapter with the diagnostic function and I got the following error message.

"No ARINC adapter
Check 10, 11, 12 in the admin settings menu
Press any key to continue"

The serial connections are setup as follows:
Serial #1: ARINC
Serial #2: TRFC/ICARUS
Serial #3: SL-30
Serial #4: AFS GPS

GPS/NAV 1 = Serial 1
GPS/NAV 2 = Serial 3
GPS/NAV 3 = Serial 4

I verified that the green light is lit inside the ARINC module. Any idea why this configuration fails the ARINC diagnostic check? Considdering that at least some of the data is coming across (GPS position and VDI), could it be related to the module being on serial #1 and not serial #4 (which I think is ok to do on the 4500)? Any other tests you would suggest to verify the installation?

Thanks,
Bill

[Trevor Conroy]

Bill, what version software are you running? Please make sure it is the latest from our website, 8.3.28

[Trevor Conroy]

Please give me a call when you are at the airplane.

[Bill Rogers]

Trevor,

I tried calling this afternoon when I was at the airport, but I could not catch you (message said you were on the phone). I checked the function of following interfaces to the 480 and they all worked:

VOR CDI
GPS CDI
VDI
GPS Position

I also checked it with my trutrack VSGV and it drove that just fine.... so I think the units are communicating properly. I then tried the diagnostic check and that did came back with the same "No ARINC adapter" message.

Unit information is...
S/N: 61633
SW: s8.3.28 (Apr 13 2011)
OS: 842 (Jan 13 2011)
FS: 1.13
IC: 4.1
ARINC: V4.0
Network: 6.3
IP adress: 192.168.0.175

Not sure why the self test isn't working, but the ARINC communication seems functional between all the units. Do you see any issues flying this configuration? Any idea why the diagnostic test isn't working?

Bill Rogers

[Trevor Conroy]

I'll give this information to our software team for diagnostics.