Difference between revisions of "Robotrainer fixes"
Jump to navigation
Jump to search
(Created page with "This page summarizes problems to be solved, concerning the robotrainer framework Essential: * Update rate through ros_comm to allow more than 67hz. (Bøgild is looking into i...") |
|||
| (4 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | This page summarizes problems to be solved | + | This page summarizes problems to be solved concerning the robotrainer framework. |
| − | Essential: | + | <strong>Essential:</strong> |
* Update rate through ros_comm to allow more than 67hz. (Bøgild is looking into it). | * Update rate through ros_comm to allow more than 67hz. (Bøgild is looking into it). | ||
* Connection is lost every 10mins or so. This happens at random, sometimes after a short while, others after 30 mins. | * Connection is lost every 10mins or so. This happens at random, sometimes after a short while, others after 30 mins. | ||
| − | + | <strong>Non-essential:</strong> | |
* QT GUI's don't close immediatly when pressing ctrl-c in terminal. Only in record_ros_ui GUI. | * QT GUI's don't close immediatly when pressing ctrl-c in terminal. Only in record_ros_ui GUI. | ||
Latest revision as of 12:08, 15 January 2019
This page summarizes problems to be solved concerning the robotrainer framework.
Essential:
- Update rate through ros_comm to allow more than 67hz. (Bøgild is looking into it).
- Connection is lost every 10mins or so. This happens at random, sometimes after a short while, others after 30 mins.
Non-essential:
- QT GUI's don't close immediatly when pressing ctrl-c in terminal. Only in record_ros_ui GUI.
