[Feature] Choose different read and write rate for the hardware components

[saikishor]

Hello!

This PR helps to obtain different read and write update rates rather than having the same update rate as of the controller manager. With these changes, each and every component can run at their own chosen rate and they update the State and Command interfaces according to that rate. This is very useful for system with different communication layers such as EtherCAT, CAN and Serial. Hope this helps the community.

y axis corresponds to the nanoseconds

Thank you

[codecov]

Codecov Report

Attention: Patch coverage is 96.36364% with 8 lines in your changes missing coverage. Please review.

Project coverage is 87.83%. Comparing base (dbee650) to head (68ddc9c).
Report is 1 commits behind head on master.

Files with missing lines	Patch %	Lines
hardware_interface/src/resource_manager.cpp	75.75%	4 Missing and 4 partials ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1570      +/-   ##
==========================================
+ Coverage   87.57%   87.83%   +0.26%     
==========================================
  Files         122      122              
  Lines       12768    12926     +158     
  Branches     1146     1153       +7     
==========================================
+ Hits        11181    11353     +172     
+ Misses       1157     1148       -9     
+ Partials      430      425       -5     

Flag	Coverage Δ
unittests	87.83% <96.36%> (+0.26%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
..._interface/include/hardware_interface/actuator.hpp	100.00% <ø> (ø)
...rface/include/hardware_interface/hardware_info.hpp	100.00% <ø> (ø)
...re_interface/include/hardware_interface/sensor.hpp	66.66% <ø> (+16.66%)	⬆️
...re_interface/include/hardware_interface/system.hpp	100.00% <ø> (ø)
hardware_interface/src/actuator.cpp	80.66% <100.00%> (+5.83%)	⬆️
hardware_interface/src/component_parser.cpp	94.82% <100.00%> (+0.18%)	⬆️
hardware_interface/src/sensor.cpp	76.03% <100.00%> (+3.76%)	⬆️
hardware_interface/src/system.cpp	80.66% <100.00%> (+5.83%)	⬆️
...dware_interface/test/test_component_interfaces.cpp	97.63% <100.00%> (+0.01%)	⬆️
...e/test/test_component_interfaces_custom_export.cpp	89.25% <100.00%> (+0.36%)	⬆️
... and 4 more

... and 3 files with indirect coverage changes

[christophfroehlich]

Great addition 👍

Why not just use update_rate as attribute name (same as for controller_manager or the controllers)

Please update the docs and add also a paragraph to the release notes.

[saikishor]

Great addition 👍

Why not just use update_rate as attribute name (same as for controller_manager or the controllers)

Please update the docs and add also a paragraph to the release notes.

Sure. I forgot about the docs. I'll update it tomorrow at the earliest. Thanks for reminding me.

Well regarding the parameter name, I thought of using different because, we have update_rate for the update callback of the controllers and for the hardware I wanted to use the appropriate one, so I used rw_rate to specify the read/write_rate. How the changes are done, in future we can also have different read and write rates if needed, with just changing the parsing part. I'm open to the discussion on the parameter naming part.

[christophfroehlich]

Thanks for the docs 👍

[mergify]

This pull request is in conflict. Could you fix it @saikishor?

[saikishor]

Resolved conflicts!

[mergify]

This pull request is in conflict. Could you fix it @saikishor?

[saikishor]

@christophfroehlich I've just fixed the conflicts after your merged PR on deprecating mimic stuff

[mergify]

This pull request is in conflict. Could you fix it @saikishor?

[mergify]

This pull request is in conflict. Could you fix it @saikishor?

[bmagyar]

thank you!