Vaughan

Does the ECU show any errors for CAN2? Have you got CAN 1 and CAN 2 plugged in the right way around?

It is possible to use the cam sync but you will have to be careful how you set it up. The 1jz vvti pattern looks like what you say your pattern is so I would recommend giving that trigger mode a go. I'm not sure if it's possible to setup a cam with multiple teeth for sync when using multi/missing trigger mode in G4+, it is possible in G4X. You will need to recheck your calibration angle if you change to the 1jz vvti mode

I believe you want to use the 1jz vvti trigger mode in terms of offset you'll need to figure that out with your fuel turned off and a timing light

A lot of the PCLink software is visually very similar, the biggest difference being that unlike in G4+ where you go to the aux/DI/anv pin and then set what it is you now go to the function and select what pins that function is using. I recommend just having a play with the software, have a look through all the features and read the help manual if you are unsure what something does. I also recommend using the new asynchronous injection function (under Fuel Main) which greatly reduces the need for accel fuel and is a lot faster to react than traditional accel fuel.

If it is a distributor car from factory the tacho most likely needs modification to work with an ecu signal instead of a coil signal. I've modified an mr2 tacho before with a couple of resistors, not sure how to do your one but some people have managed to trigger coil controlled tacho's by wiring a relay coil up to simulate the coil signal. I believe the sweeps happen when the ecu powers up.

That basemap doesn't appear to have fuel turned on and is setup for modelled fuel (which doesn't have a master fuel value). have you had it running long enough to get a Lambda reading? Have you tried putting more fuel into it just to get it running and allow you to warm it up and set it up properly? Do you have any logs of your start up? I believe there is also a newer firmware available than what you are running, never a bad idea to use the most up to date PCLink and firmware especially if it's a new tune.

I don't have any experience with that particular motor but you should just need to connect your trigger 1 to the crank sensor (I assume the 1.8vvt motor has a crank trigger unlike the earlier 1.6 with cam sensors only) and trigger 2 to your cam sensor. Connect an aux (one of aux1-10, aux ign5-8 or aux inj5-8) and a switched power wire to the vvt solenoid. That should be all you need to do specifically for the vvt wiring. You might have to add wires to the loom for inj3&4 to run sequential fuel as they are connected to the ECU header but the earlier vehicles don't use them and so might not have wires connected to those pins. Other than that have a look through the plugin pinout and the loom in your car to make sure you have all the wires you need to do what you want, you may even be able to use another pin like aux7 (purge) for your vvt control instead of adding an expansion loom. One final note, the factory wiring for the early mx5s has the MAF turning on the Fuel pump so you may want to rewire that.

I use the link 1/8BSP sensor, seems to work fine

Will require quite a bit of rewiring but don't see why not

@RossobianconeroThere is now a new release on the website which has that axis dp issue fixed.

Use Aux 1 and Aux 2, set to ISC Solenoid and ISC Solenoid Slave.

Your ECU most likely has a second CAN bus available which can be used for any additional CAN stuff you want to add.

Attach a copy of your basemap please

The advanced settings allow you to change the initial cut, final cut and cut range among other things. The help manual has a section explaining how it all works but smaller start cut values might help as could a larger limit control range.

If that's a PCLink log then it is possible that knock occured on all cylinders but the log wasn't fast enough to capture it. Have a look at the post start enrichment settings if the engine is lean for a time after startup.

In the Engine Fan menu there is a setting for each of the 3 fans called "Engine Fan X on with AC" where X is the fan number. Turning this setting on means that the fan will turn on when AC is on. If you attach a copy of your map I can change that setting for you. What do you mean by "hard wire kilometer"?

Apologies if I got that wrong, I did test it with a relay I had lying around and it seemed to work but it was done on a G4X plugin not a G4+

The help does only specify storm, xtreme and fury but I believe the plugins have the same hardware. The section of the help manual is Wiring Information -> Output Wiring -> Auxiliary Output Wiring -> High Side Driving There is more help information under G4+ Tuning Functions -> Auxiliary Outputs -> Wiring Auxiliary Outputs as well

Driving high side means outputting 12v so you can use any of Aux5-8 to send 12v to a relay which has a ground on the other side of a coil to activate it.

Aux 5-8 can drive high side, ignition drives can only drive low side when being used as an auxiliary. In PCLink set the Driver Type to High Side. On the S13 plugin: Aux 5 is pin 113 Aux 6 is pin 25 Aux 7 is pin 32 Aux 8 is pin 33

That reply was related to the part about using math on a 4D ignition table @Adamw. Had a play with using Lambda on a GP Limit table axis and it works perfectly when you are connected or have been connected and disconnected but doesn't appear to work correctly when being offline and loading a basemap. So a work around for the moment is just to set it up while connected to the ECU. Just checked the Math stuff again and it runs into the same problem.

What have you got your Math Block's Decimal Places setting set to @Rossobianconero? The number of dps you can use in the axis is limited by this setting, have just tried it and it appears to be working for me.