RB25DET - Sync Issue After Upgrading to EMU Black V3 from V2

V3 BETA TESTS
1

Hey everyone,

I recently upgraded from ECU Master EMU Black V2 to V3 on my RB25DET Series 2 and I’m running into trigger synchronization issues. Before the upgrade, the car started and ran fine on V2, but after switching to V3, I’m only getting “Synchronizing” but not “Synchronized” in the trigger status. The car cranks but does not start.

Here’s my setup and what we’ve tested so far:

Setup Details:

• RB25DET Series 2 (Stock CAS Disk)

• Nissan Trigger

• Stock CAS (360-slot inner, 6-slot outer)

• Trigger Edge: Currently set to Falling (we suspect Rising might be needed)

• First Trigger Tooth: 8

• Trigger Angle: 50°

• Cam Sync Window Min: 4

• Cam Sync Window Max: 12

• 12V Power to CAS confirmed

• Steady cranking RPM at ~105 RPM

• Trigger log attached (Scope Data Available)

Symptoms & Issues:

  1. Cranking RPM is low (105 RPM)

• In V2, I had no issues with syncing.

• In V3, the engine cranks but won’t sync.

  1. Trigger Log Shows Signals, but No Sync

• Logged trigger scope shows a clean cam and crank signal, but the ECU won’t sync.

  1. Drive-by-Wire Issue Also Noted

• After switching to V3, the throttle doesn’t hum at key-on like it did in V2.

• Short to ground error appears when key is on, but disappears when applying throttle.

Steps We’ve Tried So Far:

:check_mark: Checked Wiring to CAS – All Good (12V, Ground, Signal)

:check_mark: Confirmed Trigger Settings – Matches V2 Config

:check_mark: Tried Cranking While Logging Trigger Scope

:check_mark: Tested Adjusting Cam Sync Window Min & Max

:check_mark: Confirmed No Physical CAS Damage

:check_mark: Tried Copying Over V2 Configuration to V3 Manually

Questions:

  1. Does EMU Black V3 handle Nissan CAS signals differently from V2?

  2. Should I switch from Falling Edge to Rising Edge on the Primary Trigger?

  3. Would a PRP or AEM 24-1 CAS disc help eliminate potential issues with the stock Nissan optical disc?

  4. Are there any trigger signal filtering or input delay settings in V3 that could help?

  5. Could the low cranking RPM (105 RPM) be causing the sync issue?

2

Could you please publish your configuration and make scope with the parameter Take skipped edges on scope marked ?

AEM 24-1 disc is better solution, however it should work with OEM CAS.
Is 105 RPM your real engine rotational speed during cranking or V3 firmware shows that speed ?

According throttle just fix your TPS / PSS calibration. Make sure the TPS / PPS ranges are within fail save min / max voltages.

I removed your duplicated post from other Topic.

3

Hey Jadzwin, thanks for getting back so quick
First off, I want to apologize for the duplicate post earlier. That wasn’t my intention—I appreciate your time and help.
Here’s an update on the troubleshooting steps I’ve taken so far:
1. Converted Back to V2 for Testing
• I reverted to V2 firmware, and cranking RPMs were reading around 150 RPM, which seems more realistic.
• This confirms that the trigger setup and hardware are working correctly under V2.
2. Switched Back to V3
• After updating back to V3 firmware, I made sure to enable “Take Skipped Edges on Scope” and captured a new scope log.
• However, V3 is only showing 105 RPM during cranking, which seems lower than expected.
3. What I’ve Checked So Far:
• Trigger Settings: Confirmed all trigger settings match my working V2 setup.
• Scope Capture: Verified scope data with skipped edges enabled.
• TPS/PPS Calibration: Recalibrated and confirmed min/max voltage values are within the correct range.
4. Issues Noticed:
• In V3, the RPMs seem lower (105 vs. 150 RPM in V2) during cranking.
• The ECU doesn’t fully synchronize (stays at “Synchronizing” but not “Synchronized”).
• Drive-by-wire behavior seems slightly different, but the short-to-ground error disappears once I press the pedal slightly.

Next Steps / Questions:
• Could the RPM discrepancy between V2 and V3 indicate a difference in trigger decoding?
• Should I adjust the trigger angle or first trigger tooth to account for this?
• Is there a recommended trigger log format or setting I should use to verify if the ECU is detecting all the necessary pulses?

I’ll upload my configuration file and the new scope log with skipped edges enabled for further review. Let me know if there’s anything specific you need me to test. Thanks again, and sorry for the duplicate post earlier!
march14.emub3 (62.5 KB)
march14.emubscp3 (592 Bytes)

4

Your problem is with the sensor setting for primary trigger and CAM1

Set it as a hall and use 820R pullup. Input filter None.

image
image377×324 12.6 KB

5

How is your pedal and throttle position connected ?