Lowrance HDS-9 Carbon - No Transducer Installation Manual EN - Page 37

Diagnostics, Bus state, Rx Overflows, Rx Overruns, Rx/Tx Errors, Rx/Tx Messages

Page 37 highlights

Ú Note: Setting the instance number on a 3rd party product is typically not possible. Diagnostics The NMEA 2000 tab on the diagnostics page can provide information useful for identifying an issue with the network. Ú Note: The following information may not always indicate an issue that can be simply resolved with minor adjustment to network layout or connected devices and their activity on the network. However, Rx and Tx errors are most likely indicating issues with the physical network, which may be resolved by correcting termination, reducing backbone or drop lengths, or reducing the number of network nodes (devices). Bus state Simply indicates whether the bus is powered, but not necessarily connected to any data sources. However, if bus shows as off, but power is present along with an increasing error count, it is possible that termination or cable topology is incorrect. Rx Overflows The unit received too many messages for its buffer before the application could read them. Rx Overruns The unit contained too many messages for its buffer before the driver could read them. Rx/Tx Errors These two numbers increase when there are error messages, and decrease when messages are received successfully. These (unlike the other values) are not a cumulative count. Under normal operation these should be at 0. Values around 96 upwards indicate a heavily error prone network. If these numbers go too high for a given device, it will automatically drop off the bus. Rx/Tx Messages Shows actual traffic in and out of device. Software Setup | HDS Carbon Installation Manual 37

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88

Ú
Note:
Setting the instance number on a 3rd party product is
typically not possible.
Diagnostics
The NMEA 2000 tab on the diagnostics page can provide
information useful for identifying an issue with the network.
Ú
Note:
The following information may not always indicate an
issue that can be simply resolved with minor adjustment to
network layout or connected devices and their activity on the
network. However, Rx and Tx errors are most likely indicating
issues with the physical network, which may be resolved by
correcting termination, reducing backbone or drop lengths, or
reducing the number of network nodes (devices).
Bus state
Simply indicates whether the bus is powered, but not necessarily
connected to any data sources. However, if bus shows as
off
, but
power is present along with an increasing error count, it is possible
that termination or cable topology is incorrect.
Rx Overflows
The unit received too many messages for its buffer before the
application could read them.
Rx Overruns
The unit contained too many messages for its buffer before the
driver could read them.
Rx/Tx Errors
These two numbers increase when there are error messages, and
decrease when messages are received successfully. These (unlike
the other values) are not a cumulative count. Under normal
operation these should be at 0. Values around 96 upwards indicate
a heavily error prone network. If these numbers go too high for a
given device, it will automatically drop off the bus.
Rx/Tx Messages
Shows actual traffic in and out of device.
Software Setup
| HDS Carbon Installation Manual
37