[®win]

First session with ESYS, went through the following steps:
- hooked up computer to cable, then connected cable to car (engine running)
- started ESYS (expert mode, coding)
- clicked Connect button, connection via VIN (vin displayed is correct)
- Read -> FA activated
- Read (ECU)
So far, so good.

But then I selected the CAFD from FEM_BODY with the green button, right mouse click and selected 'read coding data'. That's where I get the following error

Transaktions-Report:       Aktion: Codierdaten lesen


CAFD_00000794_015_048_005 Fehler:
CPS read from ECU "ECUId:FEM_BODY_0x40" failed! [C070]
openECUConnection for link FEM_BODY_40_ETHERNET failed
with error MCDError Severity: 2051, Error Code: 49184, 
Description: Object with name not found, Vendor Code: 3, 
Vendor Description: provided name FEM_BODY_40_ETHERNET 
doesn't map to an item [1694]

Where do I go wrong?


More info:
car: BMW F31
PC: Win10 laptop, with ESYS (version from kretzu )
Windows firewall disabled
Ethernet connection succeeded

[Almaretto]

Originally Posted by ®win

First session with ESYS, went through the following steps:
- hooked up computer to cable, then connected cable to car (engine running)
- started ESYS (expert mode, coding)
- clicked Connect button, connection via VIN (vin displayed is correct)
- Read -> FA activated
- Read (ECU)
So far, so good.

But then I selected the CAFD from FEM_BODY with the green button, right mouse click and selected 'read coding data'. That's where I get the following error

Transaktions-Report:       Aktion: Codierdaten lesen


CAFD_00000794_015_048_005 Fehler:
CPS read from ECU "ECUId:FEM_BODY_0x40" failed! [C070]
openECUConnection for link FEM_BODY_40_ETHERNET failed
with error MCDError Severity: 2051, Error Code: 49184, 
Description: Object with name not found, Vendor Code: 3, 
Vendor Description: provided name FEM_BODY_40_ETHERNET 
doesn't map to an item [1694]

Where do I go wrong?


More info:
car: BMW F31
PC: Win10 laptop, with ESYS (version from kretzu )
Windows firewall disabled
Ethernet connection succeeded

You selected incorrect chassis in launcher or connection target in e-sys.

• Launcher: F031
• E-sys: F020 (without _direct)

[®win]

I don't recall selecting a body type. Isn't that selected at startup of ESYS?



Ah, I see, I missed a step.

TargetSelector: Project=F020_11_07_504, VehicleInfo=F020

F020 – 2, 3, 4 Series (all) (including ///M variants and Alpina variants)


I'll try again tonight. Thanks!

[Almaretto]

Originally Posted by ®win

I don't recall selecting a body type. Isn't that selected at startup of ESYS?



Ah, I see, I missed a step.

TargetSelector: Project=F020_11_07_504, VehicleInfo=F020

F020 – 2, 3, 4 Series (all) (including ///M variants and Alpina variants)


I'll try again tonight. Thanks!

If you are using Launcher Pro, then no chassis is selected.
But, you always select connection target.

Yes,

• F001 psdzdata covers F001/F002/F003/F004/F007/RR04/RR05/RR06 (5-Series GT = F07 ≠ F10)
• F010 psdzdata covers F006/F010/F011/F012/F013/F018
• F020 psdzdata covers F020/F021/F022/F023/F030/F031/F032/F033/F034/F035/F036/F080/F082/F083/F087
• F025 psdzdata covers F015/F016/F025/F026/F085/F086
• F056 psdzdata covers F039/F045/F046/F047/F048/F049/F052/F054/F055/F056/F057/F060
• I001 psdzdata covers I001/I012
• RR01 psdzdata covers RR01/RR02/RR03
• S15A psdzdata covers F090/G001/G002/G011/G012/G030/G031/G032/RR11/RR12/RR31

NOTE: Incorrect Launcher Chassis selection results in unmapped (ie without descriptions) ECU in FDL-Editor and Incorrect Connection Target results in "doesn't map to an item" read errors

[®win]

I use the ESYS Launcher premium, so, at startup I need to select F031 in the launcher window.

[Almaretto]

Originally Posted by ®win

I use the ESYS Launcher premium, so, at startup I need to select F031 in the launcher window.

Yes, in launcher, you always select actual vehicle chassis (eg, F031 for 3-series touring).

In E-sys Connection target, you select representative chassis (choices above in post 4).

[®win]

Went through the process again tonight. All worked as described and as I saw on a youtube tutorial. I think it's now as it should. Will test tomorrow (light sensor can't be tested at night and for the rain sensor I need rain).


kretzu : I did read the documentation, but apparently I skipped one step (partially). Tonight I took all the required (and described) steps.


Thanks.

[Almaretto]

Originally Posted by ®win

Went through the process again tonight. All worked as described and as I saw on a youtube tutorial. I think it's now as it should. Will test tomorrow (light sensor can't be tested at night and for the rain sensor I need rain).

RLS (Rain Light Sensor) is on rearview mirror. It can be tested by covering it up or with a hose.

[®win]

Almaretto I know where it is, I put it there myself

Only, when it's dark outside the lights will come on anyway with the swith on Auto, which was also the case when the light sensor wasn't coded yet...

Do the wipers do anything with the handle at automatic at stand still with the engine running idle?

[Almaretto]

Originally Posted by ®win

Do the wipers do anything with the handle at automatic at stand still with the engine running idle?

yes

[tgmsocal]

Originally Posted by ®win

Do the wipers do anything with the handle at automatic at stand still with the engine running idle?

When you first hit the "automatic" button, the wipers should go once. Then they go when triggered by the sensor.

- tgm

[®win]

Both light and rain sensor work