[RowdyDouglas]

Oh man! I am getting consistent RPM! I got a fresh copy of speeduino 202210-dev and just did small modifications to Jeep2000 locally then worked up to add all 16 tooth angles, decoderIsSequential=true, added some lines to deal with revolution. I am wondering if more logic needs to be added to triggerSec to handle all 16 teeth, something like:

Code: Select all

void triggerSec_Jeep1994CNP4cyl()
{
  if(toothCurrentCount < 17) {toothCurrentCount = 0; revolutionOne = 1; } //happens when cam sensor goes high first time after two crank cycles and resets tooth count back to zero, indicating that we're at the beginning of a new revolution
  return;
}

[jonbill]

yay! is the current code checked into your github fork?
did you change the setting of secondaryTriggerEdge = CHANGE in init.ino? (to same handling as primary).
I haven't thought it through thoroughly, but I think that if it's on CHANGE, you'll be able to differentiate your two revolutions of the 720, but they might not be the same cylinders across multiple starts. Hope that makes sense!

[RowdyDouglas]

My latest changes are committed in my fork on GitHub but I am about to try secondaryTriggerEdge=RISING in combination with all 16 teeth tooth angles defined. This is for 720 degree tracking as I want to run sequential ignition and injection. I am also going to look at the decoder with my new perspective and see what else needs to be changed (probably triggerSetEndTeeth?).
Note: Using secondaryTriggerEdge=CHANGE is sufficient for paired injectors and dizzy, i.e. stock 2000 Jeep 6 cylinder, and it only requires entering 12 toothangles.

Sidenote: I have learned a bunch through this process over the past several months; I may have been missing time-master library in Arduino IDE at one point, I messed up the init.ino at one time, I wasn't loading the proper custom firmware speeduino.ini from my sketch in TS. The list goes on but I feel like I am getting much closer!

[RowdyDouglas]

That worked except I needed to change the RPM detect to 720 rather than 360.
Now, reworded from Slack, I am going to mess with

Code: Select all

if (toothCurrentCount == 0) { crankAngle = 174 + configPage4.triggerAngle; } 

because JAKY47's ignition improvement using a lower number. I am going to try 234 on my next attempt, which is 60 degrees before tooth 1, rather than the 236 on the diagram.

[Mr_Hypnotic]

Oh man! I am getting consistent RPM!

That's exciting!

[reliant_turbo]

Decoder hasn't been put into GitHub that I am aware of. I could do that even though @reliant_turbo did the work (I'll put his handle in the comments or something). The battery is new (I'll double check voltage with my multimeter though). I do have an alternator regulator I was thinking about disconnecting for testing. Thanks for the replies, it's always nice to have people to bounce ideas around with.

thats fine with me. as long as the development continues. ive been busy with other stuff.

Brian

[RowdyDouglas]

First PR submitted https://github.com/noisymime/speeduino/pull/931
Early testing showing success but needs to be tested more. I wanted to get the decoder out there for the community to provide feedback.

[reliant_turbo]

any progress on this front?

I still have my cam and crank trigger lines extended into the cab on my wrangler and the speeduino sitting there in the back seat since my last test, last year when saw it sync and had RPM readout in tunerstudio.

I can test some stuff here and there if you need me to.

Thanks,

Brian

[RowdyDouglas]

A few days ago a friend printed the case you designed so I have been installing wiring with that. Next I plan to buy an extra fire extinguisher and then put fuel in the tank!
The GitHub PR has the latest updates to the decoder so I am interested for you to load that build and check your logs.

[reliant_turbo]

cool. glad to see someone is giving it a go with that case. that said, its not perfect. if i were to do it over i would just make ends for an aluminum case or make it all a big box but it works.....

i see the pull request. ill see what i can do to test them.

Thanks,

Brian