Nån som har koll på vad man hittar prylarna till kabeln så man kan föra över infon till datorn? Kopierad från uk forum
http://www.bike-pix.com/forum/viewtopic.php?t=20340
tack för allt gunter och sonic
The ECMSpy FAQ
OK, here is a single one-stop place for all the recent ECMSpy information. I will update it with stuff as we go and as people suggests changes.
Disclaimer: Although we must point out that people make their own decisions and take responsibility themselves on this stuff. You can break you bike, big time...
Contacts
id073897 is Gunter the Project creator and Main Man...
New ECM EEPROM data to: support (at) ecmspy.de
ECMSpy for PC
This is the PC version of the program it runs on Windows 2000 and XP and in administrator mode on Vista.
http://www.ecmspy.de/download/EcmSpySetup.exe
Below is the latest model file, usually included in the above, but updated between releases of ECMSpy. Put it in the ecmspy program folder (usually c:\program files\ecmspy\.
http://www.ecmspy.de/download/ecmspymod.ini
(you will have to right-click and save the link, as it will be displayed in the browser otherwise)
ECMSpy for Palm
ECMSpy is also available for the Palm handheld. This device is somewhat more handy than a PC or Laptop.
ECMSpy for Palm should be downloaded from here:
http://www.ecmspy.de/download/ecmspy_palm.zip
This will run direct on a Palm device.
To run the software on a PC you need the Palm simulator, The ShaggyOne has very helpfully put it here for uploade. Or you can sign up with Palm One for it.
http://rapidshare.com/files/28499308/Palm_simulator.zip
You have to build a special interface circuit to use the Palm, there are some posts in the main ECMSpy thread for information on this.
http://www.bike-pix.com/forum/viewtopic.php?t=17934&postdays=0&postorder=asc&start=22
So far no one is offering this comercially, so you are on your own.
The source of the current palm version has now been GPL'ed and is available for download here:
http://www.ecmspy.de/download/ecmspy_palm_src.zip
PC Interface lead
To connect ECMSpy 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
* 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
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 - n/c
Sonic's lead
I've bought a big bag of 100 connectors through my work and am buying batches of 10-20 of the FDTI interface leads. I'm building these up as complete leads and making them available to everyone at beer or two over cost price. PM or e-mail me for current availability. I have to get groups of people together to make this viable, so sometimes there is delay of a week or so. When the initial rush dies down, I'll atill build leads in ones and twos, but they will cost a bit more.
Glossary of terms in ECMSpy
From Gunter
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
http://en.wikipedia.org/wiki/Resistance_Thermometer
NAK - negative 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
Technical stuff
Snippets from Gunters posts
Low level EEPROM and Map Data viewing
For all those interested, I've uploaded a new archive of collected eeprom data to the download area:
http://www.ecmspy.de/download/Evc.zip
You need to have the WinOLS demo installed:
http://www.evc.de/de/download/default.asp
Just put the extracted Evc-folder into your "My Documents" folder lying on the desktop an start the application. Then you will get all projects automatically.
Non supported ECM
If you find strange tps/rpm data this usually indicates a non supported ECM. This can be easily fixed and needs only the donwload of a new .ini-file, but we need your help.
First of all, got to the program options (tool icon) and set "EEPROM fetch: next page after NAK".
Next go to the eeprom tab an fetch your data. You will see the byte counter in the status line, bottom right.
If fetching is done, save the eeprom data: File -> Save EEPROM.
Please name the file exactly like the eeprom type, which can be found in the status line, bottom left: "BUEXXYYY 11-22-33". We need this type to successfully include an unknown ecm type. If it's a race ecm, then point this out too, in your mail or in the filename itself.
Then, go to the eeprom subfolder of the program's folder (usually c:\program files\ecmspy\eprom) and you will find two new files; one .txt file and one .epr file. Please send both files (one is human readable, the other contains binary data) to the developers team:
support (at) ecmspy.de
Please, use the e-mail address above, because all members of the team get your mail then and I'm a bit released from forwarding your mails. Please tell us the bike's type (XB9, XB12) and it's model year in that mail. The current models share the same ecm type, but the data in eeprom differ.
This is a list of eeprom data that I already got:
- X1 EC-type KA210, stock only
- X1 US-type JA120, stock and race, but I'm not sure if the race ecm is really a race ecm. Sorry for that.
- XB9 EC-type CB060 stock and race (all pre-CityX models)
- XB9 EC-type IB310, stock only (CityX and current models - XB9R/S are not sold in germany any more, but maybe otherwhere)
- XB12 EC-type GB231 (first series of XB12, MY 2004, I guess), stock only. Here too I got data said to be from a race ecm, but they don't look like that.
- XB12 EC-type IB310 (current models), stock only
As you see, what we need are mainly race ecm eeprom data. If anyone could get hands on a XBRR eeprom, well, fetch it, run away and send it to me, before they get you
I'm not sure if there still are any US-type ecms as with the X1.
Datalogging stuff
The best tool to take a look at datalogged with ECMSpy is the MegaLogViewer, which should be downloaded following this link:
http://www.ideasandsolutions.biz/MegaLogViewer/download/
Here are some datalogging files we made at the track in Oschersleben last weekend. Although under really bad conditions (raining most of the time ...) we got some very interesting data, including realtime AFR from a wideband O2 sensor.
http://www.ecmspy.de/download/OC_Logs.zip
Interface lead set-up for Palm simulator
(Thanks to pashlipops)
Instructions how to look at the files are included in the archive.
Right clicking on My Computer - Properties
Then the Hardware tab
Then Device Manager
Then look down the list for Ports (COM and LPT)
Click on the plus if it is not expanded
With the cable connected, it should say USB Serial Port (COMxx)
It is this xx that you want (a number)
Then File, Exit
Then Cancel on the System Properties window
Open up your Palm OS Simulator
Right click, then Settings, Communication, Communication Ports...
You will see a list, click on the one that says Cradle and then Edit
Then change the Bound to drop down box to COMxx, i.e. the virtual port the USB cable represents.
Then OK
The Palm OS reboots, so you will have to fanny about with the location and stuff again.
After this, it should work.
I think the problem is that some systems that have their own built in COM port will result in the Palm OS defaulting to that, rather than the nifty cable.
Interface lead set-up for PC version
If ECM Spy cannot find your ECM through Sonic's cable (and the ignition is turned on etc.), it may be a problem with your connection.
If you have a PC that has had everything connected to it via USB, it is likely that it will allocate a large number to the COM port, you can find this number using the method I describe above.
If you click on the connections button, you can select the COM port identified as being allocated to the cable. Mine was 21, which ECM Spy would not support, so I did the following:
Right click on My Computer - Properties
Then the Hardware tab
Then Device Manager
[You can also get here with Start - Control Panel - Printers and Other Hardware - System (on the left) then click on the Hardware tab then Device Manager.]
Then look down the list for Ports (COM and LPT)
Click on the plus if it is not expanded
With the cable connected, it should say USB Serial Port (COMxx)
If this number xx is not found by ECM Spy, make a note of the lowest COM port in use, then right click on the virtual cable and click Properties.
Click on the Port Settings tab then advanced, then in the drop down box, select the lowest COM port noted to be not in use. Windows will give you a lecture on choosing the same COM port for two different bits of kit, but we need not worry about this as you dont have both plugged in at the same time.
Then click OK, then OK, then File - Exit then OK on System Properties.
Then, in ECM Spy, click on Options then Communications (or on the communications button) and select the COM port you have assigned.
If this was your problem, it should be solved.
--------------------------------------------------------------------------------------
That's it for the moment, suggestions to improve this are very welcome
Sonic