Members Login
Username 
 
Password 
    Remember Me  
Post Info TOPIC: 2006 GSX-R600 K6 ECU Bench Test Help


Member

Status: Offline
Posts: 18
Date:
2006 GSX-R600 K6 ECU Bench Test Help


Hello guys...

I'm new here and i was hoping someone could help me out...

i'm helping a friend try to solve a No Spark issue on his bike, and i wanted to know if there is any way we can bench test the ECU to see if its OK or if there is anything wrong with it...

He already tested basically all sensors, switches and fuses but there is still no spark on it...

the bike cranks and we can here the fuel pump working, but no spark

already tested the coil wires and they are ok...

the cluster has also problems and some things are not working, so i just tried to re-solder all components and will test in the next days to see if we can put in dealer mode to try and get some codes out if it...

i also testes the voltage to the ECU and according to the wiring's i got, the should be 2 signal cables. Main one and a "backup" one (don't know if this backup one should get any voltage, but the readings i made there is no voltage on this cable).

The main one is getting something like 10.5V. I read that in some models it should have 8.5V.

Could anyone help me out with some tips on this?

I hope that this weekend i can have tome to go there and check things with him, but i was hoping to get some tips and if possible see how can i bench test this ECU.

this is the ECU info:

32920-01H10

112100-5121

12V NEPOII

Thanks



__________________


Veteran Member

Status: Offline
Posts: 46
Date:

If the ECU has to low voltage, the ecu will not boot. Please check the dealer fault reading, if this works, the ecu has sufficient voltage.

__________________


Member

Status: Offline
Posts: 18
Date:

Thanks for the tip.

I don't think i can get into "dealer mode" because the dash is also faulty.

Only Neutral light comes up and Revs.

No info in display.

The bike is in my friends house but i will move it in the next days to my house for better checking



__________________


Veteran Member

Status: Offline
Posts: 46
Date:

Maybe you can share some background information. What happen, did the bike shut down during normal operation or did he crash or something...

For me, this sounds like an cam/crank position sensor issue... The bike does not know the engine position so there is no spark at an certain degree for TDC.

My tip, get the dash-up and running or get an flash/ftdi interface and look at the fault codes.



__________________


Member

Status: Offline
Posts: 18
Date:

Hello there... (sorry for the late repply, but i didnt had checked the bike untis now)

So, i finally was able to get the bike in my house to make things "easier" for me to review...

About the "background":

The bike was runnig fine and when my friend stoped to do some stuff, when he came to turn the bike on, no start / spark.

So, i started checking the wirings and it seems to be pretty much ok.

I measured the peak voltage for the CKP sensor and its giving 0.23-0.26V, when according to the manual it shoud be 0.28V or more...

Dont know if this affects or not.

Now, about the USB-FTDI interface.

I was able to get one, an ive been reading a lot but all i see is for the flashing "procedure" and im a bit confused as for the "diagnostic" part.

Can anyone help me out on how can i connect this USB-TTL Ft232RL interface to the SDS connector on the bike to do the Code Readings and see if i can get something out of it that can point me into a more accurate direction on the problem?

the adapter i have is similar to this one:

https://www.amazon.com/HiLetgo-FT232RL-Converter-Adapter-Breakout/dp/B00IJXZQ7C

I know i could use ecueditor to connect and check codes, but im not sure on the wiring for this onto the SDS connector on the bike, and also if i need to put into dealer mode to be able to read codes or if it would read directly like with cars obd diagnostic...

Thanks for the help...



__________________


Veteran Member

Status: Offline
Posts: 37
Date:


You can use the Vag-com 409.1 and connect to the bike with the sw ecueditor.

__________________


Member

Status: Offline
Posts: 18
Date:

I dont have the Vag-Com cable that you mention...

I have the VCDS Hex2 cable but i dont know if it would work...

Also, i have doubts with the wiring onto the SDS connector for diagnostic



__________________


Veteran Member

Status: Offline
Posts: 46
Date:

Boxsport, why not place the bike in dealermode so it's displaying the code on the dash?

__________________


Member

Status: Offline
Posts: 18
Date:

Wiebren wrote:

Boxsport, why not place the bike in dealermode so it's displaying the code on the dash?


The bike dash doesn't display. It just have the lights working....

This is why i i need to connect with the laptop



__________________


Veteran Member

Status: Offline
Posts: 46
Date:

HEX pinout

  • 5 Ground
  • 7 Kline
  • 16 12V


SDS

  • 1 B/W PIN 36 (ECM ground)
  • 2 GR PIN 62 (KLINE)
  • 6 O/G PIN 12 (PWR SOURCE)

Open with Ecueditor



__________________


Member

Status: Offline
Posts: 18
Date:

Wiebren wrote:

HEX pinout

  • 5 Ground
  • 7 Kline
  • 16 12V


SDS

  • 1 B/W PIN 36 (ECM ground)
  • 2 GR PIN 62 (KLINE)
  • 6 O/G PIN 12 (PWR SOURCE)

Open with Ecueditor


Thanks for the answer, but my doubt is:

In the FT232rl adapter that i have, where to connect with those lines from the SDS/Hex connector (just for diagnostics)

I have in adapter these pinouts:

  • DTR
  • RX
  • TX
  • VCC
  • CTS
  • GND

Could you help me to understand where to connect these pinouts into the SDS or ECM so that im able to make the Code Reading?

Sorry if this is a dumm question, but i cant seem to find this "clear" answer to these pinouts... (and honestly im still in the nobb fase on this)

Thanks



__________________


Veteran Member

Status: Offline
Posts: 46
Date:

Use the VCDS Hex cable you mentioned

Connect Hex cable to SDS connector
5 to 1
7 to 2
16 to 6

Numbers are on the connectors, otherwise lookup OBD pinout. ECM pinout is stated in my previous post

