he was looking for a bin file

 

He also mentioned XDF files in his last post, which is essentially mapping memory locations to tables, variables etc.

 

If I knew how he got the Bin file and an adapter to the E67 ecm, so I don't have to rewire if it doesn't work to get it back, I would do this. I, more or less, think I have the idea of what he did. It appears he never got it running right because he disappeared.... Or just wanted to sell his findings.

 

may I sugest that you get a fried LSJ pcm rip the conector out of it and wire it up to pigtails that will fit into the E67 ecm and creata a plug and play harnes for testing with, I think it will make things easier for you in the end

 

Subd

 

I was just literally talking to someone about doing the same thing haha. Swapping back and forth if it didn't work would be a pain in the ****

 

Well, that and find I spare harness to take the connections from

 

why not circumvent all of this crap and stick a damn standalone and a cable driven tb on it and call it a day.

The last lsj ecm up date from hpt was the dynamic airflow table adder. nothing since then. that was 2008.

 

What system do you suggest?

 

keeping the gauges is the key and unless some makes a plug and play I doubt anyone would bite on it

 

This shouldn't be an issue...in theory. You can still retain your gauge cluster and all auxiliary items controlled by the ECM/ECU/Whatever. A Parallel install will allow this.

A parallel ecu install allows the stock ECU to see all the sensors and think it is working normally because everything is within parameters of the stock ECU. An aftermarket ECU will ACTUALLY control the engine and share some sensors (some that are resistance based sensors, such as engine coolant sensor, can't be shared).

Why I say in theory is sometimes the stock ECU can find out that its outputs have been shut off (stock ECU demand one thing but another thing happens) and throws a code. You disable the code and problem solved. There might be little glitchy things that will happen, though.

This would NOT be a piggy back system because you are NOT sharing any engine responsibility between the 2. Only the aftermarket ECU


I have wondered about doing this and have researched it a bit. It is VERY involved and being the first would be pretty tough (or at least not getting help from others whom have done it). It has been done with racing Ecotecs but none of them stick around.

In the GM build book for Ecotecs, doesn't it talk about a F.A.S.T. X.F.I. system?

 

the pcm sends the engine info to the bcm so you need a standalone that will communicate accordingly

 

and what stand alone would that be?

 

you tell me

 

exactly

 

That's lwrs10 from this forum.... I'll ping him and see what's up.

 

someone dose custom pcm stuff zzp was considering doing one for the lnf

duh ya don't say

 

I did say and the post from the other site was Nov of last year in case you didn't catch that.

So if he has the file, in which the first poster mentioned he does, then why have we, or he, not done anything with it....

Answer that smart assss.

 

I caught before you threw it and I already know what has happened with it all

so answer that smart ass

 

The aem standalone is reasonably priced. I don't think retaining gauge operation would be that difficult.
Heck even an ms3 is a decent and affordable way to go of you can do basic wiring and follow instructions.

 

What info that the sensors a ND the processor wouldn't send?

 

The reason is he doesn't has been messaged but won't answer. We also posted on his thread asking with no response.

 

no not that

 

it would be extremely difficult. the aem probably wont work with gm's secret squirrel can bus

 

Difficulty is directly proportional to the skill level of the user