[compat] <Model 3> <2023> <HW3> <2026.8.6.1> — <EU>

[szjeng]

Tesla model

Model 3

Year

2023

HW version

HW3

Tesla firmware version

2026.8.6.1

Region / market

Europe (Netherlands) FSD sub

App mode used

Auto Detect

Force FSD setting

OFF (using car's Traffic Light toggle)

Result

Did not work — FSD never activated

Anything else

Using ESP32 Atom Lite on Model 3 MIC 2023 (Ryzen). I get a green LED but FSD has status “Waiting”. Nothing happens in UI, TLSS is enabled. Tried Force FSD but nothing happens either. Maybe firmware version is not compitable?

[hypery11]

@szjeng Model 3 2023 Ryzen (MIC) is HW3 AMD — slightly different platform from Intel HW3 but same CAN logic applies.

A few things to check:

1. Connection point: are you on OBD-II (under steering column) or X179 (under dash passenger side)? OBD-II connects to Party CAN where 0x3FD lives. X179 pin 13/14 connects to Bus 6 which also carries it.

2. FSD status "Waiting" means the app hasn't seen the 0x3FD frame with isFSDSelectedInUI = 1 (bit 38). This happens when:

   • The TLSSC toggle in the car's Autopilot menu is OFF (you said it's enabled — good)
   • The car isn't in Drive/Park with AP ready
   • The connection isn't on the right CAN bus

3. Firmware 2026.8.6.1 — this is recent enough that the region lock may apply. Since you're in the Netherlands with an FSD subscription, the entitlement should be present. But 2026.8.x added additional server-side checks. Try the TLSSC Restore feature (Settings → TLSSC Restore → ON) which works via 0x331 instead of waiting for the UI toggle.

4. Green LED confirms the ESP32 is in Active mode. Check the web dashboard (192.168.4.1) — what does RX count show? If RX is increasing, you're connected to the CAN bus. If TX is still 0, the app hasn't seen a frame worth modifying.

5. Ryzen MCU: HW auto-detect reads das_hw from 0x398. The 2023 Ryzen Model 3 should report das_hw=2 (HW3). If you have the web dashboard open, what does it show for HW version?

Report back with the dashboard screenshot and I can narrow it down.

[szjeng]

1. Connection Point: OBD II under steering column

2. See screenshot:

3. Nothing happens with TLSSC Restore On either

4. RX frames are increasing. TX stays 0, see screen:
   Listen Only:

Active:

5: HW version show: Unknown

[fishredleung]

I’m experiencing the exact same issue here.

Vehicle: Model Y (EU version)
Software: 2026.8.3

Status shows:

• FSD: “waiting”
• Hardware: “unknown”
• TX modified : 0

In my case, I haven’t purchased FSD yet — I was hoping to verify whether the tweak works before committing. However, I can’t even get basic functions like Nag Killer to work at all.

Has anyone managed to get past this state, or is this related to not having an active FSD subscription?

[szjeng]

Similar here, Nag Killer is not functioning here as well!

[deftdawg]

Connection Point: OBD II under steering column

In my experience w/ HW3+MCU2 the ODB II port in the steering footwell goes silent when the car goes into drive, you likely need an X179 connection to do rx/tx anything useful

[szjeng]

Even in Park it doesn’t do anything it seems.

[hypery11]

@szjeng @fishredleung @deftdawg Multiple reports of the same pattern: FSD="waiting", HW="unknown", TX=0 on OBD-II.

Root cause is likely the OBD-II connection going silent in Drive. @deftdawg confirmed this — on HW3+MCU2, the OBD-II port in the steering footwell goes silent when the car enters Drive. This is a known Tesla behavior on some Model 3/Y builds.

Solutions in order of reliability:

1. Switch to X179 connector (behind passenger kick panel, 20-pin or 26-pin). This stays active in all drive modes. See HARDWARE.md for pinout.
2. If staying on OBD-II: check that you see RX frames counting up on the dashboard while the car is in Park. If RX=0 even in Park, the connection isn't working (check wiring, crystal frequency, termination resistor).

@szjeng You said RX is increasing — that means frames ARE arriving. But HW="unknown" + FSD="waiting" means 0x398 (GTW_carConfig) hasn't been seen. Try v2.12.0 (just released) which adds fallback HW detection and fixes the crystal frequency hardcoding issue.

@fishredleung Same — v2.12.0 should help. Also try "Force HW3" instead of Auto Detect to skip the 0x398 wait.

[fishredleung]

Tried the latest version, the error was still the same.
Also , there should be no “Force HW3” toggle in the Atom lite dashboard.

[szjeng]

In my experience w/ HW3+MCU2 the ODB II port in the steering footwell goes silent when the car goes into drive, you likely need an X179 connection to do rx/tx anything useful

I have an X179 OBDII (female) adapter to connect with the 16 pins Male pigtail OBDII. But this adapter comes standard connected to pin 18 and pin 19 of the X179. Will this work or do I need to bypass this so that it will connect to pin 13 and 14?

[hypery11]

