![Saab R5 SUPREME Secure W-AIS Скачать руководство пользователя страница 45](http://html1.mh-extra.com/html/saab/r5-supreme-secure-w-ais/r5-supreme-secure-w-ais_operation-and-installation_794513045.webp)
R5
SUPREME Secure W-AIS System
TROUBLESHOOTING
7000 118-524, C1
Page 45
5
TROUBLESHOOTING
5.1
W-AIS Status view
The
W-AIS Status
view shows a summary of the Warship AIS settings that are currently
used by the R5 SUPREME W-AIS transponder. Therefore it can be helpful during
troubleshooting to see if there is a mismatch of settings between two R5 SUPREME W-
AIS systems. In this view it is also possible to see the currently transmitted bogus position
and bogus static and voyage data if these functions are enabled in the system.
Figure 29
– W-AIS Status view
5.2
Configuration mismatch
The most likely reason why two W-AIS systems cannot communicate with each other is
due to configuration mismatch between the transponders. The
W-AIS Status
view
described in section 5.1 shows the summary of the currently used W-AIS configuration.
Ensure that all W-AIS systems conform to the following:
Cipher must be the same on all systems
Encryption key must be the
same
on all systems on must be valid for the current
UTC time, see section 5.3.
Operational Mode should be set to Tactical to send encrypted messages on the
encrypted link
Ensure that external Tx switch is not preventing transmissions.
MMSI must be set on all systems
Note that the encryption key may override some configured settings but the
W-AIS Status
view always show the currently used settings regardless if the settings is taken from
configuration or active encryption key.
Depending on which link type is used, all W-AIS systems must also conform to the
following:
Secure Link Type
Link Type
must be set to “Secure”
Secure Org.Id must be the
same
on all systems
Secure ID must be
unique
for each system.
Secure channel frequency must be the
same
on all systems