Skip to content

Releases: Unity-Technologies/ROS-TCP-Connector

ROS-TCP-Connector v0.7.0

03 Feb 01:18
c27f00c
Compare
Choose a tag to compare

ros-tcp-connector package

Added

Added "Listen for TF Messages" to Settings

Enabled Android and IOS builds

Added Sonarqube scanner

Added more tests

Add support for cloud rendering

Added MessagePool to enable message reuse and reduce garbage collection

Can configure what direction is "north" for NED and ENU coordinates

Changed

CameraInfo.msg field names are different in ROS2

Bug fix - cope with tab character in a .msg file

Bug fix - no padding when serializing an empty array

Can publish messages from threads other than main

visualizations package

Upgrade Notes

Making the package version consistent with the ROS-TCP-Connector release tag to avoid confusion.

Added

Visualizations work with ROS services

ROS-TCP-Connector v0.6.0

04 Oct 17:29
7f05510
Compare
Choose a tag to compare
  • Add the Ros Tcp Connector assembly to support Universal Windows Platform

  • Added the CameraInfoGenerator that takes a Unity Camera and a provided HeaderMsg, generate a corresponding CameraInfoMsg, see:
    CameraInfo Generator

  • Added API to create TransformMsg using local frame of a transform in Unity

  • Added an optional pooling system for ros publishers

  • Implemented a queueing and latching system to mimic the ROS implementation in Unity

  • Collected the various service/publisher/subscriber tables into a single table of RosTopicState

  • Hud becomes a generic display platform to support visualizations

  • Unity service implementations can be async

  • Publishing a message to an unregistered topic will show an error.

  • Registering a service now requires both the request and response message type.

  • Fixed the issue when queuing a message fails if the type is unspecified in compile type.

  • Fixed and issue that Time.realtimeSinceStartup was being called on another thread when publishing from another Thread.

  • Added the missing SerializeTo function for DurationMsg

  • Allow switching protocol to ROS2 in different build targets (Standalone, WSA, etc.).

  • Fixed dotnet format

ROS-TCP-Connector v0.5.0

16 Jul 01:25
f7f669f
Compare
Choose a tag to compare
Pre-release

[0.5.0-preview] - 2021-07-15

Upgrade Notes

Update third party notices also

Known Issues

Added

Add the option to connect to ROS2. User can use a dropdown menu and choose ROS1 or ROS2 protocols to connect to the ROS side

Add badges to main README

Changed

Deprecated

Removed

Fixed

Fixed byte conversion method in the serialization process

ROS-TCP-Connector v0.4.0

01 Jun 20:55
1588c15
Compare
Choose a tag to compare
Pre-release

Note: the logs only reflect the changes from 0.3.0-preview

Upgrade Notes

RosConnection 2.0: maintain a single constant connection from Unity to the Endpoint. This is more efficient than opening one connection per message, and it eliminates a whole bunch of user issues caused by ROS being unable to connect to Unity due to firewalls, proxies, etc.

Known Issues

Added

Add a link to the Robotics forum, and add a config.yml to add a link in the Github Issues page

Add connection status lights to the HUD - blue if ok, bright blue if actively sending, red if there's a problem. Turning off "Connect on Startup" will allow to set the IP to connect

Add lint and test coverage reporting

Changed

Reduce character count for path to generated messages. The folder Runtime/MessageGeneration/PregeneratedMessages is moved to the parent directory and renamed Runtime/Messages

Deprecated

Removed

Fixed

Correct the namespace for the MDuration class