Hey guys! Running an emublack on my stock rb25det. I’ve got it starting and idling with v2 however when I convert to v3 I can no longer get it to start up. When I scope with the sync window width set at 12 it looks like the primary trigger syncs. There must be a configuration I’m misunderstanding between the two. On v2 the Nissan sync window width is set to 4 and it fires and idles no problem. If I select window width 4 on v3 I don’t get the primary sync.
If you can go back to V2 (not sure if you can) then just do that and leave it alone. Personally I have seen many issues with V3. I personally don’t use anything “beta” when it comes to any tuning software. I wait until a stable version comes out and just use it. Has never led me astray.
I can go back to v2 and actually did last week and made sure everything was mechanically sound, which it was. I have a couple of things I want to try before I resort back to v2, thanks for the response.
Did you ever resolve this? I have an rb25 and an EMUblack. Looking to set it up soon, also curious how it runs on the rb25.
Unfortunately I haven’t yet. I’ve been dialing in the ve table on v2 and didn’t spend much time trying to resolve. In the future I may revisit, for now I have plenty to do and learn that v2 provides.
Overall I’m happy with how it compares to the stock ecu. The internal wideband was giving me some fits with inaccuracies too so I’m currently using the output from an aem controller.
Bummer since v3 seems to have some decent updates. I also have an AEM wideband, tru boost and oil pressure controllers. I’m in the process of getting my s13 running again after the clutch fan blew apart but after that I’ll try setting up the ecumaster and play with it. Unfortunately I haven’t touched a standalone since running a Neptune RTP in a Honda years ago.