Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
H harvest-automation
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 4
    • Issues 4
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Henrik Andreasson
  • harvest-automation
  • Wiki
  • client

client · Changes

Page history
Update client authored Jul 30, 2020 by Nicholas Shindler's avatar Nicholas Shindler
Hide whitespace changes
Inline Side-by-side
Showing with 1 addition and 1 deletion
+1 -1
  • client.md client.md +1 -1
  • No files found.
client.md
View page @ ef36e3de
...@@ -8,4 +8,4 @@ To send a message to the robot data is taken in by the client as a probe id and ...@@ -8,4 +8,4 @@ To send a message to the robot data is taken in by the client as a probe id and
## Reading from the robot ## Reading from the robot
Data from the robot can be captured by the *Listener* which is a *Thread* child class. And probes that have been enabled will have their data sent by the server to the client on every broadcast interval. The base client class will read that data in and add it to a message queue, unless it is a debug message or a probe message. probe messages are added to a buffer and can be read out at a later stage. In the **hv_client** the probe messages are pushed to the data storage objects in the corresponding `Reader` classes that will the publish the data to ROS topics. Data from the robot can be captured by the *Listener* which is a *Thread* child class. And probes that have been enabled will have their data sent by the server to the client on every broadcast interval. The base client class will read that data in and add it to a message queue, unless it is a debug message or a probe message. probe messages are added to a buffer and can be read out at a later stage. In the **hv_client** the probe messages are pushed to the data storage objects in the corresponding [Reader](reader) classes that will the publish the data to ROS topics.
\ No newline at end of file \ No newline at end of file
Clone repository
  • client
  • Home
  • probes
  • reader
  • ros services
  • setup
  • writer