Comma AI self driver assistant

[UncleTony]

I'm not sure if you looked at the github threaad recently, but there is someone on there petitioning very hard to collect the bounty simply because he suggested adding resistors, even though he didn't invest anything in the prototypes. I basically told him have fun collecting from Comma, we would take up a gofundme to reward UncleTony.

Man, If I knew all I had to do was make suggestions to fix the issue...

Idk, I don't get that train of thought. I don't even claim credit for the final product, my goal was to understand the issue and turn the resolution into something the average person can do. It would have taken me much longer to do this without input from people that know more than me on all the subjects leading to a proper resolution.

This is supposed to be an open source project, not a money grab.

Sponsored

 

[UncleTony]

Yeah props for even taking this project on. It's only the Lightning that has the issue correct? That shrinks the pool of potential buyers even more with the comma being such a niche product already.

Yeah, something in the lightning modules causes a stub with the comma connected.

You can see it when you compare an ICE F-150 to the lightning.

My truck:

Alans ICE F-150:

The pins don't match their designations since Alan got a reversed set. But you can see one of the 128 readings is sitting at 85 on the lightning which is causing reflections for whatever is on that Bus. The PSCM disconnects with reflections, which is why we get a Christmas tree on startup.

 

[UncleTony]

The 120 drops us into over-termination territory and the 360 puts us at 55 ohms and 69 respectively. Still slightly out of spec, but within margins. I don't expect 69 ohms to matter much since that is coming from the comma power. The 55 ohms is what we care about.

 

[PJnc284]

That's way above my paygrade. I'm just glad yall know what you're doing or at least how to look like you do.

 

[UncleTony]

That's way above my paygrade. I'm just glad yall know what you're doing or at least how to look like you do.

I'm glad it comes off that way. I just wanted my truck to drive itself

 

[B177y]

Man, If I knew all I had to do was make suggestions to fix the issue...

Idk, I don't get that train of thought. I don't even claim credit for the final product, my goal was to understand the issue and turn the resolution into something the average person can do. It would have taken me much longer to do this without input from people that know more than me on all the subjects leading to a proper resolution.

This is supposed to be an open source project, not a money grab.

Hardly a money grab. More of just a "Thank you for your time and effort".

 

[UncleTony]

Hardly a money grab. More of just a "Thank you for your time and effort".

Not intentionally replying to any funding. Was referring to the github user complaining that he's not getting a payout for theorizing the problem.

 

[UncleTony]

Also, I appreciate the sentiment, but im ok with putting the effort and resources into it. This stuff is what I live for.

 

[oafydude28]

Alright – a couple of updates before I forget:

1. I'm cutting off orders for breakout boards starting today. PCBWay has sent me photos confirming the production boards were produced correctly, which means they'll ship in the next couple of days. I’d rather ya'll get the proper design instead of the breakout board workaround. And with USPS shipping times, it's just not worth it anymore. If anything goes wrong for any reason, I’ll reopen orders.
   
   
2. Alan (@Ajzride) and I revisited the USB-C cable discussion offline, and we’ve agreed that going forward, USB-C 3.2 Gen 2x2 and USB4 are the only cables we will recommend. These are the only ones that include the necessary internal connections by specification. (We are working on finding specific cables on amazon that are known to work to recommend).

More updates are hopefully coming soon—we’ve been working on a lot behind the scenes.

I suspect the cable is the issue.

https://www.amazon.com/USB-Cable-3-...d=1752283222&sprefix=USB+c+3.2,aps,227&sr=8-3

It looks like this cable from Amazon doesn’t work. Still getting errors on startup. I tried it again with the short jump only and there was no errors on startup. Should I try a USB 4?

I put on about 1,000 miles in the last few days and the was 2 instances were no errors appeared for a section of the drive. If I clear the codes after startup they do not come back for that drive.

 

[UncleTony]

It looks like this cable from Amazon doesn’t work. Still getting errors on startup. I tried it again with the short jump only and there was no errors on startup. Should I try a USB 4?

I put on about 1,000 miles in the last few days and the was 2 instances were no errors appeared for a section of the drive. If I clear the codes after startup they do not come back for that drive.

Do the errors only exist at startup or are they sticking around once the comma is up?

 

[oafydude28]

The stick around

Do the errors only exist at startup or are they sticking around once the comma is up?

Do the errors only exist at startup or are they sticking around once the comma is up?

I have the Comma powered by the OBD port so it stays powered up. The codes stick around and do not clear.

 

[UncleTony]

The stick around

I have the Comma powered by the OBD port so it stays powered up. The codes stick around and do not clear.

So an important thing to keep in mind is that it doesn't matter if the hardware is powered on. It matters if sunny pilot is up and controlling the signals and hardware.

From what I am gathering, you are having errors stick around after sunny pilot boots (When the camera opens and shows the overlays), and the "one pedal fault" and "service vehicle now" are the only errors that stick around. Is this correct?


If so, you are able to clear those errors with something along the lines of forscan and they don't return until you turn the truck off?

 

[oafydude28]

So an important thing to keep in mind is that it doesn't matter if the hardware is powered on. It matters if sunny pilot is up and controlling the signals and hardware.

From what I am gathering is that you are having errors stick around after sunny pilot boots (When the camera opens and shows the overlays), and the "one pedal fault" and "service vehicle now" are the only errors that stick around. Is this correct?


If so, you are able to clear those errors with something along the lines of forscan and they don't return until you turn the truck off?

Thank you for clarifying. You are correct the only errors that stick around are the service vehicle now and one pedal fault.

I clear the codes through car scanner app and a Bluetooth connection that I use for ABRP. The code do not return until the truck is turned off.

 

[UncleTony]

Thank you for clarifying. You are correct the only errors that stick around are the service vehicle now and one pedal fault.

I clear the codes through car scanner app and a Bluetooth connection that I use for ABRP. The code do not return until the truck is turned off.

I'm between two possible theories here,

1. You have a bad harness or box.
2. The CAN reflections are manifesting slightly different in your truck than what we normally see and are causing the one pedal to fault.

Option one doesn't make sense to me since the short cable resolves all of it for you. The fact that you can clear them with a scanner and they don't return also would point to it being caused by an error that doesn't clear once the reflections are resolved.

DM me your shipping info and I will send you a breakout so we can at least eliminate the reflections if nothing else. I will have to order a set, so it will take a bit to get to you.

 

[PJnc284]

I can send him the one I'm using and just remake mine since I have a spare board and a bazillion resistors

Sponsored