Maybe once the new datens are figured out it may fix things. Unless the new ones wouldnt work on mine?

 

Newer datens always work on earlier versions installed on cars. - It's the opposite of that which is an issue.

 

Whats the difference on the Soft or Hart for the parking light 2 for welcome lights?

 

Also, I read on another thread you can activate the alarm light without the hardware. I changed the code in the module but didn't see any difference.

Anyone have an experience with this?

 

Not sure where you read that, because I was the guy working on that (with help from others, including those brave enough to disassemble certain parts for me).

I kind of gave up on it, since it requires wiring the cluster to the passenger fuse area.

 

I think I read it in another thread. I would have thought the lights would already be wired and they just would have to install the horn and stuff but at least the lights would turn on.

No big deal though.

 

The LEDs are physically there, but they are not wired to any power source in non-alarmed cars.

Ergo, you need to specifically send a pulsed signal that the normal alarm-equipped car would send. Coding, alone, won't work.

 

Alright, all - and especially Triple_O - here's what I promised:

These are the very latest datens used on all Mini Coopers produced before this month (pre-10/12):

Version 46.3

The next version will presumably arrive with the 2013 R60 and JCW. That should be Version 47.1, but we'll cross that bridge when we get to that point.

These are getting EXTREMELY difficult to get ahold of, even with legit subs to ISTA. Also, BMW is cracking down pretty hard on this... so enjoy it while we still can.

Triple_O - let me know how these work!

 

Θ,

Interesting...

When you write that "BMW is cracking down", I assume that this means that they have limited the access to the datens file (restricted availability)? Do you think that BMW might institute a more active restriction like instituting (software) "keyed" access to the computer modules? I realize that secured access would mean changes to both the CM modules' software and the software program used to access them. Surely this could only be done in future models that have had the supporting changes burned into the modules' firmware, yes? ("...and stop calling me Shirley").

So, would it be safe to say that as long as you have a current CM and a V45/V46 datens file, you should be able to preserve the ability to change settings via NCSExpert?

TIA,

 

Love the Θ notation!

They are actually going after this twofold according to several BMW Coding sites that have received C&D letters and takedown notices for simple daten files.

I could get into how the datens are actually distributed by BMW, but most of you already know that. It's starting to look like this may move to an online ISIS update instead of discs -- that would be nearly the end of coding (the newer datens, that is) unless we were able to get dumps from the ISTA/ISIS system, which is very unlikely - I've not seen a feasible way to do it with the file system it has.

Anywho... They wouldn't have to change the software security on our vehicles at all - they simply would stop the flow of information and then our newer daten files go *poof*. No way to interact with the higher daten level at that point. So, as I always do unless there's something big, the best bet at this point is to ask the dealer NOT to flash a system update. There is no reason to unless there is a larger issue, but some dealers are flash-happy.

If you have a current Countryman (or really any 2nd Gen), it should have v46.3 or lower. Ergo, you have full coding access with these. The new-productions (JCW R60, Paceman, etc) will presumably have the v47.xx installed, and that's already an issue. Though, the BMW side was able to find a way through and has datens all the way through v47.5 at current, so I'm not too worried yet.

More of speculation for the future, I guess you could say. The name of the game in all of this is "lock up the system". You can see that by the DMEs (removal of OBD flashing, removal of JTAG), and it's only a matter of time here, too.

Ominous music plays....

Or... I could be completely wrong. In that case, I apologize in advance.

 

So is there any reason for us that already coded with the older versions to recode with the newer ones?

Also, would disconnecting the battery possibly reset my sunroof error that I am receiving?

 

No, the newer versions simply interface with the newer software versions on the cars.

Coding changes settings in NVRAM, so a battery disconnect will not do anything for you. If you still can't get everything back to default and start over, you'll need to get a baseline flash / software "update" done at the dealer at your next service appointment.

 

