COBHAM Sailor 250 FleetBroadband, Training Manual, Page: 154 / 270

144
Chapter 5
Troubleshooting
5
telnet:/$ cnav -m pos
55.79411 (lat) 12.52293 (lon) 50.49m (hmsl) (3D)
Fix at: Tue Jan 05 11:50:25 2010
System time: Tue Jan 05 11:50:26 2010
ECEF x: 3508374.790000 y: 779261.320000 z: 5251665.320000
Satellites 8
Must be displayed: yes
Time to first fix 00:01.01+-
**
Signal / C/No status: debug:/$ iai2_cn0_show
Figure 5-56
Figure 5-57
CRC error is calculated for each FEC block.
If for example E6 FEC blocks is received and one FEC block has
one or more CRC error THEN CRC errors = 1 ppm.
High CRC error indicates a poor signal.
To give an indication on the load of the forward bearer compare
the ’all data received’ with ’data only for me’.
Small difference = low load. (only me on the bearer)
Big difference = high load. (more terminal on the forward bearer)
Like with the error log it is possible to monitor the C/No status
online.
In the debug shell use the cmd:
telnet:/$ iai2_cn0_show (where 0 = digit 0)
NOTE!
C/No for all data received on
the forward bearer.
’All data’ is ’my data’ + ’data to
other terminals’ on the same
forward bearer.
NOTE!
C/No for data, only for me,
received on the forward beare.
’Data for me’ is ’all data—’data
for other terminals’.