ruzki´s Megane Coupe 2.0 16V F7R and Turbo

[ruzki]

Owner: Me
Make: Renault
Model: Megane
Engine: atmospheric 16v 4cyl
Capacity: 1998cc
Power : 150hp
Hardware: Hopefully some day FreeEms but now a MS-II "derivate"
Description: custom build PCB to fit a MS-II processor
This car is daily driven.

Photos:



Also got the same car in green and with turbo conversion.

Owner: Me
Make: Renault
Model: Megane
Engine: turbo 16v 4cyl
Capacity: 1998cc
Power : 250hp+
Description: Garrett TB2804 Turbo, custom air to air intercooler, forged pistons and bad con rods from PPM that caused a engine failure ...
Regarding to the fact that green Megane has an engine failure the red is getting the FreeEms.
So plan for the future is to develop a bullet proof ECU and use it in the turbocharged Megane.

Photos:

[ruzki]

At the Moment im running as i said before a M$ derivate. It is running pretty well buuuut Mr. Robert Bosch says that my ECU is no t legal
So i want to build a FreeEMS !

Configuration

Engine: 1998cc 4cyl 16v
Crank: 60-2 wheel
Cam: half moon wheel
Injectors: 221cc Bosch full sequential
Ignition: Wasted Spark coils (driver inside of ECU)
IAT: GM with 2,49kOhm Bias
CLT: GM with 2,49kOhm Bias
TPS: some GM stuff
MAP: GM 1bar
Lambda: Innovate LC-1

My next goal is to build a firmware wich can support the engine configuration.
People in Germany need to go stealth with their modifications so i will build the FreeEMS in the original ECU housing.

[Fred]

Neat! :-) I moved your thread here, because this is where it belongs. This is the section for talking about your car, mods, etc. The vehicles section is an exclusive section for those who have actually run their engine on FreeEMS. No offense intended! Check this out: viewtopic.php?f=3&t=2378

[ruzki]

After trying to build the firmware on Windows Vista and MacOSX i finally had success with Ubuntu ..
First Firmware build .. created an ID for my build..



After i checked all the sensor readings i tried to crank the engine.

LOST SYNC Reason: 71

[Fred]

#define VRWiringBackwardMatchedPairWideNarrow 71 // 0x47

http://builds.freeems.org/firmware/dev/ ... ource.html

Only that code? No others? Usually you get a number of different codes if you have noise issues. If your setup is an OEM one I doubt the VR wiring is backward but I guess it could be? What were you previously using on it? MegaSquirt? It's possible, and you'd not be the first to experience it, that you had it setup wrong before and M$ simply ignored that.

Or something else could be wrong.

Please post your EMStudio derived log file from fully committed and pushed firmware in compressed format as noted here: viewtopic.php?f=54&t=2323

It'd pay to read this, too: viewtopic.php?f=54&t=2369

Fred.

[ruzki]

Switched the polarity of the VR sensor and made a second datalog.
Yes there are more than one Sync error reasons.
I think i know why it is not working ! (pictures below)..
Also attached the datalog and source code ..



It is a kinda 57 +1,5 tooth -1,5 gap .. something like this ..
It think it is that way to prevent the engine from turning in the wrong direction.

[ruzki]

With the M$ it is running with the 60-2 decoder but i add 0,1ms Tach interrupt masking.
Maybe ist is working because of the interrupt masking

[Fred]

Interesting re the sensor style. I'll have a think about that after (my already late) breakfast.

I deleted your code attachment. That's not an acceptable way to share code here. Commit your changes and push them to a new named branch "ruzki-config" or simialr to github after setting up an account there.

[ruzki]

Ok done .. had some problems to push to Github ..
Fred do i have to comment every file i changed in Github ?

https://github.com/ruzki/freeems-ruzki-config

[Fred]

That's getting closer, but still not right, sorry! Thanks for trying, though! :-)

What you should do, very carefully, is this:

1. Go to this URL https://github.com/fredcooke/freeems-vanilla
2. Click the fork button and wait until the fork completes
3. Take the clone URL and run "git clone <that URL>" on your machine
4. Type "cd freeems-vanilla" to get into the repo
5. Type "git checkout -b ruzki-config origin/dev" to get on the latest
6. Apply your config changes to that directory cleanly
7. Fix your git config to contain your real name (first and last, for me Fred Cooke)
8. Commit those changes with a comment something like "Adding my config for the Renault"
9. Type "git push origin ruzki-config"
10. Post here again :-)

It's important to use your name in git as this is serious business. Nicknames are for forums and so forth.

I hope the above helps! :-)

Fred.