Yet another CAN module - Shiftlights, MDrive, NBT and more

[superwofy]

Thanks for clearing that up. I have another two questions now:

1. Did the blue plug change position after the LCI or why did you mention that? Because there's two versions it seems, one where the blue plug is left and the other where it is right.

2. In regards to your .txt file, PIN 3, 4, 6 are connected directly to your Teensy, right? POWER switch, LED and DSC Switch.

1. Yes the Blue and Black connectors on the JBE are flipped on older models. I believe pre-JBE2.
The notes in that text file were made with an LCI M3 as the subject. It had a JBE3.

2. Yes, that's correct. The teensy drives those LEDs and contacts directly as it is in charge of those functions.

 

[bosolanu]

......
The feature is disabled if the move seat back option isn't ticked on iDrive.
......

Hi @superwofy,
Am I understanding this right? Are you able to add any kind of option in iDrive or just some pre-programmed ones?

 

[superwofy]

Hi @superwofy,
Am I understanding this right? Are you able to add any kind of option in iDrive or just some pre-programmed ones?

There's a checkbox in the locking settings section that returns the seat to the last memory setting.
If that's not checked, my code will not move the seat back when opening the door.

 

[doublespaces]

Took one, see here: https://github.com/superwofy/E9X-M-CAN-Integration-Module/raw/main/vid/shiftlights-startup.mp4

I did it because in normal operation you almost never see them. Kinda nice to have them animate when starting the engine.



I now added:
Exhaust flap control with MDrive
and
Launch control flag display.

This link is dead

 

[TiAgAu]

This link is dead

Clips

E9X-M-CAN-Integration-Module/Video at main · superwofy/E9X-M-CAN-Integration-Module

Contribute to superwofy/E9X-M-CAN-Integration-Module development by creating an account on GitHub.

github.com

 

[superwofy]

I'm very happy to announce that I've completed and released the NBT emulation code. I've been working on it for the last few months and it is now a part of the CAN module.

As far as I am aware, this is the only non-commercial solution. Anyone can read the source and modify as they please. No VIN locking, no bs. Everything I've tested so far works.

Since it is part of the module, *some* work is required to run it standalone. I'm not particularly interested in doing that since for my application I don't foresee ever using the car without all the other functions provided.

All CAN message documentation can be found in the txt files of the repo and obviously the source code.

Hopefully this brings some more life to this platform. Happy coding



P.S. This was designed for ID3 however, I've just gotten an ID4 unit that will replace the NBT. It's unlikely I will work on ID5/6 however, they should be mostly functional out of the box.

 

[Xantor]

First of wow. That's really amazing. Secondly does that mean I could skip id3 and go to id4 directly?
You know I need to copy that setup. That's just awesome.
How does it handle the servotronic on sport plus? In cic it only has two settings right?

 

[superwofy]

First of wow. That's really amazing. Secondly does that mean I could skip id3 and go to id4 directly?
You know I need to copy that setup. That's just awesome.
How does it handle the servotronic on sport plus? In cic it only has two settings right?

Sure, you will be able to skip ID3. I have the ID4 unit ready to go but have to wait for cables to be delivered. I'm quite confident that little or no changes will be made to the code. Alas, I haven't tested it.

While ID5/6 have many advantages, for me, ID4 will integrate better. I've already replaced the car photos and will create a portal for it akin to the CIC one I made. I wanted this "retrofit" to provide all functionality that the CIC did.

Presently it only recognizes Sport. Pressing Sport+ still goes to Sport. I might use a 6F1 job to tell the SVT to set PWM to 0% on Sport+, that might work nicely - it's on the TODO list.

 

[Xantor]

According to your Repo a 6F1 is sent via DCAN so it's a diagnostic job, right? Does that mean it has to be refreshed every 255 seconds?

Other questions that arise now since you've publicly launched the NBT update are:

1. What are the key advantages from going CIC to NBT / NBT EVO? Other than it being newer of course. Newer Web Engine so your homebrew server setup might be of more use? Better Navigation?

2. Is there any drawback to upgrading to ID3/4?

3. Do you have to code the NBT via Esys / Ethernet instead of a K+D-Can Cable?

4. Can you change the donor vin in the nbt? Possible drawbacks maybe? Losing FSCs(?)

5. Do Check Control messages appear correct?

6. Did BMW just maintain most functions canbus wise when they developed the NBT? I sadly can't look that up lmao

7. Will you try and retrofit a HUD? They are much smaller on F series cars than E60/E70 ones, they might clear our dashboards.

