DESIGNER’S HANDBOOK 4189350049C EN
Page 16 of 206
The library needs to be compliant with the size and performance class of the XDi indicator:
Library class
Dual
Multi
Nav
XDi type
Dual
•
Multi
•
•
Nav
•
•
•
This means that an XDi Nav will accept all library classes, where a XDi Multi will only accept Multi or Dual libraries
and a XDi Dual will only accept a Dual library.
Since all library classes can be installed on an XDi Nav, it can be used as a universal service unit, where the needed
library can be uploaded from a laptop or PC whenever needed.
3.1.6
Upload a new library
It is possible to upload a new library via the USB service port on the XDi unit. The library is encrypted and requires
a special
“XDi
update tool
”
to be installed on your PC or laptop. The tool is available for download at
The zip-package includes a detailed installation and user instruction. If you need further help,
please contact DEIF support.
Be aware that the library package selected for an update must match the XDi size and performance class as
explained in the previous chapter.
3.2
Input data for XDi
Virtual indicators in the XDi library may present data from one or more data sources depending on the XDi
performance class (Dual or Multi). The standard XDi unit is designed to receive data via the two CAN bus ports.
When an extension module is mounted on the XDi, data can also be received from an analogue, digital or NMEA
input. Input data from an extension module may even be shared on the CAN bus, making the XDi act as a data
source for other XDi indicators on the bus.
Utilising this function limits the number of extension modules needed and only one adjustment or calibration of an
analogue, digital or NMEA input is needed in such a CAN base system.
Other devices on the CAN bus may also use CAN data provided by the XDi.
The DEIF XL, BW and BRW-2 indicators with CAN interface and TRI-2 CAN panorama indicator can be integrated
in a system where XDi is providing calibrated CAN data.
3.2.1
Object dictionary
– Object index table
All variable input data types are firmly defined and stored in the manufacture specific part of the CANopen object
dictionary. Object index 0x3000 to 0x3FFF.
In the XDi-net specification, all variable data used for indication is structured in a fixed format making it possible to
broadcast data without complicated setup.
Each data type has a name (source name) and data is stored as a value with a defined resolution and with a
standard data unit. When data is shared on XDi-net or CANopen it is the standard data value that is sent.
The detailed description of how XDi utilises CANopen
can be found in the “XDi-net/CANopen reference manual”.
3.2.2
Data type instance
To be able to handle several instances of the same data type in a CAN bus system, each defined data type can
support up to either 7 or 15 instances dependent of the data type.
An example: in a large system with 4 azimuth thrusters on the same CAN bus, each thruster is using a different
instance of the data
type “azimuth angle”.