@szjeng Pin 18/19 on X179 is Chassis CAN (Bus 3) — a different bus from where autopilot frames live. You need pin 13/14 (Bus 6) for FSD/TLSSC/NAG features. Your X179-to-OBD-II adapter is wired to the wrong pins.

Options:

1. Rewire the adapter — move the CAN H/L wires from pin 18/19 to pin 13/14 on the X179 side
2. Buy a direct X179 pigtail that exposes individual pins (available on AliExpress for ~$5)
3. Bypass the adapter entirely — solder directly to pin 13 (CAN H) and pin 14 (CAN L) on the X179 connector

See HARDWARE.md for the full X179 pinout diagram.

@fishredleung Still seeing FSD="waiting" HW="unknown" on v2.12.0 with ESP32 — can you check the web dashboard (192.168.4.1):

1. What does "RX count" show? If 0, the ESP32 isn't receiving any CAN frames
2. What does "HW Version" show?
3. Which connection are you using (OBD-II or X179)? If OBD-II, the car may go silent in Drive (see @deftdawg's note above)
4. Try "Force HW3" button on the dashboard if available

Also: the "Force HW3" toggle on the ESP32 dashboard IS correct — it's the web equivalent of the Flipper's manual HW selection. It should be there.

[fishredleung]

@szjeng Pin 18/19 on X179 is Chassis CAN (Bus 3) — a different bus from where autopilot frames live. You need pin 13/14 (Bus 6) for FSD/TLSSC/NAG features. Your X179-to-OBD-II adapter is wired to the wrong pins.

Options:

1. Rewire the adapter — move the CAN H/L wires from pin 18/19 to pin 13/14 on the X179 side
2. Buy a direct X179 pigtail that exposes individual pins (available on AliExpress for ~$5)
3. Bypass the adapter entirely — solder directly to pin 13 (CAN H) and pin 14 (CAN L) on the X179 connector

See HARDWARE.md for the full X179 pinout diagram.

@fishredleung Still seeing FSD="waiting" HW="unknown" on v2.12.0 with ESP32 — can you check the web dashboard (192.168.4.1):

1. What does "RX count" show? If 0, the ESP32 isn't receiving any CAN frames
2. What does "HW Version" show?
3. Which connection are you using (OBD-II or X179)? If OBD-II, the car may go silent in Drive (see @deftdawg's note above)
4. Try "Force HW3" button on the dashboard if available

Also: the "Force HW3" toggle on the ESP32 dashboard IS correct — it's the web equivalent of the Flipper's manual HW selection. It should be there.

I’m connecting the device with OBD II , please see my previous reply with the screen capture , the RX count kept stacking up , but the TX count remained 0, in both parking and driving mode

[szjeng]

2. Buy a direct X179 pigtail that exposes individual pins (available on AliExpress for ~$5)

Do you have an example of such cable, like a picture so that I know where to look for? At the moment I cant find such cable on AliExpress or anywhere else.

[hypery11]

@szjeng Here's what you need — an X179 pigtail that exposes individual pins:

Search AliExpress for "Tesla X179 20pin harness" or "Tesla diagnostic connector 20 pin pigtail". You want one that breaks out to bare wires or screw terminals, not one that converts to OBD-II (those map to specific pins you can't choose).

Example keywords: Tesla Model 3 Y X179 20P diagnostic plug pigtail wire harness

What to connect:

• Pin 13 → CAN H (to your ESP32/Flipper CAN H)
• Pin 14 → CAN L (to your ESP32/Flipper CAN L)
• Pin 20 → GND (optional, for power reference)
• Pin 1 → 12V (optional, to power your device from the car)

The X179 connector is behind the passenger-side kick panel (lower dash, right side). On 2023 Model 3 MIC it should be a 20-pin white connector.

If your existing adapter only wires pin 18/19, you can also just cut those two wires and resolder to pin 13/14 positions on the X179 plug. Check the HARDWARE.md pinout diagram to confirm pin numbering on your specific connector.

[szjeng]

Update: I connected the Atom Lite with the X179 26 pin under the center console at the back. I now have BMS values en it shows HW3. It also shows TX modifications but still nothing changes in the UI. No FSD UI in Park nor in Drive unfortunately. What am I missing here? I used your latest build.

[hypery11]

@szjeng Progress — HW3 detected + BMS working + TX modifications happening means the hardware connection is solid. But "nothing happens on the car" with TX running suggests the frames are being sent but either:

1. Wrong bus for FSD frames — the 26-pin X179 at the rear center console has a different pin layout than the 20-pin. On 26-pin: pins 18/19 = Chassis CAN (Bus 3), pins 13/14 may not be Bus 6 on this connector. Which exact pins did you connect to?

2. 2026.8.3 firmware region lock — you're in EU with FSD subscription. On 2026.8.x, Tesla added server-side region checks. Try enabling TLSSC Restore in Settings (uses 0x331 instead of 0x3FD) and wait for an MCU reboot (~15 seconds). This approach has been confirmed working on 2026.8.6 by @kp43h8.

3. Force FSD — try enabling Force FSD in Settings. On some EU cars, the TLSSC toggle is hidden by the region UI gating even though the entitlement exists.

What does the Flipper/ESP32 display show for FSD status — "ON" or "WAIT"?