iDrive 6 + Keyless entry + BMW Connected Drive

[YoitsTmac]

Small update. The encryption thing of head units is a big problem. I think it happens when you have a head unit registered with BMW connected services. It wants the signed cert or something like that and it has this lock to prevent online services abuse. I have someone claiming to bypass it and they're sending me their module so I can look at it and reverse engineer.

My aux chord on my car now only plays on the right side. So I'm speed running any implementation into the e46, even if it's not fully baked.

That means I had to turn back to my bezel. My bezel is about 3mm too narrow. I had to double check all my measurements and it seems the person who printed it may have an accuracy issue.

I bought a spare dash just to r&d with. Unfortunately, the Idrive screen is basically the size of the opening. It's going to take some really careful engineering. I may have to hit up Heinz for my soldering of the chip to communicate with the E46 and to also talk about mounting the head unit and amp in the trunk.

[Bry5on]

All part of the process! Of course nothing is ever easy

[YoitsTmac]

I figured everyone deserved an update, so here we go. It's taken me a while because I've also been restless about figuring out what's going on with my car. I'd love if you could weigh in if you feel you have any ideas what's going on because I'm at a lost. I digress. Lots of updated, good news and bad news.

Good news: the headunit wasn't bricked. And in fact, the signal I pass to headunits is sufficient to power them on. Unforutnately, I have to return the unit I bought, but that's not a big deal.
Bad news: After discussing with others, it seems that GPS signals are passed to the iDrive 6 unit not over CAN but over OABR. I have to reinforce that I am a software dev first and a hardware guy far second. OABR is just so far from my wheelhouse - it's effecrtively ethernet. So you'd need an iDrive unit with a GPS plug (if you're out of the loop: rare) or to get an ATM (the telematics) that are paired to a used headunit.

I also want to be clear I have been really focusing on the connectedDrive aspect. Apparently, once you want to give someone cellular, the FCC won't let me be and let me be me. I have spent hundreds in dev boards for modems, and found the least fun way to burn $300 by accidently connecting power to the GND of a NLA dev board for cellular. It's been mountains of frustration.

I have also been working hard on building the backend server to manage all cellular (and mobile) devices, so that when you want to remotely lock your car, your phone has a server to tell what you're trying to do, and a server that can make that request to your car on your behalf, and then return a confirmation of success to you. It handles all your connectedDrive aspects and features. It also means that if someone disconnects power to your car when your away, a battery backup with my chip can send that to my server, to notify you, and start updating your location more frequently. Being able to also be notified that your car is started when you're not in range is another feature I want to bring - especially for those without EWS. Another feature I think I want to bring is the ability to set time windows or conditions that your fuel pump will work. This is adopted as an additional layer of theft deterrance and admittedly, was more designed in mind of cars with keyless entry.

Outside of security, my intended features are really trip logging. You can see average fuel burn, cool stats about your driving habits, comparisons with other people that share your drivetrain, and insights on your warm-up procedures. And just like the BMW ConnectedDrive app, you'll see how your driving behavior, distance, MPG, number of trips and time at WOT compare against other people with my connectedDrive chip. You can also share drives and manually start a "sport drive" to record a good driving road with others. I think it'll be a really great communnity tool.

If anyone here has a mind like me, you're probably already seeing other ways you'd want data from your car recorded. I'm trying to avoid scope creep and have an achievable goal. I plan on launching a website soon where I'll have a community page where people can vote and suggest future features. Since I control the full stack, it's easy to start requesting more information from the car, and updating thebackend to save it and updating the mobile app (and maybe future website?) to support it. If I felt I could identify CE codes on CAN, I would offer that as well. I also want to keep the installation as easy as possible. I will likely make an interception harness on the steering angle sensor as a point of install. If that is my path, going to OBD may not be very approachable to some.

Keyless entry is in the name of this thread so I want to address it. I've definitely back-burnered this. Please read in entirety to understand why. One, I'm sure you can feel it, but I feel a lot of passion behind building this connectedDrive aspect of the car. I think that's something a lot of people can get excited about. If you can't, please wait until I finish my implementation to demo the app I have. It has moved mountains since it was last shared. I'm just not ready to show it off quite yet. Two, the installation difficulty is a real thing. There are tons of pros and cons to various methods, along with genuine power and security implications if I wanted anyone else to be able to follow along. The idea is far from abandoned, but definitely back-burned. Third, the keyless entry system needs to be isolated and simplified. I want it to be able to work fully independently so that if say, my connectedDrive board were to freeze, it wouldn't prevent someone from starting there car.

And my last point is with iDrive. Still damn near top of the list, but here's how it's going to work. Anyone can get the connectedDrive-like board, and then iDrive can add iDrive onto it later. Every board will essentially be iDrive ready. But, iDrive is expensive. The headunit, the screen is roughly $500 on it's own, then printing the buttons and the screen bezel. Then the PCB to control the buttons. You also need BT and Wifi antennas for CarPlay. And likely a $100 cable for the screen to run the length of the car. I think to some, like many in this thread, it is totally cool and worth it, but it's difficult.

iDrive allows me to do some really cool stuff too. Set your coolant warning temp in the app and have iDrive bing when it gets hot. Same with voltage (uncustomizeable, just whatever factory's threshold is). I can send unique notifications to the headunit, auto-dim with the rest of your car. I want it desperately and already bought a MOST amp, so it's near the top of my list.

Hoping to share more concrete and exciting stuff soon.

[YoitsTmac]

Update to keep people up to speed. I am working with PCB designers to design the board itself. Here were my big requirements for the board:

• LTE connectivity
• GPS tracking
• iDrive expandable compatibility
• Tolerant to the noise and voltage variability of a car
• Direct read of voltage to report to you and also to know when it's time to switch the board off
• Ability to turn off modules to enter a more power-efficient state to be ready for remote commands for longer

I also have expanded the featureset a little bit. I wanted there to be a little bit for everyone, so I'm also adding a maintenance tracking tool. Obviously, if you have my little board plugged in, I always have your odo and can give you reminders like "oil change coming up!" etc.

You'll also be able to click or hold a button in your car (TBD) to then activate a "sporty drive" and you can share those with other people! Great way to share driving routes. I'll share the name in my next big update because I need to secure the domain and the like.