1995 Dodge Neon

Post by **AndreyB** » Wed Jan 22, 2014 9:16 pm

This table looks pretty linear to me, I would make it a linear function based on two points for now.

Vanquizor · Post by **Vanquizor** » Wed Jan 22, 2014 10:04 pm

Sorry temp measurements are all in F as thats what my MS reads.

Post by **AndreyB** » Wed Jan 22, 2014 10:12 pm

Vanquizor wrote:Sorry temp measurements are all in F as thats what my MS reads.

Fixed.

I guess I would use this project to torture our friends from Belize, the Cayman Islands, Palau, and the United States and use Celsius.

Vanquizor · Post by **Vanquizor** » Thu Apr 03, 2014 3:13 pm

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?

Post by **AndreyB** » Thu Apr 03, 2014 3:27 pm

Vanquizor wrote:Am I still in the running to be running engine #2?

Mx-5 is now in the lead, but yes, the race is still on!

You would need to download fresh java console and fresh firmware from http://rusefi.com/build_server/ you would need to execute
set_engine_type 2 command in the console to switch it to your defaults, you would need to wire trigger input either using the op-amp inputs http://rusefi.com/wiki/index.php?title=Manual:Hardware_Frankenstein_board#Step_2a:_Hall_sensor_input or the VR chip http://rusefi.com/wiki/index.php?title=Manual:Hardware_Frankenstein_board#VR_input (you are the yellow and green jumper wires)

you would also need a red jumper wire from +5 to 'vp' pin in the high-side corner if you are driving your ignition module with +5 http://rusefi.com/wiki/index.php?title=Manual:Hardware_Frankenstein_board#High_side_driver

While you are looking at the trigger I would post the recommended injectors/fuel pump pinout a bit later.

puff · Post by **puff** » Thu Apr 03, 2014 6:09 pm

don't forget dodge neon recently got rid of one of the trigger sensor inputs by default

Post by **AndreyB** » Thu Apr 03, 2014 6:41 pm

puff wrote:don't forget dodge neon recently got rid of one of the trigger sensor inputs by default

That's just for now. Once we crank it and record actual angle information for both trigger signals it would be reinstated.

Post by **AndreyB** » Thu Apr 03, 2014 9:57 pm

These three links could help
http://rusefi.com/wiki/index.php?title=Manual:Software:User/en
http://rusefi.com/wiki/index.php?title=Manual:Engine_Type
http://rusefi.com/forum/viewtopic.php?f=5&t=210#p4038

You would need set_engine_type 2
I am working on your configuration to get it closer to reality, will post once I have it ready.

Post by **AndreyB** » Thu Apr 03, 2014 11:09 pm

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.

Now, output pinput: dodge_neon.c

General Frankenstein pinout is here

Post by **AndreyB** » Thu Apr 03, 2014 11:16 pm

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.

Vanquizor · Post by **Vanquizor** » Fri Apr 04, 2014 1:46 am

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

Vanquizor · Post by **Vanquizor** » Fri Apr 04, 2014 2:03 am

ooohhhh exciting times... I think it knows its a neon!

