About | Support | answers.ros.org	Search:

rososc: diagnostics_handler | osc_bridge | pytouchosc | teleop_handler | touchosc_bridge | touchosc_msgs

Package Summary

osc_bridge contains the core functionality of ROS-to-OSC communication.

• Author: Michael Carroll
• License: BSD
• Repository: au-automow
• Source: git https://github.com/Auburn-Automow/rososc.git

Overview

osc_bridge provides the core functionality of communicating with both the OSC protocol and the ROS system.

touchosc_bridge extends this node, so most users will not need to interact with osc_bridge.

osc_bridge may be used to communicate with other OSC-compatible hardware and software via both TCP and UDP, but these features remain largely untested.

Node API

Parameters

~osc_name (string, default: Test)

• Name of the node as it will appear in the Bonjour/Zeroconf system.

~port (int, default: 8000)

• Port that the OSC server will listen on

~regtype (string, default: _osc._udp)

• Bonjour registration type of the OSC server

~print_fallback (bool, default: False)

• setting the parameter to "True" will cause unhandled incoming OSC messages to be printed to the console.