Another Option for NA ECU Performance?
#1
Another Option for NA ECU Performance?
Team-
Is this a viable option for getting some timing advance and better fuel mapping for a na car with only intake and exhaust? The price is right - but the 'monitor' - not 'tune' or 'modify' makes me wary... Does it even cover our car? (It says 'not vehicle specific')
<see below>
Venom Engine Mgmt Systems - PB
Performance Control Module - Venom 400
The VENOM 400 Performance Control Module is an add-on control unit that features its own micro-controller. This module is connected to the vehicle's sensors and increase engine performance by monitoring the sensors output.
Note: The VENOM 400 requires no modifications to existing engine components and can be completely disabled at the flip of a switch, restoring performance back to original equiment specifications.
Click www.venom-performance.com for more information about this product.
Purchase Rating (1-10) Make Model Part Number Details MSRP Sale Price
New Not Vehicle Specific VENO V49-209 (93-94) 2.3L 293.96
Is this a viable option for getting some timing advance and better fuel mapping for a na car with only intake and exhaust? The price is right - but the 'monitor' - not 'tune' or 'modify' makes me wary... Does it even cover our car? (It says 'not vehicle specific')
<see below>
Venom Engine Mgmt Systems - PB
Performance Control Module - Venom 400
The VENOM 400 Performance Control Module is an add-on control unit that features its own micro-controller. This module is connected to the vehicle's sensors and increase engine performance by monitoring the sensors output.
Note: The VENOM 400 requires no modifications to existing engine components and can be completely disabled at the flip of a switch, restoring performance back to original equiment specifications.
Click www.venom-performance.com for more information about this product.
Purchase Rating (1-10) Make Model Part Number Details MSRP Sale Price
New Not Vehicle Specific VENO V49-209 (93-94) 2.3L 293.96
#5
its a crock...it's a fuel adder and our ecu will override it anyway at WOT. This is the problem with almost all little piggyback controllers like the S-AFCII and so forth.
Spend the money to have good fuel control and buy the Haltech F10X from protegegarage.com I think he has them for right at $900 or so with the protege harness.
Spend the money to have good fuel control and buy the Haltech F10X from protegegarage.com I think he has them for right at $900 or so with the protege harness.
#9
RPM Input Question
If the RPM output is a simple analog voltage level output, and a throttle position sensor is in place, it'd be interesting to try and put together a small, cheap system that used just these two factors and manipulated the crank sensor to change the ignition timing of the motor. You could easily do this with a $2 microcontroller, the tough part would be writing the code and figuring out the output scheme for the crank sensor....Man...if I had a shop and someone capable to work on the car with, i would definitely be all about doing the electrial and programming aspects once we figured out the scheme. Could probably put it together for <$50 and it'd be a programmable ignition system...might be worth some money too...damn...
#12
Crank sensor? Why does it stop using the crank sensor above 5K RPM?
That doesn't make sense (to me - i am 'mechanical' not 'lectronic-ee). The computer should be using the base timing as a reference point to adjust from for RPM/fuel emisions tuning.
Vielster! Now you have me intrigued! You are getting close to what *i* see as the solution to bump our timing a wee bit! Follow that thought to a conclusion...
That doesn't make sense (to me - i am 'mechanical' not 'lectronic-ee). The computer should be using the base timing as a reference point to adjust from for RPM/fuel emisions tuning.
Vielster! Now you have me intrigued! You are getting close to what *i* see as the solution to bump our timing a wee bit! Follow that thought to a conclusion...
#13
Schematic
Here's a sort of Block Diagram of what the setup would basically look like.
The Code Would go something like this
{Initialization Code}
long currentRPM;
long currentThrottle;
While(true){
currentRPM = convertToRPM(ADC3);
currentThrottle = convertToLoad(ADC1); //converts fo level 1->100 based on plate position
if(currentRPM > 1000 && currentRPM < 1500) { //Idle Speeds
CrankOut = ADC2;
}
if(currentRPM >= 1500 && curent RPM < 2000){
switch(currentThrottle)
case 1,2,3,4,5,6,7,8,9,10: CrankOut = ADC2;
break;
case 10,11,12............. : CrankOut = ADC2 - 5;
break;
case 20,21,22............. : CrankOut = ADC2 - 8;
break;
//finish cases up to 100
}
if(currentRPM >= 2000 && currentRPM < 2500){
switch(currentThrottle)
case 1,2,3,4,5,6,7,8,9,10: CrankOut = ADC2;
break;
case 10,11,12............. : CrankOut = ADC2 - 2;
break;
case 20,21,22............. : CrankOut = ADC2 - 4;
break;
//finish cases up to 100
}
//Finish for all RPM up through 7000 changing ignition timing based on RPM
}
I'm not sure exactly how ignition timing is supposed to relate to RPM and Load, so what I did in the code might be wrong, but it's just an example. If a mechanical guy could tell me how much I need to advance or retard the timing, it could be manipulated. Additionally, this scheme could be easily made to work for every 100RPM instead of 500...just more code. Since the ATiny26 is programmable, it could be updated with new programs if a different ignition timing is found to be more beneficial. Of course this sytstem isn't nearly as useful since we don't have control over the fuel/air mixture. there are still 6 more ADC (analog to digital converters) and many more outputs that could be used, but it would be very complicated code. Could easily incorporate an on/off switch as well. Anyway, I've just been thinkin about it so thought I'd put it out there.
The Code Would go something like this
{Initialization Code}
long currentRPM;
long currentThrottle;
While(true){
currentRPM = convertToRPM(ADC3);
currentThrottle = convertToLoad(ADC1); //converts fo level 1->100 based on plate position
if(currentRPM > 1000 && currentRPM < 1500) { //Idle Speeds
CrankOut = ADC2;
}
if(currentRPM >= 1500 && curent RPM < 2000){
switch(currentThrottle)
case 1,2,3,4,5,6,7,8,9,10: CrankOut = ADC2;
break;
case 10,11,12............. : CrankOut = ADC2 - 5;
break;
case 20,21,22............. : CrankOut = ADC2 - 8;
break;
//finish cases up to 100
}
if(currentRPM >= 2000 && currentRPM < 2500){
switch(currentThrottle)
case 1,2,3,4,5,6,7,8,9,10: CrankOut = ADC2;
break;
case 10,11,12............. : CrankOut = ADC2 - 2;
break;
case 20,21,22............. : CrankOut = ADC2 - 4;
break;
//finish cases up to 100
}
//Finish for all RPM up through 7000 changing ignition timing based on RPM
}
I'm not sure exactly how ignition timing is supposed to relate to RPM and Load, so what I did in the code might be wrong, but it's just an example. If a mechanical guy could tell me how much I need to advance or retard the timing, it could be manipulated. Additionally, this scheme could be easily made to work for every 100RPM instead of 500...just more code. Since the ATiny26 is programmable, it could be updated with new programs if a different ignition timing is found to be more beneficial. Of course this sytstem isn't nearly as useful since we don't have control over the fuel/air mixture. there are still 6 more ADC (analog to digital converters) and many more outputs that could be used, but it would be very complicated code. Could easily incorporate an on/off switch as well. Anyway, I've just been thinkin about it so thought I'd put it out there.
Last edited by vielster; September-23rd-2004 at 09:51 AM.