Recent content by 00Schnitzel

2018 MX100D EAP v2018.49.20 Hello Firmware Fairies.... Remember me...? Used to get updates Day 0-2... Feeling not so special, thought we had something special...... :-(

2018 MX100D MCU 2.0 AP2.5 v9.0 2018.39.5 - pushed a few days ago. V9.0 2018.39.6 pushed today. I'm sure something's different, but haven't been able to discern a difference. Anyone else?

Addendum: blind spot "red-line" is active feature. Just missed requisite conditions it during inital evaluation.

While a purely qualitative observation, It seems significantly improved from 2018.36.2. <It seems> The car will attempt to coast to slow (for a short period) and then resort to a physical brake. <Previously it seemed> The car would -> travel at set speed -> approach forward traffic @...

Initial thoughts: Instrument Cluster (IC) displays 360' degree proximity w/t wide field of view (+3 lane left / +3 lanes right) - ghost silhouette added for Large and Medium sized trucks. - Anything smaller than a sedan displayed as a sedan silhouette, including people delivering orders in fast...

2018 MX100D MCU2 AP2.5 v9.0 2018.39.5 (a1c2332) Select MCU Images:

2018 MX100D MCU2 AP2.5 v9.0 2018.39.5 (a1c2332) Release Notes:

Sorry I mispoke - I was informed my Q2 2018 MX100D was the first generation based entirely on INTEL chipsets (no NVIDIA at all). But that was the sales guy.

I was told my MCU v2.5 was based on an Intel chipset.

Had no idea Tesla had a problem with TeslaFi. Just cancelled my subscription. Now I'm sure to get Early Access !

I find <think> there's a correlation between periods when my phone app won't connect to the Tesla server and an imminent update coming down the pipe ...and my apps not connecting now. So we shall see shortly. MX100D / mcu2.5 / 2018.36.2

2018 MX100D MCU2.5 2018.36.1 (904a9a4) Cc'd release notes of 2018.34.x (e.g. new "PIN to drive"). Have yet to drive. No obvious changes to system's presentation layer (IC, MCU).

Thanks, shadowndust. I should have thought to try that first.

MX100D MCU2.5 2018.32.2 Sorry, but the thread got bloated, so I skipped to the end. Can anyone confirm EAS auto deactivation when signaling a lane change, and lack of parallel lane recognition (left or right) even though forward looking traffic recognition still active?