Map Loading Software

Map Loading Software

Because of the differences between the EOC17 and EOC19 firmware, two different map-loading software installations for the PC were produced. (Although both versions of K-Scan will work with either ECU Firmware). This causes a bit of a complication when installing the tools because one can overwrite the other. The recommended installation procedure is to first install the older tool and append “11” to the .EXE file and path names. Then install the newer tool, and append “12” to those file and path names.

Unfortunately, this results in there being a total of four different map loaders for the OSSA's Kokusan Denki ECUs. There are two for the early EOC17 (ECU part number ending in 11) platform and two for the later EOC19 (ECU part number ending in 12) platform. The thing to remember is:

KWritePro works with .KDS files. These files were intended only for factory production, but that is what got released into the wild (at least here in the US) for the early EOC17 platform. I do not think I have seen any .KDA files for the older platform, but there may be some.

KWriteDataPC works with .KDA files. These are the files you will primarily see for the EOC19 platform. But some .KDS files are around as well.

There are only 280 and 300 maps under EOC17 because it was phased out prior to the introduction of the 125 and 250.

Yes, I know it is all confusing. It is confusing for me too!

.KDS Maps

All .KDS files are exactly the same size at 114,696 bytes. These are maps for the old (ECU P/N 5200030211) EOC17 platform, which is sometimes called the eleven ECU.

I have used a binary file comparison tool to look for differences between the maps. There are significant differences in all the maps. I am guessing that the map itself occupies approximately the first 1/3 of each file. The last 2/3 of each file is identical, and I assume this is the EFI operating firmware itself. When a new file is loaded, the old global fuel trim and idle throttle position settings are retained. I assume these values are stored in EEPROM (along with the operating-time clocks), whereas the map and firmware are stored in Flash memory.

There is no documentation as to how the maps are different, but I have made some guesses. The first eight digits of the filename probably indicate when the map was introduced. For example, 20130312 would be the 12^th of March, 2013.

I rode my TR280i for a bit with the Explorer map in it. I assumed it would have a “softer” map than the trials version – and it does. But it is not suitable for trials as it lacks what I will call “snap,” or the ability to make power instantly. This is pretty obvious when you look at the ignition timing with K-Scan. Both maps idle at about 20° BTDC, and reach a maximum advance of about 30°. The trials map reaches max advance just off idle and at any throttle opening, whereas the Explorer map is much lazier getting to full advance.

.KDA Maps

All .KDA files are exactly the same size at 32,792 bytes. These are maps for the new (ECU P/N 5200030212) EOC19 platform, which is sometimes called the twelve ECU.

As an aside, GasGas also uses a Kokusan Denki ECU in their 4T bikes (EC450 and EC515). GasGas had a public webpage where software and maps could be downloaded. Their map files have the .KDA extension and are only 16,408 bytes in size. I assume this is just a map file and contains no operating firmware. I tried using the GasGas version of K-Scan on the OSSA, but it gave the message, “The ECU returned an unsupported maker code.” Clearly, it could communicate with the ECU, but would not do anything useful. It has the same user interface as the OSSA version of K-Scan.