History of MembersPage/Koskar
Older Newer
2017-07-31 11:51:13 . . . . l163.ip6.netikka.fi [Cleared old questions and added new question about vemstune VE-table TPS-axis]
2016-11-28 02:56:03 . . . . a82-197-29-2.mpynet.fi [Update: got engine running after long break]
2015-11-02 01:38:28 . . . . 195-240-176-40.ip.telfort.nl [asked for elaboration on steps followed, some more hints]
2015-10-31 18:59:42 . . . . j138.ip6.netikka.fi [ECU is now connected, so I continue to firmware issues]
2015-10-27 02:51:35 . . . . 195-240-176-40.ip.telfort.nl [added hints to revive the ecu]
2015-10-24 08:58:31 . . . . j138.ip6.netikka.fi [Answer to Dave /Koskar]
2015-10-24 06:12:18 . . . . 195-240-176-40.ip.telfort.nl [added some addional quesitons ]
2015-10-23 04:09:19 . . . . separator.rejlers.fi [Answer to counter-question /Koskar]
See complete list (17 entries)


Changes by last author:

Deleted:
Plans to season 2011: Install VEMS and throttle bodies

On July 2010 I got it to the dragstrip and results are: ET 14,32 s and speed 158,73 km/h

On August 2010 we got it to the dyno and results are: 129,9 Kw and 231,3 Nm.

[Escort Mk4]

Deleted:
- Ford Escort RS2000 ECU (EEC-IV) with Collins chip and EDIS4 with dual coils

[Engine bay pic in Botniaring Race Cirquit 2009]

----

Deleted:
My VEMS history :)

I build one VEMS project in 2008, but I sold it forward because I didn't have time to tune it. So it's time to try again!

Old wiring harness and ECU: [old harness]

Changed:

Coolant sensor: maybe GM because resistance range is suitable and it's got correct thread

Coolant sensor: GM because resistance range is suitable and it's got correct thread
Deleted:
VEMS related shopping list

Soon I will make order to VEMS shop and I have allready collected some VEMS related items to my project (LCD, knock sensor and wiring harness stuff).

--> Done

Products

1 x GenBoard v3.6

- Ship start: 2 weeks 247.30EUR

1 x Alubos1600

- Drill-count: 6 27.04EUR

1 x Alubos EC frontplate

- Drill-count: 0 15.97EUR

1 x Alubos Endplate

- Drill-count: 4 5.84EUR

2 x Alubos gasket 4.14EUR

3 x clamping plate 7.89EUR

1 x Additional VR or Coil interface 3.99EUR

1 x Econoseal18-PCB 9.87EUR

1 x Econoseal36-PCB 13.89EUR

1 x Econoseal18-Wire side 9.90EUR

1 x EconoSeal?36-Wire side 16.70EUR

1 x Wideband connector

- With wire: without wires 5.60EUR

1 x Idle stepper motor driver 3.00EUR

4 x Ignition driver 14.64EUR

1 x Ignition driver insulator sheet

- Size: 3lines 1.90EUR

9 x Injector or WBO2 heater driver 17.10EUR

1 x PTC fuse 0.71EUR

1 x Throughole Diode

- Model: 30V flyback 0.38EUR

1 x Throughole Diode

- Model: 18V unidir 0.43EUR

2 x VEMS sticker

- Color: white 0.56EUR

2 x VEMS sticker

- Color: red 0.74EUR

1 x VEMS sticker

- Color: metallic: silver 0.45EUR

Total: 412.94EUR

----

VEMS ECU assembly

Got ECU #3397 [Econoseal connectors soldered] and [underside]

[Black/green inverted LCD screen] and [LCD power on]

[LCD cable grommet and MAP-tube panel mount]

Is this 30V Flyback done correctly? And how about that 4+4 ignition setup. I use EC36 pins 34 and 36, other two IGBT-outputs are now shorted to GND and other 4 without IGBT:s are now connected to logic level.

[MAP, LCD-header, Flyback] and [underside]

Are these wires OK? Especially that 2nd VR from EC36-13 to 2nd LM1815. I measured that EC18-6 (Ch6) and EC18-12 (Ch7) already have pullup resistors (R85 and R86) to +5V.

[2nd VR, TX+RX, Analog Ch5/6/7 and Knock]

Connection from laptop USB -> Belkin F5U109 -> VEMS is working fine =).

[VEMS + LCD + Vemstune running!]

----

Some new pics and short video (added 16.08.2011)

Deleted:
[Analog inputs]

[VEMS wiring harness]

[Trigger log with 36-1]

[Just some pic of enginebay]

[Short video of second startup]

----

Changed:
1. I want to be sure with primary trigger config. So, when using 100% same 36-1 triggering that Ford EDIS use, what are correct settings?

* use the 4cyl 36-1 configlet (we make sure it's available nov 12)

** toothwidth=10 degrees

** next trigger tooth: 18

** reftooth 0,18,0,18

** EDIS4 = missing tooth is 90 degrees before VR sensor when first cylinder is in TDC.

--> Thanks for advice :)

----

Story continues... with old connection problem

