Make the KSS-RSI driver real-time safe

[Svastits]

Heap allocations in control loop should also be removed! RSICommand heap-allocates in consctructor, and it is instantiated in every cycle (write)

[altex111]

Tasks:

• [x] Heap allocation in udp server
• [x] Heap allocation in control loop and RSI Command
• [x] Redesign RSI Command and RSI State so it makes direct connection between buffer and hw param
• [X] working stop action when ROS side stopped
• [ ] working stop action when robot side stopped

Low prio tasks (possibly in different branch):

• [x] Modify ros_rsi.src and remove PTP movements
• [x] IP set via config file
• [ ] add cartesian control
• [ ] controller handler and control mode change integration

[altex111]

Evaluating PUGI XML

After creating my own xml parser i implemented the pugi xml parser too. The parser is capable of working on C style character strings which is compatible with the udp library i use. The user is also able to redefine the allocation functions. I redefined them with the memory resources library so the memory is allocated at the start of the algorithm.

Results

As the following diagrams shows there is a significant difference between the two xml parser both in encodeing and decodeing.

Decode

Encode

Conclusion and Tasks

The driver for encodeing and decoding messages to and from the RSI should use the PUGI XML parser. However further tests should be created to prove the real-time nature. The PUGI can be configured multiple ways. It should be checked whether the parser can be more stable. While decodeing there are a few spikes where the decode takes longer It should be investigated further whether thees comes from useing the memory resource or the algorithm need more time. Further task is to integrate the pugi xml into the driver. Also there is an open pull request which updates the pugi with its own pmr style memory resource.