Xoptiinside

• THE ECMSPY IS CLOSED.

•  WE ARE DONE NO LONGER ARE WE DOING ANY WORK ON THE PROJECT.

• IT WAS A GREAT PLEASURE BEING A PART OF THE 6 TEAM GUYS AND ON THE BETA LIST.
• THANK YOU FOR ALL THOSE THAT FOLLOWED. I TOO AM CALLING IT OVER. 

PC Interface lead  for ecmspy and directlink is the same cable.

To connect ECMSpy/directlink running on a PC to your bike you need a special lead. The ECU on the bike uses a TTL (5V) serial data port - NOT RS232. To connect to you PC you have to convert the TTL to RS232 data levels. There are several ways to do this.

I sell the cables as assembled units.

* Use a MAX232 level shifter chip and build up a little electronic circuit, powered from the PC RS232 COM port. If you do this use the MAX232E device as it is ESD protected.

* Use a FTDI interface lead, this connects to you USB port, emulates a RS232 COM port and provides 5V TTL signals direct.

FTDI Drivers

The required drivers can be found here:

http://www.ftdichip.com/Drivers/VCP.htm

vcpdriver.exe

The correct driver type is VCP. I assume you will need administrator rights to install the driver.

FTDI offers various installation guides in their library:



http://www.ftdichip.com/Documents/InstallGuides.htm

There's one trap: if the driver installation is interrupted after installing the USB driver (this is the first part of the driver installation), the virtual COM port driver has not been installed, but you will not get the usual "New device found ..." dialogue in windows if you unplug/replug the cable, and therefore never get asked to specify a location for the missing serial port driver. Best is, to deinstall the USB driver completely. Unplug the cable and replug after a few seconds. Then again follow the instructions from FTDI.

A very basic test could be done using hyper terminal (Start -> Run -> hypertrm.exe). Open a new session using the new virtual com port and (important!) set flow control to "none".

Then shorten the yellow (pin 3) and the orange (pin 1) wire using a straightened paper clip or something similar.

Every keypress in the hyperterm window should be echoed immediately. If not, check if flow control is disabled and you're using the correct port.

Bike connector

This is a Deutsch connector and very hard to get in ones, you have to be in the trade and buy 100+

The Deutsch part numbers are:
Connector: DT06-4S-C015
Wedge: W4S
Socket contact: 0462-201-16141 (Buell part number: 72191-94)

The pinout is (numbers as printed on the back side of the plug):

1 - orange
2 - black
3 - yellow
4 -not used

 Glossary of terms in ECMSpy

ACK - acknowledge character http://en.wikipedia.org/wiki/Acknowledge_character
AFV - adaptive fuel value
BAS - bank angle sensor
CPS - camshaft position sensor http://en.wikipedia.org/wiki/Camshaft
CLT - coolant sensor (more exact: engine temperature sensor)
DTC - diagnostic trouble code
EGO - exhaust gas oxygen sensor

http://en.wikipedia.org/wiki/Exhaust_gas_oxygen
ETS - engine temperature sensor

http://en.wikipedia.org/wiki/Resistance_Thermometer
IAT - intake air temperature sensor

K ative acknowledge character

http://en.wikipedia.org/wiki/NAK
TPS - throttle position sensor

http://en.wikipedia.org/wiki/Throttle_position_sensor
ve - volumetric efficiency

http://en.wikipedia.org/wiki/Volumetric_efficiency

The EEPROM is a non-volatile storage for a small amount of data. The EEPROM is built into the ECM and holds about 1 kbyte of configuration data, which could be read from and written into the storage. From 2004 on XB9 as well as XB12 models share the same ECM hardware, but with different data in them. The ECMs used for XB12 models have to support the exhaust valve and either the maps, timing tables and rev limiter look different. The EEPROM content is made up of more than 200 different scalars and tables, many of those could be identified. The following chapter shows a list of values together with their offsets, scaling and translation factors, the units and a short description.

How to access the EERPOM?

The EEPROM content could be read and written with the EEPROM editors in both EcmSpy versions. The PC version of EcmSpy has an additional access, hidden behind the chip-with-pencil icon. The direct access form requires the input in another way than the EEPROM editors do: here you need to know at which page and at which offset (relative to page start) the values shall be accessed.
The EEPROM has a size of about 1 kbyte, but one byte can only hold a value up to 255 - so offsets above this would never be accessable. Therefore the EEPROM is divided into pages, this is a common procedure. The ECM's EEPROM is divided into 5 or 6 pages, depending on the ECM type - the tube framer's ECMs are on 5 pages large. Each page consists of up to 256 bytes, with an offset from 0 (first byte) to 255 (last byte). Pages 1, 2, 4 and 5 are usually 256 bytes large, the pages 3 and 6 are of variable length. Page 3 always ends with the fuel map's and timing table's X and Y axis, and page 4 always start with the timing tables, followed by the fuel maps.
So to access the EEPROM via the direct access form, you have to calculate the page and the page-offset of the byte you want to access. The following tables shows the various pages sizes for different ECM types:

Megalog Viewer

Tunerpro homepage

Xdf Files zip

BUECB

BUEGB

BUEIB/BUEIC

BUEYD

BUEZD

BUE1D

BUEJA/BUEKA

BUE2D

 SUSPENSION SETUP

WHEELIE BAR SETUP