07-01-2023, 10:43 AM | #1 |
New Member
0
Rep 25
Posts |
VIN change issues with retrofit EVO and ATM
Hello Coding forum!
Here's the issue. I'm retrofitting an EVO into a F30. I have the EVO working properly. I have the ATM in the car and I created an FA that matched the VIN for the ATM so that I could detect SWE and code it in my car as the CAFD was the 255_???_???_???. So I did that and it appeared to work, but it didn't. I used ESYS FSC Extended to check the VIN in the ATM, using the diagnosis address of 0x61. When checking the VIN, it showed 17 30's (in HEX), which means that the VIN is blank (all zeros). So using BimmerUtility, I was able to look at the FDL and in the options, the VIN showed that it was the VIN per the car it was pulled from. The issue that I'm seeing is the fact that when I check the connection of the ATM in ISTA, it's only showing emergency calls as opposed to logged in, which is what it should be showing (the ATM does still have the ability to get a ConnectedDrive activation code). It has 2 bars of connectivity, so it appears as if it's working such that the SIM is getting signal (ISTA shows control to be green, no errors, or no SOS error), however, I feel that since the VIN in the FDL is not matching the VIN when I use ReadDatabyIdentifierVIN, the BMW servers are seeing a VIN mismatch on the ATM and are not letting the ATM to log in. When I try to use WriteDatabyIdentifierVIN, I receive the following error: --> WriteDataByIdentifierVIN <-- Error: SWT diagnosis for ECU "[BaseVariant=ATM, DiagAddress=61]" failed! [C057] MCDError Severity: 2051, Error Code: 49184, Description: Object with name not found, Vendor Code: 3, Vendor Description: provided name FINALIZE_ECU_FSC_DEPLOY doesn't map to an item [2130755616] I've connected to the car properly, using F20, NOT direct, using ESYS 3.40.2 with latest PSDzData files. I feel that somehow the ATM is VIN locked, similar to how EVO can have the same thing happen when improperly VO coding, but it's just a guess. Therefore, with all of the above, is there any programming, coding, fixes, Tool32 options, etc. that could get me out of this situation such that I can write the VIN back to the ATM. I firmly believe that as soon as I can get the VIN written properly back to the ATM, then it would connect, ISTA would show that it's logged into the BMW servers and then I could move onto the ConnectedDrive activation. Thanks for the help anyone can provide guidance!!!! |
07-01-2023, 08:58 PM | #4 |
New Member
0
Rep 25
Posts |
I've injected CAF into ECU and everything is blue. The issue is the fact that the ATM isn't logged in.
I have a 2015 with NBT/TCB and retrofitting EVO/ATM. I've updated istep so as soon as I can get the ATM functional, I'll see what features that work when I can access ConnectedDrive. |
Appreciate
0
|
07-01-2023, 10:08 PM | #5 | |
Major
595
Rep 1,117
Posts |
Quote:
The only things you can ever do with your vehicle is what it came out of the factory with. As you had a TCB from the factory, I doubt the option for Connected Drive even shows up available to you for subscription in 2023. |
|
Appreciate
0
|
07-01-2023, 11:13 PM | #6 |
Lieutenant Colonel
557
Rep 1,599
Posts |
I do not know EVO well...but can you change the Zeitkriterium for the HU ECU and its dependency ECUs to a date after the EVO came out for that model?
My car is May 2012 F30 and NBT did not come out for that model until in 2013. So I had to change the ECU's Zeitkriterium from the original May 2012 to (if I recall) May 2013 or after.
__________________
Help each other: if you manage to fix your issue (especially with help from this forum), don't be a d*ck and disappear. Follow-up by posting the solution so you can help others.
|
Appreciate
0
|
07-02-2023, 02:31 AM | #7 |
Lieutenant
145
Rep 536
Posts |
If you have ATM from donor car and still can connect to BMW server I can vo code and activate all dienste without remote.
__________________
Successfully retrofit on BMW F30 335xi 248,302,3AG,430,5AG,5AS,6NS,8TH and IHKA3
|
Appreciate
0
|
07-02-2023, 07:59 AM | #8 |
New Member
0
Rep 25
Posts |
So here's an odd happening, this morning, I checked the ATM with ISTA and it showed Logged in. And the Update BMW Services is no longer greyed out, with BMW Messages now showing up. So at least at this point, it's indicating that it is connected to the BMW Servers, even though when I check the VIN with ISTA, it's showing all zeros. When I check the FDL VIN field with BimmerUtility, it does show the VIN from the ATM. Very odd...
If I'm able to sign up for ConnectedDrive services, I'll post a final resolution in case someone else runs into this issue. |
Appreciate
0
|
07-02-2023, 02:18 PM | #9 | |
Lieutenant Colonel
557
Rep 1,599
Posts |
Quote:
__________________
Help each other: if you manage to fix your issue (especially with help from this forum), don't be a d*ck and disappear. Follow-up by posting the solution so you can help others.
|
|
Appreciate
0
|
09-12-2023, 10:55 AM | #10 |
Private
4
Rep 60
Posts |
hi, i have nbt evo in a f46 with Nav pro and someone stole the ATM. I have bought another one second hand from a very similar car and understand i will need to VO code the NBt with the vin from the ATM to get a gps signal etc. My question is regarding the NBT emulator i believe i will need to fit to the NBT. Will i need to fit this one at all and will i need another emulator between the ATM and the car? the wiring diagrams i have from ista are not clear on the can connections between the modules and the car and i havent found definitive answers yet. Im not interested in connected drive or even emergency call for that matter, i would just like a gps signal. thanks guys
|
Appreciate
0
|
09-14-2023, 02:17 PM | #12 | |
Major
595
Rep 1,117
Posts |
Quote:
|
|
Appreciate
0
|
Post Reply |
Bookmarks |
|
|