Samenvatting

The log data generated by a motion control system contains valuable information about the system's behavior. When a problem or error arises while the system is running, the log data can be a good source of information to pinpoint and, eventually, resolve the problem in the motion control system. However, depending on the size and complexity of the NYCe4000 application, the log data can be very large and complex to process manually. Therefore, in this graduation project, a software tool was developed to analyze and visualize the log data generated by the NYCe4000 application in order to assist the internal engineers of Bosch Rexroth in interpreting the information contained in the log data.

During the project, it was found that there are different types of log data generated by the NYCe4000 motion control system. Although different, these data have connections with each other, e.g. the NYCe log data records the function calls on the host software, and the trace data records the real time physical values, e.g. temperature, position, currents, etc, as wel as internal variables on the nodes, e.g. position error, setpoints, axis states, etc. By examining and linking these data, the behavior of the NYCe400 system as part of the overall customer's application can be understood in more detail. Thus, the idea to combine the different log data for analysis in the log analyzer tool came up.

The end result of this project is the LogAnalyzer, a software tool independent of the NYCe4000 software architecture that is able to take the different log files generated by the NYCe4000 motion control systems as inputs and visualize the log data contained in it.

Because of the time constraints of the project, the LogAnalyzer has not yet been tested to solve an actual problem in the NYCe4000 application. Therefore, the LogAnalyzer leaves several areas for potential improvement. The following list describes enhancements that can be considered for the future releases of the LogAnalyzer tool:
1. Creation of parser plugins for log data other than the NYCe log and the trace data.
2. Additional functionality that allows the users to choose possible translations of the NYCe log's values.
3. Additional translation functionality for the internal event IDs in the NYCe log data.
4. Proper alignment of the trace data timeline with setpoints timeline.
5. Possibility to build a knowledge base to be accessed by the LogAnalyzer.

Additionaly, some issues with the logging system that needs some attention in the future releases of the NYCe4000 software are encountered during the project, such as:
1. The accuracy of timestamps in the NYCe log data.
2. The correctness of the calculation results for data IDs on the NYCe log data.
3. The possibility of missing log data when all available subsystems are logged.
4. The connection between the logged parameters and their owning function calls data.