I agree. I'm thinking some of our difficulty was trying to code shared modules (CIC, KOMBI) as an M3 but with our VO set as a 335i(s).
Discussion about issues encountered whilst converting to M3 Flash and GWS
- Thread starter aus335iguy
- Start date
I agree. I'm thinking some of our difficulty was trying to code shared modules (CIC, KOMBI) as an M3 but with our VO set as a 335i(s).
Exactly. Besides throwing a couple things in the VO, there's nothing we're doing that differentiates us from a M3. Maybe with that M3 code added in for coding, KOMBI, CIC, and whatever else actually defaults to M3 values and operates as such without touching a thing.
Exactly right guys, everything correct. It is a euro spec as said, it just happens to be the one I remember at the top of my head. Since we want the euro MDM and that will have us mdm values etc, it's fine to stick to euro, perhaps to KG 93 for the US guys 
Please be super careful with other modules using in this method. It's generally fine but you need as follows.
1. When you read the first file the first time make a backup. Besides the obvious it useful to compare the your original 335 spec files to the backed up m3 you read and the default file it flashed.
2. An example of something silly to do would be to flash say a retrofitted m3 kombi as a m3 vehicle type and forgetting to analyse all the 335 value for service interval rev limit on the cluster etc so you can have it operate correctly as allot of it would be the same but also very much different. This is where ncs dummy comes in handy. Just always have a backup you can copy paste over everything and always take a photo of the version numbers in ncs before you hit execute for sg_coderen . The version numbers are not like zb and do not need to match. Ncs will get it correctly.
3. It's very important to remember just because something of the same label have a value like wert 01 in both 335 and m3 specs for example, DOES NOT mean they are the same 100%. This is where netodat coding in ncs comes in handy. There is a document made by some called revtor I think who created ncs dummy and he explains what netodat coding is and how to understand it extremely well.
Good stuff, keep at it, here if you need me.
Please be super careful with other modules using in this method. It's generally fine but you need as follows.
1. When you read the first file the first time make a backup. Besides the obvious it useful to compare the your original 335 spec files to the backed up m3 you read and the default file it flashed.
2. An example of something silly to do would be to flash say a retrofitted m3 kombi as a m3 vehicle type and forgetting to analyse all the 335 value for service interval rev limit on the cluster etc so you can have it operate correctly as allot of it would be the same but also very much different. This is where ncs dummy comes in handy. Just always have a backup you can copy paste over everything and always take a photo of the version numbers in ncs before you hit execute for sg_coderen . The version numbers are not like zb and do not need to match. Ncs will get it correctly.
3. It's very important to remember just because something of the same label have a value like wert 01 in both 335 and m3 specs for example, DOES NOT mean they are the same 100%. This is where netodat coding in ncs comes in handy. There is a document made by some called revtor I think who created ncs dummy and he explains what netodat coding is and how to understand it extremely well.
Good stuff, keep at it, here if you need me.
This is correct and mostly works that way. However it always needs to be checked. You will eventually create 1 file that suits your car using your original 335 file for base values for most things and those changes in the default file written to the module is what it needs, this is where all the time will go, but it's fun.
If your a e91 wagon car and you flash the m3 coupe vehicle type cic file, which car do you think will appear on the screen in reverse gear. That's why having your original file and chafing the value in the default file you flashed is important.
It can be buggy that why it's always important when you have the perfect file save it and keep it so you don't need to do it each and every time. For example, if you have servotronic in a non m3 the jbbf value is something like servitronoc_ventil and even with then SA code added, ncs default flash always has it turned off, which is should not do. Time and analysis is the key and of course a little common sense. 2 other pointers,
1. Never process whole car, not a good idea as painful as it can be working out all the values.
2. The first time your in NCS, when you hit the back button, go back to your work folder and you will see a 255kb files who h has all your value for all modules. Copy it to your backup, it's great to have but do not rely on it solely as I've see problems. The independant individual files are better.
3. Since the car stores VO in 2 places the cas and nfrm, design a method in your hard. For example original parts coding always through cas, retrofit coding always through nfrm, this way you won't make a mistake and you always have your original VO handy quickly.
4. It's probably best to also change the build date in the VO, that's at the top like for example #0909
This words for things like say your original car is #0308 and you have retrofitted combox media. CMedia won't appear in the list because it was not available until something like #0311 . Once you punch in 0311 it appears in the list.
Revtor pdf is a great read for netodat for who over is keen. Understanding that you can do things which are impossible in a regular trace files but not necessary for what your doing here.
I'm pretty stoked. The DSC box coded and goes through all adjustments fine. This is where we are at with the errors as of now. I think 00CDAD is the front wheel speed sensors. I bought M3 sensors, but was sent regular 335i sensors . I'll need to get some M3 sensors to clear that. The other two 00D378 and 00D379 I'm not so sure on. I'll dig more into those tonight.
. I'll need to get some M3 sensors to clear that. The other two 00D378 and 00D379 I'm not so sure on. I'll dig more into those tonight.I doubt the EU/US is very different overall in DSC, was more for the sedan vs. coupe vs. convertible thing. E90/E92/E93 have different coefficient values for various things.Exactly right guys, everything correct. It is a euro spec as said, it just happens to be the one I remember at the top of my head. Since we want the euro MDM and that will have us mdm values etc, it's fine to stick to euro, perhaps to KG 93 for the US guys
I was planning to put this off until after I sold the house now, but I'm kinda chomping at the bit here. Appreciate all your insights!
@dyezak still on the 2.56 diff? How are things now or are you still coding bits?
I'm pretty stoked. The DSC box coded and goes through all adjustments fine. This is where we are at with the errors as of now. I think 00CDAD is the front wheel speed sensors. I bought M3 sensors, but was sent regular 335i sensors
View attachment 9969
Well done.
Reverse gear switch is an adjustment in the dsc coding, under tranmission type o think and the other is sensors I believe.
Dsc no message does not ring a bell.
Very close now mate.
I'm pretty stoked. The DSC box coded and goes through all adjustments fine. This is where we are at with the errors as of now. I think 00CDAD is the front wheel speed sensors. I bought M3 sensors, but was sent regular 335i sensors
View attachment 9969
Derek, also play with 2MK (mdct with drove logic) in the VO (as m3) since your running the gts tune instead of the 335 dct, code the dsc and tcu with that and play with those settings.
I think you will be pleasantly surprised
Derek, also play with 2MK (mdct with drove logic) in the VO (as m3) since your running the gts tune instead of the 335 dct, code the dsc and tcu with that and play with those settings.
I think you will be pleasantly surprised
And do not forget backup and compare files as it will give you all the clues.
Notepad ++ has a very nice compare plugin, I found it really good.
Derek, also play with 2MK (mdct with drove logic) in the VO (as m3) since your running the gts tune instead of the 335 dct, code the dsc and tcu with that and play with those settings.
I think you will be pleasantly surprised
Yes, I have 2MK in my VO.
And I've been using Excel with a DIFF script that compares two TRC files and highlights the differences.
This wheel speed sensor thing pissed me off. Shady people selling mis-branded items. I'm going to call it a night. See you guys tomorrow!
That's more like it
Msa usually refers to stop start system but it should not affect the car.
Have you driven and tested it yet ?
Derik,
I have a strange feeling these errors are unrelated to wheel sensors.
Try and clear absolutely all adaptations from engine and gearbox and see what happens. If that does not work code our cruise control all together and see what happens.
I think it will fix it.
That's more like it
Msa usually refers to stop start system but it should not affect the car.
Have you driven and tested it yet ?
I just took it on a test drive. I agree, not the wheel speed sensors, as I had no problems driving. If the front speed sensors are a problem and the rears are working you get the traction control light.
I think the active cruise coding may not be right.
I'll reserve adaptation clearing for after I double check ACC coding to ensure it is off everywhere.
EDIT: And BTW the DSC didn't fix the mushy shift into 4th gear. I didn't go above that. Once I saw the mushy 4th gear shift I came home.
On a side note, My R270+ showed up yesterday and I set it up and tested it on a blank ROM. Works flawlessly. My SOIC8 Test Clip is out for delivery now. When I get it I will virginize the M3 KOMBI I have (wipe the milage and VIN) then I'll code that in with the VO trick we used on the DSC.
ALSO!! The M3 DSC requires the hard wired connection to the DSC button (can't use the factory 335i DSC button). It can't go through the JBB (junction box) like the 335i. So you'll have to add that pinout to be able to control your DSC.
ALSO!! The M3 DSC requires the hard wired connection to the DSC button (can't use the factory 335i DSC button). It can't go through the JBB (junction box) like the 335i. So you'll have to add that pinout to be able to control your DSC.
Would coding US_VEHICLE and MDYNAMIC_MODE_US to nicht aktiv in a DSC flashed with a US M3 code accomplish the same thing? I know that's what I've done for guys locally that wanted Euro MDM enabled and it definitely made a difference. The steering coefficients can be changed individually but without Servotronic and a M3 rack I don't think it would make a difference, correct?Definitely go with euro dsc. It's difderent to US mdm and much more liberal and gives you much more rope to hang yourself
The coefficients can be changed, probably not a good thing however certainly not to experiment
Similar threads
