Avidyne FlightMax EX500, Руководство пилота, Страница: 129 / 184

Optimizing MultiLink for ORBCOMM (Release 4.0 and earlier)
600-00078-001 Rev 05 -117- Avidyne EX500/EX600 MFD
selected, the MultiLink system will attempt to send complete 2-Way
Datalink weather coverage for the route.
The reason is that Frederick is only 396 NM from Montreal! In this
case, the “400 NM” setting causes the NOC to determine that the
flight extends outside of CONUS, and it initiates full weather service
via 2-Way Datalink. For this flight, it would be better to set the
Coverage Area to “Current Position” and “200 nm”. With these
values, the NOC will not send 2-Way Datalink weather data for this
flight unless the Broadcast system fails.
Use the following guidelines as a starting point, and as you gain
familiarity with the system, you can strike your own balance between
2-Way Datalink usage and data availability:
● Expanded Coverage - If you regularly fly outside of CONUS and
plan to use MultiLink for expanded data coverage, consider
setting the coverage area to “Flight Plan” and “200 NM.”
●
Backup - If you plan to use MultiLink mainly as an active backup
for Broadcast, consider setting the coverage area to “Current
Position” and “200 NM” or even “100 NM” if you regularly fly in the
northeastern United States. Remember that in the Boston area,
for example, a setting of “200 NM” puts the Coverage Area
outside of CONUS and will cause the NOC to send 2-Way
Datalink data for every flight.
●
Datalink Messaging & Flight Tracking Only - If you plan to
enable MultiLink weather only when specifically needed and want
to have Datalink Messaging and Flight Tracking available on all
flights, you can de-select all weather types but leave MultiLink
enabled. This will cause the system to use a minimum of 2-Way
Datalink data on each flight for session management and position
reporting.