docs.unity3d.com
Search Results for

    Show / Hide Table of Contents

    Troubleshooting the ROS Endpoint Connector

    Diagnose and resolve common ROS Endpoint Connector connection and messaging problems.

    These issues can occur when you use a RosEndpointConnector to bridge a scene to a live Robot Operating System (ROS) 1 or ROS 2 environment, as described in Connect to a live ROS environment.

    No connection

    Symptoms

    The RosEndpointConnector doesn't connect to the ROS TCP Endpoint. No messages are published or received, and the connector reports that it isn't connected.

    Cause

    The ROS TCP Endpoint node isn't running, or the connector's Endpoint IP Address and Endpoint Port don't match the address and port the endpoint is listening on.

    Resolution

    To resolve a failed connection, follow these steps:

    1. Confirm the ROS TCP Endpoint node is running on the target machine.
    2. Verify that Endpoint IP Address and Endpoint Port on the RosEndpointConnector match the IP address and port the ROS TCP Endpoint node is using.
    3. Check that no firewall is blocking the TCP port between the two machines.

    Protocol mismatch warning

    Symptoms

    The connector logs a protocol mismatch warning shortly after connecting, and messages fail to serialize or deserialize correctly.

    Cause

    The Is Ros 2 setting on the RosEndpointConnector doesn't match the ROS version (ROS 1 or ROS 2) of the environment it's connecting to. ROS 1 and ROS 2 use different wire encodings.

    Resolution

    To resolve a protocol mismatch, follow these steps:

    1. Confirm which ROS version the ROS TCP Endpoint is running.
    2. Set Is Ros 2 on the RosEndpointConnector to match: enabled for ROS 2, disabled for ROS 1.

    Messages not arriving

    Symptoms

    A publisher or subscriber registers successfully, but expected messages never arrive on the topic.

    Cause

    ROS topic names are case-sensitive, and a small difference between the topic name used in the scene and the topic name used by the other ROS node results in two distinct topics.

    Resolution

    To resolve a missing message issue, follow these steps:

    1. Compare the topic name in your RegisterPublisher, Subscribe, or DefaultTopic call against the topic name used on the other end of the connection.
    2. Correct any difference in capitalization, spelling, or leading/trailing slashes.

    Reconnect loops

    Symptoms

    The RosEndpointConnector repeatedly disconnects and reconnects instead of maintaining a stable connection.

    Cause

    The connection has enough latency that reads exceed Network Timeout Seconds before a response arrives, so the connector treats the link as lost and reconnects.

    Resolution

    To resolve reconnect loops caused by high latency, increase Network Timeout Seconds on the RosEndpointConnector to a value that accommodates the link's round-trip time.

    Additional resources

    • ROS Endpoint Connector reference
    • Connect to a live ROS environment
    • Introduction to messaging
    • Set up publishers and subscribers workflow
    • Message types reference
    In This Article
    Back to top
    Copyright © 2026 Unity Technologies — Trademarks and terms of use
    • Legal
    • Privacy Policy
    • Cookie Policy
    • Do Not Sell or Share My Personal Information
    • Your Privacy Choices (Cookie Settings)