Aftermarket ECU
|
| compatible |
|
| compatible |
|
| compatible |
|
| not compatible (uses proprietary communication protocol?) |
|
| not compatible (proprietary hardware and communication protocol) |
|
| not tested (probably not compatible, proprietary communication protocol?) |
Chipped Honda ECU
In case of chipped ECUs (P28, P30, P06, P75 etc.), the compatibility with Hondash depends on the combination of used ROM editors and installed board jumpers. Check all following points.JUMPERS
-
jumper J12 or J4 must be connected (usually bridged with a zero ohm resistor), if it was cut or disconnected, reconnect it with a metal wire
- P28, P30 (non-JDM rectangular chips): J12 jumper
J12 reconnected with a metal wire
J12 factory stock zero ohm resistor - P30 (JDM square chips): J4 jumper
J4 reconnected with a metal wire
- P28, P30 (non-JDM rectangular chips): J12 jumper
- jumper J1 must be connected in order to use an external modified ROM stored on a EEPROM chip.
However if the other board jumpers (J12/J4) are connected as described above and you're still not able to get Hondash to communicate (due to used incompatible Rom editor) and you want to restore the compatibility with Hondash at any cost, just cut or remove this jumper J1.
This will force the main processor to use the internal stock ROM instead of the external ROM stored on a EEPROM chip.
Please be advised, if your engine is highly modified it's not recommended to run it on a stock map outside of low engine load conditions. Do this on your own risk.
J1 jumper
ROM Editors
CROME
ROM editor can make maps (ROMs) with unaltered stock Honda communication protocol, compatible with Hondash.
Just make sure that the datalogging plugin (Plugins » Enhancements » Quick Datalogger +RTP) is disabled in the editor before exporting the map (ROM)
ECTUNE, NEPTUNE
ROM editors use their own proprietary communication protocols and thus all maps (ROMs) created in these editors are currently not compatible with Hondash. Cutting the J1 jumper is the only solution currently