2014-04-03 19_58: SerialManager: Opening port: COM4
2014-04-03 20_00: CommandQueue: SerialIO started
2014-04-03 20_00: CommandQueue: Sending [sec!17!set_engine_type 2]
2014-04-03 20_00: EngineState: FLASH_DATA_VERSION=20140401
2014-04-03 20_00: EngineState: unrealistic intake temperature 2147483647.83647
2014-04-03 20_00: EngineState: Reseting flash=3348
2014-04-03 20_00: EngineState: Flashing with CRC=80
2014-04-03 20_00: EngineState: Flash programmed in (ms): 1929
2014-04-03 20_00: EngineState: Flashed: 0
2014-04-03 20_00: EngineState: Dodge Neon
2014-04-03 20_00: EngineState: configurationVersion=1
2014-04-03 20_00: EngineState: RPM bin: 0.00000 0.00000 0.00000 0.00000 0.00000 0.00000 0.00000 0.00000 0.00000 0.00000 0.00000 0.00000 0.00000 0.00000 0.00000 0.00000
2014-04-03 20_00: EngineState: Y bin: 0.00000 0.00000 0.00000 0.00000 0.00000 0.00000 0.00000 0.00000 0.00000 0.00000 0.00000 0.00000 0.00000 0.00000 0.00000 0.00000
2014-04-03 20_00: EngineState: CLT: 1.00000 1.00000 1.00000 1.00000 1.00000 1.00000 1.00000 1.00000 1.00000 1.00000 1.00000 1.00000 1.00000 1.00000 1.00000 1.00000
2014-04-03 20_00: EngineState: CLT bins: -40.00000 -30.00000 -20.00000 -10.00000 0.00000 10.00000 20.00000 30.00000 40.00000 50.00000 60.00000 70.00000 80.00000 90.00000 100.00000 110.00000
2014-04-03 20_00: EngineState: IAT: 1.00000 1.00000 1.00000 1.00000 1.00000 1.00000 1.00000 1.00000 1.00000 1.00000 1.00000 1.00000 1.00000 1.00000 1.00000 1.00000
2014-04-03 20_00: EngineState: IAT bins: -40.00000 -30.00000 -20.00000 -10.00000 0.00000 10.00000 20.00000 30.00000 40.00000 50.00000 60.00000 70.00000 80.00000 90.00000 100.00000 110.00000
2014-04-03 20_00: EngineState: vBatt: 0.00000 0.00000 0.00000 0.00000 0.00000 0.00000 0.00000 0.00000
2014-04-03 20_00: EngineState: vBatt bins: 8.00000 9.00000 10.00000 11.00000 12.00000 13.00000 14.00000 15.00000
2014-04-03 20_00: EngineState: rpmHardLimit: 4000
2014-04-03 20_00: EngineState: rpmMultiplier=0.50000
2014-04-03 20_00: EngineState: tpsMin: 0
2014-04-03 20_00: EngineState: tpsMax: 0
2014-04-03 20_00: EngineState: timingMode: 0
2014-04-03 20_00: EngineState: fixedModeTiming: 50
2014-04-03 20_00: EngineState: crankingChargeAngle=70.00000
2014-04-03 20_00: EngineState: crankingTimingAngle=0.00000
2014-04-03 20_00: EngineState: globalTriggerAngleOffset=510.00000
2014-04-03 20_00: EngineState: idlePinMode: 0
2014-04-03 20_00: EngineState: malfunctionIndicatorPinMode: 0
2014-04-03 20_00: EngineState: analogInputDividerCoefficient: 2.00000
2014-04-03 20_00: EngineState: idleValvePin: 66
2014-04-03 20_00: EngineState: fuelPumpPin: mode 0 @ PC13
2014-04-03 20_00: EngineState: injectionPins: mode 0
2014-04-03 20_00: EngineState: injection 0 @ PB9
2014-04-03 20_00: EngineState: injection 1 @ PB8
2014-04-03 20_00: EngineState: injection 2 @ PE3
2014-04-03 20_00: EngineState: injection 3 @ PE5
2014-04-03 20_00: EngineState: ignitionPins: mode 1
2014-04-03 20_00: EngineState: ignition 0 @ PE8
2014-04-03 20_00: EngineState: ignition 1 @ NONE
2014-04-03 20_00: EngineState: ignition 2 @ PE10
2014-04-03 20_00: EngineState: ignition 3 @ PE1
2014-04-03 20_00: EngineState: confirmation_set_engine_type 2:17
2014-04-03 20_00: CommandQueue: got valid conf! set_engine_type 2

Post by **AndreyB** » Fri Apr 04, 2014 2:45 am

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

Vanquizor · Post by **Vanquizor** » Fri Apr 04, 2014 3:01 am

Good news I've attached some jumpers and the STM powers up when docked on frank powered by my 5v source!

Vanquizor · Post by **Vanquizor** » Fri Apr 04, 2014 3:10 am

pd1-pd6 gives me this:

If I'm reading it right it looks like 10ms of fuel x4 per cycle and 15 degrees spark lead at 200RPM

Vanquizor · Post by **Vanquizor** » Fri Apr 04, 2014 3:36 am

even better news- with crank and cam on in11 and in12 frank is happy and we get signals while cranking.

Post by **AndreyB** » Fri Apr 04, 2014 7:58 pm

If you are trying anything this weekend: on Saturday I am busy at the garage between noon and 4pm CST, no plans for Sunday yet.

I've added some commands to the wiki - see Manual:Software:dev_console_commands#Fuel_Control

And you have most of the base values in https://sourceforge.net/p/rusefi/code/HEAD/tree/trunk/firmware/config/engines/dodge_neon.c

Vanquizor · Post by **Vanquizor** » Fri Apr 04, 2014 8:46 pm

We can drink beers and celebrate this week-end... I'll start the car engine tonight.

Post by **AndreyB** » Fri Apr 04, 2014 11:28 pm

I've just updated the firmware - the bins were all zeros in both tuning tables so values were totally static for your engine configuration.

Post by **AndreyB** » Sat Apr 05, 2014 12:56 am

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.

Vanquizor · Post by **Vanquizor** » Sat Apr 05, 2014 1:11 am

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.

kb1gtt · Post by **kb1gtt** » Sat Apr 05, 2014 1:21 am

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.

Vanquizor · Post by **Vanquizor** » Sat Apr 05, 2014 1:30 am

I think either I broke something in my soldering or something is buggy in the new firmware- here is my crank over after updating:

Post by **AndreyB** » Sat Apr 05, 2014 1:34 am

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.

