Hello!
A long post for a first, but I've been lurking for a few months...
A little about me:
I have been tinkering with cars since I was 16, rebuilding my first engine when I was 17 in a '65 Olds 442.
In the last twenty some years or so I have experimented on a hobby basis with electronic design, programming and various processors.
My oldest hacks include a memory expansion card for the VIc-20 and a SCSI HDD interface for the Amiga 500. (Sometimes it's hard to believe that I paid $300 (in 1988 dollars) for a 20 MEGAbyte SCSI disk drive)
I currently work in the technology industry as a C/C++ programmer.
My project:
I am preparing to install a GM L67 (3800 Superharged from a GTP) engine in my playtoy, an '88 Formula Fiero 5 speed.
After considering ODBI and OBDII options, I decided on GENBOARD 3.3, a VERY impressive piece of hardware!
I have a few questions before I plunk down some cash on one...
I noticed on the Wiki that the VEMS-GROUP is moving towards ver 4. Does this obsolete 3.3, or is that an entirely different product line?
What is the future for support of 3.X?
What hardware features of 3.3 are currently supported in the software?
Knock? Both banks?
EGT? Both banks?
WBO2? Both banks?
NB02? Both banks?
SPI MMC data logging?
Mass Airflow (MAF) Sensor?
If I choose to use NBO2 (factory sensors) is the code for this functional?
It appears that A/D channels are available for EBP and FP, are they used with the current firmware?
Is there any code to support emission controls (EGR, EVAP release, etc)?
Is there a timeline to support unimplemented features?
Is the VEMS version of MegaTune a fork of the orginal, or are the source trees common? It appears that firmware and MegaTune are released as a package?
Is there a live repository of source code for the firmware and MegaTune? (CVS, SVN) The sourceforge one is of date with the code in the Wiki. (028)
I plan on doing some firmware hacking once I get the board...
What is the current resource allocation and utilization? Percentage FLASH Memory, RAM, ports, etc. (How much overhead for new functions is available? Assuming current release with default make)
Is there a 'recommended' matrix for un/seldom used pins in order to preserve compatibilty with existing fuctions?
I'd like to add:
1. MCP2515 CAN controller to eventually connect a (yet to be designed) intelligent LCD display of some kind. (Digital dashboard). I'll need an interrupt to interface. Is there one available on the '128 that is available and won't break compatibilty with existing firmware? It appears that a CS line is already in place (CS_CAN)
2. Removable media MMC datalogging via SPI. (Again a CS appears to be available (CS_FLASH). (Very simple FAT32, Single file, root only) || (RAW format, read out through 3.3 RS232?)
3. Shift light, and generic 'idiot lights' (TOO HOT, TOO LEAN, etc) , for use until I design a display. (Extend LBUS w/ another '259 if not enough lines? CS? What is the function of SS pin 10 on header?)
4. Oil level input (Sensor factory installed on L67, it's there why not use it) (A/D channel allocations?)
5. Possibly unimplemented features inquired about above.
Maybe with the addition of the VSS (Vehicle Speed Sensor) input it should be possible to calculate MPG? Add a Fuel level input and have instantaneous MPG, Distance to empty... (I think I saw an article on this recently, can't seem to find it right now, Circuit Cellar?)
Finally, What is the process for contributing code to the group?
Answers appreciated!