Goal is to make a two step rev limiter with anti-lag in order to spool the turbo on my truck quickly for launch.
To make the experience fit your profile, pick a username and tell us what interests you.
We found and based on your interests.
W39728ASR12_WiFi-TwoStepV5-GERBER.zipPCB GerbersZip Archive - 113.16 kB - 08/05/2021 at 00:07 |
|
|
Wifi Two-Step.zipSoftwareZip Archive - 788.62 kB - 08/04/2021 at 23:56 |
|
a quick update where i talk about why the previous plan would not work and also show the new plan.
At the time of this video i had a different plan utilizing an attiny85 which would have resulted in erratic spark behavior which could be bad for the engine.
Create an account to leave a comment. Already have an account? Log In.
I have been asked this a few times, It wouldn't be hard to use OBD2 to grab the RPM, but it is fairly easy to count the time between the previous and current ignition event and use that to calculate RPM. In fact i am pretty sure this would be much faster and more accurate than grabbing it from OBD2. The code is dead simple for the atmega328p.
Fair point, I guess that makes sense. Looking forward to more updates!
Become a member to follow this project and never miss any updates
By using our website and services, you expressly agree to the placement of our performance, functionality, and advertising cookies. Learn More
Have you considered getting RPM data from the OBD2 port? I recently built a small device to get a bunch of ECU stats from the OBD2 port with a standalone atmega328p soldered on protoboard and it's been working great for a few months so far -- and its pretty cheap, only around ~15 bucks in parts. Just get a generic ELM327 OBD2 scanner on amazon that has a UART based bluetooth module inside, desolder the bluetooth and connect tx/rx to the 328p...pretty elegant solution and you don't have to deal with reading ignition events to estimate RPM, which might slow down the loop time especially if you're reading that through interrupts