[DieStream]

Hello Guys, I need your help.

A friend of me, try to flash his g30 with ISTA 4.31.40 with a eNET cable, but BDC failed and now i try to flash the bdc.
E-sys: Now I want to flash the BDC with eNET but the g30 don’t response.
Have someone any Idea?

<>
SVT-Lesen vor TAL-Abarbeitung gestartet.
TAL-Abarbeitung gestartet.
VCM Update: Automatische VCM-Aktualisierung ist deaktiviert. VCM wird nicht aktualisiert.
<run()-> Value of 'httpServerActivation': true>
<run()-> Value of 'isDeactivateHttp': true>
<MCDDiagService<Id: 84900, Jobname: com.bmw.psdz.jobs.uds.MCD3_ReadFlashTimingParameters, Diagnoseservice: RDBI_FTP - ReadDataByIdentifier FlashTimingParameter, Beschreibung: error: timeout, LogicalLink: BDC_BODY2_40_ETHERNET> [DIAGSERVICE]>
<MCDDiagService<Id: 36900, Jobname: com.bmw.psdz.jobs.uds.MCD3_ReadFlashTimingParameters, Diagnoseservice: RDBI_ADS - ReadDataByIdentifier ActiveDiagnosticSession, Beschreibung: error: timeout, LogicalLink: BDC_BODY2_40_ETHERNET> [DIAGSERVICE]>
<[] Aufgrund eines vorangegangenen Fehlers werden Default-Werte für die Flash-Timing-Parameter verwendet. [WARN]>
<[] - [Exception - BDC_BODY2 - 40] negative response error:
code: the result contains an error
description: Service RDBI_FTP has error in result: [Severity=2051][ErrorCode=53327][ErrorCodeDescription=service execution failed][VendorCode=32768][VendorCodeDescription=VCI-specific error (WRONG_TARGET) occurred: 67][InterfaceErrorCode=0x43][InterfaceErrorCodeDescription=interface-specific error]; LinkName: BDC_BODY2_40_ETHERNET
severity: ERROR
>
<ExecutionID=2022/09/06-01:55:32.693>
<[] "prepareTALExecution" wurde gestartet. [PROGRESS]>
<MCDDiagService<Id: 48900, Jobname: com.bmw.psdz.jobs.uds.MCD3_CheckProgrammingCounterExtended, Diagnoseservice: RDBI_PC - ReadDataByIdentifier ProgrammingCounter, Beschreibung: error: timeout, LogicalLink: BDC_BODY2_40_ETHERNET> [DIAGSERVICE]>
<MCDDiagService<Id: 464900, Jobname: com.bmw.psdz.jobs.common.MCD3_PrepareTALExecution, Diagnoseservice: RC_TAS_ROUTING - Routine Control for TAS, Beschreibung: error: timeout, LogicalLink: TAS_F0_ETHERNET> [DIAGSERVICE]>
<MCDDiagService<Id: 464900, Jobname: com.bmw.psdz.jobs.common.MCD3_PrepareTALExecution, Diagnoseservice: RC_TAS_ROUTING - Routine Control for TAS, Beschreibung: error: timeout, LogicalLink: TAS_F0_ETHERNET> [DIAGSERVICE]>
<MCDDiagService<Id: 464900, Jobname: com.bmw.psdz.jobs.common.MCD3_PrepareTALExecution, Diagnoseservice: RC_TAS_ROUTING - Routine Control for TAS, Beschreibung: error: timeout, LogicalLink: TAS_F0_ETHERNET> [DIAGSERVICE]>
<MCDDiagService<Id: 464900, Jobname: com.bmw.psdz.jobs.common.MCD3_PrepareTALExecution, Diagnoseservice: RC_TAS_ROUTING - Routine Control for TAS, Beschreibung: error: timeout, LogicalLink: TAS_F0_ETHERNET> [DIAGSERVICE]>
<[] "prepareTALExecution" wurde beendet. [PROGRESS]>
<[] null [THROWABLE]>
<[] "prepareTALExecution" wurde beendet. [PROGRESS]>
<[] "finalizeTALExecution" wurde gestartet. [PROGRESS]>
<MCDDiagService<Id: 464900, Jobname: com.bmw.psdz.jobs.common.MCD3_FinalizeTALExecution, Diagnoseservice: RC_TAS_ROUTING - Routine Control for TAS, Beschreibung: error: timeout, LogicalLink: TAS_F0_ETHERNET> [DIAGSERVICE]>
<MCDDiagService<Id: 464900, Jobname: com.bmw.psdz.jobs.common.MCD3_FinalizeTALExecution, Diagnoseservice: RC_TAS_ROUTING - Routine Control for TAS, Beschreibung: error: timeout, LogicalLink: TAS_F0_ETHERNET> [DIAGSERVICE]>
<MCDDiagService<Id: 464900, Jobname: com.bmw.psdz.jobs.common.MCD3_FinalizeTALExecution, Diagnoseservice: RC_TAS_ROUTING - Routine Control for TAS, Beschreibung: error: timeout, LogicalLink: TAS_F0_ETHERNET> [DIAGSERVICE]>
<MCDDiagService<Id: 464900, Jobname: com.bmw.psdz.jobs.common.MCD3_FinalizeTALExecution, Diagnoseservice: RC_TAS_ROUTING - Routine Control for TAS, Beschreibung: error: timeout, LogicalLink: TAS_F0_ETHERNET> [DIAGSERVICE]>
<[] Bei der TAL-Nachbereitung ist ein Fehler aufgetreten. [WARN]>
<[] - [Exception] Job-Ausführung ist fehlgeschlagen: negative response error:
code: exception in job
description: exception in job
severity: ERROR
>
<[] "finalizeTALExecution" wurde beendet. [PROGRESS]>
<TAL-Abarbeitung beendet. [TAL_EXECUTION_FINISHED]>
TAL-Abarbeitung beendet mit Status: "FinishedForHWTransactionsWithWarnings".
TAL-Abarbeitung beendet. Dauer: "22s".
<>
SVT-Lesen nach TAL-Abarbeitung gestartet.
SVT-Lesen nach TAL-Abarbeitung beendet.

