Hi have you changed the vin of the nbt evo unit to your vehicles vin

Furthermore just for myself - I'm trying to do a NBT EVO retrofit too, where did you install the atm module? And what connections did you connect into it other than the GPS antenna? Do you know the part number for ethernet cable as I can't seem to find it

 

Hi, yes nbt evo is flashed with car vin. ATM has a different VIN from donor, I can see it in BMW-Support app in Connecteddrive menu after performing a connection test. Everything seems fine, really strange I don't get the confirmation message... Even when I add my car with ATM VIN.

ATM is behind trim in the trunk, and Ethernet cable needs to be built manually from diagram.

 

Where is the diagram? Are you able to send me this diagram as well please?
Other than the ethernet connection that goes to the head unit, what else did you have to plug into the atm module for it to work

 

Sorry I do not have it. And I don't think it is easy to get.

A specialist should be able to do it for you, but it requires lot of soldering. As of today only a few succeeded to retrofit new ATM module with nbt evo as far as I know.

You can buy an ATM emulator if it is more easy for you.

 

Nobody tried to retrofit ATM with remote services?

 

I would assume that it works the same as an NBT with TCB, and therefore, for full functionality, the VIN of the ATM needs to match the VIN of the NBT, otherwise messages will not be sent from the ATM to the car.

You can't change the VIN of the ATM, because BMW has a record of the SIM/IMEI of the ATM to the VIN of the car it went to.

What I did was I updated the NBT VIN to the VIN of the TCB donor. I also got a FSC Repair kit for the TCB donor, and updated the FSC's in the NBT. Afterwards, both the NBT, and the TCB, were fully functional. As far as the BMW servers are concerned, my car is the 2016 TCB donor car - even though it's actually a 2007 E93.

The thing that allowed me to do this, was the NBT emulator, which allows the NBT/ATM to use a different VIN than the car.

 

Thanks a lot Mashman.

That seems to be the issue here. I have already flashed the nbt evo with my original VIN and got the FSC codes for it.

Is it not a problem to flash the nbt unit with a VIN code from totally different model? I thought it had to be the car original VIN or same model?

 

It is only a problem if you have no emulator in place to stop the head unit locking itself

 

I'm trying to change my tcb to atm module. Can anyone help with what the wires should be that connect to the atm?

I have a twin pink and black cable, one pink cable, one blue cable and one really wide blue cable. Does anyone know which ones goes where in atm?

Seriously any help in the right direction is appreciated

 

I can't imagine the face of bmw dealer when they see a serie 1 with nbt serie 7 vin

The warranty would be completely screwed, if it is not already with original vin.

Except for remote services, why bother installing an emulator if we can get fsc for original vin?

Does the donor vin of ATM need to have at least the same options as original vin if I decide to flash nbt with it, or it does not matter?

 

Hi,

I'm trying to retrofit an ATM to EVO. I'm stuck at connecting EVO to ATM. My connection is:

atm oabr
pin 2 .......> evo oabr pin 4 Ethernet
pin 4 .......> evo oabr pin 2 Ethernet
pin 7 ......> to any CAN 2 high
pin 9 ......> to any CAN 2 low

atm black 6 pin
pin 3 ..... +12
pin 4 ...... ground

I set it up on the bench using ZGW02. I used to flash the EVO with this setup and it worked. When I add the ATM to the bench, ESys refuse to flash the ATM using ethernet and had fallback to use CAN bus which took almost an hour. Is there something wrong with my setup? It seemed that the ethernet connection between EVO and ATM could not be established.

I then put the ATM into car and the navigation could work normally with that ATM GPS. Very strange. Afterwards, I used TOOL32 to check the internal IP configuration of the ATM, and it was 0.0.0.0 (subnet mask 255.255.255.255). Did the GPS signal send to the EVO via CAN bus?

puzzled.

 

Hi,