In 2011, after last editing of this page and after a couple on engine start-ups, I tried to update latest firmware (from 1.1.84 to something that was newest in Aug 2011) before I start to tune engine. Something went wrong and now I don't have connection to ECU thru COM-9. ECU Detect on VemsTune: received ~80+ bytes and send ~5 bytes. So, big guestion is; what to do?

AVR ISP cable USB from VEMS Shop and try Bootloader update? Or am I totally lost with this ECU?

Or throw this ECU away and back to basics with original injection :(. After four years, I have got back some tiny pieces of motivation to get this car back to road and track again =).

----

Q: Could you elbaborate on exactly what steps you took to upgrade firmware ? did you use firmware upgrade wizard or non-wizard, what firmware did you try to upgrade to ? This information will provide some insight into what might be going on.

Best regards, Dave

A: Because I don't maybe remember correctly all the things that I did four years ago, I can't be sure about all details. It's sure that I have connection thru VemsTune and from VT I tried that Firmware upload from 1.1.84 to last released code. I guess it was 1.1.94 and day was maybe 6. Aug 2011? I have to dig out some old files and notes, if theres some additional information. [Pic of last working FW on LCD]

I have put two indicator LEDs on board, should I see something if ignition power is on?

And TX/RX -bootloader jump/shorting is something that I may try?

cheeRS, Koskar

-----

Hello Koskar,

So if i understand correctly the firmware upgrade gone bad was already in 2011 and you are now trying to revive your ecu, which now has 1.1.94 to a previous state working state of 1.1.84 ? Or do you intend to start over with a clean slate and new firmware (1.2.31 recommended in that case) ?

Best regards, Dave

A: Hello Dave,

And thanks for you reply!

You understand correctly that fw upgrade went wrong in 2011 (and whole car project was left behind to wait better days, which are now I hope). After that upgrade I haven't had any connection to my ECU from laptop. I don't know, did upgrade go to state where 1.1.94 is in AtMega chip already, or is 1.1.84 still there or is there just some corrupted data.

1.

Now (31.7.2017) I'm using FW 1.1.94 and it seems to work ok and after MOT I have driven car ~300km last week.

On weekend I have some time to study VemsTune and I have now disabled "IAC Alpha-N Load Compensation", but I have another problem to solve.

I try to Remap VE-table TPS-axis from 0-1-1-3-5-xxx-99 to something more reasonable like 0-1-2-4-6-9-xxx-99. After change, Alt+B and everything seems ok. Logging on and start my journey. Next time when I'm going to start my tuning session, TPS -values are back to that 0-1-1-3-5-xxx-99 -form. How to fix that?

Changed:
You are right, clean start is something that I'm now after. I don't specially need any of those old firmwares. Just newest fw in, car running and hard tune with vt ;). But how to revive from state where ECU is now? And what I have done wrong, any ideas? Did the whole bootloader upgraded in 2011 from nhex to uhex?

Best regars, Koskar

And does VE Tune by statistics or Live VE analyzer mess my "new" values? These TPS -values (don't mind about bumpy map, I have already smoothed it after this run);

20170728_VE_botnia.jpg

Deleted:
----

Hello Koskar,

By following the steps outlined here: GenBoard/Firmware/BootLoaderLoopback you should be able to force your ecu back into a known state and upgrade the firmware to a more recent version. If you have the non-crypted bootloader (without upgrade) the newest version is 1.2.11.

Best regards, Dave

A: Hello Dave,

And thanks again for you reply!

I just get my ECU to bootloader mode with TX/RX link. So connection is now ok and ECU is "alive" again. Great success.

Firmware upload to 1.1.94_BootUpdate? didn't go to ECU. So I have to study a bit more about upload process and what to do with old bootloader. I also tried to upload 1.1.84 and 1.2.11, but neither didn't go in ECU.

Then I tried firmware verify without any match. From 1.1.xx -series I tried 1.1.78/80/82/84/85/87/91/94/94BU and 96. I tried both options, wheelspeed and PS2, but no hits to current firmware.

Changed:
After those tests I look some old files from my archives. I find out, that in 19.5.2011 I have 1.1.88fw running in, so I try that also without verify result. In next weekend I hopefully get some more info about what was last used firmware.
BR,

Koskar

Deleted:
Hello Koskar,

Could you elbaborate what you mean with "firmware-xxx did not go to ecu", please tell me exactly what steps you followed (in order) so i can diagnose what might be going on.

If the bootloader is still in working order (which it seems to be) you should be able to upload your firmware (from VT) without any problems. When VT makes connection to the ecu, make sure to choose stay in bootloader on the dialog.

Best regards, Dave

A: Hello Dave,

First things first; I got engine running yesterday (27.11.2016)!

Thanks for you guys!

Now I used Expresscard34/RS232 -converter and oldest downloadable VEMStune. Now I use 1.1.94 firmware with old config that was in the ECU already. Started engine after five year break, what a lovely moment for me ;).

I have to re-check trigger setup because engine sounds a bit harsh. I'm worried about missingtooth position, was it right after all last time (EDIS4 == missing tooth 90 from TDC).

Also I have to synchronize throttle bodies to get engine idle properly under 2000rpm.

It seems appropriate to move forward from here. =)