[arturjfonseca]

Hi everyone.

Really need your help!

Last night I was trying to code a replacement FRM3 to a E84, using IstaP.

It prompted me with new modules detected in car, which I tought it was strange, but decided to code them as well in process, so choose Complete Programming.

Suddenly it stopped programming, and showed me Final Report with indication of Cancelled by User, and after that car won’t start and can’t even comunicate with any diagnostic tool.

Tried with IstaP, Inpa, Launch diagnostic tool and there are no modules recognized!

The car was connected to a Battery stabilizer!

How can I get comms back? I believe that ZGM probably lost it’s configurations during the programming action!

[lustek]

Hi,

First of all - ISTA-P is for programming, not coding.

Complete programming is releted with multimedia modules such as CCC, CIC etc. and if they should be excluded from execution plan or not.

I think you crash CAS module while programming. Try expert mode with WinKFP. Or write good dump and correct ISN

[arturjfonseca]

You're right.

English is not my maiden language, and when I wrote code I mean program.

All I wanted was to program the replacement FRM3 to the car, and completely messed up.

I'll try with WINKFP, so let'see what happens. Hope it works, as car isn't mine, and the owner is rightfully upset with this.

If Winkfp works do I need to run NCS Expert afterwards?

[Beard]

Hello.
Does the ignition turn on?
Try synchronizing CAS and DME using ISTA+ or INPA. Maybe after this it will start,
try connecting the old FRM first.
Your car data is there.
If you replaced only the FRM, you first had to write your car FA and your VIN into it using NcsExpert.
The ISTA-P can then be interrogated.
In general, there is Winkfp for programming.
It’s better to ask ISTA+
Your vehicle data is stored in CAS and FRM

After replacing a block, you must encode it.
Read your vehicle's data from CAS, write that data and your VIN into your new FRM, and then be sure to encode using NcsExpert.

[arturjfonseca]

Yes, the ignition turns on, the car cranks but no start.

Some things work other won't... for example windows works but the remote won't open/lock doors

[Node]

WHY don't you just read all faults and present here??? Everything would be more or less CLEAR what is going on. Now you ask us to GUESS what COULD have gone wrong...

[arturjfonseca]

WHY don't you just read all faults and present here??? Everything would be more or less CLEAR what is going on. Now you ask us to GUESS what COULD have gone wrong...

I would really like to present here all faults.

However as I explained in first post I can't communicate with car, so I can't read fault codes.

If you have any suggestion on how I can read them, please share.

Thank you for your help.

[Node]

Ah ok. Then your new FRM3 is dead. If you have tools to read flash from it you can try repairing it. It's what FRM3s do

What was the issue with original one?

[arturjfonseca]

The old FRM was dead, and it was replaced with a 2nd hand with same OEM number. Upon install the car worked and apparently everything was working properly with the exception to the side mirrors.

When I tried to programm it with ISTA-P, something happened that cancelled the programming without any intervention from me, and then the car wouldn't start, and all communication with car was lost.

Tried connection with INPA, that returned "No connection to the module", ISTA-P could retrieve VIN from car, and even when I mannualy introduced it, couldn't get any connection, and my Launch Diagnostic tool showed all modules in grey, which for this diagnostic tool those modules are not installed.

Once I get to the car, I'll try to connect with ISTA+ and see if I can connect to any module.

[Node]

You are not able to connect to any unit because ALL diag comms in E84 are going through FRM3. FRM3 are known to die due to EEPROM emulation faults. So clearly old FRM3 developed this issue and new one was one the verge of the issue. So it died during firmware update. Just accept it, it happens. If you would have done just coding, it would have died EITHER. With no fault of yours.

FRM3s can normally be revived by using programming devices to repair and rewrite emulated EEPROM.