[painsage]

Originally Posted by RedErik

Do you get no signal message or completely black screen? If all black screen check what have you under VEHICLE_STATE_CONCEPT, should be conventional_clamp.

I realized that someone had rewired the emulator, not to be the factory pinout like in the schematics, today im gonna revert it back to stock and try then. I noticed on my bench, changing gatewaytable to 5 or 7 makes it blackscreen, im guessing the eNBT will fix this when its all in car?

[RedErik]

Originally Posted by painsage

I realized that someone had rewired the emulator, not to be the factory pinout like in the schematics, today im gonna revert it back to stock and try then. I noticed on my bench, changing gatewaytable to 5 or 7 makes it blackscreen, im guessing the eNBT will fix this when its all in car?

Mine's set to 5 and runs fine on the bench without emulator connected.

[painsage]

Originally Posted by RedErik

Mine's set to 5 and runs fine on the bench without emulator connected.

My ID6 is from G30 so its KCAN4, i have not gotten an answer yet does the adapter support KCAN4...

[RedErik]

Originally Posted by painsage

My ID6 is from G30 so its KCAN4, i have not gotten an answer yet does the adapter support KCAN4...

So is mine, but that makes no difference. KCAN4 in G30 is an equivalent of KCAN2 in Fxx. It's just an arbitrary number to differentiate CAN buses - i.e. they were given numbers to differentiate their use. KCAN4 connects HU, ATM, IHKA and ZBE, but the technical spec of each is the same.

[painsage]

Originally Posted by RedErik

So is mine, but that makes no difference. KCAN4 in G30 is an equivalent of KCAN2 in Fxx. It's just an arbitrary number to differentiate CAN buses - i.e. they were given numbers to differentiate their use, 4 does HU, ATM, IHKA, ZBE etc. But the technical spec of each is the same.

You saved me of hours of overthinking, thanks a lot. Im using ZBE3 from NBT from F10, i did zbe_35UP to nicht aktiv in my EVO, this should make the controller work, correct?

[rlesko]

Originally Posted by RedErik

So is mine, but that makes no difference. KCAN4 in G30 is an equivalent of KCAN2 in Fxx. It's just an arbitrary number to differentiate CAN buses - i.e. they were given numbers to differentiate their use. KCAN4 connects HU, ATM, IHKA and ZBE, but the technical spec of each is the same.

I'm not sure this is totally accurate- aren't some of the KCAN buses are actually running at different frequencies and possibly data length? While I'm sure that some of properties of the different KCAN networks in the car are the same, I don't think they are all the same and the numbering is totally arbitrary.

[RedErik]

Originally Posted by rlesko

I'm not sure this is totally accurate- aren't some of the KCAN buses are actually running at different frequencies and possibly data length? While I'm sure that some of properties of the different KCAN networks in the car are the same, I don't think they are all the same and the numbering is totally arbitrary.

This is from TIS:

The K-CAN is counted according to the number of bus connections that lead from the central gateway module: for example K-CAN2 to K-CAN8.

Overview of the bus systems

In principle, two groups of bus systems are distinguished:

-> Main bus systems: for example, Ethernet, FlexRay, K-CAN2 to K-CAN8, MOST, PT-CAN and PT-CAN2

‐> Sub‐bus systems: BSD, D‐CAN (diagnosis-on-CAN), LIN, local CAN

Body CAN: Body CAN

The K‐CAN is responsible for communication of the components with low data transfer rates. The K-CAN is also linked to the other bus systems via the central gateway module (ZGM). A number of control units in the K‐CAN have a LIN bus as sub‐bus. The K‐CAN has a data transfer rate of 100 kBit/s and consists of 2 twisted cores (two twisted wires). The K‐CAN has the possibility to be operated as a single-wire bus in the event of errors.

Body-CAN2 to body-CAN8: K-CAN2 to K-CAN8

The K-CAN2 to K-CAN8 is responsible for communication of control units with high data transfer rate. The K-CAN2 is also linked with the other bus systems via the central gateway module (ZGM). The K-CAN2 to K-CAN8 has a data transfer rate of 500 kBit/s and consists of 2 twisted cores.

Powertrain CAN: PT-CAN

The PT‐CAN connects the engine control system with the transmission control unit, but also interconnects systems in the area of safety and driver assistance systems. It is line-based with tap lines to the individual systems. The PT‐CAN has a data transfer rate of 500 kBit/s and consists of 2 twisted cores.

Powertrain CAN2: PT-CAN2

The PT‐CAN2 forms a redundancy for the PT‐CAN in the area of the engine control system and also transfers signals to the fuel pump control module. The PT‐CAN2 has a data transfer rate of 500 kBit/s and consists of 2 cores with an additional wake-up line.

Ethernet

Ethernet is a manufacturer-neutral, cable-based network technology with a data transfer rate of 100 MBit/s. The TCP/IP (Transmission Control Protocol/Internet Protocol) and UDP (User Datagram Protocol) protocols are used as transfer protocols.

FlexRay

With a maximum data transfer rate of 10 MBit/s per channel, FlexRay is significantly faster than the data buses used so far in vehicles in the areas of body and drive/chassis and suspension. The central gateway module sets up the link between the various bus systems and the FlexRay. Depending on the equipment fitted in the vehicle, the ZGM has one or two so-called star couplers, each with four bus drivers. The bus drivers forward the data of the control units via the communication controller to the central gateway module. The deterministic data interchange ensures that each message is transferred in the time-controlled section in real time. Real time means that the transmission takes place in a specified time.

