When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
I've attached the FW files to this post. Assuming that I did that correctly, the files can be compiled in the Arduino IDE.
The "Time" Library needs to be included/installed for the project to compile. In Arduino IDE's library manager you can find this by typing in "Timelib". The library is written by Michael Margolis.
The only changes in here as far as I'm aware are the Cam profile and the overflow fix. Other than that it should be the same as the October 2023 release.
Thx SimBa for the good info, I merged the modifications for the +1 cam in the new firmware but I can't test it my car is in the middle of a turbo iunstall.
Here is the *.HEX file I compiled
You can flash your Arduino Mega directly with this program https://github.com/binaryupdates/xLoader
you will have to change the *.ini file in your Tuner Studio project with the one included.
I will test it as soon as I can, if someone tests it and it is good plz let me know.
EDIT: I removed the attached file it was not working
I messaged Mike, the creator of the Cam pattern, but he doesn't seem very active on Discord. A week or so ago he asked about how it was working for me, and how much testing I did. He still hasn't responded to my last message. I'm guessing he'll try to get it pulled in once he sees my message, especially if there's more people testing it.
I will probably try to patch the Cam FW over the latest master at some point, but I'm fine with what I've got at this point. Plenty of other things to focus on for me.
I will probably try to patch the Cam FW over the latest master at some point, but I'm fine with what I've got at this point.
This is what I did. See post #23, I implemented the new cam trigger pattern to the new master. The code is compiled ready to test, I have tested it on a spare mega and a simulator and seems to work.
I'm still going to hold off for a bit as I've been chasing the 36-2 FW issue and that misfire issue for a while, and my car is finally stable. Once I have my tune fully dialed and I need something to tinker with then I'll try it out.
Again, like I told Mike, I see no reason to stop using this trigger setup.
I finished installing the turbo on my car and wiring sequential ignition. Got it running on wasted spark and pared injection. After that I tried sequential injection and ignition with the +1 cam trigger code from Mike but it only sync correctly half of the time. SimBa got it working because if you run wasted spark but sequential injection, the car will run anyway the fuel is just injected when the valves are closed on the wrong phase. As soon as the valves open the fuel is there waiting.
So I modified the decoder code to sync correctly every time on the right phase of the engine. I use the poll level method I look at the cam signal at a specific crank teeth. The miata cam trigger as one tooth larger than the other so it works very well.
You need to run the car (or crank) and take a composite log. As you can see the level of the cam trigger is different from tooth 8 to 14. So the polling can be done on tooth 8 to 14
Here are my settings, you should set the level of the first phase high if your cas has not been rotated 180°. if the car is not starting change it to low.
I attached the Xloader software to upload the compiled speeduino code (speeduino.ino.hex) to the ecu.
It is simple juste open Xloader.exe, go find speeduino.ino.hex, choose the right board, choose the COM port the ecu is on, clic upload. It will take about 45s
Please get back to this thread with the result if this is working for you, I made a pull request to Speeduino and I need feedback.
Thx, it was my goal to use the stock cas as a secondary trigger for the miata. I didn't want to cut a tooth from my stock trigger.
The code has been implemented on the current dev firmware.
02-21-2024, 05:34 PM
0
