switch to BM3 from HEX tune fault code.

[stanqian]

Hi guys, I'm new to the BM3 tunning platform and very excited to test it out. so I decided to reflash my Hex stage 2 tune to BM3 OTS stage 2. However, when I successfully flashed the DME, Drivetrain Malfunction, max power not possible warning showed up and the car drives like there is no boost at all.

DME fault code: 1F2102, according to BM3.

Here is what I did:
I re flashed my Hex tune to the stock file using VF cable and flashed the BM3. I first flashed OTS stage 2 93 octane, same problem and fault code. I thought it could be the gas because I had 92 octane at that time so I purchased the 91 octane file and re flashed, no luck. Tried to use the online recoding tool, nothing.

Now my car is back to the Hex tune and no problem. Can anyone help me to figure out what is going on? Is it the gas problem? I really want to try out the BM3 and don't want to waste my money.:

[nioh_lbbm2]

Open a ticket with BM3. They're very fast to respond and assist with technical issues like this

[f80_sturmgewehr]

Open a ticket.

I made the switch and also ran into issues. For some reason VF had coded my non ZCP car as a ZCP so when the shop went to install bootmod3 all kinds of codes came up. I do not remember them off the top of my head but the car was then not recommended to be driven until PTF resolved it, which they did swiftly.

[stanqian]

Opened ticket with BM3 and they are figuring this out. Will report back when this is fixed.

[stanqian]

Originally Posted by f80_sturmgewehr

Open a ticket.

I made the switch and also ran into issues. For some reason VF had coded my non ZCP car as a ZCP so when the shop went to install bootmod3 all kinds of codes came up. I do not remember them off the top of my head but the car was then not recommended to be driven until PTF resolved it, which they did swiftly.

Seems like VF coded our car in a unique way and need special treatment when switching.

[dheanswer]

Originally Posted by stanqian

Seems like VF coded our car in a unique way and need special treatment when switching.

I made the switch without issues. I flashed back to stock using the HEX cable and went to BM3 without issues after.
Not sure if it depends on the year, mine is a 2016.

[stanqian]

Problem solved! Serge from OTF remoted my computer and did some coding behind the scene. Now the car runs perfectly and no more warnings. He said the coding from the DME when I flashed back to stock was all messed up and need to be manually recoded. I'm so impressed with their costumer service.

The power is so linear and my clutch is much easier to operate now. unlike VF tune the power is really on after 5500 rpm which I dislike when driving on the track.

[FSociety]

Originally Posted by stanqian

Problem solved! Serge from OTF remoted my computer and did some coding behind the scene. Now the car runs perfectly and no more warnings. He said the coding from the DME when I flashed back to stock was all messed up and need to be manually recoded. I'm so impressed with their costumer service.

The power is so linear and my clutch is much easier to operate now. unlike VF tune the power is really on after 5500 rpm which I dislike when driving on the track.

Serge from PTF u mean .... and its OTA (Over The Air)

[ruley74]

Funny, my ECU was coded as a CS when VF did my tune... they seem very random. Alex but mine back to original non-zcp prior to loading his tune, he picked it up as soon as he connected and seem the SWFL mismatch.

[FSociety]

Originally Posted by ruley74

Funny, my ECU was coded as a CS when VF did my tune... they seem very random. Alex but mine back to original non-zcp prior to loading his tune, he picked it up as soon as he connected and seem the SWFL mismatch.

Alex from Alpine?

So many issues ppl switching from VF because of the wrong software version its crazy the past month I've seen/read about 5 ppl (random locations too). Just saw 2 locals who got offered free ECUTEK beta and that is also screwing up their stock version with a DTMAL they can't get rid of now.

[ruley74]

Originally Posted by FSociety

Alex from Alpine?

Yes

[VF-Engineering]

Hey Guys,

Just to be clear, our software (whether Stock File or Tuned) does
not affect the coding of the vehicle in any way.




Without getting overly technical this type of incompatibility error
would only occur if...

(1) The ECU is flashed with another brand of software with our
tuned software version still present in the ECU.

-or-

(2) The ECU version is read by the 3rd parties system while our
tuned software version is still present in the ECU.




It is ALWAYS strongly recommended that when switching between
any brand(s) of software that the ECU is properly flashed to stock
and test driven before any subsequent reading/writing/flashing
activities are performed.

This is a required step when we are contacted by customers looking
to switch to our software from another brand, and similarly when we
are contacted by customers before they switch to another brand.

[tom @ eas]

Originally Posted by FSociety

Alex from Alpine?

So many issues ppl switching from VF because of the wrong software version its crazy the past month I've seen/read about 5 ppl (random locations too). Just saw 2 locals who got offered free ECUTEK beta and that is also screwing up their stock version with a DTMAL they can't get rid of now.

Originally Posted by f80_sturmgewehr

Open a ticket.

I made the switch and also ran into issues. For some reason VF had coded my non ZCP car as a ZCP so when the shop went to install bootmod3 all kinds of codes came up. I do not remember them off the top of my head but the car was then not recommended to be driven until PTF resolved it, which they did swiftly.

Had 2 cars here with the same issue going from VF to BM3, and had to reflash the DME to true stock on our end. Caused all sorts of issues on on the BM3 end as the car was being identified incorrectly.

[VF-Engineering]

Originally Posted by tom @ eas

Had 2 cars here with the same issue going from VF to BM3, and had to reflash the DME to true stock on our end. Caused all sorts of issues on on the BM3 end as the car was being identified incorrectly.

As we stated above, this issue is only possible if the process is
being performed out of sequence.

IE: the "read" / "identification" process being performed prior to
flashing back to stock.


The Stock file we provide is a TRUE Stock File,... and as long as
the read being performed by the next tuner is performed after
the ECU is properly flashed to stock - the end result is exactly
the same as flashing a brand new car from scratch.




We see the SAME issue when customers switch to VF Engineering
from other brands without properly flashing the car to stock first.

There are also a number of of cases with similar instances of BMW
Dealerships attempting to apply software updates to "tuned" ECU's.




This is why we have always been diligent about flashing both the
program and data area (file size: 4096k), as opposed to data area
only, which helps prevent this issues in most (but not all) circumstances.

Originally Posted by VF-Engineering

Solution?

It is ALWAYS strongly recommended that when switching between
any brand(s) of software that the ECU is properly flashed to stock
and test driven before any subsequent reading/writing/flashing
activities are performed.