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
  • Issues
  • #3

Closed
Open
Created Jul 27, 2020 by Nicholas Shindler@nicholasMaintainer

Add Line Sensor

currently lidar data is only published when a whole scan has been taken, determine if each reading can be published in real time. this would give an option to get scan data as it happens, rather than waiting for all the data to be collected and published in a point cloud.

To implement this, the probe that returns a single beam from the range finder must be found, and then the angle of the beam must be determined as well.

finally a new sensor class must be created and publish a LaserScan message in ROS.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking