![Saab R5 SUPREME Secure W-AIS Скачать руководство пользователя страница 27](http://html1.mh-extra.com/html/saab/r5-supreme-secure-w-ais/r5-supreme-secure-w-ais_operation-and-installation_794513027.webp)
R5
SUPREME Secure W-AIS System
CONFIGURATION
7000 118-524, C1
Page 27
NOTE: Numerical input format keys will not be available in all Secure Key
generator releases.
2. Choose a key index for the key. The R5 SUPREME W-AIS Transponder can
have up to 127 keys in the memory at the same time. The R5 SUPREME will
o
verwrite any existing key on the given index as long as the keys don’t overlap
in time.
If the key index is set to “0”, the R5 SUPREME Transponder will
automatically try to save the key on the next free index.
3. Fill in the hexadecimal (or numerical) code from the generated paper sheet (or
key file) in the fields named “Key Part 1” to “Key Part 4”.
4. When all 60 hexadecimal (or 75 numerical) characters have been input, press
the “Save” button.
5. If the key is valid, a popup will appear with information about the key settings:
Figure 15
– Valid Key
If the
key settings are as expected, press “Yes” to try to save the key.
6. A virtual keyboard popup prompting for password will appear. Enter the correct
password (default user password is “user”) and press
ENTER
on the virtual
keyboard.
7. If the key is successfully set it will automatically be used by R5 SUPREME
Transponder from the key
’s start time until it expires. A key symbol will appear
under the Operational Mode icon in the status bar if the key is currently used.
3.5.3
Keys on USB Memory
The R5 SUPREME W-AIS Transponder can load keys from USB memory. This is done
in the
Keys on USB
view which is accessed from
Main Menu
Maintenance
Configuration
W-AIS
Encryption Keys
Keys on USB
.
In addition to load keys, keys can be sent on VHF secure link to other users on the
secure VHF link. Keys sent over VHF secure link are sent as encrypted messages
using broadcast transmissions. Users sharing same secure channel configuration and
same secure key are able to receive new secure keys sent on secure link. See section
3.5.5 for handling of secure keys received on secure link.