2025 MY Juniper Standart hw4 26.14.6 LHD All test Result

[mamixsystem]

FSD_ENGAGE_14X_FINDINGS.md
MANIFEST.md
FIRE6_DELTA0.txt
CAP_GESTURE_DAS.txt
CAP_GESTURE.txt
COMBO_ENGAGE_RESULT.txt
FIRE_RESULT.txt
FIRE2_RESULT.txt
FIRE3_VEHICLE_ONLY.txt

FIRE4_PARTY_ONLY.txt

FIRE5_PARTY_THEN_VEHICLE.txt
FIRE7_BITMATRIX.txt
FIRE8_NO_BIT19.txt
FIRE9_MUX0_ISOLATE.txt
PASSIVE6_MONITOR.txt

[fboulegue]

Can you once confirm the CAN Pin Layout of your Car? As its the one from last year I assume it still got the old layout?

[hypery11]

This is the most rigorous 14.x FSD-engage investigation the project has had — thank you for the frame-level discipline and the honesty notes. It answers the question the tracker (#122) has been circling for months, with evidence. Let me pull out the load-bearing conclusions so they don't get lost:

1. 0x39B byte0 low nibble is the live DAS state (2 avail / 3 engaged / 5 active / 6 ACTIVE_FSD / 8 aborting / 9 aborted) — and it's live, unlike the ~1 s-lagged 0x3F8. That alone is the right measurement primitive; I'll point people here for it.
2. The 14.x preflight is a content-specific tamper check on the Vehicle-CAN copy of 0x3FD. The delta=0 control (exact duplicate → no abort) proving it's content not presence, and the Party-only vs Vehicle-only split (FIRE if I haven't bought or subscribed to FSD #3/Can this project be used in China? #4/CAN Add-On termination resistor? #5) proving the checker reads the Vehicle-CAN copy, are the two cleanest results in here. That Party-only injection never aborts explains a lot of past confusion.
3. Looking "entitled" doesn't help — tier already SELF_DRIVING on 0x7FF (3), and a 0x331 TLSSC spoof adds nothing; both still abort. So the region lock is off-CAN (gateway/VIN/backend entitlement), which also makes a MITM unlikely to help. That matches every other datapoint we have (the EU capture on [compat] Model S Plaid 2023 (HW3) 2026.26.1 — Italy (EU) #153, the crackdown reports) — you've now shown why at the frame level.
4. The win it confirms: your Summon EU-6m recipe — 0x3FD mux1 byte2 0E→06 (bit19 clear) + byte5 08→88 (bit47 set) — is exactly the project's shipped Summon EU Unlock (beta.25). Independent on-car confirmation that the summon distance unlock is real and CAN-reachable is genuinely valuable — thank you.

Two things:

• The safety note (a single-byte mux0 injection on a moving, engaged car briefly signalled + started a lane change before preflight cut it) is important and I want it visible — FSD-enable injection can actuate the vehicle; bench/closed-track only. I'll make sure that caveat is echoed wherever the FSD-activate toggle is documented.
• Would you mind if I referenced this write-up (or a trimmed version) from [tracker] 2026.14.x / 2026.20 — nag killer + FSD activation: status & how to help #122 as the definitive "FSD-engage on 14.x" finding? Credit to you. It saves the next dozen people from re-running the same aborts.

Outstanding work.

[mamixsystem]

Of course, you are free to use the content. There's a small mistake; the car signaled instantly during injection because there was a vehicle in front of us, and its intention was to overtake it, but it never attempted to change lanes. I wanted to correct this by bringing it to your attention. If you have any other tests or raw data you'd like to share, I'd be happy to. I also apologize profusely for my poor English :)

[hypery11]

Thank you — and no apology needed, your English was perfectly clear. I've noted the correction: the car signalled instantly during the injection because there was a lead vehicle it intended to overtake, but it never actually attempted the lane change. I'll phrase it that way wherever this is referenced so the caveat stays accurate (FSD-enable injection can trigger a turn-signal / intent on a moving engaged car — still bench/closed-track only, but not a completed maneuver).

I'll add the pointer from #122 now, crediting you. If you're up for more, a full-rate listen-only 0x39B capture from a stationary run would help others reproduce the DAS-state primitive cleanly. Really appreciate the rigor here.