Owner: Me
Make: Renault
Model: Megane
Engine: atmospheric 16v 4cyl
Capacity: 1998cc
Power : 150hp
Hardware: MS2-compatible FreeEMS daughter board in custom PNP ECU
Description: custom build PCB to fit a MS-II processor

This car is daily driven, but in the moment not with FreeEms due to the fact that that the Firmware 0.2.0 Snapshot has no Idle control.
Also i can not Rev higher than ~ 1600rpm.
So the current status is: Experimental use

Photos:



Proof : https://www.youtube.com/watch?v=g3Npt8c ... ata_player

Link to the pin compatible Board : viewtopic.php?f=9&t=2358

And the "build story" : viewtopic.php?f=3&t=2380

Neat! :-) For years people have talked about doing that with the CPU and you're finally the first to do it! Cool :-)

I can't believe how laggy those gauges are on your machine! Also, be careful with MTX, it's not as safe to use as EMSTune is, even if it's prettier and more polished on the outside. The FreeEMS-related guts are more hacky and could burn you.

I think your "hardware" description above is (unintentionally) misleading. Maybe: "MS2-compatible custom FreeEMS daughter card in custom PNP ECU" or similar? :-)

Which year is the car, btw?

Fred.

Hopefully more people will follow


I usually use emstudio but on this day it somehow quit working .. Next time will do vid with emstudio under ubuntu ..

changed ! i had it just copied and pasted it from my other thread

It is the 96 model but build in 98 nowadays this car is getting pretty rare here in Germany

Fred ! now i will annoy with idle control in the firmware section haha

had a mistake in fixedconfig1.c
changed anglesofTDC to 84,264,84,264,84,264
now the car runs on VE 40 before it was 65
working .s19 attached..

i had not enough time to make a datalog, hopefully i will have enough time in 2 weeks.

Good progress!

http://c2.com/xp/OnceAndOnlyOnce.html

What if I change the way scheduling works and you can't set those angles anymore? Please use the offset for its intended purpose.

Fred.

Fred, i tried
anglesOfTDC: 0,180,0,180,0,180
decoderEngineOffset: 84

but the car was not starting but 84,264.. is working ???

I saw that you tried, but then you gave up, instead rethink and come up with the solution or just ask.

viewtopic.php?f=54&t=1523

"Make the offset number larger to advance the base timing, make it smaller to retard the base timing."

In the angle array changing 0 to 84 means more retarded and changing 84 to 0 means more advanced.
In the offset changing 0 to 84 means more advanced.

So what you did was advance the timing by 84 + 84 = 168 degrees.

What you needed to do was subtract 84 from your decoder angle of 360 yielding 276, try this ;-)

Of course, if you'd used 0, 180, etc from the start, you'd have setup your offset correctly from the start, and not be in this boat :-)

Fred.

Finally i managed to log the engine running !
Decoder changes made and it is working !

so here is my Datalog ..

OK, good work! Config looks sensible now! :-) VE is unchanged in your git repo, though, and you appear to be building as Aitor! :-D

Firmware Version: 0.2.0-SNAPSHOT-250-g7b49703-AITOR51
Build Date: Sa 26. Jul 15:20:52 CEST 2014
Decoder Name: MissingTeeth-Crank-60minus2

Great to see no -DEV marker in there, though.

IAT is off the scale. I know it's summer, but 50C is excessive :-p This will be leaning you out a lot, and partly responsible for your high VE requirements.
CHT seems reasonable, unless it was warm, in which case it's reading too cold.
EGO is WAY too rich or not calibrated at all, or not present.

Re idle, choose a fixed duty for the time being, and add it to config. You'll also have to comment out some demo-spec code in main.c. If you need help, or code change review, hit me up! :)

That ought to keep you busy! :-)

Fred.

why it does it shows aitor ??

sadly IAT is correct while idle it sometimes rises up to 60-65°C and while driving it drops back to 30°C at this wheater conditions (25°C outside).
So that´s why i need a 3D idle valve pwm table
and a idle spark advance table.


what duty do you mean ?

Georg