Sorry, I've been away for a while, I'm reading through everything I missed to reply appropriately. In the meantime, Theta, thank you for the files!! I will not be able to test them for a week or two as I won't be meeting with the guy anytime soon. It is a 2013 JCW. Hopefully they will work.

 

Sure thing. If those still don't work, I'll be working on getting the newer ones for the Oct/Nov productions - will take a little while, though.

 

Theta, maybe you could delete the download link(s) and then provide the files to people via PM on an as needed/requested basis. Might be a safer route. Just a thought so you don't get any negative attention your way.

cwileyrrt, you have A LOT of questions. This is not a bad thing, but please read through the thread because many of your questions will be answered already. Also read NCS_DIY atleast 2 or 3 times to fully understand the process. I know it is tempting, but don't rush through it to prevent damaging your vehicle.

1) Reset your entire car to it's default settings and then start coding again. This will ease your mind.

2) INPA is a diagnostic tool that can clear errors for you as well.

3)
SCHIEBEHEBEDACH_TIPP_AUF
SCHIEBEHEBEDACH_TIPP_SENK
SCHIEBEHEBEDACH_TIPP_ZU
SCHIEBEHEBEDACH_TIPP_HEB

For one touch opening and closing, make sure all of these values are set to aktiv. I
have had a couple of situations where the settings for one touch close do not take
effect right away. It may take 20 minutes or so but after that it is fine. The car
may just have to go through a reset. Just code it and wait.

4) You only have to change this 'TUERAUF_STOP_MAUT' in the FRM module. Don't
worry about changing it in any other place.

5) Always read a module, open the .TRC file, save it as a .MAN file and then modify the
.MAN file.

6) Soft is a fade on of the lights and Hart is hard turn on of the lights.

7) For the alarm, Theta is right about the hardware but if the car has any alarm wiring,
you can update the VO with the alarm option and then default the vehicle.

8) For the key in ignition door dong, if you disable it, it may dong for 3 times but then shutoff if that is what you're referring
to.

 

Excellent point! I had forgotten to add that some cars without the alarm package actually did have the wiring. You need to peek at the passenger footwell junction box to see if there is a fuse or physical wiring to the fuse location.

It's rare, but it has happened in the past!

 

I know how to access the fuse, do you know which one is for the alarm?

 

Sooo, I made an appt for tomorrow to get my error light reset. I just tried to reload all my original files to revert my car back to normal before taking it into service.

When I tried to pull up my VIN in the first steps, I get the VIN is faulty error and "No answer from ECU" Although all the lights come on fine in the INPA.

After a little google research, I went ahead and uninstalled all the programs and did a fresh install. This time I also loaded the newest datens.

Still getting the same error.

 

Fuse should be -- F24 5A Electronic immobilizer control unit/Horn for antitheft alarm system EWS

You need to physically trace that circuit to see if you have anything running there. It's very rare - only done when a car is a change order or when a car ordered with an alarm is grabbed to fulfill another order (and does not have the horn and sensor hardware).

As for your coding, at this point there's no telling what's been done. If you're getting it re-flashed tomorrow, it will overwrite everything and you can start from scratch. They won't be able to see anything was done to the car.

 

Well I changed the center tach to show the time and temp as default which isnt the normal set-up. This is the only change they could physically see :/

 

I guarantee you they won't notice or care. I take mine in coded all the time, and after it's flashed all the light warnings come up and the car freaks out.

Everybody just rolls their eyes and moves on. Trust me, you'll be fine.

 

Is it a common practice for them to reflash the car with an error light or something of the sort or do I need to say something specifically to get them to do it?

 

What is the error light (I may have missed that somewhere in your posts)? Can you post a picture?

 

It's about a page back. It's a image of the sunroof.

 

Just an FYI - coding an October 2012 R60 right now, and was able to do everything but the FRM module.

Debugged it, but it's just not compatible with the v46.3 or v46. S keep a lookout for the late MY2012s.