Does anyone know what active projects there are pertaining to ECU deconstruction and development of tuning programs? I'd like to get involved somehow but a lot of the Honda stuff is pretty much dead or controlled by companies such as Hondata. I wanted to see if there were any active grassroots projects going on.

 

I think the DIY PGM-FI development is a dieing market. HRTuning is really the last guy that I think is still developing stuff for OBD1 ECU's, Neptune. IIRC he said something about working on some K series stuff, but I'm not 100%.

You could try to get hold of him and see what's up. I'm sure he will probably chime in and let you know. He is a regular helping hand in this forum.

There was a couple guys on CB7tuner that were deconstructing the Accord and Prelude ECU's. Haven't heard much from them in the past few months though.

 

People still have an outlet to develop plugins for Crome, but as Crome's creator isn't around taking care of the software, neither are those developers who tried to make it better.

If you can get in on the Accord/Prelude dev mentioned above, that'd probably be fun as it's mostly new terrain in the public eye. I have not heard what they're working on, though.

 

It doesn't have to be Honda if that helps at all. I know some people are working on the Genesis 2.0T ECU but it looks like a lot of that is being covered by a few people. I'll look into the Accord stuff.

As for Crome, I'm well aware it's dead. Waiting to get a full time position so I can pick up Neptune :-)

 

I'd like to see someone make some definition files for tunerpro RT

 

For what cars? Why TunerPro specifically?

 

You may want to check out the Subaru stuff. It's a very open group and all of their tools are public.

 

The Subaru and EVO stuff looks interesting if you can get over the initial learning curve.

Where is the Accord stuff going on at?

 

Although I don't know anything about this, that's what he said above.

 

Thanks. For some reason I completely missed the CB7tuner part.

 

I'm really struggling with Suby's management strategies - so complicated. mass air + dynamic advance + knock = uuugggghhhhhh. I really dislike it, but I'm toughing it out because I'm confident this is how they're all going to be pretty soon. I haven't tuned one, but from what I understand, the Nissan GTR is very similiar.

 

I'm applying for engine calibration engineer positions (just graduated with an MSME) so I'm sure I'll be force fed this stuff in a month or two. Do you have any good sources for getting up to speed on the Subaru stuff?

 

not sure if it still interests you but over on pgmfi.org forums they are still developing OBD0 code.

 

OBD0 isn't exactly exciting but it may be a good place to get started.

 

all i can say is winOLS.. tunes virtually everything, i got my obd2 maps from obd2 bins through it..need thousands of euros for the checksums and other stuff...

if you were to write a program, get an idea from winols, download the demo.

 

I feel your pain I have tuned many boosted Honda's and just picked up a 07 wrx, figured it will be no problem, my head hurts from all the reading and figuring out all the extra maps on these dam ecu's. After playing with romraider and ecuflash if really makes you appreciate all the good tuning platforms we have in the honda word like neptune and ectune.

 

What are the limitations of the WinOLS demo? Can I still pick out maps? (You already mentioned the checksum stuff.)

 

pretty much you can do everything with the demo version, its the saving/burning part thats where it stops. you can download memory dump everywhere and import it through winOLS. you cant save the modified dump into lest say .bins or any extension, youd have to burn/save the file through winOLS.

its an advanced hex editor with mapping features 8/16/32bit 0-255limit, i like maps and graphs im not like matrix where i can read raw numbers and see through it. those a the hex editor mostly made of. ive tried looking for hex editors with 2d/3d support but nothing useful yet...unless you make one

 

regarding ecuhack,misubishi,toyota,aem,motec... all of them, its mostly addressing that they develop.. they all use 10110, get a full winOLS and an engine simulator, i guarantee it hondata will keep an eye out on you.

 

thinking back to the tunerpro RT thing... that would be pretty cool. id like to mess around with some BMW's and VW's sooner or later... and im too stupid to develop my own software.

so i suggest you go there, since i already own ectune. hehe

 

uhhh why?

 

one of these days im going to look over at tunerpro..


that fancy hexeditor automatically looks up potential maps, tells the address where theyre at, its just up to you to distinguish which is which or their system lets you know what they are if they have them(checks the memory dump in their servers). i mean you can adjust a certain address and then the engine simulator tells you whats changed. i only suggested get a registered version because it makes it easy and fast to determine these address. and you get to do it on all ecu, petrol/diesel.

i want full control with my ecu granted neptune/hondata does some of that.. for instance i know theres an injector phasing in obd1 because i found it with these hexeditor.. why they dont use them? maybe checksum bugs.

standalone on the other hand... perfect control and very very clean. obd1 uses only about 10 out of 256bytes, the rest of that 246 is random numbers and trash. i imported my aem dump, what i saw in aem tuner, i saw them in winOLS. i just looked up the values and 1-255 verified everything.

 

I'm not sure what context you're referring to here, but in every one I can think of that's a false statement. If you care to elaborate.

 

sorry typo about 10 kbits not bytes. it looks misleading but i didnt mean that. also youre right i shouldnt have said trash because most likely its the on board diagnostics as whats occupying the unrecognized areas, look at the overview window

1st screen shot shows p73 ignition timing low/hi. in 8bit counting 10 column and 35 rows you get 2800 bits. including fuel map and injector phasing, add another 5kbits and a few more for fuel/ign correction...yeaay! about 10...good guess hehehe

2nd shot is 16x20(16x16 showing) ignition map in 3d from my aem calibration +

16x20 fuel + 16x20 inj phasing + 32x40 nitrous fuel/ign= 13kb

 

Pretty neat software.