CANape and CANalyzer
Approaches for finding the right software version:
SAP:
1. Login to P72 database of SAP
2. Click on /RB04/2L3_ROM_BOSCH
3. Enter the Material Number (e.g. 0203.300.693) and plant code (0780 Reutlingen)
4. In the Stücklist search for FSW_Container and click on it
5. Go to description tab and click the desired entry
6. Here you will find SW-Revision (e.g. SYSBPLUS_AUDI.MLBevo.REAR.SLAVE-0230.I3.1)
7. Try to find the right software directory here:
\\bosch.com\dfsrb\DfsDE\DIV\CS\DE_CS$\Prj\DA\EZKL_Radar\03_Customers\90_SWStaende\SYSB_PLUS
STIL:
Identifying the used software on the radar is possible by using STIL routine. The routine can be found in
the tsw_id80.xxxx.bin file. To get the hardware information a 1 byte message has to be sent to the
radar. The message: 0x31
Further information on STIL routine:
https://inside-docupedia.bosch.com/confluence/pages/viewpage.action?pageId=503251455
The CANape has to be started by opening the DiaTester_MRR\DiaTester.cna file.
In the CANape under the 1: DiaTester USER INFO tab it is possible to find the software version that is in
use in the project. If the software is not the same on the radar, the CANape stays offline.
The CUSTOMER ERROR MEMORY contains the DTC (Diagnostic Trouble Code) messages. Like in all
config files, the user interface can be slightly different for different software versions. To reread the
faults, click on the button that is over the number 1 on the picture.
If it is necessary to delete the errors, first click on the right side on the PreCondition – Get button. After
that you can click on the button that is above the number 2 on the picture.
In some cases it is not possible to delete the messages, it depends on the software. In these cases the
only possible way to erase the messages is to reflash the microcontroller.
The other place where it is possible to read out error messages is the BOSCH STORAGE MEMORY. It also
shows the number of occurrences of the errors. With the Clear button we can erase the error messages
and with the Read button we can read them.
Like before, here it is also possible that the software doesn’t allow the deletion of the errors. In this case
flashing the microcontroller is one solution like with the DTC errors. Another solution is to mask the
errors that are not relevant for the measurement.
The meaning of the errors and the process to mask them can be found in the documentation\errordocu
subfolder of the software folder.
CANalyzer (resbus simulation):
For each software there is a file with cfg extension in the measurement\canalyzer folder. Open it with
the CANanalyzer to have a similar picture like this:
This can be different, it depends on the project of the given software.
The CANanalyzer doesn’t load in automatically the correct dll files for the simulation, it has to be done
manually. Under the Configuration tab select the Options… option.
Here select under the Programming the CAPL DLL option. This is where the proper dll files have to be
added, and the unused removed. The location of these dll files is in the measurement\canalyzer\dll
subfolder. Include all of them that you can find in this folder.
If everything is set, on the top left corner it is possible to compile with a tub like icon that has two blue
downward arrows. Then to run the project, click on the lightning bolt icon.
In the trace window we can see if the CAN communication is working between the Vector hardware and
the radar.
For simulation first we need to press the Initialize button. Then we can give actions that we want to
simulate. For example we can toggle the gas pedal or we can set a speed to hold.