Closed zdf-bot closed 1 month ago
Robotics010
commented
1 month ago Hey @zdf-bot, could you add more details of your setup? It helps to find out the root cause of your error.
Is it your first setup or was it working before? What docker image do you use? What autoware tag do you use? Do you have GPU? What cuda/nvidia drivers do you have? Did you have perception engines generated successfully? How this error can be reproduced?
zdf-bot
commented
1 month ago Thank you @Robotics010 , it works only once when I increase the space of swap from 2G to 32G(memory is 32G). Now it's all failed, the error information is the same as before. I don't know whether perception engines generated successfully, The install step I follow the video in Youtube. The launch stage, I follow the steps in README.md, CARLA->CARLABridge->Autoware
Follows are details of setup: bruce@bruce:~$ docker images REPOSITORY TAG IMAGE ID CREATED SIZE
zdf-bot
commented
1 month ago @Robotics010 , wait for a long time, it works, I do nothing during the waiting time.
Robotics010
commented
1 month ago @Robotics010 , wait for a long time, it works, I do nothing during the waiting time.
I can assume your perception engines were not generated. They are generated when you launch perception for the first time. Next times it is not needed to wait until engines are generated.
zdf-bot
commented
1 month ago @Robotics010 ，how to know that perception engines are generated? Or how to generate perception engines ?
Robotics010
commented
1 month ago @Robotics010 ，how to know that perception engines are generated? Or how to generate perception engines ?
well, it's out of scope of the bridge responsibility, I would recommend to start reading perception related docs, but usually you can find the data folder path in the corresponding launch file and you can go there and check if for example $(env HOME)/autoware_data/tensorrt_yolo/yolov3.engine is there
another way of how I check that easily is that:
zdf-bot
commented
1 month ago root@bruce:~/autoware_data/tensorrt_yolo# ls coco.names yolov4-tiny.onnx yolov5l.onnx yolov5s.onnx yolov3.onnx yolov4.onnx yolov5m.onnx yolov5x.onnx
there's no yolov3.engine
zdf-bot
commented
1 month ago @Robotics010 , I only installed GPU driver in my computer, should I install CUDA Toolkit?
TUMGEKA
commented
1 month ago Another options is to force the auto mode as described here: https://tier4.github.io/AWSIM/GettingStarted/QuickStartDemo/
Using the following command: ros2 topic pub /autoware/engage autoware_auto_vehicle_msgs/msg/Engage '{engage: True}' -1
zdf-bot
commented
1 month ago Thanks @TUMGEKA
Error Information: ... [system_error_monitor-22] [ERROR] [1717456182.973000596] [system.system_error_monitor]: vehicle_state_report msg is timeout... [component_container_mt-76] [INFO] [1717456184.590174946] [default_ad_api.node.operation_mode]: perception component state is unhealthy. Autonomous is not available. [component_container_mt-70] [WARN] [1717456189.312649806] [planning.scenario_planning.lane_driving.behavior_planning.behavior_velocity_planner.traffic_light_module]: Failed to calculate stop point and insert index [component_container_mt-70] [WARN] [1717456189.312701596] [planning.scenario_planning.lane_driving.behavior_planning.behavior_velocity_planner.traffic_light_module]: the traffic signal data associated with regulatory element id is not received [component_container_mt-76] [INFO] [1717456190.375389685] [default_ad_api.node.operation_mode]: perception component state is unhealthy. Autonomous is not available. [system_error_monitor-22] [ERROR] [1717456192.562001896] [system.system_error_monitor]: vehicle_state_report msg is timeout... [component_container_mt-76] [INFO] [1717456196.004920461] [default_ad_api.node.operation_mode]: perception component state is unhealthy. Autonomous is not available. [component_container_mt-70] [WARN] [1717456198.794032538] [planning.scenario_planning.lane_driving.behavior_planning.behavior_velocity_planner.traffic_light_module]: Failed to calculate stop point and insert index [component_container_mt-70] [WARN] [1717456198.794093723] [planning.scenario_planning.lane_driving.behavior_planning.behavior_velocity_planner.traffic_light_module]: the traffic signal data associated with regulatory element id is not received [component_container_mt-76] [INFO] [1717456201.759390581] [default_ad_api.node.operation_mode]: perception component state is unhealthy. Autonomous is not available. [system_error_monitor-22] [ERROR] [1717456202.042719076] [system.system_error_monitor]: vehicle_state_report msg is timeout... [component_container_mt-76] [INFO] [1717456207.499882634] [default_ad_api.node.operation_mode]: perception component state is unhealthy. Autonomous is not available. [component_container_mt-70] [WARN] [1717456208.344776105] [planning.scenario_planning.lane_driving.behavior_planning.behavior_velocity_planner.traffic_light_module]: Failed to calculate stop point and insert index [component_container_mt-70] [WARN] [1717456208.344850717] [planning.scenario_planning.lane_driving.behavior_planning.behavior_velocity_planner.traffic_light_module]: the traffic signal data associated with regulatory element id is not received [system_error_monitor-22] [ERROR] [1717456211.634117040] [system.system_error_monitor]: vehicle_state_report msg is timeout... [component_container_mt-76] [INFO] [1717456213.284798141] [default_ad_api.node.operation_mode]: perception component state is unhealthy. Autonomous is not available. ...