raspimouse2 repository

Repository Summary

Checkout URI https://github.com/rt-net/raspimouse2.git
VCS Type git
VCS Version fix_for_foxy
Last Updated 2020-11-19
Dev Status DEVELOPED
CI status No Continuous Integration
Released UNRELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Packages

Name Version
raspimouse 1.0.1
raspimouse_msgs 1.0.1

README

Raspimouse Node

ROS 2 node for the Raspberry Pi Mouse.

raspimouse

Build Status

master branch

industrial_ci

Source Build Status on ROS2 Buildfarm

Bionic + Dashing (dashing-devel)

raspimouse raspimouse_msgs

Requirements

Installation

$ cd ~/ros2_ws/src
# Clone package
$ git clone https://github.com/rt-net/raspimouse2

# Install dependencies
$ rosdep install -r -y -i --from-paths .

# Build & Install
$ cd ~/ros2_ws
$ colcon build --symlink-install
$ source ~/ros2_ws/install/setup.bash

QuickStart

# Terminal 1
$ source ~/ros2_ws/install/setup.bash
$ ros2 run raspimouse raspimouse


# Terminal 2
$ source ~/ros2_ws/install/setup.bash
$ ros2 lifecycle set raspimouse configure

# Set buzzer frequency
$ ros2 topic pub -1 /buzzer std_msgs/msg/Int16 '{data: 1000}'
$ ros2 topic pub -1 /buzzer std_msgs/msg/Int16 '{data: 0}'

# or rotate motors
$ ros2 lifecycle set raspimouse activate
$ ros2 service call /motor_power std_srvs/SetBool '{data: true}'
$ ros2 topic pub -1 /cmd_vel geometry_msgs/Twist '{linear: {x: 0.05, y: 0, z: 0}, angular: {x: 0, y: 0, z: 0.05}}'
$ ros2 lifecycle set raspimouse deactivate

Node Description

This is a managed-lifecycle node. The node must be configured and activated after being launched before the robot can be used. If running the node manually, after launching the node execute the following command to configure it:

$ ros2 lifecycle set raspimouse configure

If configuration succeeds, execute the following command to activate the node:

$ ros2 lifecycle set raspimouse activate

The robot can now be controlled and sensor information will be published.

The node can be deactivated using the following command:

$ ros2 lifecycle set raspimouse deactivate

This will disable publishing sensor data and stop the motors.

When the node is active, motor functionality can be tested by turning on the motors and sending a velocity command.

$ ros2 service call /motor_power std_srvs/SetBool '{data: true}'
$ ros2 topic pub -1 /cmd_vel geometry_msgs/Twist '{linear: {x: 0.05, y: 0, z: 0}, angular: {x: 0, y: 0, z: 0.05}}'

Odometry information can be checked by echoing the odom topic.

$ ros2 topic echo /odom

Similarly other sensor information can also be viewed by echoing the relevant topic.

Topics

Subscribed

  • buzzer

Type: std_msgs/Int16

Used to control the buzzer. Provide a value in Hertz and the buzzer will emit that tone.

  • cmd_vel

Type: geometry_msgs/Twist

Controls the motors. Specify the forward and turning speeds of the robot.

  • leds

Type: raspimouse_msgs/Leds

Turns the four LEDs on the front of the robot on and off.

Published

  • light_sensors

Type: raspimouse_msgs/LightSensors

Provides the raw values from the light sensors on the front of the robot.

  • odom

Type: nav_msgs/Odometry

Provides odometry. If hardware pulse counters are available and the use_pulse_counters parameter is set to true, the odometry is calculated from the motor control pulse counts. Otherwise, the odometry is estimated based on the velocity commands given to the robot and elapsed time.

  • switches

Type: raspimouse_msgs/Switches

Provides the status of each of the three push switches on the side of the robot.

Services

  • motor_power

Type: std_srvs/SetBool

Call this service and pass true to enable the motors. Pass false to disable the motors.

Parameters

  • odometry_scale_left_wheel

Type: double

Default: 1.0

Use to adjust the odometry input from the left wheel (when using pulse counters to calculate odometry). This is used to account for slight differences in wheel diameter and wheel slip between the left and right wheels.

  • odometry_scale_right_wheel

Type: double

Default: 1.0

Use to adjust the odometry input from the right wheel (when using pulse counters to calculate odometry). This is used to account for slight differences in wheel diameter and wheel slip between the left and right wheels.

  • use_light_sensors

Type: boolean

Default: true

Enable or disable the light sensors on the front of the robot.

  • use_pulse_counters

Type: boolean

Default: false

Use hardware pulse counters as the odometry source. When set to true, hardware pulse counters will be used only if present.

License

This repository is licensed under the Apache 2.0, see LICENSE for details.

Contributors

