Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How does CARLA server transmit simulation data through the TCP Socket to ROS? #706

Open
ansb5 opened this issue Oct 31, 2023 · 1 comment

Comments

@ansb5
Copy link

ansb5 commented Oct 31, 2023

I'm trying to understand deeply the communication architecture between CARLA and ROS and I cannot find much information about the TCP socket connection between these two parties.

I understand that in ROS the ROS-Bridge is launched in a node that obtains the simulation data from a TCP socket connection with CARLA server. Having this, I dont have clear how CARLA server transmits simulation data from the TCP connection. ROS-Bridge obtains the data in JSON format, but what module in CARLA server transmits this information? Is this information coming from the same Python API that is used to transmit data to CARLA client? Or is it another module? As i didn't install or configure anything in CARLA server to achieve this connection I dont know how does establish it.

If anyone knows the architecture I will be gratefoul for a reply.

@ansb5 ansb5 changed the title How does CARLA server transmit simulation data through the WebSocket? How does CARLA server transmit simulation data through the TCP Socket? Oct 31, 2023
@ansb5 ansb5 changed the title How does CARLA server transmit simulation data through the TCP Socket? How does CARLA server transmit simulation data through the TCP Socket to ROS? Nov 2, 2023
@Billthekidz
Copy link

I have limited time working with CARLA ros bridge.
It looks like the ros bridge uses nodes that communicate with CARLA server using CARLA's python API.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants