BLUEPIRAT2 | USER MANUAL/
page 73 of 82
15.2.2.2
The points in detail
Observed behavior
What exactly have you observed that does not match the behavior you expected or described in
the manual?
Exact time
The most accurate possible time when an unexpected behavior was observed.
Please always remember: Since we do not know which tests you are doing at what time, a con-
crete error time is absolutely necessary for the analysis. Without this information, an effective
analysis is unfortunately not possible.
Used hardware
A list of the exact devices you were using when you observed the behavior. Is it a single device
or a TSL group? If so, with which TSL participants and in which order are they connected?
Which system client / firmware version
Exact information about the version of the system client and the firmware used is also important,
since it could possibly be a known problem in an older version. It is also important to specify
whether you process data with the System Client, the Download Terminal or the ClientLib.
Location
Was the behavior observed in a vehicle or in a test system?
Reproducibility
Has the problem occurred once, or can it be reproduced with defined steps? Does the behavior
occur with one or more setups?
Does the problem still occur after a restart and can it possibly be solved by a firmware update?
Last Steps
What was done last before this behavior was observed?
Screenshots
Screenshots can often explain something faster than words, so screenshots of the problem are
always welcome to show or compare something. Especially for screenshots from your own tools
please include an explanation of the values / representation.
Error report
An error report of the device / TSL network contains internal logs of the devices, the configura-
tion, the error report of the system client with which the error report was created and optionally
trace data. This combination helps us to understand what happened in the device at the speci-
fied time.
The creation of an error report is described in detail in the
User Manual of the System Client.
Offline data set
Especially if you have the feeling that something is wrong with the recording or conversion of
the data, we also need an offline data set to be able to reproduce / analyze the problem.
The creation of an offline dataset is described in detail in the
User manual of the System Client
