Home | Trees | Indices | Help |
---|
|
object --+ | Master
API for interacting with the ROS master. Although the Master is relatively simple to interact with using the XMLRPC API, this abstraction layer provides protection against future updates. It also provides a streamlined API with builtin return code checking and caller_id passing.
Instance Methods | |||
|
|||
|
|||
int |
|
||
int |
|
||
XMLRPCLegalValue |
|
||
str |
|
||
XMLRPCLegalValue |
|
||
int |
|
||
[int, str, bool] |
|
||
[int, str, [str]] |
|
||
int |
|
||
str |
|
||
int |
|
||
|
|||
(int, str, int) |
|
||
(int, str, list(str)) |
|
||
(int, str, int) |
|
||
[str] |
|
||
int |
|
||
str |
|
||
[[str, str],] |
|
||
(int, str, [[str,str]] ) |
|
||
[[str,[str]], [str,[str]], [str,[str]]] |
|
||
Inherited from |
Properties | |
Inherited from |
Method Details |
:param caller_id: name of node to use in calls to master, ``str`` :param master_uri: (optional) override default ROS master URI, ``str`` :raises: :exc:`ValueError` If ROS master uri not set properly
|
Check if Master is online. NOTE: this is not part of the actual Master API. This is a convenience function.
|
Parameter Server: delete parameter
|
Parameter Server: set parameter. NOTE: if value is a dictionary it will be treated as a parameter tree, where key is the parameter namespace. For example:: {'x':1,'y':2,'sub':{'z':3}} will set key/x=1, key/y=2, and key/sub/z=3. Furthermore, it will replace all existing parameters in the key parameter namespace with the parameters in value. You must set parameters individually if you wish to perform a union update.
|
Retrieve parameter value from server.
|
Search for parameter key on parameter server. Search starts in caller's namespace and proceeds upwards through parent namespaces until Parameter Server finds a matching key. searchParam's behavior is to search for the first partial match. For example, imagine that there are two 'robot_description' parameters: /robot_description /robot_description/arm /robot_description/base /pr2/robot_description /pr2/robot_description/base If I start in the namespace /pr2/foo and search for 'robot_description', searchParam will match /pr2/robot_description. If I search for 'robot_description/arm' it will return /pr2/robot_description/arm, even though that parameter does not exist (yet).
|
Retrieve parameter value from server and subscribe to updates to that param. See paramUpdate() in the Node API.
|
Retrieve parameter value from server and subscribe to updates to that param. See paramUpdate() in the Node API.
|
Check if parameter is stored on server.
|
Get list of all parameter names stored on this server. This does not adjust parameter names for caller's scope.
|
Get the PID of this server
|
Get the URI of this Master
|
Register the caller as a provider of the specified service.
|
Lookup all provider of a particular service.
|
Unregister the caller as a provider of the specified service.
|
Subscribe the caller to the specified topic. In addition to receiving a list of current publishers, the subscriber will also receive notifications of new publishers via the publisherUpdate API.
|
Unregister the caller as a publisher of the topic.
|
Register the caller as a publisher the topic.
|
Unregister the caller as a publisher of the topic.
|
Get the XML-RPC URI of the node with the associated name/caller_id. This API is for looking information about publishers and subscribers. Use lookupService instead to lookup ROS-RPC URIs.
|
Get list of topics that can be subscribed to. This does not return topics that have no publishers. See getSystemState() to get more comprehensive list.
|
Retrieve list topic names and their types. New in ROS 1.2.
|
Retrieve list representation of system state (i.e. publishers, subscribers, and services).
|
Home | Trees | Indices | Help |
---|
Generated by Epydoc 3.0.1 on Tue Mar 7 03:44:33 2017 | http://epydoc.sourceforge.net |