[Gmecm] P6 ECM information?

Steve Ravet Steve.Ravet
Fri Apr 7 14:17:31 UTC 2006


 

> -----Original Message-----
> From: gmecm-bounces at diy-efi.org 
> [mailto:gmecm-bounces at diy-efi.org] On Behalf Of Ryan Hess
> Sent: Thursday, April 06, 2006 11:15 PM
> To: gmecm at diy-efi.org
> Subject: RE: [Gmecm] P6 ECM information?
> 
> It may be better than *writing* assembly, but makes it close 
> to  impossible for us to undo their thoughts.  On the ASICs, 
> does this  mean that we're stuck using whatever crank 
> reluctor and # cylinders  they're originally intended for?  
> In otherwords, with the 7730,  you can just change the 
> cylinder select and run anything.  If the  timing logic is in 
> the hardware, and built for one specific app,  doesn't that 
> mean that they're no longer universal?

It's my understanding that the TIO (which is similar in concept to the
CPU32 TPU) has microcode to match the engine configuration.  There is an
L4 box, a v6 box, and a v8 box.  Architecturally I think these boxes are
very similar, meaning that code written to run on one will likely run on
all of them.

>   
>   Now here's my deal - I very much like the GM code.  They've 
> spent  their money to make it run an engine in all 
> conditions.  I scanned  over the EFI332 stuff, and it's not 
> what I want.  It appears to be  similar to the megasquirt project.  

There are 2 codebases for efi332 but you're right that they're likely
not as sophisticated as the GM code.  On the other hand they're well
documented unlike GM code, and the high level source code is available.
With the GM stuff you're reverse engineering so it's difficult to gain a
full understanding of the code, and therefore more tricky to make
changes.  Certainly there are fans of both approaches.

--steve


-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium.  Thank you.





More information about the Gmecm mailing list