You mean just the .cpp/.h files? Wouldn't be compiled at that point but I could do that no problem.

 

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

 

was this not added to Feb release?

https://github.com/noisymime/speedui...q8cgPn54pVMmF4

i didn't see anything on the release notes :/

still will try it for the **** of it.

 

no not added, I will ask around in the discord

 

whats their discord?

 

https://speeduino.com/home/ under the community tab

 

I’m in. Thanks.

 

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.

 

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.

 

Awesome! I misread that post earlier.

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.

 

Good work figuring that one out Adam. Is this based on the latest master firmware as of April 2024?

 

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.

 

I've done a lot of reading on this and have confused myself. If I have a 36-2 crank trigger wheel and a stock intake cam gear with 3 teeth and the pickup bolted on the front of the valve cover, is this the correct firmware to use?

 

I believe Adam's firmware would be appropriate, as would the older firmware I linked (if you're running batch ignition).

 

I can't figure out what I'm doing wrong here. I installed the 36-2 wheel and the front mounted cam sensor with proper timing belt gear. Runs great in semi-sequential but if I switch to full sequential injection it struggles to start/idle and sounds like a constant misfire but it completely goes away and runs great past 2000 rpm. Injector pulse width goes up bigly when it's doing the misfire dance below 2000 so I tried pulling fuel but it's obviously still misfiring horribly. High speed logger shows proper signal from the crank and cam sensors. It says I have no sync loss. But it also runs the same with the cam sensor unplugged and sequential selected and still says I have no sync loss. How can that be with the cam sensor unplugged?

It did this before and after switching to the modified firmware above. It's a 1994 so I should have the proper factory harness for sequential injection and I'm pretty sure I was running sequential on the stock cam sensor that mounts to the back of the intake cam.

If I wanted to grind off the cam gear teeth to turn it into a supported 1 tooth cam sensor to eliminate that variable which teeth would I grind off?

 

Have you tried changing the trigger edges around?

I'm not sure which teeth you would cut off. I'm pretty sure people on the Speeduino Discord would be able to point you in the right direction on that though.

 

Trigger edge didn't change anything. I did more reading and decided to grind off the two teeth that are close together and switch back to the official firmware with single tooth cam selected, works perfectly now and correctly displays half sync/full sync.

 

Sorry that didn't work for you man. I'm still surprised that hasn't been integrated into the main firmware yet. Seems like a common enough trigger pattern and the codes already there. I think if it was merged into the main branch properly it wouldn't seem as finnicky to get setup.