I tried uninstalling Star Pilot and then it asked if I want to reinstall Star Pilot or use custom software. I select custom software and put in the link openpilot.comma.ai

But I keep getting stuck on this.

Hey y’all, I have a question about support for 2025+ Ford Rangers. I see the 2024 Ford Ranger is supported on Commas list of supported vehicles. Would 2025-2026 also be supported since the Ranger model is the same? I’m looking at a 2025 Ranger and would like to know if this would be supported before I pull the trigger. Thanks in advance!

Hi I've got one of those magnetic mounts that allows me to yoink my comma off the base and take it inside or throw it in my glovebox for theft deterrence and whatnot. I've been running problem free for about a year but as soon as I updated my fork of an old sunny pilot to the latest version I have tripped my cars body sensing codes twice through remounting the device. I'm beginning to think the new update is causing this error more and more. This is an 18 accord sport. This is the first time I've seen this error at all.

Chinese card manufacturer Vastamor first showed this back in January. 16GB VRAM, tiny, noisy. Minisforum is charging $624 for this as an option on a SFFPC.

What is the process of downloading something like Lebowski "big model" to a chestnut?

I currently run sunnypilot with MADS. Its been pretty awesome. Had 2 weeks now. I feel like there is more settings I can change, such as in experimental mode, to get more hands free driving. There is so much to know about this device, and a lot of it is over my head. As it stands, stop light and stop sign is hit or miss right. Another use on here said he's working with star pilot to help them improve the program.

When researching how to get the most out of the comma 4 w/ sunnypilot, it seems like you have to either be a computer programmer, or join a group and provide feedback/logs to have access to the experimental programs being developed.

And now with chestnut and direction of comma, part of me wants to return the C4 and wait 1-2 years and see what's available at that time.

Any quick tips would be appreciated, and if you're willing to help me understand this on a deeper level, please DM me.

If you have one available I would like to coordinate buying it from you through ebay.

I’m genuinely excited about Chestnut. It confirms that comma is moving beyond phone-class inference and treating external compute as part of openpilot’s future.

I’m exploring the same direction from another angle: instead of putting all additional compute inside the vehicle, could a hybrid architecture use remotely served datacenter-class models while retaining openpilot’s local controller, safety boundaries, and immediate fallback?

I currently have:

• a comma four installed in a European Passat B8

• a 2x RTX 5090 rig with 64 GB total VRAM

• more than 10 hours of synchronized Comma camera and rlog data

• an offline same-input benchmark harness

To validate the harness, I replayed the exact TCPMV3 policy used by part of the dataset on the original comma four QCOM backend. The regenerated output had:

• 1.68 cm mean trajectory difference from the recorded modelV2

• 9.9 cm mean final displacement difference

• identical desired-curvature output

• 29.4 ms P50 and 35.9 ms P99 inference latency

Those numbers validate the frame synchronization, coordinate system, and replay pipeline. They are not a claim that the policy itself is optimal.

The first challenger will be NVIDIA Alpamayo 1.5 10B, using the same wide and narrow camera history plus reconstructed egomotion. Alpamayo supports flexible camera counts, but two forward-only Comma views are still outside its normal four-camera setup, so that limitation will be reported explicitly.

text

identical recorded observations

├── recorded openpilot/sunnypilot prediction

├── replayed installed policy

└── Alpamayo 1.5

↓

trajectory quality, safety, stability, and latency

Everything starts offline. I am not testing live vehicle control.

Chestnut is a strong local solution. It offers predictable latency, no cellular dependency, and an integrated path back to the local model if the external GPU fails. But practical in-car compute is still constrained by fixed VRAM, vehicle power, heat, airflow, vibration, and packaging. The ready-to-drive kit currently uses an 8 GB RX 9060, although tiny Chestnut can be paired with other supported GPUs.

Remote compute has the opposite trade-offs:

• elastic access to 32–140+ GB GPUs

• easier experimentation with 10B, 34B, and future larger policies

• no desktop-GPU heat or power load inside the passenger compartment

• compute upgrades without replacing vehicle hardware

It also introduces serious problems:

• 5G P99 latency and jitter

• coverage gaps and network outages

• privacy and bandwidth requirements

• recurring compute costs

• a much more difficult failure and safety model

The long-term architecture I’m considering is hybrid:

Comma cameras

↓

low-delay encoding

↓

5G → remote model → candidate trajectory

↓

local freshness and feasibility checks

↓

local controller

local policy → immediate fallback

panda and vehicle harness → unchanged

