Trigger pattern Problems to start with
GM 60/2/2/2 Trigger Pattern Selected
Tried both Cam and Crank on Primary still unable to Sync
2021-02-19_17_00_23_537: EngineState: engine has STOPPED
2021-02-19_17_00_23_537: EngineState: templog engine has STOPPED [2][1761DA1B] [2][15A30E20] 29281275
2021-02-19_17_00_23_537: EngineState: trigger ICU hw: 10040 10040 1
2021-02-19_17_00_23_537: EngineState: Template MINIMAL_PINS (99) trigger TT_GM_60_2_2_2 (54) useRiseEdge=Yes onlyFront=Yes useOnlyFirstChannel=No tdcOffset=0.00
2021-02-19_17_00_23_537: EngineState: trigger#1 event counters up=0/down=6346
2021-02-19_17_00_23_537: EngineState: expected cycle events 7/0/0
2021-02-19_17_00_23_537: EngineState: trigger type=54/need2ndChannel=No
2021-02-19_17_00_23_537: EngineState: expected duty #0=0.36/#1=0.00
2021-02-19_17_00_23_537: EngineState: synchronizationNeeded=Yes/isError=No/total errors=3 ord_err=0/total revolutions=7/self=No
2021-02-19_17_00_23_537: EngineState: gap from 4.50 to 7.50
2021-02-19_17_00_23_537: EngineState: primary trigger input: PC6
2021-02-19_17_00_23_537: EngineState: primary trigger simulator: NONE OM_DEFAULT freq=1200
2021-02-19_17_00_23_537: EngineState: trigger error extra LED: NONE OM_DEFAULT
2021-02-19_17_00_23_538: EngineState: primary logic input: NONE
2021-02-19_17_00_23_538: EngineState: secondary logic input: NONE
2021-02-19_17_00_23_538: EngineState: totalTriggerHandlerMaxTime=915
just an example of what the sniffer looks like
self simulation sniffer log
Ignore the spark.. forgot i had wasted spark on
i tested with the factory ECU, and 1st Cyl Fires on 10 Deg BTDC
also out of interest i changed the trigger to 2jz 1/12, just to confirm my inputs were working and it showed sync on the sniffer screen but i didnt get a shot of that
F8CV Engine In a Mightyboy
-
- Posts: 5
- Joined: Sun Feb 21, 2021 3:34 pm
- Github Username: hewball
- Slack: hewball
F8CV Engine In a Mightyboy
You do not have the required permissions to view the files attached to this post.
- AndreyB
- Site Admin
- Posts: 14727
- Joined: Wed Aug 28, 2013 1:28 am
- Location: Jersey City
- Github Username: rusefillc
- Slack: Andrey B
Re: F8CV Engine In a Mightyboy
I see only one channel showing up signals?
Also it looks like first channel is the one with 60/2/2 many teeth while first one should be the one with just single, and second channel with many?
Also it looks like first channel is the one with 60/2/2 many teeth while first one should be the one with just single, and second channel with many?
Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
-
- Posts: 5
- Joined: Sun Feb 21, 2021 3:34 pm
- Github Username: hewball
- Slack: hewball
Re: F8CV Engine In a Mightyboy
swapping to the single tooth as primary sensor, i forgot this in the top post
You do not have the required permissions to view the files attached to this post.
-
- Posts: 5
- Joined: Sun Feb 21, 2021 3:34 pm
- Github Username: hewball
- Slack: hewball
Re: F8CV Engine In a Mightyboy
also now uploaded the tune
https://rusefi.com/online/view.php?msq=430
https://rusefi.com/online/view.php?msq=430
-
- running engine in first post
- Posts: 1501
- Joined: Mon Jan 30, 2017 2:05 am
- Location: Seattle-ish
Re: F8CV Engine In a Mightyboy
It looks like both hardware channels are fine, but that trigger pattern isn't listening to both.
-
- Posts: 5
- Joined: Sun Feb 21, 2021 3:34 pm
- Github Username: hewball
- Slack: hewball
Re: F8CV Engine In a Mightyboy
yes Both Cam and Crank trigger led's flash with what i would expect the trigger pattern to be
but as i said this is the 2jz 1/12 trigger log in the console just to confirm 2nd trigger
but as i said this is the 2jz 1/12 trigger log in the console just to confirm 2nd trigger
You do not have the required permissions to view the files attached to this post.
- AndreyB
- Site Admin
- Posts: 14727
- Joined: Wed Aug 28, 2013 1:28 am
- Location: Jersey City
- Github Username: rusefillc
- Slack: Andrey B
Re: F8CV Engine In a Mightyboy
You definitely need to flip your input settings - the cam sensor thing has to be on top while crank sensor signals have to be on the bottom.
Are we starting to suspect a defect with trigger shape definition? I am unable to properly focus on this to properly diagnose this at the moment
Are we starting to suspect a defect with trigger shape definition? I am unable to properly focus on this to properly diagnose this at the moment

Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
-
- running engine in first post
- Posts: 1501
- Joined: Mon Jan 30, 2017 2:05 am
- Location: Seattle-ish
Re: F8CV Engine In a Mightyboy
We've been DMing and he's tried a bunch of different combinations of flipping the inputs around. We should still see signals on both channels even if they're mapped wrong. On the 2JZ config he sees the expected pattern, but on the 60/2/2/2 GM it's inexplicably missing one of the channels.AndreyB wrote: ↑Fri Feb 26, 2021 1:17 amYou definitely need to flip your input settings - the cam sensor thing has to be on top while crank sensor signals have to be on the bottom.
Are we starting to suspect a defect with trigger shape definition? I am unable to properly focus on this to properly diagnose this at the moment![]()
-
- Posts: 5
- Joined: Sun Feb 21, 2021 3:34 pm
- Github Username: hewball
- Slack: hewball
Re: F8CV Engine In a Mightyboy
Red Herring this one 
did a dfu firmware update on windows and now it works and sync's
thanks for the help, just damn annoying

did a dfu firmware update on windows and now it works and sync's
thanks for the help, just damn annoying
You do not have the required permissions to view the files attached to this post.