[bruce68]

Disconnect the battery negative, wait half an hour to try again, and usually reprogram the BDC successfully

[DieStream]

Disconnect the battery negative, wait half an hour to try again, and usually reprogram the BDC successfully

Doesnt work.

Someone can help me over TeamViewer?

[hojo29]

Is BDC visible in ESYS?

[elthox]

Disconnect the battery negative, wait half an hour to try again, and usually reprogram the BDC successfully

Doesnt work.

Someone can help me over TeamViewer?

Pm me, i can check

[DieStream]

Thx for the help.
I found the "problem"

I dont press the button "HW-IDs from SVTactual"

After them, i can flash the BDC.

All FSCs are reject. Its enough, if i buy a repair fsc?

[sambir]

Thx for the help.
I found the "problem"

I dont press the button "HW-IDs from SVTactual"

After them, i can flash the BDC.

All FSCs are reject. Its enough, if i buy a repair fsc?

who presses this button anyways.... If you calculate the tal and your hwel is different then you calculated wrong... FSC repairpack you can get from bavarianvin.

[Elf11]

Thx for the help.
I found the "problem"

I dont press the button "HW-IDs from SVTactual"

After them, i can flash the BDC.

All FSCs are reject. Its enough, if i buy a repair fsc?

Provide vin can give you fsc repair package

[jaramillo]

Send me the info I can help

[DieStream]

Thx for the help.
I found the "problem"

I dont press the button "HW-IDs from SVTactual"

After them, i can flash the BDC.

All FSCs are reject. Its enough, if i buy a repair fsc?

Provide vin can give you fsc repair package

Thx for ur work.

Here is the vin: WBAJC9104HG942017