ARINC424简介ppt课件

IntroductiontoARINC424,Amsterdam22-23June2005,FlashBack(1),ARINC-AeronauticalRadio,Inc.-acooperationofavarietyofstockholderssuchasairlines,aircraftmanufacturesandotherairtransportcompanies.ARINCactivitiesincludeoperationoflandradiostations,theallocationandassignmentoffrequenciesandtheexchangeoftechnicalinformation.ARINCsponsorstheAirlinesElectronicEngineeringCommittee(AEEC).AEECformulatesstandardsforelectronicequipmentandsystemsforairlines.,FlashBack(2),PurposeofARINCSpecifications1.Indicatenewequipmentrequirementstothemanufacturersofelectronicequipmentbasedupontheconsideredopinionoftheairlinetechnicalexperts.2.Influencenewequipmentdesignsinordertoachievethemaximumpossiblestandardisationofthosephysicalandelectricalcharacteristicswhichaffectequipmentinterchangeability.,FlashBack(3),Therequirementforon-boardnavigationdatabaseswasidentifiedinthe1970swiththedevelopmentofthefirstFlightManagementSystems(FMS).ARINC424-firsteditionwaspublishedinMay1975andadaptedbytheindustryinJuly1975.AtthisstagetheARINC424documentwasdevelopedtosupportconventionalNavigation.Withtheimplementationoftheareanavigationmethods,andthecapabilitytouseinputsfromdifferentsensors,therequirementtohaveaccesstoasophisticatedon-boardnavigationdatabasebecamemandatory(TGL10).ARINC424hasbeencontinuouslyimprovedandadjustedovertheyearsinordertoaccommodatenewnavigationalprocedures,capabilities,standardsandtechnicalcharacteristics.,ARINC424-isastandardforthepreparationandtransmissionofdataforassemblyofairbornenavigationsystemdatabases,ARINC424aSpecificationforNavigationSystemDataBases,TheARINC424documentenablesdatabasesuppliers,avionicssystemsandotherusersofthedatabasestoflyandflightplanproceduresasprescribedbydesigners.Thedocumentisnotmeanttobeaprescriptivedocumentforproceduredesignexperts.CurrentlyARINC424-16isinuseARINC424-17isunderdevelopment,1.Assembleadatabank.2.Produceelectronicmediameetingtheoperationalrequirementsofthenextlinkinthedatachain(avionicsmanufacturer,airlines,ATC).3.Mergethedatawiththeoperationalsoftwareofairbornenavigationcomputers.4.Produceelectronicmediacontainingthemergeddataforuseonindividualaircraft.Participantsinthedataprocessingchainarepublicorganisations,States,avionicsmanufacturers,datahousesandvariousend-users.Anyparticipantinthedatachainmayoriginate,transmit,assemble,prepareorintegrateaeronauticaldata.,AeronauticalDataProcessingSteps,DifferencesinAvionicsSystems,Individualnavigationsystemsrequiredifferentformatsfornavigationreferencedata.Theavailablestorageinmanyavionicssystemspreventsallproceduresordataelementsfrombeingloadedintotheairbornedatabase.Airlinesarecostdrivenandhencedonotupgradeequipmentunlessthereisaclearbenefit.Thesystemlifecycleofmostavionicsequipmentis15to20years.Overtheyears,differentearthmodels,geodesiccalculationsandusesofvariablessuchasmagneticvariationhavebeenused.Differencesinavionicssystemsneedtobeconsideredduringtheprocessingofaeronauticaldata.Asaresult,databasesfromdifferentdatahousesmaynotalwaysbeconsistent.,NavigationSystemDataBaseFileContent,SortingProcessSortedinalpha/numericalorderDividedintostandard(S)andtailored(T)recordsSrecordsorderedbyAreaCodeTrecordsorderedbyAirlineCodeIndividualrecordsdividedinsections/sub-sectionsofmax.132charactersRecord:AsinglelineofcomputerdatamadeupofthefieldsnecessarytodefinefullyasinglepieceofinformationField:ThecollectionofcharactersneededtodefineoneitemofinformationEachrecorduniquelydefinedandstoredinthemasteruserfile,GeographicalAreaCodes,AccesstoNavigationData,Anaeronauticaldatabaseisacollectionofdatathatisarrangedforeaseofelectronicstorageandretrievalinasystemthatsupportsairborneorgroundbasedaeronauticalapplications.Thedatabasestructure,sortingrulesandtherelationshipsbetweendataelements,laiddowninARINC424standardareindispensableprerequisitesforthefunctionofsuchsystems.Eachprimaryrecord,completedbyadditionalprimaryandcontinuationrecords,coversallrequireddataelements.Basicprinciplesofdatabasesisthatinformationneedtobeentered,corrected,changedordeletedonlyonce.On-boardRNAVsystemshaveaccesstopre-programmedroutes,theairspacesconcerned,thenavaidsservingthisairspace,theairportsalongtherouteincludingdepartureanddestinationairports.Thesystemidentifiesthenextwaypoint,calculatestheaircraftpositionandprovidesinputstotheflightcontrolsystems.,MasterAirlineUserfile,Alternativepathstoindividualmasterairlinefiles,DataRecord(1)LayoutVHFNAVAID,Contains:customer/areacode,stationidentifier,navaidname,co-ordinates,frequency,elevation(DME),variation,datumcodeetc.,DataRecord(2)LayoutWaypoint,Contains:WaypointIDCo-ordinatesTypeENRorTerminalRNAVIAF/IF/FACF/FAF/MAPtStepdown(Terminalonly)Arccentre(Terminalonly)SID/STAR/APP/MultipleUsageRNAVairwayTerminal,DataRecord(3)LayoutHolding,Contains:RegionCodeFixIdentifierInboundCourseTurnDirectionLegLengthLegTimeHoldingSpeedMinAltitudeMaxAltitudeCycleDate,DataRecord(4)LayoutAirport,Contains:AirportICAOIdentifierATA/IATADesignatorLongestRunwayMagneticVariationAirportElevationARPSpeedLimitTransitionLevel/AltitudeAirportNameDatumCodeetc.,DataRecord(5)LayoutGate,Contains:AirportIdentifierCustomerAreaCodeGateIdentifierLatitudeLongitudeNotesetc.,DataRecord(6)LayoutSID/STAR/App_1,Contains:ProcedureIdentifierRouteTypeSID/STARRunwayTransition,EnrouteTransition,CommonRouteAppAppTransition,GPSApp,RNAVApp,PrimaryMISAP,SecondaryMISAP,CirclingApp,Straight-inApp,HelotoRWYTransitionIdentifierSequenceNumberWaypointIdentifieretc.,DataRecord(6)LayoutSID/STAR/App_2,Contains:WaypointDescriptorEssentialFly-overwaypointStepdownfixPathpointIAF/IF/FAF/FACFMAPtHoldingTurnDirectionPathandTerminationRecommendedNavaidArcRadiusThetaRhoMagneticCourseRoute/HoldingDistance/TimeAltitude1,Altitude2,VerticalAngle,DataRecord(7)LayoutRunway,Contains:RunwayIDRunwayLengthRunwayMagneticBearingThresholdCo-ordinatesRunwayGradientThresholdElevationThresholdCrossingHeightDisplacedThresholdDistanceLOC/MLS/ILSRefPathIDLOC/MLS/ILSCategroy/ClassRunwayDescription,DataRecord(8-29),NDBNavaidsLocaliserandGlideSlope/MLS/GLSCompanyRouteLocaliserMarkerPathPointsAirportCommunicationsMSAAirwaysMarkerCruisingTablesFIR/UIR,GRIDMORAEnrouteAirwaysEnrouteAirwaysRestrictiveEnrouteCommunicationsPreferredRoutesControlledAirspace,DesignandCodingIssues,WaypointClassificationRho-ThetaValuesRecommendedNAVAIDCo-locatedVOR/DMESpeedRestrictionsAltitudeRestrictionsWaypoint,NAVAIDandFixCoordinatesNamingConventionsPathTerminatorConcept,WaypointClassification,Theenroutewaypointsubsectionfileshouldcontainallnamedintersectionsdefinedintheenroutestructure.Asaminimumallwaypointsreferencedinsections.shouldbeavailableintheenroutesubsection.TheterminalwaypointsubsectionfileshouldcontainthosewaypointsnecessarytosupportSIDsandSTARsandapproachprocedures.Ifawaypointisusedinboththeterminalandenrouteareas,itshouldappearinboththeterminalandenroutesubsectionfile.Inordertoachieveconsistentcoding,StatesourcesmustclearlyclassifyanymultipleuseofwaypointsintherespectiveAIPsections.,Rho-ThetaValues,“Rho”isdefinedasthegeodesicdistanceinmilestoawaypoint.Source:officialgovernmentsourceswhenavailable.“Theta”isdefinedasthemagneticbearingtoawaypoint.Source:officialgovernmentsourceswhenavailable.IfaprocedurelegrequiresRho-Thetainformatione.g.fromarecommendednavaid,itmustbepublishedinAIP.ThecontentiscontrolledthroughrequirementsofthepathterminatorsandcodingrulescontainedinARINC424.,RecommendedNAVAID,TheRecommendedNAVAIDinanyEnrouteAirwayRecordmaybeanyVOR/DMEorVORTACavailableinthedatabase.TheRecommendedNAVAIDinanyTerminalProcedureRecordotherthanfinalapproach,shallbetheprocedurereferencefacilityinaccordancewiththerulesgoverningrecommendednavaidsforpathterminators.OnNDBbasedprocedures,therecommendedNAVAIDinformationisprovidedwiththeFinalApproachCourseFix(FACF),theFAFandtheMissedApprochFixrecord.ThisNDBorLocatorwillbetheprocedurereferencenavaid.DifferentpossibilitiesofdeterminingmagneticvariationinaTMA(individualnavaidstationdeclination,variationatairportreferencepointetc).FordatabaseconsistencytherecommendedNAVAIDisrequiredforcertainprocedurelegstoenabletheRNAVsystemtodeterminethecorrectmagneticvariation.,Co-locatedVOR/DME,NAVAIDfilecontainsdetailsofallVOR,VOR/DME,VORTACandTACANstationswithinageographicalareaofinterest.ForVOR/DMEandVORTACfacilities,iftheidentificationcodeoftheVORandDMEcomponentsisthesame,theDMEidentifierwillbeblank.Iftheyarenotthesame,theDMEidentifierfieldwillcarrytheidentificationoftheDMEcomponent.AccordingtoICAOAnnex10co-locatedmeansthatthelatitudeandlongitudeofthetwofacilitiesdifferbynomorethan1/10arcminutes(6seconds).Ifeitherthelatitudesand/orlongitudesofaVORandTACANorDMEcomponentsofafrequency-pairedVHFNAVAIDdifferby1/10arcminutesormorethecharacter“N”needstobeenteredintocolumn32onVHFNAVAIDrecord(navaidclass).,SpeedandAltitudeRestrictions(1),SpeedRestrictionsThespeedlimitwillbederivedfromofficialgovernmentsourceandshowninknotsonaSID/STARrecord.OnSIDs,thespeedlimitwillapplytoalllegsuptoandincludingtheterminatorofthelegonwhichthelimitisencodedfromthebeginningoftheprocedure.Ifasecondspeedlimitiscodedonasubsequentleg,thelimitwillbeappliedfromthatlegbackwardstothepreviousterminatorwhichcontainedaspeedlimit.OnSTARs,thespeedlimitwillbeappliedforwardtotheendofarrivalunlessasecondspeedlimitisencoded.,SpeedandAltitudeRestrictions(2),AccordingtoARINC424speedlimitationscanbecodedindifferentwaysbyusingdifferentpathterminators.InordertoachieveconsistencyallspeedrestrictionsinRNAVproceduresshouldbeappliedatspecificwaypoints.Speedrestrictionsthatareonlyappliedduringspecifictimeperiodsarenotcodedindatabase.Somelegacysystemscanonlyprocessspeedrestrictionsincombinationwithanaltituderestriction.,SpeedandAltitudeRestrictions(3),AltitudeRestrictionsThealtitudedescriptionfieldwilldesignatewhetherawaypointshouldbecrossed“at”,“atorabove”or“atorbelow”specifiedaltitudes.Theconditionalterminationaltitudecanbecodedincolumns90through95oftheSIDrecord.Ifa“+”,“-”orblankiscodedinthealtitudedescriptionfield,inputofasecondaltitudemustimplyaconditionalaltitudetermination.Ifapublishedtake-offrequiresaturngreaterthan15degreesfromtherunwayheadingwithoutanaltitudespecifiedbeforetheturn.aCA,VA,orFAontherunwayheadingtoanaltitudeof400feet(orasspecifiedbysource)mustbecodedbeforetheturnorasfirstlegofthedeparture.,SpeedandAltitudeRestrictions(4),ARINC424providesanumberofwaystocodealtituderestrictions.Forsimplificationandtoavoidcodinginconsistenciesaltituderestrictionsshouldbeappliedatwaypointswhereverpossible.Altituderestrictionsintheterminalareathatareonlyappliedduringspecifictimeperiodswillnotbeincludedintheairbornedatabase.,Waypoint,NavaidandFixCoordinates(1),Thegeographicpositionofwaypoints,intersections,navaids,runwaythresholdsetc.isdefinedinthelatitude/longitudefields.Ninealpha/numericcharactersdefinethelatitudeindegrees,minutes,seconds,tenthofsecondsandhundredthsofseconds:N45562518Tenalpha/numericcharactersdefinethelongitudeindegrees,minutes,seconds,tenthofsecondsandhundredthsofseconds:E015523622.Thisresolutionreflectstheairlinesdesirefortheuseofbestavailabledata.,Waypoint,NavaidandFixCoordinates(2),Aviationindustryrequirementsforaccuracyandresolutionforelecteddataelements.,Theseindustryrequirementsrepresenttheresolutionsthatcanbeusedbythevariousavionicssystems.Manynumericalvaluesusedindescribingproceduresarecalculatedvaluese.g.fixes,TMAentryorexitpointsetc.,Waypoint,NavaidandFixCoordinates(3),Theaccuracyofcalculatedvaluesislimitedbytheaccuracyofthevaluesusedinthecalculation.Thedesignershouldbeawareofallthenavaidsthatanaircraftflyingacertainproceduremayuse.ThisincludesnavaidslocatedinnearbyTMAsorinneighbouringcountries.Specialagreementswithhostcountriesmayberequired.Thenavaidfunctionandreliabilityandtheconsequencesofnavaidoutagesneedtobeaddressedduringdesign(operatinghours,maintenancestatus,requiredflightchecks,emergencypowersupplyetc),ARINC424NamingConvention(1),ICAOAnnex11definestheinternationalstandardsforthecodeddesignatorsofNAVAIDs,waypoints,airways,SIDsandSTARs.Trackchangepointsorturningpointsshouldbenamedanddefinedbyco-ordinatesintheAIP.ARINC424establishescodingrulesforidentifiersandnamefieldswhenthegovernmentsourcedoesnotprovideidentifiersornamesinaccordancewithAnnex11.Example:ARINCnamingruleforRNAVwaypoints,intersectionsandreportingpointsifthename/identifierismoreorlessthanfivecharacters:-iffiveorlesscharacters,usethefullname-ifmorethanfivecharacters,eliminatedoubleletters,keepthefirstletter,firstvowelandlastletter,dropothervowelsfromrighttoleft,dropconsonants,startingfromrighttoleft,ARINC424NamingConvention(2),AnyplanneddeviationfromtheICAOnamingconventionshouldbeavoided.Deviationscreateadditionalworkload,causemisinterpretationsandencourageerrors.Ifrequiredwaypointse.g.turningpointsarenotnamedanddefinedbycoordinatesindatabase,thesepointsmustbeidentifiedinanRNAVdatabase.ThesocalledComputerNavigationFixes(CNFs)willbecreatedbythedatahouses.Incertaincases,ATCisunawarethatthesefixesexist.Aserioussafetyproblemcanarisewhenapilotneedstoselectanavaidfromthedatabasebyidentifierandthedatabasehasmultiplenavaidswiththesameidentifier.,ThePathTerminatorConcept(1),ThePathandTerminatorconceptwasdevelopedtopermitcodingofterminalareaprocedures,SIDs,STARsandapproachprocedureswithoutproliferatingthenumberofwaypoints.ThetwoelementsPathandTerminatorprescribingthewayinwhichapathistobeflownandhowthepathistobeterminated.OvertheyearsandinparticularwiththeintroductionofRNAVnewlegtypeswereadded.Currently,theARINC424documentdescribes23pathterminators.Certainlimitationssuchaslegsequenceorfly-by/fly-overrulesmustbeconsideredbyproceduredesigners.Databasesuppliersmustbeaccomplishedusingpath/terminatorsmosta