Bus Traffic of 0% for a single node means that the node
(MACID) has stopped communicating since the
NetMeter was plugged in or reset!
!
!
!
Check the scanner configuration.
Setting the scan interval (or inter-scan delay)
too short can cause device timeouts due to
bandwidth or node performance limitations.
Setting the scan interval (or inter-scan delay) too
long reduces system performance and makes
inefficient use of available bandwidth.
!
Check for Change-of-State devices consuming
excessive bandwidth (look for one or more
nodes with excessive bandwidth or a MAX
bandwidth much higher than average)
Note about frame rate:
If you know the input and output
size (in bytes) for a polled or strobed device (see your
configuration or the device documentation) you can
determine the scan rate (per second) as follows:
Bus Traffic deals with
these two wires
(CANL & CANH)
Scan rate =
Frame Rate (from NetMeter)
Input Output Frames
Input Frames =
Output Frames =
Input Bytes 8
(round up to whole number)
¸ ¸
( 7 if > 8 bytes)
Output Size 8
(round up to whole number, always 1
frame for strobe devices)
¸ ¸
( 7 if > 8 bytes)
Bus Traffic
Thresholds:
Bus Traffic High Warn
Bus Traffic Low Warn
90.0%
10.0%
3
BUS
TRAFFIC
9
For networks with
bandwidth we suggest:
