Requiredadditionalcomponents
Tocompleteyourautopilotsystem,youwillneedthe
followingcomponentsanddatasourcesinaddition
totheEvolutioncomponents.
Essential:
•Compatibleautopilotcontroller(See:3.4
Compatibleautopilotcontroller).
•DriveunitappropriateforyourvesselandEvolution
EVandACUunits(See:3.5Driveunit).
•ACUpowercable(notsupplied).
•SeaT alkng®backbone.
Recommended:
•Compatiblespeeddatasource.Theautopilotuses
speeddatawhenmakingcalculationsrelating
tonavigation.Asaminimum,thisinformation
mustcomefromaGNSSreceiverprovidingSOG
(SpeedOverGround)data,orideallyfroma
dedicatedspeedsensor.
•Compatiblewinddatasource(onlyrequiredfor
sailingvessels).Theautopilotuseswindvanedata
tosteerrelativetoaspeciedwindangle.This
datamustcomefromananalogwindtransducer
connectedtotheSeaTalkng®backbone.
•Rudderanglesensor.T oensureoptimumautopilot
performance,itishighlyrecommendedthata
rudderreferenceunitisused.
Note:Thesystemcomponentslistedabove
are“recommended”becausetheyhelpto
provideoptimumperformanceforautopilot
systemswhenusedinconjunctionwiththe
“essential”componentslisted.However,these
“recommended”componentsarenotincludedin
allautopilotproductsorsystempacks.Consultthe
Raymarinewebsiteoryourlocaldealerforafull
listofthecomponentsincludedwithyourautopilot
system.
Optional:
•Positiondatasource–Theautopilotusesposition
datawhenfollowingroutesandcalculatingthe
optimumcoursetosteer.Thisdataisusually
suppliedbyaGNSSreceiverontheSeaTalkng®
backbone.
SeaTalkng®
SeaTalkng®(NextGeneration)isanenhanced
protocolforconnectionofcompatiblemarine
instrumentsandequipment.Itreplacestheolder
SeaTalkandSeaT alk2protocols.
SeaTalkng®utilizesasinglebackbonetowhich
compatibleequipmentconnectusingaspur.Data
andpowerarecarriedwithinthebackbone.Devices
thathavealowdrawcanbepoweredfromthe
network,althoughhighcurrentequipmentwillneed
tohaveaseparatepowerconnection.
SeaTalkng®isaproprietaryextensiontoNMEA2000
andtheprovenCANbustechnology.Compatible
NMEA2000andSeaT alkandSeaT alk2devicescan
alsobeconnectedusingtheappropriateinterfaces
oradaptorcablesasrequired.
Multipledatasources(MDS)overview
Whenasystemincludesmultipleinstancesofa
datasourcethepreferreddatasourceisselected
automatically.Thesystemspreferredsourcemaynot
beyourpreferredsource,orifyouareexperiencinga
dataconictyoucanmanuallyselectyourpreferred
datasource.
MDSenablesyoutochooseapreferredsourcefor
thefollowingdatatypes:
•GNSSPosition
•GNSSDatum
•Time&Date
•Heading
•Depth
•Speed
•Wind
Thisexercisewouldusuallybecompletedaspart
oftheinitialinstallation,orwhennewequipmentis
added.
ForMDStobeavailableallproductsinthesystem
thatusethedatasourceslistedabove,mustbe
MDS-compliant.Thesystemwillreportanyproducts
thatareNOTMDS-compliant.Itmaybepossible
toupgradethesoftwarefortheseproducts,to
makethemcompliant.VisittheRaymarinewebsite
(www.raymarine.com)toobtainthelatestsoftware
foryourproducts.
IfMDS-compliantsoftwareisnotavailableforthe
productandyoudoNOTwanttousethesystems
preferreddatasource,youmustremoveany
non-compliantproductfromthesystem.Youshould
thenbeabletoselectyourpreferreddatasource.
Note:Onceyouhavecompletedsettingupyour
preferreddatasources,youmaybeabletoadd
thenon-compliantproductsbackintothesystem.
Multipledatasourceexceptions
WiththeEvolutionsystem,thereareanumberof
importantexceptionstothehandlingofmultiple
sourcesofcertaintypesofdata.
Specically:
•Headingdata—Ifanon-Evolutionsourceof
headingdataisdesignatedbytheuser,the
Evolutionsystemcomponentswillcombinethis
headingdatawithitsowngyroandaccelerometer
data,andthenusetheimprovedheadingdata.
Thiscombinedheadingdatawillalsobeavailable
tootherequipmentontheSeaTalkng®bus.
•Rudderangledata—Wheretherearemultiple
sourcesofrudderreferenceinformation,the
Evolutionsystemcomponentswillignorerudder
angleinputsfromanyrudderreferenceunitsthat
areNOTconnecteddirectlytotheACU.
12