[Efi332] (from a Newbe) Just want to know...

[BowTieVette at aol.com]

Hi Paul,
There is not too much traffic on the old efi332 list these days. We lost  
most of the subscribers when the diy server took a dump a while back and many  
folks never came back. I still have a working system in my car, and it still  
works great.
 
I know that Doug's target is an FSAE car, what is your target?
 
Make it three nuts on the use of the Phytec. I have a carrier board  designed 
and built, with software bringing up the rear. There are a couple of  photos 
of the board at James MPC555 site here: 
_http://www.ee.ualberta.ca/~jasmith/mpc555/_ (http://www.ee.ualberta.ca/~jasmith/mpc555/)  look  at bullet number 8 
near the top amongst a note about the mc33394 power  supply. Its chockablock 
full of drivers and IO capability with all TPU  lines going to drivers of one 
sort or another. There are at least a couple of  other lurkers also working 
with the 555/565 on this list.
 
I'm using a port of my 332 code with a pile of enhancements. I use a  Labview 
based console program for serial comm, datalogging, replays etc. Most of  my 
old stuff, although now quite dated is on the sourceforge efi332 site  
including a few notes on the 58XX TPU functions. I should be replacing the  venerable 
332 in my car sometime this summer.
Jeff
more notes below..
 
 
In a message dated 6/3/2005 5:41:37 AM Eastern Standard Time, doug at udel.edu  
writes:

I'm also  working on a new Phytec-555 based computer, for the University 
of  Delaware's Formula SAE car. I had a system based on the old EFI332 
4-layer  board working, but it suffered a series of glitches after 
sitting for a  few months that I was unable to fix, or even trace down. 
We decided to go  with a new system that could avoid the shortcomings of 
the original 332  board (large, high component count, glitch-prone). 
Doug, ... Thats too bad about your 332 board, I have had great luck with my  
units, they are solid performers. I'm puzzled by your high component count  
comment. It seems to me that despite the greater integration of the 555, you  
will need far more "components" to take advantage of the IO on the 555. Those  
pullups/downs and switches really add up. 
 

I'm  
presently designing the carrier board that will hold input buffers,  
signal conditioning, injector drivers, and open-collector outputs to  
connect to the ignition box.

I expect a lot of my code to carry  over, and the remainder is mostly 
configuration, which should be simple  (no need to interface with 
external ADC's, etc., like on the 332 board). I  developed a 
serial-port-based tuner program of my own that can be  configured for 
multiple arrangements and sizes of tables (e.g. you can  change table 
resolution without any programming changes), which I'll be  updating to 
support floating-point data types. 
Hee, I just use large by huge tables right off the bat..

You can  take a look at my codebase on 
the DIY-EFI ftp site, in /incoming; the code  for the 332 is 
efi332-code-udsae-2005.tar.gz and the tuner program is  zut-1.0.tar.gz.

--Doug Brunner

Paul  Helmuth wrote:

> ...if there is any current activity on the original  EFI332 project, or 
> of course, an updated version of the  project.
>  
> I have been working on developing an ECU based  on the 
> Motorola/Freescale MPC555 for some time. I am working with the  Phytec 
> development board, the GCC tool chain, a Macraigor Wiggler,  and a 
> Flash Programmer from Macraigor.
>  
> I am  working with a 60-2 crank trigger wheel from Electromotive (with 
> one  of there sensors). I am using the TPU micro code from the EFI332 
> FTP  archive that is set up for a 60-2 input train.
Same here although with slightly modified microcode.


>  
> I have quite a bit of stuff working, though not  a complete system yet. 
> I will be testing the ignition triggering this  month, then work on 
> adding the fuel injection.
>  
>  I have a pretty nice lap-top monitor/tuner application that 
>  communicates with the MPC555 through one of it's on-chip serial  ports.
>  
> In the past, I have had some questions about the  TPU microcode, but I 
> have the major functions (PMMX, PSP12, LPWM2)  working just fine now.
>  
> Just wanted to see if there were  some other nuts like me, that I could 
> share being nuts  with.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.diy-efi.org/pipermail/efi332/attachments/20050603/505907c0/attachment.html