rosbridge_suite | Server Implementations of the rosbridge v2 Protocol | Robotics library

by RobotWebTools Python Version: 1.3.1 License: BSD-3-Clause

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | rosbridge_suite Summary

rosbridge_suite is a Python library typically used in Automation, Robotics applications. rosbridge_suite has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. However rosbridge_suite build file is not available. You can install using 'npm i ros2bridge' or download it from GitHub, npm.

rosbridge provides a JSON interface to ROS, allowing any client to send JSON to publish or subscribe to ROS topics, call ROS services, and more. rosbridge supports a variety of transport layers, including WebSockets and TCP. For information on the protocol itself, see the [rosbridge protocol specification] ROSBRIDGE_PROTOCOL.md). For full documentation, see [the ROS wiki] This project is released as part of the [Robot Web Tools] effort.

Support

Quality

Security

License

Reuse

Support

rosbridge_suite has a low active ecosystem.

It has 714 star(s) with 463 fork(s). There are 45 watchers for this library.

It had no major release in the last 6 months.

There are 38 open issues and 357 have been closed. On average issues are closed in 214 days. There are 17 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of rosbridge_suite is 1.3.1

Quality

rosbridge_suite has 0 bugs and 0 code smells.

Security

rosbridge_suite has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

rosbridge_suite code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

rosbridge_suite is licensed under the BSD-3-Clause License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

rosbridge_suite releases are not available. You will need to build from source code and install.

Deployable package is available in npm.

rosbridge_suite has no build file. You will be need to create the build yourself to build the component from source.

It has 6929 lines of code, 489 functions and 82 files.

It has high code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed rosbridge_suite and discovered the below as its top functions. This is intended to give you an instant insight into rosbridge_suite implemented functionality, and help decide if they suit your requirements.

Defragment a fragment
Handle incoming message
Deserialize message
Decode a base64 encoded string
Subscribe to a client
Update parameters
Return a TransitionHandler for this action
Handle a service advertisement
Cleanly shutdown the service
Unadvertise a service
Publish a message
Open the connection
Set a parameter on a node
Handle a request
Main thread
Gets the globals from the node
Called when a new subscriber is received
Prewrite a message
Transition the queue
Wait for incoming messages
Unsubscribe from all clients
Delete a parameter
Decorator to log exceptions
Called when a service fails
Create a service response
Get services for a given type

Get all kandi verified functions for this library.

rosbridge_suite Key Features

No Key Features are available at this moment for rosbridge_suite.

rosbridge_suite Examples and Code Snippets

No Code Snippets are available at this moment for rosbridge_suite.

Community Discussions

Trending Discussions on rosbridge_suite

Jupyter notebooks: Tornado pointing to incorrect path

Service Fabric Strategies for Bi-Directional Communication with External Devices

QUESTION

Jupyter notebooks: Tornado pointing to incorrect path

Asked 2019-Apr-15 at 16:39

I'm trying to run a Jupyter notebook. I installed Anaconda 5.3 with the Python 3.7 version. The notebook starts up, but the Kernel fails to run because it's pointing to another version of Tornado that I've installed for some of my ROS projects (output below). How do I ensure the Jupyter kernel is using Tornado installed in the Anaconda path?

...

ANSWER

Answered 2019-Apr-15 at 16:39

A little late, but answering my own question. PYTHONPATH was set for a bunch of other projects. Since conda doesn't set PYTHONPATH, running

Source https://stackoverflow.com/questions/52784178

QUESTION

Service Fabric Strategies for Bi-Directional Communication with External Devices

Asked 2018-Jul-16 at 12:06

My company is interested in using a stand-alone Service Fabric cluster to manage communications with robots. In our scenario, each robot would host its own rosbridge server, and our Service Fabric application would maintain WebSocket clients to each robot. I envision a stateful service partitioned along device ids which opens connections on startup. It should monitor connection health via heartbeats, pass messages from the robots to some protocol gateway service, and listen to other services for messages to pass to the robots.

I have not seen discussion of this style of external communications in the Service Fabric documentation - I cannot tell if this is because:

There are no special considerations for managing WebSockets (or any two-way network protocol) this way from Service Fabric. I've seen no discussion of restrictions and see no reason, conceptually, why I can't do this. I originally thought replication would be problematic (duplicate messages?), but since only one replica can be primary at any time this appears to be a non-issue.
Service Fabric is not well-suited to bi-directional communication with external devices

I would appreciate some guidance on whether this architecture is feasible. If not, discussion on why it won't work will be helpful. General discussion of limitations around bi-directional communication between Service Fabric services and external devices is welcome. I would prefer if we could keep discussion to stand-alone clusters - we have no plans to use Azure services at this time.

...

ANSWER

Answered 2018-Jul-16 at 07:21

I hope I understood everything right.

About the obstacles:

I think the major issue here is that bi-directional connection can be established between service replica and the robot.

This has two major problems:

Only primary replica has write access - i.e. only one replica would be able to modify state. This issue hence could be mitigated by creating a separate partition for each robot (but please remember that you can't change partition count after the service was created) or by creating a separate service instance for each robot (this would allow you to dynamically add or remove robots but would require additional logic related to service discoverability).
The replica can be shutdown (terminated), moved to another node (shutdown and start of new replica) or even demoted (the primary replica get's demoted to secondary and another secondary replica get's promoted to primary) by various reasons. So the service code and robot communication code should be able to handle this.

About WebSockets

This looks possible by implementing custom ICommunicationListener and other things using WebSockets.

Source https://stackoverflow.com/questions/51331357

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install rosbridge_suite

You can install using 'npm i ros2bridge' or download it from GitHub, npm.
You can use rosbridge_suite like any standard Python library. You will need to make sure that you have a development environment consisting of a Python distribution including header files, a compiler, pip, and git installed. Make sure that your pip, setuptools, and wheel are up to date. When using pip it is generally recommended to install packages in a virtual environment to avoid changes to the system.