-
Notifications
You must be signed in to change notification settings - Fork 9k
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
Running openpilot in Carla, manual control and model inference is working, but control is not #27743
Comments
Hello, I am also experiencing the same issue. OS VersionUbuntu server 20.04 LTS openpilot version or commitAdditional infoI also installed libzmq from source. |
I have the same problem. Does anyone have more suggestions of what I can do to understand the problem or other things to test? |
I have the same problem, I can manual control the car, but press 1 ,always show "OpenPilot Unavailable press set to engage" |
I finally got some some time to solve it. I write it down, hope it helpful to others. After reading a lot code but still fail to figure out the state machine, the test in https://github.com/commaai/openpilot/blob/master/tools/sim/tests/test_carla_integration.py stands up. The failure in this test help me find two issues preventing the openpilot to engage:
right now, I can run close-loop openpilot in Carla. |
Hi, I've tried your solution and it seems not working for me. May I see your second terminal where you run your ./launch_openpilot.sh? Because it seems the modeld keeps crashing on my part. Did your modeld turns out red as well? |
I fixed model inference by following #23666 (comment) to install libzmq. As a result, the
|
Hi, thank you for the reply. Yes, I've tried that and my modeld is not crashing anymore (even though it do actually crash sometimes, depends on my luck but better than before). However, then my simulator shows "Vehicle Parameter Identification Failed" and I solve it using this #27282 Hope it helps anyone who is facing the same issue. |
I also installed libzmq from source, which fixed the modeld problem. I'm still stuck at the Openpilot Unavailable problem however. The suggestion by @dvorak0 did not work, and I keep getting Openpilot unavailable message as soon as I press "1". Interestingly, when I run it using the --joystick option and I press the square button on my steering wheel, the car starts accelerating, and it correctly steers itself halfway through the first corner. Then, I get the error "Vehicle Parameter Identification Failed". Also, the rest of the steering wheel controls does not work. |
If the error is "Vehicle Parameter Identification Failed", try this solution #27282. Then, to engage the openpilot, make sure that "Disengage with Pedal" on the OpenPilot UI toggle option is enabled. You also need to press button '1' and '2' alternately for few times to engage the OpenPilot (not just button '1' alone). |
I also encounter a similar problem. When I use --joystick option, it is able to turn on and off the cruise mode of openpilot through the buttons of my steering wheel Logitech g29. But the cruise mode seems not very effective, the vehicle accelerate from the starting point, begin to turn right and hit a wall. In addition, the steering ,throttle and brake function of my steering wheel cannot be used when i exit the cruise mode, and I am sure these functions perform well in the jstest-gtk driver. |
Check out our new simulator, MetaDrive. It works a lot better. |
Describe the bug
I run openpilot with carla simulation, and end up with openpilot not able to control the car.
start_carla.sh
launch_openpilot.sh
bridge.py --dual_camera
w
for a few times. when the speed reachs 40km/s, press1
for a few times. expect to see openpilot engaged and control the car.Thanks for help.
OS Version
run everything inside docker(with ubuntu_setup.sh setup)
openpilot version or commit
3555a08
Additional info
I installed the libzmq from source, otherwise the onnx_runner will crash.
I also tried pressing
1
when the car is still, and get the same results(showing openpilot unavailable).The text was updated successfully, but these errors were encountered: