Simon

Essentially the issues is something electrical as the ECU can only work with the signals its given. The ECU looks at the calibrated % reading off the 2 signals and if it drifts by more than 2% it will start to clock errors. Once it hits 100 errors it will shut the throttle down. (takes roughly 2 seconds to do this if in constant error. The target is all based off the TP main reading

Nope

What type of sensor is being used/ VR or HAll/Optical? For a VR sensor you need to get the speed up enough to have the positive voltage go above 1.5V before the Di will register it.

Low, Medium and highspeed modes

Check the power and grounds to the cam sensor and also where the tooth is relative to the gap on the crank. You don't want the cam tooth at same time as the gap / tooth after gap is gong past crank sensor.

The Red cased Xtremes did not have CAN 2 they only have CAN 1

As something to consider it might not be the sensors them selves. The timing between them could be an issue (Sync happening very close to the gap on crank) Or it could be a coil / ignition issue where it is breaking down and radiating noise. (arcing out of coil / lead and not firing the plug)

Looms have been unchanged on these so V1 -V5 all suitable Injector drive will be happy with 0-4 High impedance injectors on it. Any TPS that is 0-5V output can be used. Regards Simon

Yep it sure is. Just need to have that input as one of the boost target or WG DC table axis.

Its a G1 Linkplus with V14 firmware. Manual can be found at http://forums.linkecu.com/applications/core/interface/file/attachment.php?id=2537 It has a Opto/Hall board fitted so will suit any application that has a tooth for each TDC and opto or hall sender.

It is PC tunable. It has a sub-board to suit a tooth per TDC VR sensor (Reluctor) Mazda mixed and matched a bit but their early stuff was often reluctor.

On the 185 ECU we have no outputs wired for Fan control, As we are expecting them to be controlled as per cj's response above. Can you confirm if they are actually wired back to the ECU?

You will need to have the sub-board changed to suit the new application.

No VVt control on that unit. It could do switched like Vtec or the type used on the RB series engines but not the fully variable as found on the 2J VVT motors.

ECU has been unlocked?

Options are all going to have 2 injectors per drive. You can run sequential and injectors paired, or run Group staged where drives 1,3,5,7 are for the primary injectors and 2,4,6,8 are for the secondary injectors.

The LinkPlus G2 used a standard 9pin D serial cable available form most places doing PC sales

No it is only suitable for a single input. One sensor will likely be ok provided you can get it towards the center of the engine.

Just one ground and the power on A plug will be all you need.

The find CAN device only works for the Link CAN Lambda modules currently. It will not find other 3rd party devices.

I'm assuming you are looking for the ECU logging to activate of the conditions. Can you attach a copy of the MAP from the ECU and if possible capture a PC log during a time where the ECU logging didn't activate as expected. also be aware that the ECU logging on the V series will only take 10 logs and no more even if memory is not 100% full.

First step would be to get some current firmware into the unit. The G4+ firmware and software works on the I series units. You will need to assign the Di as a wheel speed and then set this in the speed sources menu. https://www.youtube.com/watch?v=u54915wuLYc

The Vipec adapter being serial based will not allow PC coms at the same time. Top port is the USB coms (which piggyback of the serial coms) The lower port is Serial and CAN depending on what wires are in use. Try with the data stream mode on off.

The issue comes from the cable used. If you are using the CAN dash cable it has the TX and RX serial wires also connected and this causes noise on the RS232 which is what the USB also uses. You would be best to use a CANF connector to replace the CANdash and only wire the CAN wires. Regards Simon

You would connect the MAP and then have a 4D overlay table based on MAP