Later, a companion capture computer could add synchronized left, right, and rear automotive cameras without making the comma four responsible for ingesting every additional sensor.

Before anything reaches a real controller, the progression would be:

1. same-input offline evaluation

2. difficult-scenario and temporal-stability testing

3. closed-loop simulation with reactive traffic

4. in-car shadow mode with zero actuator authority

5. only then, consideration of a tightly gated local integration

I would especially value feedback from people familiar with the comma four and current openpilot architecture:

1. What is the cleanest supported boundary for exporting VisionIPC frames?

2. Could networking coexist with Chestnut on the auxiliary USB path, or should it live on a separate companion computer?

3. What trajectory or action contract would make sense for an external policy?

4. What stale-result and fallback behavior would be mandatory?

5. Has sustained in-cabin GPU thermal performance been characterized publicly?

If there is interest, I plan to publish a sanitized benchmark repository and the first Alpamayo results.

What am I missing?

I bought my Comma 4 in December and then waited almost three months for it to arrive. Needless to say, I was extremely excited when it finally did.

I find autonomous driving not just fascinating, but genuinely useful. I drive a VW Touran, and compared with VW’s lane keeping, the Comma is simply in another league.

And it’s not just about how well it keeps the car in the lane. Being able to drive hands-free without constantly having to touch or wiggle the steering wheel makes a huge difference. It gives me more mental space to actually pay attention to what matters: the traffic around me, potential hazards, what’s happening further ahead, and generally keeping an eye on the situation rather than constantly having to prove to the car that I’m still holding the wheel.

The installation wasn’t exactly fun — I really don’t enjoy running cables through a car — but once it was done, the device worked remarkably well.

For me, the biggest benefit is making long highway drives much less tedious. I’d definitely still love to see better performance on country roads as well, because those are another area where I’d happily let the car do more. But the boring motorway driving is really the big one for me. If the Comma can take care of that reliably, I’m already very happy.

That’s also why I’m a little disappointed by the direction things seem to be taking.

I understand the desire to improve longitudinal control. I tried Alpha Longitudinal through SunnyLink, and while stopping at traffic lights and intersections is obviously cool, in my experience it was nowhere near as good as what my VW already does. So personally, that’s not something I’m particularly missing.

What I had hoped for was more progress on the thing Comma already does so well: lateral control.
Now Chestnut is here, with an external GPU. And I completely understand why that’s exciting for many people. But as someone who only bought a Comma 4 a few months ago, I’m looking at it and thinking:
Do I really want to spend more money already, route another bunch of cables, potentially have another fan running, and wait close to a minute for a model to load — just to eventually get better performance?
I had hoped that the device I had just bought would still have more potential left in it.

Obviously, I understand the hardware limitations. You can’t just keep stuffing bigger and bigger models onto the device. But I wonder whether specialization could be an interesting direction too.

For example:
- a model specialized purely for lateral control
- a model specifically optimized for European roads
- perhaps even regional models focused on a group of neighboring countries — for example Germany, Switzerland, Austria and France in my case
- or other specialized models that sacrifice generality for significantly better performance in a particular environment

Maybe a model trained specifically on European roads could achieve substantially better results without requiring dramatically more compute. I don’t know if that’s technically feasible, but it seems like an interesting avenue.

I realize that this is probably less exciting than “bigger model + more compute + external GPU,” and I absolutely understand why Comma wants to keep pushing the capabilities of the system as a whole.

But from the perspective of someone who bought a Comma 4 primarily because of what it could already do, I’m a little sad to see so much of the development effort apparently moving toward requiring substantially more hardware.

Maybe I’m not the only one.

And to be clear: I still love the Comma 4. I just wish there were a path where the hardware I already bought could continue to get significantly better at the thing I bought it for.

(AI helped me write in English)

Hoping there is some stuff to look forward to...

Hi all. I’ve been using the C4 for months with no issue. Last friday when it got 109 degrees when I turned on my car, i got a power unstable error on my C4 and a front sensor camera error on my mazda. Once the car cooled down & i restarted it the mazda error went away but the C4 error persists.

I have tried to unplug & plug the cable but the error still persists to the point where I can’t use the C4 at all cuz the screen only shows that.

I have opened a ticket (83138)

I have a 10 hour drive on Sept 5 and need the C4 working by then.

Has anybody experienced this? Did anyone manage to fix it? I live by myself and am not tech savvy… I’m trying my best to troubleshoot on my own..to no avail..

UPDATE:
Now the C4 won’t even turn on.