To use the FT232 things are different. I need to look this up, this will require some soldering maybe...

__________________


Veteran Member

Status: Offline
Posts: 37
Date:

You can build k-line interface using USB TTL cable, I am attaching the diagram



Attachments
__________________


Member

Status: Offline
Posts: 18
Date:

Wiebren wrote:

Use the VCDS Hex cable you mentioned

Connect Hex cable to SDS connector
5 to 1
7 to 2
16 to 6

Numbers are on the connectors, otherwise lookup OBD pinout. ECM pinout is stated in my previous post

To use the FT232 things are different. I need to look this up, this will require some soldering maybe...


thanks. i will try this today and i will write back...

I really appreciate your help...



__________________


Member

Status: Offline
Posts: 18
Date:

giuseppe wrote:

You can build k-line interface using USB TTL cable, I am attaching the diagram


Thanks....

I've been looking for this "clear" info so that i could understand how to make the Cable using the FTDI interface....

Thanks a LOT FOR THE SHARE....

If i have here in the house those BC547 i will assemble this also today for testing...

Thanks guys for the Share and for the Support...

i will keep you posted...



__________________


Member

Status: Offline
Posts: 18
Date:

Ok guys, so i tried to use the Hex-V2 cable like you suggested and also made the "adapter" for the FTDI232 pcb that i have, but i'm having the same error on both when i try to read the parameters...

I'm posting a picture to see if you guys can help me out.

Will this be a windows issue with the COM port configurations?

I' using COM2 with the standard win7 configurations.

Already tried to run the ECUEditor in administrator mode, same result...

already tried to put bike in Dealer mode when connectiong, and sae result...

Wiring is a bit different from the pinout numbers you shared but i traced the cables back to the ECU plug and i'm pretty sure i have all the wiring connected good in the SDS plug...

any suggestion on what could be wrong? I dont think its the ECU because i was able to read this ECU on the bench using Ktag...



Attachments
__________________


Veteran Member

Status: Offline
Posts: 46
Date:

Is the bike on contact (killswitch included), do you hear the fuelpump?

Please try to install the FTDI drivers from the installation folder of ECUeditor (under common). The std. FTDI is too new/does not work.

Also, use an .Bin file of your bike.

What pins are you using of the SDS?



-- Edited by Wiebren on Tuesday 14th of April 2020 07:32:05 AM

__________________


Member

Status: Offline
Posts: 18
Date:

Wiebren wrote:

Is the bike on contact (killswitch included), do you hear the fuelpump?

Please try to install the FTDI drivers from the installation folder of ECUeditor (under common). The std. FTDI is too new/does not work.

Also, use an .Bin file of your bike.

What pins are you using of the SDS?



-- Edited by Wiebren on Tuesday 14th of April 2020 07:32:05 AM


Yes the bike is in contact and the kill switch "on" (for test now i have bypassed the kill switch)

I dont have the tank on it, but the last time i was reviewing the bike it was on. I will test today with the tank/fuel pump connected (or check voltage for fuel pump).

Cant tell you now the numbers on the SDS pins but i will take some pictures and share here.

Will also try with the drivers you say. i have the last ones intalled, so i would hope that would be the problem...

I will keep you gues posted...

Thanks



__________________


Veteran Member

Status: Offline
Posts: 46
Date:

SDS
1 B/W PIN 34 GND
2 GR PIN 32 (KLINE)
3 DGR PIN 24 (RX)
4 W/R PIN 56 Dealer Mode
5 W PIN 7 (TX)
6 O/G PIN 17 (PWR SOURCE) +12V

YOSHI CONNECTOR
1
2 R PIN 11 (VCC)
3 BL/Y PIN 37
4 BL/R PIN 15
5 BL/G PIN 54
6 BL/B PIN 55
7 BL/W PIN 56
8 B/BR PIN 29

I added the pinout for the ECU.

__________________


Member

Status: Offline
Posts: 18
Date:

Hello guys...

Sorry for "the late reply".
So, i was able to solve the bike issue. It turns out that it was the Crank Shaft Sensor, Cam Shaft Sensor (this was totally screwed) and some wirings that were broken...
It took me some time to check all wires (basically one by one), but i was able to fix the dash and also do the connection with the adapter i made and you guys shared the info to use with EcuEditor.
At the end i didnt made much readings with ECU Editor because i wanted to finish the bike to my friend... (it was almost 4months since the bike stoped for the first time)...

So basically i had these issues:
Dash Not Working = Broken Wire on the harness going to/from the starter relay
Not being able to connect to the ECU with the interface + Ecu Editor = Broken Wire on the harness going to/from the starter relay
No Spark Issue = Crank Shaft Sensor + CAM Shaft Sensor problems...

Regarding the Crank Shaft Sensor it was sending lower voltage than what manual says
For the CAM Shaft Sensor, this was totally gone. Resistance Readings where giving me 1.6ohms, and when i got another sensor the resistance was arroung 6.2 / 6.5 Mega ohms.
I dont know if it was me "jumping" some checkings on the manual, but i didnt find any comments on the service manual regarding the "No spark" issue, that can also be related to the CAM Shaft so i was basically not thinking that it could affect the spark. after fixing the Dash, i had no codes. but after trying to crank the bike it would give the C11 FI code, but only while the key was on... After turn Off/On again it would delete the code and i only realized that after 2 or 3 tries...

I just want to Thank you Guys for the Help, patience and Support you all gave me...

Cheers and if there is anything i can do to help anyone in anyway i can, it will be my pleasure...


__________________
Page 1 of 1  sorted by
 
Quick Reply

Please log in to post quick replies.

Tweet this page Post to Digg Post to Del.icio.us


Create your own FREE Forum
Report Abuse
Powered by ActiveBoard