Raymarine Evolution EV-2, Installation Instructions Manual

Page: 12 / 42

2.2 Installation checklist
Installation includes the following activities:
Installation Task
1 Plan your system.
2 Obtain all required equipment and tools.
3
Site all equipment.
4 Route all cables.
5 Drill cable and mounting holes.
6 Make all connections into equipment.
7 Secure all equipment in place.
8 Power on and test the system.
Schematic diagram
A schematic diagram is an essential part of planning any
installation. It is also useful for any future additions or
maintenance of the system. The diagram should include:
• Location of all components.
• Connectors, cable types, routes and lengths.
Software requirements
Correct operation of this product requires software version 2.0 or
later for p70 and p70R pilot control heads.
Required additional components
To complete your autopilot system, you will need the following
components and data sources in addition to the Evolution
components.
Essential:
• Compatible autopilot control head.
• Teleflex Optimus or Volvo Penta EVC Drive interface unit (as
appropriate for your vessel’s drive system).
• Power cables.
Recommended:
• Compatible speed data source. The autopilot uses speed
data when making calculations relating to navigation. As a
minimum, this information must come from a GPS receiver
providing SOG (Speed Over Ground) data, or ideally from a
dedicated speed sensor.
• Compatible wind data source (only required for sailing
vessels). The autopilot uses wind vane data to steer relative to
a specified wind angle. This data must come from an analog
wind transducer connected to the SeaTalk
ng bus.
• Rudder angle sensor. To ensure optimum autopilot
performance, Raymarine highly recommends that a rudder
reference unit is used.
Optional:
• Position data source. The autopilot uses position data when
following routes and calculating the optimum course to steer.
This data is usually supplied by a GPS receiver on the
SeaTalk
ng bus.
Multiple data sources (MDS) overview
Installations that include multiple instances of data sources can
cause data conflicts. An example is an installation featuring
more than one source of GPS data.
MDS enables you to manage conflicts involving the following
types of data:
• GPS Position.
• Heading.
• Depth.
• Speed.
• Wind.
Typically this exercise is completed as part of the initial
installation, or when new equipment is added.
If this exercise is NOT completed the system will automatically
attempt to resolve data conflicts. However, this may result in the
system choosing a source of data that you do not want to use.
If MDS is available the system can list the available data
sources and allow you to select your preferred data source.
For MDS to be available all products in the system that use
the data sources listed above must be MDS-compliant. The
system can list any products that are NOT compliant. It may
be necessary to upgrade the software for these non-compliant
products to make them compliant. Visit the Raymarine website
(
www.raymarine.com ) to obtain the latest software for your
products. If MDS-compliant software is not available and you
do NOT want the system to automatically attempt to resolve
data conflicts, any non-compliant product(s) can be removed or
replaced to ensure the entire system is MDS-compliant.
12
Evolution EV-2