Search results

That’s right, I forgot about that. The bumper brackets on the underside of the headlight is different from reflector to matrix, but it def won’t fix that rounded oblong cut around corner of the headlight.

The OEM Tesla rear shade covers the entire rear window unlike the half amazon ones. Their photos don't really show it off that well...but it's exactly what you're looking for. I don't believe anyone makes a solid rear window shade...for obvious reasons (despite you having a camera based rear...

Matrix has been out since 2021 and the headlight shape isn't different at all. That's why people are swapping from reflector to matrix in a different thread here on TMC. Looks like you just got a overcut/messed up bumper.

Nah I bet with all the publicity this got on twitter, it’ll get locked down soon.

Have you tried enabling other options like rear fog using the service shell?

lol, this might actually work. @Durzel try this first.

Since you're already solving this using a converter, I would just pin out with a multimeter what pin does what on the converting harness, and depin/repin them so the correct lights illuminate. You probably just have to swap 2 pins on whichever side harness plugs into the vehicle side harness.

Good to know, thanks. TBH, that's kind of why I only ordered the rear first. Half because I wanted to see if this will solve the "rear being too stiff" woes before decided to revalve, but half because I wanted to see how it feels with 10k in the rear and the stock 11k in the front. 11k should...

Found a deal on some 10kg swift springs for the rear. Will try that out and see if it achieves the result I’m looking for. If so, I’ll probably change out the front to 9kg. If not, I’ll probably send it all out to performance shock and go back to the Ohlins 12kg rear setup.

How much did revalving them cost? Just curious.

Kit is relatively new, about 5k miles on the setup.

Has anyone here tried going to a 11kg square setup? I have the normal non Redwood Ohlins R&T, and I’m running 11 clicks on the front and 25 clicks in the rear. The front rides perfect, feels a bit firm but definitely has some give with damping set to 11, exactly what I wanted. But the rear...

Makes sense. I'm more familiar with the 3/Y platform where canbus is accessible from the OBD port in the rear of the center console, but the S/X sounds like its a bit different.

Early 2021.

Bad timing lol. AT&T looks like it has a outage today, both of our teslas are having connectivity timeout issues in SoCal.

This is wild. i didn't even know devices like this exist. I'm guessing it's gotta be plugged into the CANBUS somewhere right? So when purchasing used, probably a good idea to check the common OBD locations on the vehicle for any foreign devices.

Oh nice. You document this anywhere? I assume you just bought a bit of wire and some pins and repinned the connector?

rearLightType is set to global for C-style brake lights with twin reverse+twin rear fog. This is on a US car though, so YMMV.

It won't work on any inner taillight that isn't global. Those are 4 pin inners and will require a new trunk harness as well. If your car came with global outer and inner taillights (2023+), you can activate rear fog via gateway config or S3XY buttons and they will work.

Actually I tried this when I got them coded, it definitely does not work. The headlights themselves might turn on, but the signaling for CANBUS must be different because my turn signals and high beams did not function at all.

power strut is failing. Common issue and is covered by warranty.

Just adding to the data here. Did the install on my wife's 22 Ryzen Model YLR this weekend using a Model S tuner. PN 1143711-00-C. Software reinstall + letting the car sleep for 10-ish minutes and SXM popped up on the ICE and was able to activate successfully with a rep over the phone. I did...

only during the preview. It's a glitch where it plays whatever media was playing inside the car for a split second after the lock sound plays and its transitioning the audio back to the interior speakers.

Yours doesn't honk on unlock? Mine honks once on lock, twice on unlock.

Have both a Ryzen + USS 3LR and YLR. Both updated today, neither got high fidelity park assist, so it might just be a vision only feature…meh. Went to go set up the custom lock sounds, and it looks like it only plays them when you lock the car, but not on unlock lol.

Ryzen + USS here on both our Y and 3, didn’t get the high fidelity park assist. Tried setting up the custom lock sounds…but it looks like they only sound when locking the car, not on unlock lol.

I believe that user with a AMD car and plaid tuner reported that with the latest software update, XM is now working for him as well.

Oh interesting. So the global inners are 4 pin too? Asking bc when I removed one of the inners, it has rear fog with the wattage stamped on it...but it's a 3 pin inner.

lmao what.

Rear fogs are installed in the US inners. You just need to modify the wiring harness, someone documented it in this thread prior.

Yes!

Correct the new MY tails use global coding

PM also sent.

Technically I think these use the global pinout already since global coding works for both the euro tails and the new global tails. It might just be plug and play for you.

I think the headlights are one connector only, so it's odd that your accent light is working, but not the main beam. I would try removing the frunk tub (couple of bolts), and reseating the headlight connector.

This marketplace listing has expired and has been removed.

Seeing 404 not found when visiting port 8080 means you’re connected successfully. Tesla nerfed the web server output in a semi-recent update.

Didn't end up working. paid someone with access to a token to make the changes and that worked, but the methodology I posted above is sound. If you have a valid token that gives you access to unprotected/protected variables, you can push config changes using the string I posted in my OP. I was...

If you compare the 2 side by side, the knight rider is just the strip, the starlink is the strip + full tail light replacements in order to get that dashed look at the end.

Yes, VC_LEFT is reporting a tail light error. It’s the entire tail light that has an issue/internal short/something, not just a specific pin. EDIT: Oop, misread. Looks like you do have just a brake light error.

Yes? That’s what most of this thread is about. Either the OEM euro or the new global tail light. It’s the whole unit. There isn’t a specific pin. VC_LEFT is the left body side control module.

No, I have OEM Euro taillights

Oh interesting, I also have this message, but it’s a service-fix, so it doesn’t pop up in the normal alerts. Also drivers side.

Seems like a lot of work when you could just buy the adaptors from Amazon and they’d work for your 3.

fetching ICE directory contents, I get this: [ "cgdo", "checkinternet", "chromium", "chromium-adapter", "chromium-app", "chromium-fullscreen", "chromium-odin", "cid-updater", "connmetrics", "dashcam", "dashcam-viewer", "ecallclient", "firmwareinstall", "godot"...

2023 should already be coded for global. Did you car come with the new model Y style taillights where the C part of the light acts as the brake? EDIT: Nvm, just re-read. Yes, getting your car coded to global or buying the adaptors would work, adaptors have been sold out for quite a while though.

Car is a 22 so I theoretically should be able to change the config. Was going to try and use one of the alternatives to toolbox to push the raw config, but the one I found so far supposedly wont to let me do it. -_- I’m tempted to buy day access to it just to try anyway.

Reading through this thread and trying to absorb as much info as possible. Is there any documentation in terms of what config Ids are locked down and what aren't? Trying to figure out if I can modify configID 67 for rearLightType [ {"configid":67,"data":"02"} ], which is heard is not a...

I use a hydroflask 24oz standard mouth and it fits perfectly in my front cupholder.

This thread is for the general discussion of the marketplace listing MPP Sport Springs. Please add to the discussion here.