NSFW wrote: Sun Feb 02, 2025 9:06 am
"So it'd be nice to strip the binary down with all the emissions crap and stuff that a more racey application didn't need to ease the load on the processor."
Did you try disabling all of the trouble codes? I'd expect that to free up some CPU power, but I have no idea how much.
Thanks for the tip about the ECU simulator.
I can give it a whirl and see. This was the traditional '603 OS with DBW and auto trans disabled. The trouble codes I didn't think about outside of the normal stuff we disable.
I remember back in the heyday of these PCM's someone on the EFILive page touting the ability to go above 8200rpm with the stock PCM. I don't know what they did to make that happen, but it almost has to be something to relieve the processor.
What does it take to make a P01/P59 think it's happily running an engine on the bench??
This post will get edited for the next searching soul as things move along on this endeavor.
AngelMarc wrote: Sun Apr 20, 2025 5:31 pm
If anybody cares to debug this arduino code. The bug might be specific to the piPico. It's all generic code that should work with many other mCUs. Clock frequency variation if worth being aware of, and I planned to use the arduino serial interface from a PC to change RPM to avoid analog noise wildly swinging RPM and causing errors. If I remember right, the PiPico's clock should allow for up to 14,000 RPM signal, and down past idle speeds, like 40 RPM or something. I had some help making it, since I always struggle to remember exact syntax. You'll likely need something to step the voltage up from 3.3 to 12. I planned to use a TC4452v. Would be easy to adapt to a 4x crank and likely others.
ShorTuning wrote: Sat Feb 22, 2025 5:27 am
ability to go above 8200rpm with the stock PCM. I don't know what they did to make that happen, but it almost has to be something to relieve the processor.
NSFW wrote: Sun Feb 02, 2025 9:06 am
"So it'd be nice to strip the binary down with all the emissions crap and stuff that a more racey application didn't need to ease the load on the processor."
Did you try disabling all of the trouble codes? I'd expect that to free up some CPU power, but I have no idea how much.
Thanks for the tip about the ECU simulator.
I can give it a whirl and see. This was the traditional '603 OS with DBW and auto trans disabled. The trouble codes I didn't think about outside of the normal stuff we disable.
I remember back in the heyday of these PCM's someone on the EFILive page touting the ability to go above 8200rpm with the stock PCM. I don't know what they did to make that happen, but it almost has to be something to relieve the processor.
Pretty sure that was SQP here in Perth. I would hazard a guess the rev limiter was somehow removed entirely since 16 bit byte limiter is still 8192.
Tre-Cool wrote: Tue Apr 22, 2025 3:40 am
Pretty sure that was SQP here in Perth. I would hazard a guess the rev limiter was somehow removed entirely since 16 bit byte limiter is still 8192.
12799 RPM is number I see, FFFF in hex. Depending on clock scaling and other math, the exact hex number can be made to not matter.
You do not have the required permissions to view the files attached to this post.
AngelMarc wrote: Tue Apr 22, 2025 12:14 pm
12799 RPM is number I see, FFFF in hex. Depending on clock scaling and other math, the exact hex number can be made to not matter.
What app are you using in that screenshot? It's not one that I'm familiar with, so I'm curious...
Please don't PM me with technical questions - start a thread instead, and send me a link to it. That way I can answer in public, and help other people who have the same question. Thanks!
