Fejemis bridge: Difference between revisions
(Created page with "Back to fejemis. ==Bridge overview== 700px The bridge combines different inputs from hardware sources to a single socket-based interface...") |
|||
Line 14: | Line 14: | ||
The ini-file can be a set of directed commands, e.g. calibration data or subscription of data from the data sources. | The ini-file can be a set of directed commands, e.g. calibration data or subscription of data from the data sources. | ||
All data items can be logged individually with a timestamp. | All data items can be logged individually with a timestamp. | ||
The client GUI is to help configure/calibrate the sensors and low-level control loops. |
Revision as of 15:50, 12 September 2022
Back to fejemis.
Bridge overview
The bridge combines different inputs from hardware sources to a single socket-based interface point. Selected interface points are made available as ROS messages and key commands can be received from ROS. The main input and output connections are to the Drive and Front Teensy boards, these connections are protected by a simple checksum, the ';99' part, to avoid false or half messages when powering up. All data items are single lines of text. These data items start with a key and optionally additional parameters. The data item has further a data source associated. Data items can be directed to a destination (data forward). A data item can be requested or updates to a data item can be subscribed. The ini-file can be a set of directed commands, e.g. calibration data or subscription of data from the data sources. All data items can be logged individually with a timestamp. The client GUI is to help configure/calibrate the sensors and low-level control loops.