jayecu v0.3.28

Firmware 0.4.20 (build 26e7bc4)

• Trigger inputs use only the edges selected in Edge. A pulse-width cam (the 2JZ / 1JZ front or rear cam, and every
  "+ cam" wheel) used to capture both edges whatever Edge said, and timed itself from the pulse's closing edge.
  On a VR input that edge is where the signal crosses a threshold re-armed from the last pulse, so it moves with
  every change of speed and comes late after a weaker pulse. A quick stab through the cam's phase-sync rpm read
  that as a cam that hadn't arrived: phase lost (P0341), a moment on wasted spark, then a re-sync. Now:
  • With Edge on Rising or Falling, only that edge is captured, and each one is the cam's reference. On a VR
    input that's the zero crossing, which sits on the tooth. WIDTH min/max don't apply.
  • With Edge on Both, the width is measured and picks out the reference, which is timed from the rising edge.
    The VVT angle is measured at the same edge.
• VVT cam angles (VVT Cam 1-4 Advance) are published in degrees. They were in tenths of a degree, so a cam 4.3°
  from nominal read 43°, and cam control would have closed its loop on a value ten times too large.

Studio 0.3.28

• The trigger Edge setting and the WIDTH min/max help explain that only the selected edges are captured, and that a Width cam on Rising or Falling takes every selected edge as its reference.
• Manual: the trigger chapter describes the Edge rule and why a VR cam must be on Rising.

Firmware kits for jaytek_v1 and proteus_f7.