Closed batuhanbeytekin closed 1 month ago
I've tried to create same issue with the steps you've provided @batuhanbeytekin. NPC's can be spawned from the Autoware side without any problems:
rti -v /simulation/dummy_perception_publisher/object_info
Type: dummy_perception_publisher/msg/Object
Publisher count: 4
Node name: rviz2
Node namespace: /
Topic type: dummy_perception_publisher/msg/Object
Endpoint type: PUBLISHER
GID: 01.10.1b.bb.ba.5e.44.6e.92.52.ef.14.00.00.a1.03.00.00.00.00.00.00.00.00
QoS profile:
Reliability: RELIABLE
History (Depth): KEEP_LAST (1)
Durability: VOLATILE
Lifespan: Infinite
Deadline: Infinite
Liveliness: AUTOMATIC
Liveliness lease duration: Infinite
Node name: rviz2
Node namespace: /
Topic type: dummy_perception_publisher/msg/Object
Endpoint type: PUBLISHER
GID: 01.10.1b.bb.ba.5e.44.6e.92.52.ef.14.00.00.a3.03.00.00.00.00.00.00.00.00
QoS profile:
Reliability: RELIABLE
History (Depth): KEEP_LAST (1)
Durability: VOLATILE
Lifespan: Infinite
Deadline: Infinite
Liveliness: AUTOMATIC
Liveliness lease duration: Infinite
Node name: rviz2
Node namespace: /
Topic type: dummy_perception_publisher/msg/Object
Endpoint type: PUBLISHER
GID: 01.10.1b.bb.ba.5e.44.6e.92.52.ef.14.00.00.a5.03.00.00.00.00.00.00.00.00
QoS profile:
Reliability: RELIABLE
History (Depth): KEEP_LAST (1)
Durability: VOLATILE
Lifespan: Infinite
Deadline: Infinite
Liveliness: AUTOMATIC
Liveliness lease duration: Infinite
Node name: rviz2
Node namespace: /
Topic type: dummy_perception_publisher/msg/Object
Endpoint type: PUBLISHER
GID: 01.10.1b.bb.ba.5e.44.6e.92.52.ef.14.00.00.a8.03.00.00.00.00.00.00.00.00
QoS profile:
Reliability: RELIABLE
History (Depth): KEEP_LAST (1)
Durability: VOLATILE
Lifespan: Infinite
Deadline: Infinite
Liveliness: AUTOMATIC
Liveliness lease duration: Infinite
Subscription count: 1
Node name: AWSIM
Node namespace: /
Topic type: dummy_perception_publisher/msg/Object
Endpoint type: SUBSCRIPTION
GID: 01.10.a0.51.3c.c9.97.20.d3.1d.ff.2c.00.00.0e.04.00.00.00.00.00.00.00.00
QoS profile:
Reliability: RELIABLE
History (Depth): KEEP_LAST (1)
Durability: VOLATILE
Lifespan: Infinite
Deadline: Infinite
Liveliness: AUTOMATIC
Liveliness lease duration: Infinite
When I tested with main Autoware and awsim_labs_v1.4.2, I encountered the same issue. The message type used for dummy vehicles has changed with the https://github.com/autowarefoundation/autoware.universe/issues/8704 PR merged into Autoware.universe, which is why we are facing this problem. The message types will be updated and fixed. Thank you for issue! @batuhanbeytekin
It seems like my Autoware was not up to date, sorry :pray:
@batuhanbeytekin Can you test this case with the latest release? It should be okay now.
@batuhanbeytekin Can you test this case with the latest release? It should be okay now.
I tested again with the latest version and it seems the problem is solved. Thanks for your effort.
Description
I'm currently using AWSIM v1.2.1 with e2e_simulator and encountered an issue when trying to spawn a dummy car using the 2D Dummy Car button. The car does not spawn, and when I try to echo the topic /simulation/dummy_perception_publisher/object_info, I receive the following error:
When I run
ros2 topic info -v
on this topic, I get the following output:It seems that there is a conflict between the message types being published to
/simulation/dummy_perception_publisher/object_info
, as bothdummy_perception_publisher/msg/Object
andtier4_simulation_msgs/msg/DummyObject
are being used.Steps to reproduce
awsim_labs_v1.2.1.zip
file.cd path/to/awsim_labs_v1.2.1
./awsim_labs.x86_64
ros2 launch autoware_launch e2e_simulator.launch.xml vehicle_model:=sample_vehicle sensor_model:=awsim_labs_sensor_kit map_path:=/path/to/map/autoware_map/nishishinjuku_autoware_map launch_vehicle_interface:=true
/simulation/dummy_perception_publisher/object_info
.Expected behavior
A dummy car should spawn in the simulation without any issue.
Actual behavior
The car does not spawn, and the topic contains conflicting message types, preventing proper simulation behavior.
Is there a fix for this topic conflict, or is there any workaround?