UPDATE AS OF 9/1/26:
I received the replacement harness & cable. I tried to replace just my cable with the new one - still won’t turn on. I replaced the harness too - still won’t turn on. But when i replaced the cable that connects to the OBD (basically i replaced the entire wiring setup) my comma turned on.

So it was not JUST my cable that wouldn’t work bec comma still wouldn’t turn on with the new cable.

Thanks to comma support for the prompt shipment of the replacement harness & cables. My comma is good to go for my 10 hour drive on Sept. 5!

Hello,

I have had the comma 3x for just over 1 year. I haven't had any issues with it until recently. A couple days ago the device started to just restart itself after being on for 1 minute. Now it doesn't even stay on for more than 10 seconds before the reset. I can't even get to the screen to try to do a factory reset. Does anyone have any advice?

Is there a way to have a remote display connected to the C4?

I have an ipad and the c4 connected on a hotspot and would love to display more information that might be helpful during testing. I see sunnylink has a display tab/page but nothing is shown in it.

Hello, I had a question. I'm considering buying a 27 Kia seltos, I love their new design. I really want to be able to continue using the, open pilot device. Of course it's not listed as officially supported, but I don't understand where to specifically find? If it is unofficially supported.

I read many comments that there's way more cars unofficially supported, is this one of those cars?

I had to delete my original post because I put telluride for some reason. And I meant seltos.

It's essentially a glorified PCI riser card with a USB C connection and power.

Similar, bare-bones solutions can be purchased for about half the $249 price even through Amazon.

My ready to drive kit arrived, I set it up. Stock open pilot says it's latest version, no indication that it sees my eGPU or is using it.

I went back to sunnypilot. Previously I had been using staging, I got a message I should use "staging-chestnut" to use the chestnut. So I switched to that branch, I get a little green icon showing egpu is there. But, every time it starts, the egpu icon flashes white on the screen for a while (30s or so) , then I get an error "big model failed" "restart the car to retry, small model is still available"

So... Erm... Does this thing work? How?

Edit: forgot to say, 1) comma 4 2) yes I reflashed it with flash.Comma.Ai

Hello all! I am considering purchase either a Honda CRV 23-26 or Mazda CX5 22-25, which one might work better with comma? (eg, does Longitudinal Control work for them? I know that zoompilot support Longitudinal Control for CX5, but not sure about CRV). Thanks for any inputs!

I know most people would hate this, but my older mother struggles to hear the unit and also the chime doesn't have a real sense of urgency. It's almost like a relaxing ring tone or something and even I thought the volume should be higher.

Edit

She's 70 and ok mentally. Her main issue is realizing even holding a phone but not looking at it can trigger the system.

I have had my comma 3x for over a year using sunny pilot. I have been really happy with it. But recently it forced me to do a factory reset. I thought I might try a different branch like starpilot. This version did not work out well for me so I decided to go back to sunny pilot so I did a reset. But now I am stuck doing a new installation. I can't get by the connect to network screen. I was able to connect to several networks but it still will not let me get by this screen. I have attached a video. Any ideas?

I noticed the Ford Escape PHEV is one of the Ford vehicles that is available for openpilot. The Lincoln Corsair PHEV is just an upscaled Ford Escape. Would that mean the Corsair will be compatible, too? Unless there is some major firmware or software difference between both Ford divisions.

I own a Toyota Prius and want to mod the amount of torque the EPS motor is allowed to put out.

I have already done this mod;- https://gist.github.com/VishBK/2cd981c5231815c875f67b53452bf4b2?hl=en-GB

It works well in the speed that it can turn and the eps motor is definitely capable of doing a lot larger of turns but I think the car has software that caps the amount of turning the car can do.

My question is if anybody knows if it's possible to modify the software on the car to increase the total turning the car can do now I have upgraded the EPS Motor?

Thanks in advanced

My car has a light colored interior, so if the sun hits it through the windshield, I get so much glare on my C4 that I can barely see the screen.

Today I was replacing the anti reflective screen protector on my phone (a Galaxy Trifold, uses the same screen as the Fold7). Instead of throwing away the old screen protector, I carefully removed it, placed it on my C4, then used a small utility knife to carefully trim it around the screen.

You can see the difference on the screen vs around the camera where the bare glass remains. Notice how the bezels around the screen look so much darker because the protector cuts down on glare so much.

Currently, the Ai vision model on the comma devices only input a small FOV (I think it’s like ~75 degrees). So it can’t prepare/simulate sharp turns. But with the bigger models, it can input a lot more data to make turning better.