I'm trying to retrofit an ATM to EVO. I'm stuck at connecting EVO to ATM. My connection is:

atm oabr
pin 2 .......> evo oabr pin 4 Ethernet
pin 4 .......> evo oabr pin 2 Ethernet
pin 7 ......> to any CAN 2 high
pin 9 ......> to any CAN 2 low

atm black 6 pin
pin 3 ..... +12
pin 4 ...... ground

I set it up on the bench using ZGW02. I used to flash the EVO with this setup and it worked. When I add the ATM to the bench, ESys refuse to flash the ATM using ethernet and had fallback to use CAN bus which took almost an hour. Is there something wrong with my setup? It seemed that the ethernet connection between EVO and ATM could not be established.

I then put the ATM into car and the navigation could work normally with that ATM GPS. Very strange. Afterwards, I used TOOL32 to check the internal IP configuration of the ATM, and it was 0.0.0.0 (subnet mask 255.255.255.255). Did the GPS signal send to the EVO via CAN bus?

puzzled.

I'm also trying to retrofit ATM with EVO, and am having the same result, with no IP address. I've used a shielded CAT6 cable, one TP for OABR, and connected the shield to 3 <->8 .

The ATM I have is used, and has already been flashed to 3.61.

I'm wondering where the ATM gets its IP address? Is it possible that the ATM used a static IP address, and it was lost when the ATM was flashed? Everything seems to be ok, except the OABR LINK is down.

Also, my navigation does not work. Would it be possible for you to send me the NCD you have for you EVO and ATM?

Thanks!

 

Your pinout is correct. OABR Ethernet is shielded twisted pair. Shield is connected on OABR pin 3 at ATM and pin 8 on EVO. You may not have shield and line noise is preventing OABR interface from coming up.

 

I will definitely use a shielded twisted pair. On the other hand, in my current twisted pair, Tool32 atm.prg reported that the ethernet signal quality is above 90.

 

Read the release notes for Ista/P 3.61 and 3.62. According to notes, latest I-Level bricks some ATMs and they need to be replaced. I have not updated my ATM and with ATM at 3.60 it connects to EVO at 3.62 with no issues.

 

I flashed mine to 61.2, so it could be bricked already?

Is it possible to flash it back to 60.x?

:angel: OMG

 

The release notes don't offer flashing back as an option - they suggest to exchange ATM if error code 0xB7F33C is present.

 

I'm not with my car right now. However, the last time when I did I had one fault which could not be cleared and it was something like ...33..

 

You know you could generate NCD for any FA.XML file from Coding-Verification, right?

 

No I didn't - thanks! I was actually creating FA's, VO coding, to create various NCD files. Coding-Verification is MUCH easier, thanks!

 

I may have found my issue.

I have an E93 with retrofitted EVO, AMT, and ZGW. I flash, and program using the ZGW, connecting with the donor VIN. I thought the Enet connection between the ZGW and EVO was good, but it wasn't. I've been connecting to everything over CAN.

I previously had a NBT and TCB retrofitted, and it would work fine even with the ZGW not connected - I would only connect the ZGW when I wanted to flash, or program something. I'm wondering/hoping that for the EVO to create Enet link to the ATM, the EVO needs to have Enet connection to the ZGW.

I'm waiting for some replacement terminals, I should be able to see if this resolves the issue, by this weekend.

 

I have EVO ID5 with ATM in 2004 E60, no ZGW, FEM or BDC. Only EVO and ATM. Double check your connections. As long as VIN in EVO and ATM matches, you should get assist, connected drive with traffic info and other goodies. Use newtis - dot - info website for schematics.
Don't forget to set time first and then update services (or steuern_provisioning with Tool32). OABR pins are very gentle - make sure they are crimped correctly and are fully seated in housing.

 

Hi 2real4u,

Tonight I tried again to re-VO code the EVO and ATM but no luck, the IP address still returned 0.0.0.0.

