Some of you may know that I’ve been messing about with digifant 1 mapping and learning about polo g40 ecus.
Thought I would share where I’ve got up to and what’s next.
First off, I got myself a TL866ii eeprom reader in order to read the 27c256 chip that is in the G40 ecu, which will save a 32kb bin file containing the map.
https://www.amazon.co.uk/WINGONEER%C2%AE-TL866II-Performance-EEPROM-Programmer/dp/B07B985LBSI use tunerpro which is available free to download, to view the bin, although it doesn’t mean much without an associated XDF file ( definition file which gives meaning to the tables found within the bin ). These need to be specific to the bin ( ie g60 and g40 have different Xdf’s )
The polo g40 xdf is openly available on the internet via ecuconnections forum but I can supply it if anyone is interested.
The above is all well and good to read an existing map, and to make changes however to apply these to the car requires burning to a chip, so this is where an emulator comes in. ( to save time, it’s not essential )
Moates in the US created an emulator called the ostrich v2.0, it’s available via h-tune in the uk for £199
https://h-tune.co.uk/moates-ostrich-2-0-emulator-honda-obd1-ecu-p28-p30-civic-integra/This will plug directly into the ecu socket on the g40 ecu and allow to you connect to your laptop via USB. In this instance, we use tunerproRT ( real-time ) rather than tunerpro.
When you open a particular table ie fuelling or ignition, which are mapped via load sites ( rpm vs map value ), you can set address tracing and see which lookup value the ecu is referencing at any point. This makes it really easy to tune on the fly. Once you are happy with a map, you save the bin file and write it to a chip and voila one home mapped G40.
Additional you can purchase a 2timer switch from moates, and store 2 32kb maps on a 64kb chip ( 27sf512 eprom ), these maps are then switchable via a single wire which is grounded to access a different map.
https://h-tune.co.uk/moates-2timer/A few of the g60 guy’s have been messing about with replacing the narrowband with a wideband input, launch control, elimination of digi lag and really interestingly rewriting the blink protocol for error codes, in order to read various memory banks to access parameters in the ecu.
There seems to be 3 variations I have seen so far
- KDA, a Russian guy who has written his own protocol and software which loads of different features but as it’s in Russian, it’s nails to understand
- Link to files via this thread :
http://nefariousmotorsports.com/forum/index.php?topic=11719.0- Dominik Gummel from digifant -onlineabstuning. This also includes an Android app as well as pc/Linux flavours. This is tasty as it shows map values, knock flag etc.
- Link -
http://gummel.net/bofh-ng/en/digifant-1-en/digifant-1-read-live-data-over-serial-k-line- Open source logger supporting k-line with modified code
https://github.com/designer2k2/multidisplay- DigifantTool by Rafal M. He has built a Bluetooth emulator and also has modified code to output ecu values to tunerpro via an ADX file and a modified bin
- Link -
https://m.facebook.com/tuningtool/I’m currently trying to get hold of a modified g40 stock bin from Dominik or Rafal in order to give this a play.
