EfiMini Gallery

From efiHacks Wiki
Jump to: navigation, search

Our efiHacks Gallery

As the name already says Gallery. Isn't this the place where the artists hang out in their famous Ateliers :) While some of the tuners are real artists in their trade, we do not want to claim to be artists ourself, simply just engineers.

We also want to show our Hacker buddies that development doesn't need to be in a sterile office environment with a latest state of the art shop / lab and a 20k plus dyno surrounded by Snap-On. Nice to have for some, but not for all.
One of the purpose of the efiMini is the ability to make short data records wherever you drive / ride and later on analyze it.

efiMini Development Story :

Now back to reality. We are providing a small glimpse into parts of the effort to develop the efiMini.
It all started with the decision to use an arm-7 CPU with built in USB and the right timer peripherals to provide fast and accurate Timing I / O.
We chose the Keil MCB2148 eval board and the low cost of a 2 layer interface board to represent the typical I / O of the future efiMini.
Then for the firmware there was only one choice, C++ provides the modularity and encapsulation for a clean design.
Borland's C++ Builder was probably not the best choice, but we knew to write Win-GUI apps with it already, had a whole bunch of libraries and didn't want to spend more time. C++ Builder isn't bad at all, it just seems on a dead end with Borland fading away. This hardware design task was easy. What followed was month and month of USB HID and MSC code in the firmware and USB code in the Win-GUI app, all the ISR code in firmware, the SPI code and SCSI drivers for SD memory support (currently not used and not included), the FAT16 code (only partially used), the SPI flash double buffer support with main-loop state machine, the UniTalk efiLabs communications protocol and of course all of the fuel injection related code and lots more.
Did we forget all the Win-GUI forms and dialogs and then the never ending data log code where we went for about 6 month (probably more) around in circles until we found the right design concept. We're sure there was way more, but who's really interested in knowing it :)

efiMini Development Gallery :

1st Testing on the KIA :

After we tested whatever we could in simulation and long oscilloscope verification sessions, we installed a wiring harness into a KIA Sephia to do a real world test. We discovered the ECUs 2.5 V virtual ground on the 4 wire O2 sensors and revised our schematics. We developed analyzer interface connectors with injector loop-backs to avoid a dead engine in the middle of a traffic light, etc. The analyzer interface plug allowed us to test almost everything, except driving the injectors. We did do some more injector driving tests on low traffic roads and on the dyno.
It was fun sitting in the passenger seat checking the engine with the Win-GUI app.
The efiMini eval setup and the rev 1 board were used for testing.

KIA Testing Session Gallery :

Tuning at myJet :

And now back to the artists. One of our 1st visits to one of these artists happen to be during winter 2012 in Vienna Austria. We installed the new rev 1 efiMini controller board on a KTM-690 and gave it a try. We were able to discover some bugs and fixed them. It also showed that the narrow band O2 sensor can be used for tuning.

What a memorable test session.


more to come as we make time to publish the development life with our efiMini.


Note : All published design documentation is Copyright efiLabs.com and its use is without exception FOR NON COMMERCIAL PURPOSE ONLY. For commercial licenses contact efilabs.com ... try us, we're reasonable :)

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox