Adamw

I have done 3 SR20’s on G4X with stock CAS with no drama. Only mild cars with stock cams however. I believe the optical sensor in the Nissan CAS doesn’t like long slots/ windows on the outer ring, they start to behave random like you have seen generating extra teeth or skipping teeth etc. Generally the 24 slot ones work ok if they are cut well. I had an AEM one years ago that the slots weren’t on quite the right PCD and that done weird stuff too. Having said that, there have been a couple of adjustments to the 360 opto triggermode recently that gives a couple of extra degrees tolerance to the sync positions which makes it a bit more robust, so make sure you are using the latest firmware.

Yeah, one of the cam sensors will be the best option. They have 2 long teeth and 2 short teeth, but the falling edges are evenly spaced so that will work. In the ECU set up, set number of cyl to 4, set trigger mode to 1 tooth per TDC, set trig 1 to opto/hall and turn the pull-up off. Set trig 2 sync mode to none.

Typically the signal on the primary side of the coil would not be suitable as a trigger as it is not just an on/off signal like you may expect - once the plug fires you have a whole lot of voltage "ringing" or oscillation coming back out of the primary - so the ecu would see some of these oscillations and it will mess up your RPM calculation. What engine are we talking? What does it have driving the ignition coil? - i.e is the an ignition module/ignitor or is it all a sealed distributor/trigger/ignitor/coil all in one type thing? It may be possible to get a signal from the crank or cam, or maybe the input side of the ignitor but really need more info on what we are working with.

Try the file below. I have made some changes to the idle speed control settings as well as idle ignition. Idle base position table may now not be perfect for cold start/fast idle since there was no cold running in the logs, but you can adjust that yourself later. The E-throttle oscillation means the PID is not correct. I have lowered Proportional and Integral a little, see if this helps. The launch control is not disarming because you need a "non-driven" wheel speed assigned. I have now assigned that in the speed sources menu so that should work now. You can use the file compare function in the software to see all the changes I made. MitsubishiEVO9PCBV1.6G4XtremePlugin V1.1.pclr

I would lean towards the Xtreme in your case. Yes, it can run any engine from 1-12cylinders. The S13 plug-in ecu only has 6 injector drives available on the board and no e-throttle outputs available on the board so that will limit you if for instance you choose to go to a LSx or whatever. It would still be able to run a V8, but injectors would not be fired sequential.

By the look of the connector that is one of the older LSU4.2 AEM's. The analog output on them wasnt particularly accurate. The 4.2 sensors with the square plug are also hard to find in NZ. If you want a lambda controller with a gauge then I would probably suggest one of the newer AEM xseries gauges. These look similar to above but connect to the ecu with CAN. If you wanted a display for the Link CAN lambda then the cheapest option would be an old android phone with realdash or an OBD2 app on it. But you need to turn t on etc everytime you want to drive...

So why dont you try the two maps I have attached above?

Correct, the Red case G4 xtreme doesnt have internal E-throttle. It needs an external driver module. Our newer G4+ external module will still work with it: https://dealers.linkecu.com/G4RET To give you a quick history lesson, the red Xtreme was sold as the lower cost consumer level ecu at the same time as we sold a higher end motorsport grade Vipec V88 ecu. The were very similar hardware except the red Xtreme had some stuff removed to make it cheaper. The stuff removed was peak and hold injector drives, e-throttle hardware and also some advanced software functions to reduce support and development costs. As for the software you need, generally the latest V4.10.2 will work with all firmwares.

No that is a wideband controller, not just a dumb display gauge.

Most likely you have different GP tables allocated so the compare wont work correctly. It relies on the same GP table being used. You can see what tables are allocated near the bottom of the ecu settings menu tree, under table allocation.

There is no AN T 4 available on that ECU.

Just the injector PW looked more than I would expect, but with injectors that small it may not be too far off. The will unlikely be big enough to support any boost at all, but they are not going to stop you from getting it to run/idle. You need to check the timing and find why some cylinders arent working then by the sounds.

Our EvoX trigger mode was originally designed to have the Intake cam connected to Trig 2 and exhaust cam to a DI, your wiring is opposite, but I think it will possibly still work as the pattern is the same on both cams. First, on DI 2, change the active edge to rising and turn the pull-up resistor on. Next I would do a cam angle test on each cam and use the lowest result from each as your offset (trig 2 vvt offset and DI 2 offset). use a test pulse count of 2 for the ex cam test and a test pulse count of 1 for the intake test. Read this help file page for instructions on the cam angle test: G4+ ECU Tuning Functions > VVT Control > Tuning VVT Control > Cam Angle Test If they are still not happy after the offsets are set then we may have to move two pins in the ecu connector to fix it.

Your pinout shows Ign 5 is the ECU hold power, and Ign 6 is the E-throttle relay. But your ign outputs in your map are set up opposite to that. Can you swap the functions between ign5/6 in the map and see if Aux 9/10 voltage comes right. You can view Aux 9/10 voltage on the runtimes screen (F12), ecu status tab as below. Right now you only have 1.1V on that pin.

So why were you using Ign 8? Is there an error in some of our documentation or something? As far as I can see our GTR pinout and GTR map correctly shows Inj 8 for fan 1.

Obviously timing is critical so that is the first step. What size injectors are they?

Yes, pic from the help file below. Typically any relays any solenoids would be connected to the main relay which is fused. This will typically be 10 or 15A depending on how many injectors are connected.

No. It will take about 30 seconds to come alive after start up. If it’s taking longer than that then take a look at the runtimes lambda 1 status and lambda 1 error to see what they say.

That would generally indicate a wiring issue. Is it wired into the DI9/10 pins on the B plug? Maybe try swapping CAN H/L.

I dont see any obvious differences in your two maps. I have done a couple of G3 to G4 updates in my time and generally fueling stays the same if it was a conventional speed density set-up like yours. So you'll really need to get a wideband on it to see if it is a fuel related problem of something else. At least you have good logging capability now to help...

For the E-throttle, you will need to switch it in to "On" mode and go for a drive while logging. If it doesnt go into limp mode during the drive then it can probably stay in "ON" mode and no further adjustment is needed. If it does go into limp mode, then save the log and switch back to set-up mode to get you home. Then we will take a look at the log.

It sounds like you will need to get a tuner or similar involved that understands how the transmission works and what signals and interaction it needs from the ECU. It sounds like it may be missing a torque message or something.

Can you attach your ECU and dash config files and I will take a look.

If that doesnt get you any further then please do a PC log of a start up attempt and attach that and your tune file here. https://www.youtube.com/watch?v=_P1LRANeO4A

I was just going to write this up as a task and I found someone else has already reported the problem a couple of months ago so it is on the to do list already. It appears this bug is recently introduced and in older firmwares the M52 exhaust cam works correctly. Below I have attached firmware 5.6.6 which seems to be the last one before it stopped working. So give this a try for your test in the meantime and hopefully it will be properly fixed by the time you need it. Firmware 5.6.6.3604.LFM