Simon

I would suggest it likely to be many more months at this point. If time is an issue I would suggest looking at either changing the pattern to something already supported or to an alternative manufacturer

If engine speed is not correct then its not working. The issue with patterns above is they require a custom code in the firmware to make them work. We have one that matches the crank but it requires the other half from a cam sensor to decode. So that is matches what is used on the Subaru. We want a wheel that has evenly spaced teeth with 1 or 2 missing in a single location. Not multiple teeth missing in different spots.

You will need to make sure the numbers match 200kpa in MGP is the equivalent of 300kpa in MAP

Another 2 options are to use a gutted relay coil that the ECU switches to provide a coil negative signal. Or get the rev counter converted to accept a low level signal direct from the ECU.

Yes E throttle is fine.

The Mazda 3 mode would be my first pick. This runs the same crank pattern with 6 teeth on the cam

SR20 base would be an ok starting point. Triggers are the same you would just have to configure ignition mode to suit what you are running.

I'm assuming that wheel fits the crank? It looks very much like a Subaru crank wheel but this would require a matching pattern on the cam to give a matched pair to the Subaru. You want a very basic pattern such as 12 missing 1, 24-1 or similar.

The ECU will need to have the correct sub-board for the CAS if you take the lid off the ECU there will be a smaller board that is bolted in this should have a main chip with a sticker on it. It will need to read SUB24NEW to be suitable for that CAS.

You will need to go live with the ECU and set the cylinder count to 8. If you are then on direct spark and sequential fuel it will force the drives to the correct settings. In the map you are working on it was form a 6 cylinder application and so those drives were free to be used for other functions.

Generally you want a safe tune on the engine that is known to have no knock. You can then run the engine and set the gains to give good signal levels and adjust the knock threshold to suit. For more specific information head to the PC link help file Navigation: G4+ ECU Tuning Functions > Knock Control

On the G4+ plugin it is just a case of turning on the Knock control in the software and then configuring to suit the engine noise profile. No need to add additional devices.

You need an igniter channel per coil. Generally the igniters limit the max current so trying to drive 2 coils off the one channel halves the current to the coil, massively reducing the available spark energy. Going for smart coils with the igniter built in is ideal if going to pair up ignition outputs.

Right click on the table and then go to Axis setup

HI Chrispin yes with a 1K pullup to 5V you can use our cal numbers in ohms.

Comon issue was to have the cam timing skip a tooth. Other wise the connection between the micro and the socket can fail over time.

You will need to select map sensor type as CAL4,5 or 6 And then set up matching cal as per image.

Have you tried the ignition test function in the ECU to confirm coil operation without the engine turning over? With this you can check each coil for spark one at a time and it is not requiring a engine RPM or any other input to be functioning. This will confirm we have working coils and wiring to the ECU for the ignition drives.

Scott made this vid which will help you out

Yes there will be a path to ground through the components when the ecu is powered down In the pc link help file there is a good explanation of this Navigation: G4+ ECU Tuning Functions > Auxiliary Outputs > Wiring Auxiliary Outputs

No nothing at this point unfortunately it is a busy time for us currently

ECU will switch ground to control both and they will require relays as the ECU can only switch 2Amps max. Fuel Pump is on pin 18 in a factory set up. Fan is on pin 19

File is from the base maps folder in PC link BMW Mini R53 G4+ Xtreme Plugin.pclr

Thank you for sharing integraleV8

Are you able to open base maps ok with out the error? You will see a code like this in PC link sometimes if the ECU is on very old firmware or an older generation G4 not G4+