CANoe DENoe - KEMT FEI TUKE
CANoe DENoe - KEMT FEI TUKE
CANoe DENoe - KEMT FEI TUKE
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
52<br />
display functions are reduced to provide more computing time for internal data processing.<br />
When the high-load limit of the ring buffer is exceeded, the display of messages in<br />
the Trace window is interrupted briefly under load operation to provide other analysis<br />
blocks with more computing power. However, it is possible that not all messages will<br />
be displayed in the window any longer during the measurement. You can recognize<br />
this load situation during the measurement by an exclamation point (!) in the first column<br />
of the window. Although not all messages are shown, no data are lost. After you<br />
stop the measurement, the entire set of information is available to you in the Trace<br />
window, Graphic window and in logging.<br />
2.5.2 Behavior with Data Loss<br />
If the ring buffer overruns in spite of these measures, as a user you are immediately<br />
informed of this data loss:<br />
An occurring data loss is registered in ASCII logging. The ‘*’ symbol appears in the<br />
line after which the data loss occurred. In the configuration dialog for the Log file the<br />
Lost Data Message Box option also allows you to have a data loss shown in a separate<br />
message window at the end of measurement.<br />
The Bus Statistics window also indicates to you a data loss during an overload situation<br />
with the @ symbol. However, please note that the display of bus load and received<br />
messages continue to function properly, since this information is provided by<br />
the interface card and does not need to be computed by the main program first. Consequently,<br />
the Bus Statistics display allows you to estimate the extent of the data<br />
loss.<br />
2.5.3 Fill Level Indicator<br />
To allow you to observe the ring buffer between the real-time library and the main<br />
Windows program more precisely, the program has a fill level indicator.<br />
You can view the fill level during the measurement in the left corner of the status bar.<br />
If the ratio between arriving and processed events is balanced, the indicator has a<br />
green color. However, if it appears in red, significantly more events are arriving than<br />
can be processed at the given time. This is a clear indication that the system is overloaded.<br />
If the queue fill level reaches an alarming limit, the system attempts to relieve<br />
the load by selectively deactivating individual evaluation windows. If desired, you can<br />
have the queue's state displayed with the help of the entry ShowMainQueue=0 in the<br />
[System] section of the CAN.INI file.<br />
You can also have the fill level displayed in the Write window. To do this, set a minimum<br />
value of WriteLevel = 3 in the [Environment] section of the CAN.INI<br />
file. Then, when the ring buffer overflows the Write window shows the report "Load<br />
transition: NORMAL->DATA LOST" and informs you of the data loss. After the<br />
overload situation has ended (e.g. after a brief burst on the bus) you are similarly<br />
informed as soon as a normal situation has been restored. You can recognize this in<br />
the Write window by the report "Load transition: QUEUE HIGH -> NORMAL".<br />
© Vector Informatik GmbH <strong>CANoe</strong>/<strong>DENoe</strong> Manual Version 4.1.1