[inspi1981]

Unit doesn't communicate. Go to dealer and buy new Keyless Ride for Your VIN.
Keys are allready preprogrammed

[Almostsobur]

Unit doesn't communicate. Go to dealer and buy new Keyless Ride for Your VIN.
Keys are allready preprogrammed

I don't mean to question you, but are you sure about that? Because that's the point I'm at. If I can just verify ownership and give them the VIN and it's preprogrammed for the FOB I already have, I'll go down and buy myself that Christmas gift tomorrow. It's either that or a divorce and a new keyless ride will be much cheaper. The woman is very close to pulling an insurance job on this bike in our own garage.

---

Below is what I get with E-sys. I can't inject a NCD, similar message, it's all red.

<>
Read SVT before TAL execution started.
Checking Mirror-Protocol started
Mirror-Protocol: no token required
Read SVT-Reference started
Checking Programming Protection "BASIC" started
Flashing does not require a Programming Protection "BASIC" token
Checking Programming Protection "PLUS" started
Flashing does not require a Programming Protection "PLUS" token
TAL execution started.
VCM Update: VCM-Update is deactivated. VCM will not be updated.
<httpServerActivation: true>
<isDeactivateHttp: false>
<MCDDiagService<id=84900, job=com.bmw.psdz.jobs.uds.MCD3_ReadFlashTimingParameters, service=RDBI_FTP - ReadDataByIdentifier FlashTimingParameter, description=error: timeout, link=X_SLZ_40_ETHERNET> [DIAGSERVICE]>
<[] use default timing parameters as an exception occured [WARN]>
<[] - [Exception - X_SLZ - 40] negative response error:
code: TIMEOUT P2/T2 occurred
description: P2 timeout on Service RDBI_FTP has error in result: [Severity=2051][ErrorCode=58640][ErrorCodeDescription=resource not available][VendorCode=2142][VendorCodeDescription=P2 timeout occured]; LinkName: X_SLZ_40_ETHERNET
severity: ERROR
>
<ExecutionID=2023/12/22-00:47:56.188>
<[] prepareTALExecution started [PROGRESS]>
<[] prepareTALExecution finished [PROGRESS]>
<[] prepareVehicleForFlash started [PROGRESS]>
<[] prepareVehicleForFlash finished [PROGRESS]>
<MCDDiagService<id=46900, job=com.bmw.psdz.jobs.uds.MCD3_GetSVKfromECU, service=RDBI_SVK - ReadDataByIdentifier SVK, description=error: timeout, link=X_SLZ_40_ETHERNET> [DIAGSERVICE]>
<MCDDiagService<id=46900, job=com.bmw.psdz.jobs.uds.MCD3_GetSVKfromECU, service=RDBI_SVK - ReadDataByIdentifier SVK, description=error: timeout, link=X_SLZ_40_ETHERNET> [DIAGSERVICE]>
<MCDDiagService<id=46900, job=com.bmw.psdz.jobs.uds.MCD3_GetSVKfromECU, service=RDBI_SVK - ReadDataByIdentifier SVK, description=error: timeout, link=X_SLZ_40_ETHERNET> [DIAGSERVICE]>
<[X_SLZ - 40] There was an error during TAL execution, please check the log files. [WARN]>
<[X_SLZ - 40] - [Exception - X_SLZ - 40] negative response error:
code: TIMEOUT P2/T2 occurred
description: P2 timeout on Service RDBI_SVK has error in result: [Severity=2051][ErrorCode=58640][ErrorCodeDescription=resource not available][VendorCode=2142][VendorCodeDescription=P2 timeout occured]; LinkName: X_SLZ_40_ETHERNET
severity: ERROR
>
<[] null [THROWABLE]>
<[] finalizeVehicleFlash started [PROGRESS]>
<[] finalizeVehicleFlash finished [PROGRESS]>
<[] finalizeTALExecution started [PROGRESS]>
<[] finalizeTALExecution finished [PROGRESS]>
<TAL execution finished [TAL_EXECUTION_FINISHED]>
TAL-Execution finished with status: "FinishedWithError".
TAL execution finished. Duration: "27s".
<>
Read SVT after TAL execution started.
Read SVT after TAL execution finished.

---

Couple more    

[simaservis1108]

Insurance and divorce over a bike,are you 5 year old or something?

[TheNine90]

You can get someone to sell you a used SZL unit. Use BMW explorer to unlock, match ISN and program key.
Had a similar case when the SZL was missing coding data, both esys and bmw explorer couldnt fix it. Owner bought used SZL and the unit was matched using BMW Explorer.

[Almostsobur]

Insurance and divorce over a bike,are you 5 year old or something?

Very useful post, I thought it would be obvious that I was being facetious.


Quick update, part is on order from local dealer, should be in sometime this week. Almost a $1000.00 mistake but thinking back and looking back at pictures I took; at some point I was able to talk to that keyless unit. I think somewhere along the line of bench and bike connect/disconnects, I must have shorted the unit, because at some point I could not talk to it on the bench or bike. Moral of the story, if you screw something up, still try to be careful, in case it is fixable. I think I got frustrated and was being careless at some point.

[Almostsobur]

Just a follow up, ordered new Keyless from BMW, had to wait 3-4 weeks, because apparently BMW flashes them for the bike itself, as it had my VIN on the box and worked as soon as I plugged it in. Bike is perfect again, even after I flashed it and finished the job I was working on when I bricked it. Most expensive mistake I've made in a while, just under $1000 USD. Live N Learn. Thanks for the help and efforts all.