[Diy_efi] Re: [ Diy_efi ] new EFI controller
BowTieVette at aol.com
BowTieVette at aol.com
Tue Mar 11 01:15:59 GMT 2003
--===============13274189537567782==
Content-Type: multipart/alternative;
boundary="part1_71.2e5b7b69.2b9e92a8_boundary"
--part1_71.2e5b7b69.2b9e92a8_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Hey Bill,
I'm still working it. It's based on the Phytec 555 CPU core with all the
drivers on board, in a MS sized case with one or two 54 pin auto grade
connectors depending on how its configured. Should meet the needs of most
rabid efi wack jobs except Greg who may have to wait for a 565 version. Its
mostly SMD though so the diy kit format probably would not work. It uses a
port of the efi332 code at SourceForge.
jc
Re: [Diy_efi] new EFI controller
> Reply-To: List for general do-it-yourself EFI talk <diy_efi at diy-efi.org>
> Message: 6
>
> 565 is 32 bit, various speeds (40MHz springs to mind) multiple TPUs more IO
> than you can shake a stick at etc etc.Designed to run the entire car.
>
> More HP than most could use. Greg is wierd so needs NASA spec stuff :-) He
> is also bigger than me, so I'm not gunna argue.
>
> Back on topic. Worth throwing a mail at JC. A few months back he was talking
> about doing such a beast as a successor to EFI332, but more user friendly.
> All the ECU you could eat for around the $500.
>
> Before you barf, we are talking something that would cost $5k as an OEM
> part. This is a SERIOUS MCU.
>
> Bill
--part1_71.2e5b7b69.2b9e92a8_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
<HTML><FONT FACE=3Darial,helvetica><FONT COLOR=3D"#008080" SIZE=3D2 FAMILY=
=3D"DECORATIVE" FACE=3D"Tempus Sans ITC" LANG=3D"0">Hey Bill,
<BR>I'm still working it. It's based on the Phytec 555 CPU core with all the=
drivers on board, in a MS sized case with one or two 54 pin auto grade conn=
ectors depending on how its configured. Should meet the needs of most rabid=20=
efi wack jobs except Greg who may have to wait for a 565 version. Its mostly=
SMD though so the diy kit format probably would not work. It uses a port of=
the efi332 code at SourceForge.
<BR>jc
<BR>
<BR>
<BR>Re: [Diy_efi] new EFI controller</FONT><FONT COLOR=3D"#000000" SIZE=3D2=
FAMILY=3D"SANSSERIF" FACE=3D"Arial" LANG=3D"0">
<BR><BLOCKQUOTE TYPE=3DCITE style=3D"BORDER-LEFT: #0000ff 2px solid; MARGIN-=
LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">Reply-To: List for general=20=
do-it-yourself EFI talk <diy_efi at diy-efi.org>
<BR>Message: 6
<BR>
<BR>565 is 32 bit, various speeds (40MHz springs to mind) multiple TPUs more=
IO
<BR>than you can shake a stick at etc etc.Designed to run the entire car.
<BR>
<BR>More HP than most could use. Greg is wierd so needs NASA spec stuff :-)=20=
He
<BR>is also bigger than me, so I'm not gunna argue.
<BR>
<BR>Back on topic. Worth throwing a mail at JC. A few months back he was tal=
king
<BR>about doing such a beast as a successor to EFI332, but more user friendl=
y.
<BR>All the ECU you could eat for around the $500.
<BR>
<BR>Before you barf, we are talking something that would cost $5k as an OEM
<BR>part. This is a SERIOUS MCU.
<BR>
<BR>Bill</FONT><FONT COLOR=3D"#000000" SIZE=3D3 FAMILY=3D"SANSSERIF" FACE=
=3D"Arial" LANG=3D"0"></BLOCKQUOTE>
<BR></FONT><FONT COLOR=3D"#008080" SIZE=3D2 FAMILY=3D"DECORATIVE" FACE=3D"T=
empus Sans ITC" LANG=3D"0">
<BR></FONT></HTML>
--part1_71.2e5b7b69.2b9e92a8_boundary--
--===============13274189537567782==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
_______________________________________________
Diy_efi mailing list
Diy_efi at diy-efi.org
http://www.diy-efi.org/mailman/listinfo/diy_efi
--===============13274189537567782==--
More information about the Diy_efi
mailing list