EIVA A/S Page 1

NaviPac AIS IF

Vessel details ................................................................................................................. 2 Interfacing ...................................................................................................................... 4 Data output ..................................................................................................................... 5 The INI file .................................................................................................................... 9

Use for own gyro ......................................................................................................... 10

Special tug handling ..................................................................................................... 11 On the barge ............................................................................................................. 12

On the tug ................................................................................................................. 12 Migration with NaviPac ............................................................................................... 14

As soon as NaviPac is started with an AIS interface, the above window opens up

minimized. The window is not needed for ordinary NaviPac operation, but might be

very useful when obtaining detailed vessel information. It’s recommended to keep the

window running (OK minimized) all the time.

The main window displays

Vessel name

AIS Id

Call Sign

Position (Lat/Long)

Attitude (Speed, Course and heading)

Vessel type

Time since update

NaviPac AIS I/F

EIVA a/s Page 2

TugId – assigned for use in NaviPac (see later)

OID – identification number for use in Helmsman’s Display

Out – Marked with + is data is sent out on UDP/IP port for use in eg. NaviPac

main system

Please note that the static vessel parameters are updated rather slow, so you may see

vessel without name, call sign etc.

If no data has arrived from a vessel for more than 5 minutes, then it’s removed from

the display list.

Vessel details If you double click on a vessel name, then the dialogue with vessel details pops up.

It displays (read only) information about the most general vessel parameters.

The window updates approximately every 5 seconds.

You may switch to next/previous vessel by the corresponding buttons.

NaviPac AIS I/F

EIVA a/s Page 3

For Tug id please refer to Use for own gyro If your NaviPac haven’t got access to vessel gyro then you may read the data from the

AIS input – not best solution but better than no solution!

Open the AIS_NP.INI and enter OwnId and OwnPort.

After you have started AISIF again it will read and display gyro (and id) at the top

rightmost corner:

This information will bent out as UDP/IP message – and it can be captured into

NaviPac as gyro:

NaviPac AIS I/F

EIVA a/s Page 4

Special tug handling.

Interfacing The AIS module can either read data directly from COM port (recommended

operation) or get it via NaviPac.

The definition if this is made in the Edit, Data Input Setup menu:

NaviPac AIS I/F

EIVA a/s Page 5

If reading directly from port just select port and define communication settings. Data

will be displayed as shown above. Please note that the AISIF don’t receive data while

open!

If you want to read data from NaviPac (that is the interface is defined inside NaviPac)

then just select No Port and the rest is automated.

Data output The AIS module may send data to other NaviPac systems. This can be controlled via

the Edit, Data Output Setup menu:

This should only be used if AISIF reads data directly on the port!

Send position to Helmsman’s Display

The position, name and heading will be passed on to the HD and presented on

NaviPac AIS I/F

EIVA a/s Page 6

top of the ordinary vessel display:

Send position to EIVA 3D Monitor

Data will be send over to the EIVA 3D data display module via the local

SceneServer:

NaviPac AIS I/F

EIVA a/s Page 7

Send position to NaviPac LogData

Position data will be send over to the NaviPac recording system and stores in

survey and general file format. Note: Not available in NaviEdit processing

Send selected objects to NaviPac

Upgrade the AIS objects marked with a tug id to be real NaviPac object.

They will then be send out on UDP/IP (entered port) in the standard NaviPac

format and can be used inside NaviPac:

NaviPac AIS I/F

EIVA a/s Page 8

NaviPac AIS I/F

EIVA a/s Page 9

The INI file The program requires a special INI file located at the NaviPac home directory

(\EIVA\NaviPac) called AIS_NP.ini. The file includes a series of special settings –

some maintained by the operator and some by the program

[IN]

Port=5

Baudrate=38400

Databits=8

Stopbits=1

Parity=0

-1 defines that data is read via the NaviPac interface – otherwise enter real port

number and i/o setup

[IDS]

259148000=MS SULEVAER

257221700=DRONNINGEN

Definition of all vessels tracked by the system

[TUGs]

259499000=31

257285400=32

The special tug boat option

[MMSI]

201 = Albania

202 = Andorra

Mapping of IMO numbers to country

[OUT]

send23D=1

send2HD=1

OwnId=219001543

OwnPort=11111

send2LD=0

send2NP=1

Port2NP=7914

Definition of output’s from AIS module

Send23D

Send data on UDP/IP to the EIVA 3D module – see EIVA 3D for details

Send2HD

Send data on TCP/IP to the EIVA Helmsman’s Display – that is use this in

NaviPac without interfacing in NaviPac

send2LD

Send data out to LogData

send2NP

Send data out to NaviPac on port Port2NP

NaviPac AIS I/F

EIVA a/s Page 10

OwnId & OwnPort

AISID for own vessel. Pickup Gyro and send it out on UDP/IP port (127.0.0.1

OwnPort) – see next section

Use for own gyro If your NaviPac haven’t got access to vessel gyro then you may read the data from the

AIS input – not best solution but better than no solution!

Open the AIS_NP.INI and enter OwnId and OwnPort.

After you have started AISIF again it will read and display gyro (and id) at the top

rightmost corner:

This information will bent out as UDP/IP message – and it can be captured into

NaviPac as gyro:

NaviPac AIS I/F

EIVA a/s Page 11

Special tug handling If the AIS system is interfaced to a barge in A NaviPac TMS system, then you may

use the heading information from the AIS and assign this to tug boats.

NaviPac AIS I/F

EIVA a/s Page 12

This results in a simple tug setup, as no real gyro needs to be interfaced.

On the barge

For each tug coming in with AIS data you must tell the system what it’s tug id

(NaviPac object id is). This is done in the Vessel details Tug Id field.

Each time data is received from a vessel the system checks if it’s assigned to a tug,

and if so it generates automatic a telegram “$TUG-

H,<ID>,<gyro>*<checksum><cr><lf>” and sends that to the telemetry module –

which routes it out to all vessels.

On the tug

The tug boat receives a TUG-H message and check if it’s related to itself. This is done

automatically in the Remote NaviPac module:

NaviPac AIS I/F

EIVA a/s Page 13

If so, then it’s send on to he NaviPac kernel as a dynamic gyro correction.

To make NaviPac use this correction you must define it to do so in the NAVIPAC.INI

file (located at the Windows directory)

[Gyro]

UseAISGyroCorrection=1

A gyro must still be defined inside NaviPac on the TUG boat, but it could be set to

simulated mode.

NaviPac AIS I/F

EIVA a/s Page 14

The simulated input of 0 will then be corrected to 280 as the AIS heading was sending

280 degree.

If you know that there are some misalignment in the AIS gyro on a tug boat, then you

could simulate the extra C-O value or similar.

Migration with NaviPac Sample data flow migration between NaviPac and AISIF

NaviPac AIS I/F

EIVA a/s Page 15