Simon

Hi Can you please post you map so we can see the settings.

Hi Jump into the PCLink help file and search logging. This will give you a run down on PC and ECU logging options.

Sounds like you might have a back feed. There should be no voltages at the ECU once the key is turned off. You are correct in the tacho out is a AUX output and will go from there to the dash.

For the launch control the DI activation is geared to be a on off type switched input. Looking at the MAP this should be set as Di6 Looking at the set up of the Di the switch should be wired to ground. The launch control also operates of the non driven speed input so be sure to set a non driven speed in the speed sources menu. Note it can use the same source as the driven speed. The Knock used to be an upgrade option. To get the knock working you will need to upgrade the firmware to 5.4.x You can then set the knock to ON Knk internal. The sensors are not wired to a AN volt they have there own input.

Hi Im assuming its a R34 GTT not the GTR R34? On the R34 there is a speed input from the gearbox on Di4 The wheel speed sensor are not wired directly to the ECU so if you want traction control you will need to add wheel speed inputs via the XS connectors. The Narrow band sensor is wired to AN Volt 2 on pin 50. The sensor when the engine is not running will often read 0V to stop the errors you will need to set the error low value to 0V. The Di inputs can accept either a 12V or a ground input. If switching to 12V the internal pullup on the Di will need to be set to off. The stock knock sensors are able to be used if you wish. You will just need to configure the knock control. The closed loop fuelling should work so this is likely to be a configuration issue. We can look at your map to see the set up of this if you wish.

Hi Stefan You will see 12 Volts on the two wires that head off to the coils. I would not expect to see one with 5V while the engine is not running. You can also do a ignition test on each ignition drive. Also make sure you have selected the correct ignition configuration being distributor or wasted spark.

Software changes Version 5.x.x.2627 (DLL Rev 2495) - 22-05-15 New Features · The user can now start and stop logging by clicking on the logging status in the top right hand corner of the PCLink window. Changes · ECU serial number input in file encryption system will only accept up to 5 characters now. · PCLink now requires the user to save all basemaps as .pclr files. · Continued improvement of new graphical interface. · Axes in the Axis Setup of a table now display two decimal places. · Trigger Scope voltage now displays whether it is AC or DC coupling. · When opening a damaged log file, PCLink now opens any data it is able to retrieve. Fixes · Continued improvement of font visibility. · Restored log file marking and clearing on tables. · Stopped the focus from shifting away from a recently opened table or settings view. · Stopped the table/setting view history from becoming corrupt on ECU reconnect. · Parameter List scroll bar now resets its position when the scrollbar is no longer required.. · Time plot sliders are now always visible. · Increased fidelity of time plot traces. Version 5.x.x.2540 (DLL Rev 2495) - 20-05-15 Changes · Improvement in the accuracy of time plot traces. · PCLink shows busy cursor while attempting connection to an ECU. · Font sizes in windows adjusted where necessary. · Colour theme settings now displayed alphabetically. · Clear statistics now prompts for conformation before clearing. · Tidied up settings view, time plot and runtime value list. · Trigger scope and runtime value parameters window now share focus more conveniently. · Layout tabs now wrap around when scrolling with keyboard. Fixes · Fixed table chart from displaying 1D and 2D maps incorrectly. · Fixed CAN frame allocation indicator showing frame ID incorrectly. · Fixed mixture map from selecting the wrong cell when clicked. · Fixed view borders from not drawing properly. · Fixed the runtime value list window so the user cannot alter the order of tabs. · Fixed settings made offline from displaying an incorrect status colour. G4+ Firmware Version 5.4.3.2623 - 22-06-15 New Features · Toyota 1FZ trigger decoding mode. · RiDE braking control for Yamaha FZ plug in ECUs. Added RPS Analog Input options. Fixes · Improvements to internal ECU self test commands used during production testing. · G4+ Fury ECUs could report incorrect error codes for internal wideband control. This was not an issue during normal sensor operation. · DI 11 did not work on G4+ Plug In ECUs. Also requires support processor firmware revision 3.

RPM and Speed are easy but the DisplayLink is not able to do an odometer.

That would be a good coil pack but I suspect it will still require an external 3 channel igniter as it only has a 4 pin plug. This would be a 12V in and the 3 signals from the igniter.

You could likely use the Supra plugin map and then reconfigure all the I/O to suit the harness you are using. Im assuming its a non vvt motor?

The ignition trim will have no effect as with 100% cut you will have no ignition to retard. The enrichment is geared to have some extra fuel when the load comes on. I would not expect it to need to add much fuel if any at all.

Could be a number of issues. It pays to make sure the engine will hold a steady idle with no idle correction. It might be a case the throttle opening is a little too small at idle. And as the air temp increases it is just not allowing enough air into the engine. The ISC base numbers could also be out or the duty cycle is maxed out (butterfly not open enough) There could also be a IAT fuel trim that is not quite correct and the mixture is off causing the idle to become unstable. This could also be the case on hot restart too.

Hi Crispin Yes you can set the Driven Up Shift or Down shift cut to 100% if you wish. The Fuel if a % increase on the calculated fuel while the cut is active.

The ECU will put the pressure out in Kpa. As long as you scale the input to the ECU in Kpa the output should be correct with no equation needed in the dash.

The ECU just switches a ground so if you have no tacho connected will need a pullup resistor. In this case a 1K resistor between the signal and 12V will then give you a 0-12V square wave that the Omex will be happy with.

Hi Andy You need one igniter channel per coil. So if you kept the stock coils you would need two of the three channel igniters. If you pair coils on the output it halves the available current and you end up with a very weak spark. The 3 dual post coils are a good option and if you get smart coils saves on an igniter. Note if you go with dual post coils you must run resistive spark plugs.

Hi Jeff The Vi-pec range has been reduced to just the powersports. The Link NGTR+ is the unit you will be after. This is to the same specs as the Vi-Pec I series units. It supports the R32, 33 GTST and the GTR 32, 33 and 34

In theory if the PC link software is showing correct then the display is using the same information and should follow. If you change the error value to another figure does the dash follow?

Any place is fine just avoid the area around where the gap is on the crank. If you moved it 90deg in either direction from where it was would be fine.

That looks like a very good trigger 2 signal. We look at the tooth immediately after the gap and this is well clear of either edge on trigger 2. One thing you could try is setting the ECU to be group fire this will lighten the processing load on the micro.

Only unusual thing with that sensor is you will not require the pullup on the Di to be turned on. You will need to set the speed calibration number to make sure the ECU is reading the correct speed. Once the ECU is seeing speed you should then be able to add EFI speed on one of the racepak channels.

Doing a bit more looking and it seems you might be able to reprogram each channel of the Vnet. If you right click on a channel it will give set up options as highlighted in the attached image.

Hmmm that is most odd. In theory when you read the config from the Vnet module they are the only inputs you can then assign to the Display. So when you right click on the IQ3 tab and go to set the inputs these have to be form the available list the Vnet gives you. Its almost like the Vnet module is not programed correctly. Im not sure if you can reprogram the pre configured modules.

Does the adapter look like the one attached?

You won't need the logger (we don't have one) It is interesting that when you read the Vnet adapter you are not seeing the ECU options. It makes me wonder if the adapter is programed correctly.