Been fighting with this trigger for two days now and not getting any luck with it.
5V hall-sensor conditioned through a MAX9926 w. 5V pullup on VR+ and floating VR- (trialed and tested Hall-input config. on the MAX9926).
CAS in question: https://www.onesixindustries.com/product/nissan-datsun-l-series-crank-angle-sensor
TS settings:
- custom toothed wheel
- Total tooth count = 24
- Missing/skipped = 1
- "On camshaft"
*I can't seem to be able to attach any log files*
Massive sync problems during initial test cranking:
Pulling the spark plugs to get a more consistent cranking speed. Disables fuel/ign:
Perfect sync all the way.
Re-activates spark, attaches one free-hanging spark plug on cyl#1 to strobe and calibrate the ignition timing (Trigger angle advance deg btdc = 645). Perfect sync. Timing calibrates fine with strobe light.
Re-activates fuel (in case of noise) while still having plugs out. Perfect sync. OK, so no apparent noise issues with either Spark or Fuel:
Install spark plugs, re-introducing compression. Massive sync error again.
In desperation, we decided to remove one additional tooth, thus converting to a 24-2 wheel. We then defined "24-2" in trigger settings.
Initially we got no RPM sync what so ever, but manage to get some readings after multiple tries. It feels like the settings dislike having a "2" on the "Missing/skipped" setting:
Everything else is ready, so he's working on getting a 36-1 trigger fitted so that he can get the car up and running.
Would've been nice to have support for the 24-1 CAS though.
... Also, another noe; the engine is set up w. 6x LS coils and direct spark - why doesn't the log show any action on coilState5 and 6?
Trigger pattern issue: 24-1 CAS (OneSix Hall for Datsun 240Z)
Re: Trigger pattern issue: 24-1 CAS (OneSix Hall for Datsun 240Z)
Uploaded .msq and log files in a shared googledrive folder:
https://drive.google.com/drive/folders/1TLuXH59NJgeAMpMZMdUF7m_s4QqA6jLH?usp=sharing
https://drive.google.com/drive/folders/1TLuXH59NJgeAMpMZMdUF7m_s4QqA6jLH?usp=sharing
Re: Trigger pattern issue: 24-1 CAS (OneSix Hall for Datsun 240Z)
Is this thread posted in the wrong sub forum?
No takes on the 24-1 CAS trigger unit?
No takes on the 24-1 CAS trigger unit?
- AndreyB
- Site Admin
- Posts: 14364
- Joined: Wed Aug 28, 2013 1:28 am
- Location: Jersey City
- Github Username: rusefillc
- Slack: Andrey B
Re: Trigger pattern issue: 24-1 CAS (OneSix Hall for Datsun 240Z)
Here is my 60/2 skipped wheel, skipped tooth is pretty obvious
Do I expect yours to be more or less same just 24/1 or 24/2? Because I see something very very different.
Do I expect yours to be more or less same just 24/1 or 24/2? Because I see something very very different.
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
Re: Trigger pattern issue: 24-1 CAS (OneSix Hall for Datsun 240Z)
24-1:
Sensor on cam (distributor), not crank.
Change to 24-2, and I don't even get any rpm reading while cranking, even though I read the puls incremetation in the log. See last log file.
Do we have issues with software on custom wheel setting?
Syncs perfectly while cranking without spark plugs in the holes for max and smooth rpm. Doesn't sync well when compression and variable rpm is present. Battery is decent, and the rotation speed of the engine is quite good while cranking.Sensor on cam (distributor), not crank.
Change to 24-2, and I don't even get any rpm reading while cranking, even though I read the puls incremetation in the log. See last log file.
Do we have issues with software on custom wheel setting?
- AndreyB
- Site Admin
- Posts: 14364
- Joined: Wed Aug 28, 2013 1:28 am
- Location: Jersey City
- Github Username: rusefillc
- Slack: Andrey B
Re: Trigger pattern issue: 24-1 CAS (OneSix Hall for Datsun 240Z)
No, we do not have issues with custom skipped decoder.
Signal is very messed up by the time it reaches firmware, please look at two photos I've posted. Until your log looks more like mine software is irrelevant.
Signal is very messed up by the time it reaches firmware, please look at two photos I've posted. Until your log looks more like mine software is irrelevant.
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
Re: Trigger pattern issue: 24-1 CAS (OneSix Hall for Datsun 240Z)
I suppose it's time to get the oscilloscope hooked up.
Re: Trigger pattern issue: 24-1 CAS (OneSix Hall for Datsun 240Z)
The sync latest ratio plot on your 60-2 looks very high-resolution compared to a fully functioning 36-1 plot I have from a selection of different engines.
Was this recorded during cranking?
Have you enabled/disabled any logging related features in TS to make what looks like a very high sample rate?
Was this recorded during cranking?
Have you enabled/disabled any logging related features in TS to make what looks like a very high sample rate?
- AndreyB
- Site Admin
- Posts: 14364
- Joined: Wed Aug 28, 2013 1:28 am
- Location: Jersey City
- Github Username: rusefillc
- Slack: Andrey B
Re: Trigger pattern issue: 24-1 CAS (OneSix Hall for Datsun 240Z)
Cranking
Max data rate using licensed edition of TS
Max data rate using licensed edition of TS
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
Re: Trigger pattern issue: 24-1 CAS (OneSix Hall for Datsun 240Z)
So do I.
What's the time step interval in your log? Mine is more or less exactly 10ms.
What's the time step interval in your log? Mine is more or less exactly 10ms.