Members Login
Username 
 
Password 
    Remember Me  
Post Info TOPIC: Problems with interface connected


Veteran Member

Status: Offline
Posts: 65
Date:
Problems with interface connected


Hi,

I've been having a few problems hooking up the programing interface to my GSXR1000 but it sounded very similar to a problem ballard reported on here some time ago so I wanted to see whether anyone has come across it before.

I originally reflashed the stock ECU about a year ago when Petri first made his interface boards available. The flashing and monitoring engine data, etc. worked fine at the time and the ECU & wiring harness were then stripped off the bike after a few dyno runs while it went off to a fabricator for some work.

Recently I refitted the stock electronics and found I had problems when I hooked up the original Petri interface to the bike. The CHK indicator would appear on the dash when both the SDS and Yoshi connectors were plugged in. Bizarrely unhooking either of them resolved the issue and I could monitor engine data, etc. as normal.

I did struggle to reflash the ECU though as it would fail every time at different points regardless of whether I was using ECU Editor or Justin's WRT software. Error messages ranged from "No ACK after writing a block=14 page=255. Programming aborted, reset ecu and reprogram" towards the end of the ECU Editor flash or, on other attempts, "block=1 page=62" or "block=3 page=170".

The WRT software gave me a different error, "Index was outside the bounds of the array" after "Block 4 of 16 = 79.6%". At this point the ECU was effectively bricked and the fuel pump wouldn't prime when you turned the ignition on. Trying again got further but the same error after "Block 15 of 16 - 100.0%" and then "Block 11 of 16 - 60.8%" then another "Block 15 of 16 - 100.0%".

I assumed I had a fault with the interface box as when I switch to data mode and look at the engine data in ECUEditor it fails to synchronise with both plugs connected. It does however seem to trigger the fuel pump briefly and then turns it off, then on again, etc. for a few iterations accompanied by a clicking that sounds like it is coming from the front of the bike (rather than the obvious fuel pump relay noise).

You can hear the clicking/fuel pump noise it makes here:

I ordered a LogBox from Justin to rule out problems with my Petri sourced interface. Whilst I can now program the ECU reliably and the bike runs without the interface connected I am still having issues with having both plugs connected at once and still have the strange noises and odd behaviour when switching to data mode. I still get the CHK warning on the dash in both read and program mode.

I am at a loss as to what the problem is or where to start looking. Does anyone have any ideas?

Thanks.



__________________


Guru

Status: Offline
Posts: 546
Date:

Do you have problems in logging mode
the chk in data and program is normal,
as is cycling the ecu as it connects
i think 3 times

__________________


Veteran Member

Status: Offline
Posts: 65
Date:

Ah, that's useful to know. Thanks. When was that introduced as I'm convinced it wasn't like that before. Oh well...

I'm still having problems getting it to synchronise so I can view the engine data. When I switch to that mode the light on the ECU Editor screen goes green but then immediately goes to amber and the 'Synchronizing...' message appears in the title bar.

When the box is in logging mode it does record some data which is a big step forward.

Any ideas on the synchronisation issue with the engine data?

Thanks.

__________________


Veteran Member

Status: Offline
Posts: 65
Date:

Using the engine data function on EE I get around 4 seconds of good communication (green light on screen) before the software reverts to 'Synchonizing...' (yellow light on screen). It doesn't seem to matter whether the engine is running or not nor how long I leave it to achieve proper synchronisation again.

Any ideas what could be wrong?

__________________


Veteran Member

Status: Offline
Posts: 65
Date:

I recall with the original v1.0 interface from Petri Karjalainen it required a resistor to stop problems with the Engine Data screen?

Could this have anything to do with the problems I am experiencing or has anyone got any other ideas?


__________________


Senior Member

Status: Offline
Posts: 137
Date:

Try to connect to other laptop.For flashing You dont use interface circuits its connects directly FTDI cable to ECU.If You have problems with flashing then there are 2 things that can work wrong:
-laptop
-ftdi cable.
As i have bought many cables and few interfaces with ftdi chips i have never problems with FTDI.
Other things:
-xenon aftermarket stuff
-wire diameter
-external EMC noise sources

Thats my 2 words


__________________


Veteran Member

Status: Offline
Posts: 65
Date:

I'm waiting on a new FTDI cable for my original interface box I got from Petri some time ago just in case that is causing the flashing problems.

In the meantime I bought a LogBox from Justin to narrow down the variables trying to get to the bottom of the various problems. I can now flash with no problem but cannot get the Engine Data screen to work reliably.

It's a race bike so no lights of any kind. All wiring is either standard or as supplied with the LogBox kit from Justin.

Can't think of any additional noise sources but due to run the bike on the dyno tomorrow so will try there also.

Just need to get the Engine Data function working in ECU Editor and have run out of ideas or things to replace aside from my laptop which may be the next thing to discount.

__________________


Veteran Member

Status: Offline
Posts: 65
Date:

Just tried using my girlfriend's laptop and that can't synchronise to show Engine Data at all.

Is there any way to get additional information about what is causing these problems?

__________________


Guru

Status: Offline
Posts: 546
Date:

May need the lights or as you said above the resistor

does not connect to data well on the bench harness either but fine on my bikes

and have you given each of the connecting wires a tug test, just to be sure there seated and not pulled out of the crimp ?


__________________


Senior Member

Status: Offline
Posts: 137
Date:

On the first version of PetriK's interface i have one problem with connecting wire.
I removed all wires and re-solded each end connection.


__________________
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