8. Does the Faceplate fit plug and play (or at least look like it?)

9. Regarding 8 - how hard was it to change the hardware? I know the CID can be changed (probably even has to) to a higher resolution one

10. Why are you using a CCC ZBE? Is a touch or normal nbt zbe in the works?

There's probably a few other questions I missed but I think those cover the most interesting aspects.

 

[superwofy]

According to your Repo a 6F1 is sent via DCAN so it's a diagnostic job, right? Does that mean it has to be refreshed every 255 seconds?

Other questions that arise now since you've publicly launched the NBT update are:

1. What are the key advantages from going CIC to NBT / NBT EVO? Other than it being newer of course. Newer Web Engine so your homebrew server setup might be of more use? Better Navigation?

2. Is there any drawback to upgrading to ID3/4?

3. Do you have to code the NBT via Esys / Ethernet instead of a K+D-Can Cable?

4. Can you change the donor vin in the nbt? Possible drawbacks maybe? Losing FSCs(?)

5. Do Check Control messages appear correct?

6. Did BMW just maintain most functions canbus wise when they developed the NBT? I sadly can't look that up lmao

7. Will you try and retrofit a HUD? They are much smaller on F series cars than E60/E70 ones, they might clear our dashboards.

8. Does the Faceplate fit plug and play (or at least look like it?)

9. Regarding 8 - how hard was it to change the hardware? I know the CID can be changed (probably even has to) to a higher resolution one

10. Why are you using a CCC ZBE? Is a touch or normal nbt zbe in the works?

There's probably a few other questions I missed but I think those cover the most interesting aspects.

It may, I don't know yet since I've yet to experiment with it.

1. Yes on all counts +USB video.
2. Nothing functional that I've found yet. Can't code / diagnose any BN2000 MOST modules unless you use an ICOM-B. With the car images I added I'm happy with it (this took me days to do however).
3. Yes. But I'm also developing a way to use J2534 passthru. That would allow diagnosis + coding of BN2000 and BN2010 modules on one interface.
4. Yes. Read my thread on SWT patching. Or, use the vin patching code.
5. Yes, for the most part. There is a blank one I have to fix.
6. For the most part. Read this
7. No. Even if you can physically fit it, the windshield will be a big issue. You can stick something on but it won't look nice.
8. Yes. Read the code.
9. I used an F30 screen which was hell to separate from its glass without damage. F25 screen inside E90 CCC frame is the path of least resistance.
10. Because CIC RHD manual M3 consoles are pretty much non-existent used. I ordered one but it's on backorder. ZBE3,4 and 5 work out of the box already as does TBX. I have a perfectly working ZBE1 so I figured why not...

 

[808AWD325xi]

Amazing work, @superwofy !!

 

[superwofy]

So I've now made a new commit that adds full support for EVO ID6. Everything except for custom CCs is working.

ID4 was a complete bust since unlike what I expected, there is no internet through Bluetooth (DUN/PAN) and the echo issue is present.

ID6 is nice and slick but for me adds essentially nothing from ID3. I don't use Carplay and Miracast support was dropped in AOSP years ago. The car 3D models are for all intents and purposes un-editable.

ID3 on the other hand has no echo issues, does support DUN/PAN and I've successfully replaced all E92 car images. Integration in the E92 is thus near perfect.

Not quite sure what head unit I'll go forward with.

 

[Xantor]

Are the Headunits itself the same size / same connectors? And do they all connect to the same CID that you use? You probably HAD to customize the CID to fit a NBT Screen in the CIC housing. The NBT has a 8,8" Option I think. Does that support all those different ID Versions?

ID6 is nice and slick but for me adds essentially nothing from ID3. I don't use Carplay and Miracast support was dropped in AOSP years ago. The car 3D models are for all intents and purposes un-editable.

Doesn't the ID6 allow for changed pngs as a hero car? The ID3 or 6 sound like the best versions. 6 would be interesting because of increased functionality probably and the apple carplay. How does M drive work with id6?

But id3 would be the more time period - correct system.


BTW: Does the CIC offer the same custom CC possibility? I know you stopped development on your CIC. I still have mine so I could probably test some things if you could provide a small test logic / code.

How and where did you even find that? xD
Cant wrap my head around that.

 

[twinturbos]

Amazing stuff. Now this has me wondering what it could do on an LS-Swapped car with a MaxxEcu standalone that also talks with the canbus. Would be pretty dope to get the dct shift lights working.

 

