Recieved a new Frankenstein board... planning to fire up the motor this week-end on it if I can figure it out. Am I still in the running to be running engine #2?
So for just the first 'run' the only needed input would be 150/150/210 camshaft signal. It would need to be wired to PC6 either via op-amp channel 11 or via the VR chip - both ways you would need to add a jumper wire to the Frankenstein.
Another thing: I've added most of the commands as commends (stuff following '//' symbols)
If you decide to go with the commands, you should need to execute 'writeconfig' command after changing some of the parameters and reboot the MCU.
Oh, by the way most of this stuff is exposed via Tuner Studio - same thing, some changes (pinout, pin modes) would require MCU reboot. Did you try Frankenstein with TunerStudio? The .ini file is in the same .zip with the firmware binary. That miniUSB on the Frankenstein is the Tuner Studio port.
I will PM you my cell, feel free to call if you need any guidance, this is probably a lot of info.
you are on it with a lot of info- but the little one went to bed early so off I go on this- board unpackaged and power connector on... now working on firmware update
That was the hardest thing - to change engine type, should be easier from here on
Can you put a jumper wire between PD1 (trigger simulator pin) and PC6 (primary trigger input)? This would show you something on the 'digital sniffer' tab. The green vertical line is TDC and the is a status bar which shows mouse cursor angle. I hope I've set it to wasted with 10 btdc timing. Also try lower RPMs ('rpm 200') to see how it would act while cranking
I've just updated the firmware once again - there was a bug related to timing map. You are fine for a first run, but you would need to update if you want to actually change timing from the 7 BTDC hard-coded.
OK so a little bit of firmware and a bit of exhaust on the agenda tonight....
I already got busy with injectors and ignition. white is #1 brown #2 yellow #3 and green #4. 2 smaller gauge white are ignition triggers to the J701's I'm using.
Beware the 5V on the high low. You'll may need a series resistor to limit current. The hi/low can only reliably drive .125amps. At least to start you'll want the series resistor to ensure you stay under that limit. You'll want as low of a resistor as reasonably possible. It may allow for no resistor. Take note the .125A drive is a thermal limit, basically it gets to hot if you drive more. To get the datasheet specs you need a better thermal package.
Do we both see "Ford Aspire" in the title? Pretty often all your settings would be reset while updating the firmware. That's the whole reason why we have the defaults hard-coded. It has to reset so that new firmware has a valid configuration, not just some random bytes from the previous set of settings which might be shifted or just different between versions.
Good news and bad news- good news is that as its cranking frank is triggering the ignition and fuel injectors. Bad news is the timing is not stable it appears to alternate between firing cyl #1 at ~65btdc and about 125btcd. Both these are approximations as my timing light maxes out at 60 degrees advance and I had to make my own tdc mark to figure out what was going on.
That's probably because we only use your primary trigger wire.
I've just created a binary which would record the 2nd trigger so that we can use proper angles. Please disconnect spark/fuel, remove all the old logs from your old/ and record some cranking with the new firmware after you do 'set_engine_type 2' and reboot it.
first value is the angle, next is event id. 200x is secondary rise, 300x is secondary fall. I will decipher this completely tomorrow morning, right now I am morning pin PC6 already - http://rusefi.com/forum/viewtopic.php?f=3&t=469&p=7322#p7308
Sounds good- I think we are really close... if we can get the ignition stable I'm sure this thing will run! I guess I'll go in the house and chase my wife around the bedroom for this evening and check back tomorrow.