The idea is not to change anything simply to decompile the image to get the assembly code out and then make sense of it. Or to figure out if its simply encrypted and therefore decrypt. The concept is exactly what MM said above. Once you have the code, you can locate the variables, make changes, recompile it, and then use it.

For example, if they are using a formula to calculate a specific output, then by tweaking a constant within the formula or changing the formula itself you could get it to do what you wanted.

I'm sure lots of car nuts have tried all sorts of things...but I will go out on a limb and say that very very few actual software engineers have...and probably no "real" crackers have...

 

MM I did not know it was so freely availible...thanks...I really didnt feel like poking at my RX for it cause its my daily driver.

Please braindump me what you know if possible or point me to a guide. I'll need to do the obvious homework to figure out what I'm looking at.

 

Just sent you an email requesting access to your download section MM...

 

Since we are there, I might as well try getting into the Int-X code too and see what I can scoop out of that one :-) Maybe write a little add-on to the Int-X programming software...
I haven't done much decompilations, but it could be interesting to try.

 

The Int-X software will probably be fairly easy to crack since it is so sucky.

The main thing I'm interested in, at the moment, with regards to the EMU software is fixing the coolant temp input.
It simply reads maximum all the time, regardless of what is going on. I've tried sending all kinds of signals to the temp input and it ignores them.
Honestly, I'd just a soon turn the coolant variable off in the auto tune feature.

 

Assuming Int - X is used...

It just seems to me that using the MAF would be a more efficient way to monitor the temps/density. Am I wrong in thinking this?

It also seems that all other tuning modules also do not utilize the MAF when tuning...I am basing that hypothesis from the conversation I had with an FD tuner. Hence the reason they remove those sensors entirely.

F.Y.I. I happend to be a low level programmer which explains my interest in this. I understand the theory but I do not have the skill to implement.

 

The temp sensor inside the MAF housing provides temps to the ECU, which provides inputs to the Int-X. The Int-X doesn't have a temp sensor, which it sounds like you are implying.

 

Yes, but it doesn't read it correctly or with enough granularity to be useful.
It does the same with coolant temp.

The FD was a speed-density system. It is different than the SE3P, which is MAF.

 

We should start a new thread since this one seems to be going off topic...

"Cracking the ECU"

 

Wait a minute...the files on the download section are for the Greddy unit...I am looking for the firmware for the RX itself (PCM)...am I missing something...besides the Greddy unit...

 

If you do please post link I would like to participate in conversation.

 

New Thread Started

https://www.rx8club.com/showthread.php?p=1749658

 

Were not trying to crack the PCM. Dozens of really capable people are already working on that.
Dozens have already given up.
There is a huge thread on the subject.
Search button is your friend.

I want to crack the EMU software.

 

There is already a thread with that title. I think it's dead...

 

Not dead at all. I get a post nearly every day.

 

Thats cause they want to see your avatar.

 

We have had secsess with just wireing in a air temp sensor from a 3rd gen into the maf plug. Would that work with the Ultimate also. Im trying to wire in a trimmer to the coolent sensor to see if I can shave the temp a little.

 

didnt have the rite value resister, dam. Im getting 4.98 volts. Cam did gain air temp control. For some reason the intX dosnt read the stock temp gauge. He wired it through the stock wiring also.

 

Voltage is 4.84 volts almost completely cold. .20 volt sensitivity give or take.

 

I want to hear more about this.

 

The Int-X does read the air temp and the coolant temp already (though it shows the air to be 10°C colder than it is).
The problem is the granularity of the correction screen.
You need a full matrix like the load screens to get an accurate density correction.

 

hes reading the charge temp not the intake temp.

 

Well, that is much better.
However, what is he doing about the fact that you can only make corrections on an exponential scale that is at least 8°C and as much as 17°C across at the nominal intake twmp range?
Every 1/2°C on intake temp can be as much as .4ms of pulse width!

 

Not much can be done here without changes to the software, but some temp correction is better than none. And lately, with temps varying from 55 - 85 degrees within a day, it affects my charge temps too, and it is a pain to keep retuning. I Just want to bump overall fuel a bit when it is colder or pull when it gets hotter to compensate for the variations of AFR if it is outside of the reasonable range.

MM, your avatar says something in Russian...
"Будет тем запахом?"
Is that a language you can speak?

 

Its about cheese and if it smells...

well..

Avatar:
Будет тем запахом = Does it smell?

Location:
Отрезало сыр = Cut Cheese

I was confused earlier found the forum and linked it to the posting to redirect the traffic so no worries. I thought I would be a nice guy and take a look at the "Greedy" unit. I dont know how much success I will have since I dont have one but ehh...wot da hell...I'll keep ya posted...