We have recieved 83% of our goal ..


frownmonkey United States
(Bimmer Scene VIP)
Bimmer Scene VIP
*****

Registration Date: 10-15-2020
Date of Birth: Not Specified
Local Time: 03-28-2024 at 03:36 PM
Status: Offline

frownmonkey's Forum Info
Joined: 10-15-2020
Last Visit: 02-22-2021, 04:48 PM
Total Posts: 7 (0.01 posts per day | 0.01 percent of total posts)
(Find All Posts)
Total Threads: 1 (0 threads per day | 0.03 percent of total threads)
(Find All Threads)
Time Spent Online: 5 Hours, 42 Minutes, 31 Seconds
Members Referred: 0
Total Thanks Received: 1 (0 per day | 0 percent of total 23180)
(Find All Threads Thanked ForFind All Posts Thanked For)
Total Thanks Given: 0 (0 per day | 0 percent of total 23180)
(Find All Thanked ThreadsFind All Thanked Posts)
Reputation: 0 [Details]
  
frownmonkey's Most Thanked Post
Post Subject Numbers of Thanks
Getting to NBTevo_V 1
Thread Subject Forum Name
Getting to NBTevo_V BMW F / G Series Coding & Retrofits & Diagnostics
Post Message
I have a Mini F60 and my goal is to get to NBTevo version V. Flashing using psdzdata 4.25.40 (latest as of now) gives me only version U (NBTevo_U19384I). I know version V on Minis is a thing because that's the one that supports fullscreen Carplay unlock over cable.

I poked around in the binary data files for the HU_NBT module and there are definitely bin files in the distribution with "V" version numbers:
  • "NBTevo_V20153J" from btld_00001ffd.bin.007_008_010
  • "NBTevo_V20153I" from btld_00001ffd.bin.007_020_010
The version that got installed is from a "007_007_008" version data file. 

Since I know next to nothing about how all this works, can someone help me understand how the flash/calculation process selects one data file version over another? Is that stored in the car or in the psdzdata distribution? And, more importantly, is there a way to encourage esys to select a newer version for my car?

Thanks!