Filter
Top Products
4. INSTALLATION
4-19
Output data description
NRX: New NAVTEX received message
New NAVTEX message to follow in ASCII format
$NXNRX,xxxx,x,x,x,xx,xx,xxxx,hhmmss,x.x,n--n*hh<CR><LF>
encapsulated message
error rate % (xx.x)
UTC of receipt of message
year
month (1-12)
day (0-31)
freq ('490', '518' or '4209')
number of lines in message (1 to 999)
line number (1 to 999)
message identifier (B
1
B
2
B
3
B
4
)
The first NRX sentence transmitted for a particular NAVTEX message shall contain valid data
for all fields. For subsequent NRX sentences encapsulating a NAVTEX message, all fields apart
from 'message identifier', 'line number' and 'encapsulated message' are optional. If UTC time or
date are not known then the fields are NULL.
Example usage:
$NXNRX,TA21,1,4,518,10,01,2005,102000,2.2,291600 UTC JAN =*hh
$NXNRX,TA21,2,4,,,,,,,OOSTENDERADIO - INFO 37/04 =*hh
$NXNRX,TA21,3,4,,,,,,,WESTHINDER ANCHORAGE, ANCHOR LOST IN*hh
$NXNRX,TA21,4,4,,,,,,,POSITION 51-24.94N 002-40.02E.+*hh
Example usage when no UTC is available to the equipment:
$NXNRX,TA21,1,4,518,,,,,2.2, TEST MESSAGE*hh
Where the NAVTEX message contains reserved characters as defined in IEC 61162-1, then
these shall be handled by using ASCII 'escape code' :
c) Reserved character ASCII escape code
d) <CR> ^0D
e) <LF> ^0A
f) $ ^24
g) * ^2A
h) , ^2C
i) ! ^21
j) \ ^5C
k) ^ ^5E
l) ~ ^7E