MOST bus system

MOST is a data bus technology for multimedia applications. The MOST bus uses light impulses for the data transfer at a rate of 22.5 MBit/s and has a ring structure. Data transfer on the ring bus takes place in one direction only. Only the central gateway module can implement data exchange between the MOST bus and other bus systems. The car information computer (CIC) acts as the master control unit The gateway to the rest of the bus system is the central gateway module.

So as you can see there are various buses in a car, but all KCAN2 to KCAN8 are the same. They just connect different equipment to make the required topography and not overload each bus.

[RedErik]

Originally Posted by painsage

You saved me of hours of overthinking, thanks a lot. Im using ZBE3 from NBT from F10, i did zbe_35UP to nicht aktiv in my EVO, this should make the controller work, correct?

I didn't change anything for the ZBE apart from coding in all ZBE_TOUCH functions. As far as I can tell, ZBE from F10 and G30 are the same, just the button layout is different, but you can change that with coding to suit yours.

[painsage]

Originally Posted by RedErik

I didn't change anything for the ZBE apart from coding in all ZBE_TOUCH functions. As far as I can tell, ZBE from F10 and G30 are the same, just the button layout is different, but you can change that with coding to suit yours.

Hmm, im gonna try. The only thing thats weird right now is the gatewaytable thing. I am using ZGW2 on my bench, how about you?

[RedErik]

Originally Posted by painsage

Hmm, im gonna try. The only thing thats weird right now is the gatewaytable thing. I am using ZGW2 on my bench, how about you?

I'm using ZGW-02 8SK as I read somewhere that others can cause communications issues of some sort.

[painsage]

Originally Posted by RedErik

I'm using ZGW-02 8SK as I read somewhere that others can cause communications issues of some sort.

I had ZGW1 black box with most, then flashed to ZGW2, maybe thats whats causing the gatewaytable issue. Im gonna update you when im in car.
EDIT: Can you PM me any of your contact info in case i need help? I cant use PM function.

[RedErik]

Originally Posted by painsage

I had ZGW1 black box with most, then flashed to ZGW2, maybe thats whats causing the gatewaytable issue. Im gonna update you when im in car.

That would explain your issues, I think...

[painsage]

Originally Posted by RedErik

That would explain your issues, I think...

One more thing, what adapter are you using? I'm using the base NBT adapter from Adrian (CarSystems), the one with 10 pins.

[RedErik]

Originally Posted by painsage

EDIT: Can you PM me any of your contact info in case i need help? I cant use PM function.

My DMs are disabled, was getting too many messages. Here, it will save me typing all of that, at the end of this video you will find all my contact details.

[RedErik]

Originally Posted by painsage

One more thing, what adapter are you using? I'm using the base NBT adapter from Adrian (CarSystems), the one with 10 pins.

I think the forum is blocking that link... www . bmw custom retrofit . com /navigation-retrofits/bmw-nbt-retrofit-adapter-for-e-series-nbt-e-series-evo-id5-id6

[painsage]

Originally Posted by RedErik

I think the forum is blocking that link... www . bmw custom retrofit . com /navigation-retrofits/bmw-nbt-retrofit-adapter-for-e-series-nbt-e-series-evo-id5-id6

I have that exact one, im gonna shoot you a DM on Facebook, already sent a request, thanks a lot.

[calicoupe]

How can you "see" the ATM after this retrofit? I have a matching NBTEVO and ATM that was working perfectly in a 2009 e92 m3. I did not have to do any special config to get the ATM working, it just worked after cabling it up. I moved the entire setup to a different 2009 e92 m3 and everything is working except all ATM functions (no GPS or connected drive functions). Is there a way I can see the ATM to verify it is powered and connected properly? I do not see it in e-sys and Tool32 cannot connect to it. TIA!

[vilord]

I was able to see the ATM in e-sys when connecting to the ethernet port of the nbtevo, when the data link between the evo and atm were working properly and both were properly powered up and so on.
i don't remember what diagnostic functions were available, but i was at least able to see it.

[calicoupe]

thanks man! i'll keep at it until I see it in e-sys

[grahams]

Hi All,

did the majority of this retrofit yesterday. Have hit the same issue as JPToadstool with fitment of the faceplate.

Can anyone share more details on how they've approached this and which adjustments need to be made to the HU, CIC faceplate, fascia or cage.

There are locating lugs on the CIC faceplate which don't work with an NBT unit. Should these be removed?

Thanks for help in advance.

Graham

[The-Traveler]

I just smushed the fascia in there without modifying it but bending the metal pins a little to make it go through and not screwing the NBT EVO unit in. Most people can't tell, it's been this way for a year. I plan to drill holes in the NBT evo to screw it in properly, but I assure you, you can make it fit decently if you try bending the 2 metal (long) pins coming out of the plastic bezel and put them in on an angle and push. Their tension will hold the NBT evo unit in place. I track my car, trust me it's solid.

[The-Traveler]

Does anyone know what AMP I should buy for my e92 Individual audio to work with NBT EVO and get rid of echo ? Is HK enough? F01, or F30?

I thought e9x individual audio was better than HK in F series?!