EFIDynoTuning Forum

Do any of you have a good startup tune with the expanded VE table and 80 lb injectors? I'm getting closer to you installing my engine and am hoping that I don't have to do major tuning work while trying to break it in correctly.

Below is from the moates.net support site. Just put a switch between ground and A0. Program one bank with switch off and another with switch on.
Manual Switching
Like its F3 predecessor, it is possible to manually switch between programs with the F3v2.

Couple things to remember:

At our sole discretion, custom wiring for switching may void your warranty.
The connector is a Molex latching 4 pin 0.1″ header with male pins, very common. You can buy a latching 4 pin female header from the usual sources or buy short cables from us to cut up.
Do NOT feed voltage into the F3v2!!! GROUND ONLY!
The 4 pin header consists of GND, A2, A1, A0. Whenever possible, use the GND provided on the header NOT a chassis ground!
“1” (high, floating, open, unconnected) is the default state. “0” (GND) on a pin changes that address bit
Tunes are binary format, i.e. 000, 001, 010, 011, 100, 101, 110, 111. “0” on the switch is generally “111” and “8” on the switch is generally “000”
If you use a switch or otherwise to ground pins automatically (nitrous?) to switch tunes while the vehicle is running, you must also remember to ground the same pin(s) during programming.

It's pretty simple, how many tunes do you want to use? If you just have a couple you could do it with a single toggle switch. You're just connecting pin zero to pin one

I was mistaken in thinking that a standard EEPROM could interface directly with the CPU so i agree the j3 port is the way to go. It would be nice to figure out a way to write the internal EPROM via j3 as I presume that is how Ford did it in the factory. It would be cool to do a uv erase like this: https://youtu.be/_sSuzDg4ntA

MX-Brad wrote: ↑2022 Dec 06, 15:40 According to a post on the Corral, MF Kustoms will be producing/selling the Quarterhorse. Decipha probably knows stuff, but is being very quiet. :)

Thanks for sharing that great news. I have been brainstorming and I believe the CPLD code should become part of the OpenEEC project so technically anyone could produce at least a F3 style device. The EEPROM and Xilinx chips appear to be available in smaller quantities. Does anyone have access to the PCB design for the F3V2? We should make everything public so we are never tied to a company that can be threatened or shutdown.

The Quarterhorse is one I'd leave to the professionals.

xd4.1efisc wrote: ↑2022 Nov 30, 05:51 Top photo was a Moates product not available to the public. I managed to purchase 8 of them last year. A custom Burn2 was also required to program them.

That is what I was thinking just not with a surface mount device!

Would you be able to send a pic of the memory device? I assume it is not publicly available as sailorbob states but it would be a good starting point.

The point I am making is referring the weird pin out of the EEC-IV PROM/EPROM. It could be removed and adapted using a small PCB with pins soldered in it's place that routes to a standard pin out dip socket. This would be an extremely cheap part and would only require readily available EEPROMS.

I've always thought that a simple PCB with pins and a socket. Could adapt for any standard EEPROM. We could even build in a header for programming/tune switching on the fly. This could eliminate the need for a xilinx chip.

wwhite wrote: ↑2022 Oct 20, 23:04

efloth wrote: ↑2022 Oct 20, 15:48 I'll be testing this theory today.

Your code snippet is, um, not correct. R56 is written twice first value set by Func_c1ac is overwritten when Func_c2ac sets R56 again.
R5C is not set.

Not sure if you realize the code changes you have made do not look correct to me.

Nice catch! Thanks for proof reading my code The second function should be written to R5c as before.

wwhite wrote: ↑2022 Oct 20, 23:04

efloth wrote: ↑2022 Oct 20, 15:48 I'll be testing this theory today.

Your code snippet is, um, not correct. R56 is written twice first value set by Func_c1ac is overwritten when Func_c2ac sets R56 again.
R5C is not set.

Not sure if you realize the code changes you have made do not look correct to me.

Nice catch! Thanks for proof reading my code The second function should be written to R5c as before.