Vanquizor · Post by **Vanquizor** » Sat Apr 05, 2014 1:46 am

sooooo about that set engine type command... kinda important to execute after updating firmware...

Vanquizor · Post by **Vanquizor** » Sat Apr 05, 2014 2:46 am

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.

Post by **AndreyB** » Sat Apr 05, 2014 3:17 am

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.

Vanquizor · Post by **Vanquizor** » Sat Apr 05, 2014 3:34 am

new data file

Post by **AndreyB** » Sat Apr 05, 2014 3:44 am

Looks good:

analog_chart|0.00000|0.00000|20.41710|2001.00000|59.15646|3002.00000|74.27574|2003.00000|78.66276|3004.00000|100.05138|2005.00000|105.68316|3006.00000|128.84783|2007.00000|134.96539|3008.00000|201.19572|9.00000|235.09266|2010.00000|237.50628|3011.00000|250.97094|2012.00000|255.14544|3013.00000|276.88320|2014.00000|282.19619|3015.00000|304.73852|2016.00000|310.52209|3017.00000|373.20031|2018.00000|393.81475|1019.00000|416.79727|3020.00000|436.13659|2021.00000|442.36041|3022.00000|463.12664|2023.00000|468.92538|3024.00000|491.89273|2025.00000|497.82812|3026.00000|560.35455|27.00000|598.60815|2028.00000|601.78076|3029.00000|616.03479|2030.00000|620.63433|3031.00000|642.81231|2032.00000|648.53515|3033.00000|671.82128|2034.00000|677.71112|3035.00000|,
analog_chart|0.00000|0.00000|21.02783|2001.00000|60.39551|3002.00000|75.67871|2003.00000|80.04095|3004.00000|101.72927|2005.00000|106.99774|3006.00000|130.05311|2007.00000|136.19711|3008.00000|202.59838|9.00000|236.57470|2010.00000|239.04765|3011.00000|252.30334|2012.00000|256.23550|3013.00000|276.94076|2014.00000|282.27069|3015.00000|304.71163|2016.00000|310.27197|3017.00000|373.46301|2018.00000|394.01467|1019.00000|417.10076|3020.00000|436.22396|2021.00000|442.36795|3022.00000|463.53402|2023.00000|469.07901|3024.00000|492.42620|2025.00000|498.32443|3026.00000|560.85498|27.00000|599.23962|2028.00000|602.17340|3029.00000|616.28924|2030.00000|620.80505|3031.00000|643.21533|2032.00000|648.71417|3033.00000|672.09210|2034.00000|678.05175|3035.00000|,
analog_chart|0.00000|0.00000|21.02783|2001.00000|60.39551|3002.00000|75.67871|2003.00000|80.04095|3004.00000|101.72927|2005.00000|106.99774|3006.00000|130.05311|2007.00000|136.19711|3008.00000|202.59838|9.00000|236.57470|2010.00000|239.04765|3011.00000|252.30334|2012.00000|256.23550|3013.00000|276.94076|2014.00000|282.27069|3015.00000|304.71163|2016.00000|310.27197|3017.00000|373.46301|2018.00000|394.01467|1019.00000|417.10076|3020.00000|436.22396|2021.00000|442.36795|3022.00000|463.53402|2023.00000|469.07901|3024.00000|492.42620|2025.00000|498.32443|3026.00000|560.85498|27.00000|599.23962|2028.00000|602.17340|3029.00000|616.28924|2030.00000|620.80505|3031.00000|643.21533|2032.00000|648.71417|3033.00000|672.09210|2034.00000|678.05175|3035.00000|

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

Vanquizor · Post by **Vanquizor** » Sat Apr 05, 2014 3:49 am

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.

rusefi.com

[rusEfi] 1995 Dodge Neon

Re: 1995 Dodge Neon

Re: 1995 Dodge Neon

Re: 1995 Dodge Neon

Re: 1995 Dodge Neon

Re: 1995 Dodge Neon

Re: 1995 Dodge Neon

Re: 1995 Dodge Neon

Re: 1995 Dodge Neon

Re: 1995 Dodge Neon

Re: 1995 Dodge Neon

Re: 1995 Dodge Neon

Re: 1995 Dodge Neon

Re: 1995 Dodge Neon

Re: 1995 Dodge Neon

Re: 1995 Dodge Neon

Re: 1995 Dodge Neon

Re: 1995 Dodge Neon

Re: 1995 Dodge Neon

Re: 1995 Dodge Neon

Re: 1995 Dodge Neon

Re: 1995 Dodge Neon

Re: 1995 Dodge Neon

Re: 1995 Dodge Neon

Re: 1995 Dodge Neon

Re: 1995 Dodge Neon

Re: 1995 Dodge Neon

Re: 1995 Dodge Neon

Re: 1995 Dodge Neon

Re: 1995 Dodge Neon

Re: 1995 Dodge Neon