Contributions are always welcome!

CONTRIBUTING

No CONTRIBUTING.md found.

Repository Summary

Checkout URI https://github.com/rt-net/raspimouse2.git
VCS Type git
VCS Version dashing-devel
Last Updated 2020-06-10
Dev Status DEVELOPED
CI status No Continuous Integration
Released RELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Packages

Name Version
raspimouse 1.0.1
raspimouse_msgs 1.0.1

README

Raspimouse Node

industrial_ci

ROS 2 node for the Raspberry Pi Mouse.

raspimouse

Requirements

Installation

$ cd ~/ros2_ws/src
# Clone package
$ git clone https://github.com/rt-net/raspimouse2

# Install dependencies
$ rosdep install -r -y -i --from-paths .

# Build & Install
$ cd ~/ros2_ws
$ colcon build --symlink-install
$ source ~/ros2_ws/install/setup.bash

QuickStart

# Terminal 1
$ source ~/ros2_ws/install/setup.bash
$ ros2 run raspimouse raspimouse


# Terminal 2
$ source ~/ros2_ws/install/setup.bash
$ ros2 lifecycle set raspimouse configure

# Set buzzer frequency
$ ros2 topic pub -1 /buzzer std_msgs/msg/Int16 '{data: 1000}'
$ ros2 topic pub -1 /buzzer std_msgs/msg/Int16 '{data: 0}'

# or rotate motors
$ ros2 lifecycle set raspimouse activate
$ ros2 service call /motor_power std_srvs/SetBool '{data: true}'
$ ros2 topic pub -1 /cmd_vel geometry_msgs/Twist '{linear: {x: 0.05, y: 0, z: 0}, angular: {x: 0, y: 0, z: 0.05}}'
$ ros2 lifecycle set raspimouse deactivate

Node Description

This is a managed-lifecycle node. The node must be configured and activated after being launched before the robot can be used. If running the node manually, after launching the node execute the following command to configure it:

$ ros2 lifecycle set raspimouse configure

If configuration succeeds, execute the following command to activate the node:

$ ros2 lifecycle set raspimouse activate

The robot can now be controlled and sensor information will be published.

The node can be deactivated using the following command:

$ ros2 lifecycle set raspimouse deactivate

This will disable publishing sensor data and stop the motors.

When the node is active, motor functionality can be tested by turning on the motors and sending a velocity command.

$ ros2 service call /motor_power std_srvs/SetBool '{data: true}'
$ ros2 topic pub -1 /cmd_vel geometry_msgs/Twist '{linear: {x: 0.05, y: 0, z: 0}, angular: {x: 0, y: 0, z: 0.05}}'

Odometry information can be checked by echoing the odom topic.

$ ros2 topic echo /odom

Similarly other sensor information can also be viewed by echoing the relevant topic.

Topics

Subscribed

  • buzzer

Type: std_msgs/Int16

Used to control the buzzer. Provide a value in Hertz and the buzzer will emit that tone.

  • cmd_vel

Type: geometry_msgs/Twist

Controls the motors. Specify the forward and turning speeds of the robot.

  • leds

Type: raspimouse_msgs/Leds

Turns the four LEDs on the front of the robot on and off.

Published

  • light_sensors

Type: raspimouse_msgs/LightSensors

Provides the raw values from the light sensors on the front of the robot.

  • odom

Type: nav_msgs/Odometry

Provides odometry. If hardware pulse counters are available and the use_pulse_counters parameter is set to true, the odometry is calculated from the motor control pulse counts. Otherwise, the odometry is estimated based on the velocity commands given to the robot and elapsed time.

  • switches

Type: raspimouse_msgs/Switches

Provides the status of each of the three push switches on the side of the robot.

Services

  • motor_power

Type: std_srvs/SetBool

Call this service and pass true to enable the motors. Pass false to disable the motors.

Parameters

  • odometry_scale_left_wheel

Type: double

Default: 1.0

Use to adjust the odometry input from the left wheel (when using pulse counters to calculate odometry). This is used to account for slight differences in wheel diameter and wheel slip between the left and right wheels.

  • odometry_scale_right_wheel

Type: double

Default: 1.0

Use to adjust the odometry input from the right wheel (when using pulse counters to calculate odometry). This is used to account for slight differences in wheel diameter and wheel slip between the left and right wheels.

  • use_light_sensors

Type: boolean

Default: true

Enable or disable the light sensors on the front of the robot.

  • use_pulse_counters

Type: boolean

Default: false

Use hardware pulse counters as the odometry source. When set to true, hardware pulse counters will be used only if present.

License

This repository is licensed under the Apache 2.0, see LICENSE for details.

Contributors

Contributions are always welcome!

CONTRIBUTING

No CONTRIBUTING.md found.