[DayvG]

I have created a guide to show you how to load any FSC codes from any KAFAS2 module into any KAFAS2 ECU. I started exploring this initially as I wanted to flash my KAFAS2 to the latest I-Level to match my car but was told I would lose my FSC codes and need either an emulator or pay for a new FSC set for my VIN. Well I can now confirm that is not true and here is a guide to show you how. I cannot guarantee this will work on your car if you have deactivated FSC codes as this may need a newer set. 

Rep and thanks

[shawnsheridan]

What is your I-Step current? This is only possible with older Firmware.

[DayvG]

What is your I-Step current?  This is only possible with older Firmware.

I flashed the ECU using F10-19-03-530 data, attached is a picture of the KAFAS2 in the SVT. It’s possible, I have just done it. No gimmicks, no emulators, just me and my coding Pad using trial and error.

[DayvG]

What is your I-Step current?  This is only possible with older Firmware.

I’ve attached the log file if you’re interested to see that it’s possible and how it worked.

[smercki]

Thanks for the guide and the time dedicated to writing it, I in simpler way in COMFORT mode in the FSC menu load FA with inside the vin of the fsc package that you want to load and after with the UPGRADE button the fsc is written and activated, without that first go and write vin on the Ecu, and it has always worked.
After this procedure you will find the kafas with the vin of the fsc donor package, just proceed with the WriteDataByIdentifierVIN function to report your correct frame

only precautions if in the kafas2 there are already some fsc, those that go to upload must have more recent date otherwise by error and not overwrite them.
Moreover every time you launch an update plan with IstaP or ista + the fsc will all be rejected, but no problem, you can reload them again with the same procedure

[DayvG]

Thanks for the guide and the time dedicated to writing it, I in simpler way in COMFORT mode in the FSC menu load FA with inside the vin of the fsc package that you want to load and after with the UPGRADE button the fsc is written and activated, without that first go and write vin on the Ecu, and it has always worked.
After this procedure you will find the kafas with the vin of the fsc donor package, just proceed with the WriteDataByIdentifierVIN function to report your correct frame

only precautions if in the kafas2 there are already some fsc, those that go to upload must have more recent date otherwise by error and not overwrite them.
Moreover every time you launch an update plan with IstaP or ista + the fsc will all be rejected, but no problem, you can reload them again with the same procedure

Thats great info, thank you. I have someone attempting to write the FSC to their KAFAS2 but are getting an FGN error. This may be because the FSC currently loaded is newer than the FSC they are trying to load?

I wanted to create a guide that showed people how they can update their modules without needing to spend a lot of money on FSC codes. Its clearly possible but some people refuse to believe or acknowledge it. Maybe because it is they that will lose out on money for sales of FSC codes. Maybe?

[shawnsheridan]

Thats great info, thank you. I have someone attempting to write the FSC to their KAFAS2 but are getting an FGN error. This may be because the FSC currently loaded is newer than the FSC they are trying to load?

I wanted to create a guide that showed people how they can update their modules without needing to spend a lot of money on FSC codes. Its clearly possible but some people refuse to believe or acknowledge it. Maybe because it is they that will lose out on money for sales of FSC codes. Maybe?

FGN Error is VIN related.  If it was due to newer FSC Codes in ECU, one would get an "FSC Creation Date" error.

As for yours working, it is surprising.  I know of several others that without 3-Way VIN Match between Car, KAFAS, and FSC Codes, the FSC Codes are Rejected.  And when an Emulator is hooked up, the FSC Codes suddenly become Accepted, indicating VIN checking is in fact utilized.  Why yours worked and others didn't, I have no idea.  Maybe some KAFAS firmware versions are checking and others are not, or maybe there is some other unknown explanation.  People retrofitting KAFAS though should certainly try Donor FSC Codes and see if it works before buying VIN Matching FSC Codes or an Emulator.

[jackylooo]

Below is the error I got after I followed the step described in the post:

negative response error:
code: RoutineControl returned negative response
description: service Routine Control Verify FSC returned positive response with with result status = FGN_CHECK_FAILURE; LinkName: KAFAS2_5D_ETHERNET
severity: ERROR

I think there should be some additional condition are required before the mentioned procedure can work.

Maybe this method only work with car equipped with CAS?

[shawnsheridan]

Below is the error I got after I followed the step described in the post:

negative response error:
code: RoutineControl returned negative response
description: service Routine Control Verify FSC returned positive response with with result status = FGN_CHECK_FAILURE; LinkName: KAFAS2_5D_ETHERNET
severity: ERROR

I think there should be some additional condition are required before the mentioned procedure can work.

Maybe this method only work with car equipped with CAS?

Did you write FSC Code VIN to KAFAS?

Are you specifying VIN on E-Sys Import Screen that matches the FSC Code VIN, not car VIN?

[DayvG]

User Jackylooo has a theory. My TALEexecution failed when flashing the KAFAS2, it looks like the CDdeploy timed out, possibly due to ICOM clone. I carried out all of the FSC steps with no CAFD injected. Tonight I am going to flash my original donor KAFAS2 with my ENET and ensure CAFD is loaded prior to FSC work to see if I get any errors. If it doesn’t work I will flash again without CDdeploy checked and then carry out the FSC steps. Would an easier way to remove the CAFD be to code default values? I’m sure I read that it effectively removes the CAFD specific vehicle coding.