Carat11
  •  Carat11
  • 63.4% (Friendly)
  • Member Topic Starter
2017-11-15T11:23:26Z
Two bugs today HW4 1.0.45:
1. Try coding disable start / stop F30, conenct > FEM > tsa_memory > active > start coding > wait wait, module is restart, but coding not change (esys work ok)
2. Add camera to X6 E71, add to FA - > ok work, coding pdc and navi > not work, not coding camera options, I must change manual values.
Sponsor

Start ECU Repairing, ECU Cloning, and Chip Tuning today, all from an incredible price of just USD 385.00.

No annual fees, no extra charges: You pay only when you have a job.

Visit Hexprog II page

damienj
2018-03-26T09:26:14Z
I have the same issue

I modify the coding on a module in a F10 series vehicle, save it
Reopen the coding and it hasn't been saved

I would also say this perhaps extends beyond autohex as esys fails on the same vehicle
damienj
2018-03-26T11:06:50Z
Autohex online support had a go of coding

Their conclusion was it couldn't be coded i.e. its something not supported by the car

Yet others report it can be done

Make your own mind up on that I suppose
roxetteer
2018-03-26T13:05:09Z
Please take note of different CAFD mapping in F and G series...BMW has a habit of changing mapping in each I-step version.
kkxdrive
2018-04-10T18:25:06Z
Originally Posted by: Carat11 

Two bugs today HW4 1.0.45:
1. Try coding disable start / stop F30, conenct > FEM > tsa_memory > active > start coding > wait wait, module is restart, but coding not change (esys work ok)
2. Add camera to X6 E71, add to FA - > ok work, coding pdc and navi > not work, not coding camera options, I must change manual values.



1. Go to dde/dme and disable msa from there. Works.