This PR addresses part of issue #2 by adding a warning message if the RDT output rate is different than 1Hz, and provides ways to read and modify the value from the driver.
The issue #2 cannot be solved in the driver itself without huge modification with an internal thread reading all the available data.
I think the current solution is fine as long as the user knows and sets the output rate correctly according to its reading rate.
The issue can be solved in the instantiation of the driver, by either setting the correct rate or adapting the read speed to the current rate.
Another issue https://github.com/kuka-isir/rtt_ati_sensor/issues/1 was created to address this problem
This PR addresses part of issue #2 by adding a warning message if the RDT output rate is different than 1Hz, and provides ways to read and modify the value from the driver.
The issue #2 cannot be solved in the driver itself without huge modification with an internal thread reading all the available data.
I think the current solution is fine as long as the user knows and sets the output rate correctly according to its reading rate.
The issue can be solved in the instantiation of the driver, by either setting the correct rate or adapting the read speed to the current rate. Another issue https://github.com/kuka-isir/rtt_ati_sensor/issues/1 was created to address this problem