[superwofy]

Are the Headunits itself the same size / same connectors? And do they all connect to the same CID that you use? You probably HAD to customize the CID to fit a NBT Screen in the CIC housing. The NBT has a 8,8" Option I think. Does that support all those different ID Versions?


Doesn't the ID6 allow for changed pngs as a hero car? The ID3 or 6 sound like the best versions. 6 would be interesting because of increased functionality probably and the apple carplay. How does M drive work with id6?

But id3 would be the more time period - correct system.


BTW: Does the CIC offer the same custom CC possibility? I know you stopped development on your CIC. I still have mine so I could probably test some things if you could provide a small test logic / code.

How and where did you even find that? xD
Cant wrap my head around that.

CIC and ID3 are 2DIN. NBT EVO is 1.5DIN. The quadlock is the same. Yes, the screen had to be removed and re-housed in a CCC shell. I'm using an APIX1 screen with a cheap voltage adapter. There's threads on this.

It does allow custom pngs however that's just the static main menu image. It does nothing for the 3D models that appear everywhere else. I've found a sort of halfway solution where if certain widget files are deleted, the 3D model no longer appears (in those places). You can't just delete the 3D model since it's needed for PDC/camera view and FTM. And you can't edit it because they're is some format that I've yet to understand.

MDrive works the same in ID3/4/5/6.

No, I tried the 0x338 with ASCII chars with the CIC before removing it. It did not work. For now it doesn't work with ID5/6 either.

 

[Adam06]

CIC and ID3 are 2DIN. NBT EVO is 1.5DIN. The quadlock is the same. Yes, the screen had to be removed and re-housed in a CCC shell. I'm using an APIX1 screen with a cheap voltage adapter. There's threads on this.

It does allow custom pngs however that's just the static main menu image. It does nothing for the 3D models that appear everywhere else. I've found a sort of halfway solution where if certain widget files are deleted, the 3D model no longer appears (in those places). You can't just delete the 3D model since it's needed for PDC/camera view and FTM. And you can't edit it because they're is some format that I've yet to understand.

MDrive works the same in ID3/4/5/6.

No, I tried the 0x338 with ASCII chars with the CIC before removing it. It did not work. For now it doesn't work with ID5/6 either.

I'm very happy to announce that I've completed and released the NBT emulation code. I've been working on it for the last few months and it is now a part of the CAN module.

As far as I am aware, this is the only non-commercial solution. Anyone can read the source and modify as they please. No VIN locking, no bs. Everything I've tested so far works.

Since it is part of the module, *some* work is required to run it standalone. I'm not particularly interested in doing that since for my application I don't foresee ever using the car without all the other functions provided.

All CAN message documentation can be found in the txt files of the repo and obviously the source code.

Hopefully this brings some more life to this platform. Happy coding



P.S. This was designed for ID3 however, I've just gotten an ID4 unit that will replace the NBT. It's unlikely I will work on ID5/6 however, they should be mostly functional out of the box.

buddy how to contact you I need your help

 

[meatball]

Salivating at this thread. Can't wait to dig in a little bit with you guys.

 

[superwofy]

buddy how to contact you I need your help

Well, this is a public forum. If it relates to this project I'm happy to answer questions on it.

 

[Adam06]

Well, this is a public forum. If it relates to this project I'm happy to answer questions on it.

the topic is related to this... I don’t understand programming at all And so on, I have a BMW E92 N55 swap dct gws m3 deff m3 3.15 zsl m3 combi m3 dsc m3 everything works only cic MDrive and MDM doesn’t work I need someone to get everything working for me correctly... I There is no such specialist from France, I would like someone to remotely program the car for me

 

[Xantor]

the topic is related to this... I don’t understand programming at all And so on, I have a BMW E92 N55 swap dct gws m3 deff m3 3.15 zsl m3 combi m3 dsc m3 everything works only cic MDrive and MDM doesn’t work I need someone to get everything working for me correctly... I There is no such specialist from France, I would like someone to remotely program the car for me

So to answer some questions:

MDM on a non M car doesn't work. I don't know how and when this will ever happen (1M with the N54 has MDM but afaik nobody could replicate it yet). so you are "stuck" with DTC.

The problem with your Idrive Mdrive is resolved by superwofys Canbus Function Extender. The fields wont populate without it as the canbus module sends the missing data and emulates the way a MSS60 (M3 S65 DME) would send signals.

tl;dr: You CANT code Mdrive to work, you need this canbus module.