Won't detect trigger about speeduino

[apollard]

Started trying to figure out where in the code it is causing the FP to cycle on/off (ie, relay clicking) and more definition of exact conditions causing it. Put in serial prints to find area that is cycling pump. Learning a lot about the great programming done in the project.

[apollard]

OK, so did some more testing, and I've narrowed this issue down to just the "basic Distributor" trigger.

Speedy works fine with other triggers (tried 36-1, 60-2, and GM 24X). You can delay the trigger signal as long as you like and it syncs fine with other wheels. You can also remove the trigger signal, then reapply it and Speedy will sync again.

With the basic distributor setting, the trigger must be there when Speedy boots up or it won't sync and it goes into a situation where it pulses the Fuel Pump approximately every second. If the trigger is removed, it won't re-sync when it is reapplied and FP starts the pulsing.

Now to figure out what is different about the Basic Distributor code that causes this.

[noisymime]

Thanks for the report and the investigation you've done into this!

I'm not immediately seeing this on a test setup, but will keep looking into it.

[noisymime]

Can you please post a tune file (msq) for your setup?

[DarrenInwood]

That certainly sounds like a restart of the CPU to me. Is your fuel pump pulling too much current, which drops the supply voltage too low, which then restarts the whole shebang ad infinitum?

…

On 4/05/2017 13:59, "Josh Stewart" ***@***.***> wrote: Can you please post a tune file (msq) for your setup? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#81 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACI951L3Y2u0F_yJWJHXSRoukxtLwA3Aks5r2TEAgaJpZM4NMrYg> .

[noisymime]

@apollard Does TS reconnect / disconnect when the problem occurs? If it is then the resetting mentioned by @DarrenInwood may be a consideration. If TS stays connected, then that can be rules out.

I pushed up a few small fixes just now. Would be worth trying them to see if they make any difference, but I'm still unable to reproduce the issue the way you're seeing it, so I wouldn't be confident they have fixed it.

[apollard]

"fix Cranking Timing With Trigger" made no Difference.

However, with the Ardustim attached, I decided to change the filter I had (Weak) to none. That DOES show teeth in the logger. Below is the pattern I'm seeing (second image).

Since the Ardustim pattern is a 50% duty cycle square wave, the timing on each tooth should be very close, as shown by the image with sync (Tooth logger with sync - 8 cyl dizzy). The only change between these two images is that I power cycled the Speedy. Ardustim running with no change, so trigger was there on Speedy boot.

So something in code is throwing the timing of the trigger interrupt off ?

[apollard]

TS is not dropping connection, and the arduino stays operating (ie, not rebooting). Right now, I only have the FP relay hooked up in the boat, but not the FP. It isn't loosing power, since the ECU and FP relay are fed from different home runs to the main power point for the boat.

I am now simulating this on the bench with just an Mega 2560, a LED/resistor to show FP state and an Ardustim for trigger. So, no load at all really.

Current tune below - this is the one generating tooth logs above.

I'll download the commit and try it.

CurrentTune.zip

[apollard]

WOOHOO!

No idea what you changed Josh, but the issue is gone with the latest commit. I can't replicate it on the bench. I'll try in the boat, but I could replicate it reliably on the bench, so I'm sure it's solved. :)

Just for info, here's how I replicated the issue - I used the Mar release and the Apr 17 download, either did the same:

1. Start the Speedy with no trigger, using firmware above and .msq above.
2. Anytime after the Speedy boots, start the trigger signal.
3. No RPM shown in TS, sync flashes on and off, and FP cycles on and off.

Other condition:

1. Start the Speedy with trigger present (either Ardustim or by cranking the engine immediately) , using firmware above and .msq above.
2. RPM is shown in TS and FP stays on.
3. Remove trigger (I did this by simply disconnecting jumper from Ardustim). TS shows no RPM, FP is turns off and stays off.
4. Re-insert jumper from Ardustim. No RPM shown in TS, sync flashes on and off, and FP cycles on and off.

I may futz around to find what was happening, my curiosity is up. Or maybe I should just finish the install and run it...

[noisymime]

Hmmmm interesting. Almost certainly something to do with the filtering then based on your last 2 comments (and what I changed today). Anyway, glad to hear it's progress.

Happy to close this one or do you want to do more testing?

[apollard]

I think you can close it. I was able to replicate on the bench so reliably that I'm 100% sure it will work on the boat.

[noisymime]

Fixed by bae708a