- Mon May 29, 2023 3:41 pm
#63270
Also, do continue to try to get the registered version of TS so you can get a tooth log.
PSIG wrote: ↑Mon May 29, 2023 2:48 pm The 'scope trace looks good, but only first rev. We can't see the 2nd rev where the spikes occur, so please take a new shot with only the one output so results are clear. I'm not trying to make work for you, but your issue is "no RPM reading" and we are focusing on that.• We can't see the 2nd rev where the spikes occur, so please take a new shot with only the one output so results are clear.With that huge spike after the gap, the DSC is a good choice of conditioner, as the MAX conditioners would miss teeth. Verify all teeth are being seen on the output.
- Jumpers: JP1 = 5V; JP2 = VR/TSC; JP3 = VR/TSC; JP4 = OFF; JP5 = OFF
- VR polarity checked, (+) wires to (+) inputs, (-) wires to (-) inputs
- Falling edge for both sensors (DSC is non-inverting output).
- Spark settings depend on coils and wiring. CoPs on 4 outputs + crank-only = Wasted CoP
- Injector settings also depend on wiring
- Test - New Ignition Mode = NO
- Cranking RPM = 400
Verify there are no flashes on the cam signal LED output at any time. If there are, tie the VR2- input to any ground point with a 0 to 1k resistor, so it does not float and give false signals, losing sync.
The high cam VR signal voltage is OK for now, but may need a shunt resistor later when connected and tested at higher-rpm.
AL_AOA wrote: ↑Mon May 29, 2023 5:01 pm of the VR conditioner output right? And can you elaborate on 2nd rev?Of the crank VR signal. The spikes occur on the 2nd crank rev and after. Try to get a screen grab of that for a full 60-2 revolution.
AL_AOA wrote: ↑Mon May 29, 2023 5:01 pm • Test - New Ignition Mode = NO I am not sure what this point means, please helpIn TS: Spark (tab) > Spark Settings > New Ignition Mode > Use New Ignition Mode > No
PSIG wrote: ↑Mon May 29, 2023 5:13 pmthis is frustrating,AL_AOA wrote: ↑Mon May 29, 2023 5:01 pm of the VR conditioner output right? And can you elaborate on 2nd rev?Of the crank VR signal. The spikes occur on the 2nd crank rev and after. Try to get a screen grab of that for a full 60-2 revolution.
AL_AOA wrote: ↑Mon May 29, 2023 5:01 pm • Test - New Ignition Mode = NO I am not sure what this point means, please helpIn TS: Spark (tab) > Spark Settings > New Ignition Mode > Use New Ignition Mode > No
Test for changes. Use New Ignition Mode = Yes if it doesn't change anything.
JHolland wrote: ↑Wed May 31, 2023 9:20 am I don't think that you have said which VR conditioner you are using. the trace shows around 300ms between pulses, a MAX chip will time out with that interval so you will be at the minimum voltage threshold to re-arm, if that is an accurate trace then you will be getting a lot of false triggers from the noise on the signal. . You need to scope the signal from the VR conditioner to the Arduino to see what you are actually sending to the micro.Hi,
PSIG wrote: ↑Wed May 31, 2023 4:07 pm It's difficult to see each signal, but the trace is incomplete. The 'scope trace should show 58 clear pulses, and two missing. Find the combination of polarity and Trigger Edge that provides that result. The DSC should handle this fine.I really appreciate you taking the time to work this issue with me. Now I am suspecting the crank sensor. While cranking and looking at the scope, it seems like every rev I see one spike. I will swap it with a new one just to narrow down the focus area.
Verify you see signal on the Mega pin, and that the signal is making it to the processor (bent pins, bad solder, etc). If so, it should be a settings or code issue. If necessary, do not hesitate to clear the Mega with the EEPROM_Clear.ino sketch, reload your firmware, start a new TS project, load your tune, and try again with a fresh setup.
I'm not fishing for answers or trying to make work for you, but I am not clear where the failure is yet, and why it is important to prove the processor is getting the signal, and if so, is processing it properly. 60-2 is well proven, and should be working with no issues - if everything else is good.![]()
PSIG wrote: ↑Wed May 31, 2023 4:07 pm It's difficult to see each signal, but the trace is incomplete. The 'scope trace should show 58 clear pulses, and two missing. Find the combination of polarity and Trigger Edge that provides that result. The DSC should handle this fine.Alright,
Verify you see signal on the Mega pin, and that the signal is making it to the processor (bent pins, bad solder, etc). If so, it should be a settings or code issue. If necessary, do not hesitate to clear the Mega with the EEPROM_Clear.ino sketch, reload your firmware, start a new TS project, load your tune, and try again with a fresh setup.
I'm not fishing for answers or trying to make work for you, but I am not clear where the failure is yet, and why it is important to prove the processor is getting the signal, and if so, is processing it properly. 60-2 is well proven, and should be working with no issues - if everything else is good.![]()
Thanks for the reply ,also how hard to you think i[…]
Newbe again. O2 sensor and AFR table. Enabling t[…]
Hello, Please walk me through digital dash optio[…]
Still can't find what you're looking for?