However, I have a new fault (which I forgot to write down again :rofl. It was TCB Unexpected Communication Termination. Then I fired up Rheingold's Calculate Test Plan and chose HeadUnit - connected devices (ABL-DIT-AT6510_CICVB). A list of connected device was shown, and I selected 'Ethernet to telematics control unit' for a test. And the test result was:

Ethernet connection to telematics control unit was checked.
No fault found. There may have been a loose contact.

I repeated the test for Ethernet to ZGM/FEM/BDC and no fault found.

Then I went back to Tool32 to check ATM's IP address, it was still 0.0.0.0

So either my Tool32 is outdated or Rheingold version is too old. Or worst, it could be my country code (HONG KONG 8LH) which may not have any connected driver feature.

Have you ever enquire the IP address of the ATM using Tool32 atm.prg status_ip_configuration?

 

Sorry, I don't have any diagnostics connected to CAN2 in my car - I have EVO ethernet in OBD, that's it, so I can't check the the errors or run PRG jobs for TBX,ZBE3 or ATM and have no need for it - they just work. I may add a diagnostic connector in future, but right now with no gateway to CAN2 in place I cannot read any errors.
Before installing it into a car I had it on bench with CAN2 connected to ICOM - there were no unexpected errors of any kind, but I have not checked the IP of ATM.

 

One more thing, my ATM is a 'new' one which I bought from eBay. Could it be the case that this ATM hasn't been activated? Is there any way to 'activate' a virgin ATM? Besides, do I need to register the IMEI/SIM with a phone network provider for it to access the Internet? :dunno:

 

GPS should work without activation. Telematics (everything related to cellular network) need to be activated through dealer.

 

I could confirm that my EVO to ATM ethernet is working as I double checked it using Rheingold headunit - connected device - TCB ethernet checking. When I unplugged EVO to ATM ethernet, it reported connection FAILED, and when I reconnected them it said NO FAULT. Same case when I was using navigation. If I unplug the connection, the GPS Satellite signal was stopped and when I reconnect them, GPS Satellite signal resumed immediately. Though Tool32 ATM.prg still reported 0.0.0.0 ip address.

So now the remaining factor is the activation file that my FSC vendor had sent me. Maybe that file is bad, or maybe a brand new ATM can only be activated by BMW.

 

ATM has a BMW SIM card built in. There is no way you could activate it without BMW.

 

Can someone help me with disabling SOS call system failure after ATM retrofit, the only error I have on ATM is aerial antenna 1 : open circuit, and I can't do telematik disable, because I will lose online services.
So maybe someone know a way just to disable the warning message from kombi.
Thank you.

 

You only have 1 antenna connected? Have you tried coding BACKUP_ANTENNA_DISABLE to active?

 

It is disabled, otherway I will had 2 errors on, but I have only one error on antenna 1. I managed to cancel error from kombi.

 

I managed to cancel SOS error from kombi. CC_AKTIVERUNG_5 - aus , did the job.
Can I ask what command from ATM.prg did you used for geting ATM ip address?
Thank you.

 

Hey, just a quick update.

My EVO VIN (original one) is still not matching my donor ATM VIN (I do not want to use any emulator or loose my original VIN) but connecteddrive services are working great (except remote services as I cannot receive the verification code to add the car).

I do not know how but my installator succeded to make my EVO use my original VIN in connected drive services instead of ATM VIN. Now I see my original subscriptions in connecteddrive store even though the ATM VIN is different!

My last problem is this same SOS error. I already tried to add TELD in HO-WORT and code KOMBI with it, then I FDL coded ST_ECAL_ALIVE & ST_ECAL_TIMEOUT = nicht_aktiv in KOMBI, and BACKUP_ANTENNA = nicht_aktiv in ATM. The error still pops every 2-3 weeks. I don't know what triggers it.

larry_bml, where did you find CC_AKTIVERUNG_5 - aus? Is it a value I can set in FDL code of Kombi?