1. Microtronik Autohex II and Hexprog forum
  2. HexProg Programming Tool
  3. HexProg Intro
  4. VAG EDC17CP14 via OBD
jokir
  •  jokir
  • 69.6% (Friendly)
  • Member Topic Starter
2021-05-11T14:24:22Z
Hi
I'm trying to read an ECU with a table connection via OBD. SW version 1.0.33 is supposed to support work via OBD, but an error is displayed "Cannot communicate with Module ,Check OBD and Module -Ref: 2003-
How do I solve this problem?
Thanks
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

Autohex_II_BMW
2021-05-12T06:48:08Z
Originally Posted by: jokir 

Hi
I'm trying to read an ECU with a table connection via OBD. SW version 1.0.33 is supposed to support work via OBD, but an error is displayed "Cannot communicate with Module ,Check OBD and Module -Ref: 2003-
How do I solve this problem?
Thanks



did you contact support? Also make sure ECU is in working condition.
CipiCip
2021-05-12T09:21:29Z
Some versions of edc17cp14 can be read...not all
You need virtual read
jokir
  •  jokir
  • 69.6% (Friendly)
  • Member Topic Starter
2021-05-12T17:07:00Z
ECU 03L906022QJ - 0281015878
factoy mode - OK
boot mode - OK
OBD mode - not OK
Read via OBD with ODIS, VCDS - ok
Autohex_II_BMW
2021-05-13T06:52:58Z
Originally Posted by: jokir 

ECU 03L906022QJ - 0281015878
factoy mode - OK
boot mode - OK
OBD mode - not OK
Read via OBD with ODIS, VCDS - ok



please contact support to take log file also make sure you are on latest update of software.
Admin
  •  Admin
  • 100% (Exalted)
  • Administration
2021-05-14T23:06:00Z
You cannot use same wiring for factory mode to communicate by obd. In OBD hexprog uses different CAN BUS wiring than the factory mode ( white, brown). And even if you connect the right wires, you may read but you cannot program on bench as the ECU will reject entering programming session due to no gateway is connected.
The purpose of OBD function is to do the job on vehicle, the on bench job has it’s own functions.
jokir
  •  jokir
  • 69.6% (Friendly)
  • Member Topic Starter
2021-05-15T09:32:09Z
I have the ECU connected from the gateway
At ECU EDC17C46, reads the identification in order, even the virtual read is in order, downloads the file but cannot write it.
An error is displayed "Checksum cannot be corrected.Original file is invalid. -Ref: 3108-
Admin
  •  Admin
  • 100% (Exalted)
  • Administration
2021-05-15T16:23:41Z
Originally Posted by: jokir 

I have the ECU connected from the gateway
At ECU EDC17C46, reads the identification in order, even the virtual read is in order, downloads the file but cannot write it.
An error is displayed "Checksum cannot be corrected.Original file is invalid. -Ref: 3108-


Please contact support via Livechat
jokir
  •  jokir
  • 69.6% (Friendly)
  • Member Topic Starter
2021-05-16T17:17:21Z
Today, support tried to solve my problems, but failed. I'll wait and maybe the update will do it.
Autohex_II_BMW
2021-05-17T11:53:23Z
Originally Posted by: jokir 

Today, support tried to solve my problems, but failed. I'll wait and maybe the update will do it.



we have informed in the beginning itself On bench it will not work like OBD mode. When we tested it was giving rejection message because your ecu was connected on bench. As you are testing OBD mode please test it on car it will work without any issue. The main purpose for OBD mode is to read ECU without removing from car, if ECU connected on bench then factory mode is the best way to read it.
jokir
  •  jokir
  • 69.6% (Friendly)
  • Member Topic Starter
2021-05-17T14:14:12Z
I don't see the difference in whether the connection is in the car or on the table. The information goes along the bus as well.
I have ECU, Dash, Gateway and BCM connected in the circuit. Immodata are customized. Therefore, I try it on the table to verify the correct functionality and have no problem in front of the customer.
jokir
  •  jokir
  • 69.6% (Friendly)
  • Member Topic Starter
2021-05-17T15:14:01Z
Today, after updating to version 1.0.35, writing EDC17C46 on the table was successful.
Autohex_II_BMW
2021-05-18T07:42:09Z
Originally Posted by: jokir 

Today, after updating to version 1.0.35, writing EDC17C46 on the table was successful.



thank you for the feedback.
ms prog auto
2021-05-24T19:23:30Z
Hello edc17cp14 obd not possible, you contact support, not possible...
Autohex_II_BMW
2021-05-25T05:36:04Z
Originally Posted by: ms prog auto 

Hello edc17cp14 obd not possible, you contact support, not possible...



We need to take some files from your PC sir so please arrange TeamViewer again today. when you contacted support your internet was so bad to take files from your PC.
jokir
  •  jokir
  • 69.6% (Friendly)
  • Member Topic Starter
2021-05-25T15:26:13Z
Originally Posted by: ms prog auto 

Hello edc17cp14 obd not possible, you contact support, not possible...


As I wrote I EDC17CP14 does not work via OBD
What error message did she write?
Autohex_II_BMW
2021-05-26T09:15:51Z
Originally Posted by: jokir 

Originally Posted by: ms prog auto 

Hello edc17cp14 obd not possible, you contact support, not possible...


As I wrote I EDC17CP14 does not work via OBD
What error message did she write?



if you have ecu with you please contact support.
jokir
  •  jokir
  • 69.6% (Friendly)
  • Member Topic Starter
2021-06-01T14:51:42Z
Version 1.0.36 still not work
jokir
  •  jokir
  • 69.6% (Friendly)
  • Member Topic Starter
2021-06-23T13:35:28Z
Version 1.0.38 worked, problem solved
thanks
Autohex_II_BMW
2021-06-24T06:08:01Z
Originally Posted by: jokir 

Version 1.0.38 worked, problem solved
thanks



Thank you for the feedback.
Similar Topics
Users browsing this topic
    1. Microtronik Autohex II and Hexprog forum
    2. HexProg Programming Tool
    3. HexProg Intro
    4. VAG EDC17CP14 via OBD