Adamw

Please do a log and attach your map: https://www.youtube.com/watch?v=_P1LRANeO4A There is no fault code worded as you describe.

Ok, attached below is a firmware file containing firmware 5.6.5.3430, copy this to your harddrive firmware folder found here: C:\Link G4\PCLink G4+\Firmware. Open up PC Link then do a firmware update on your ecu as normal and choose 5.6.5.3430. After that you will have a new trigger mode "Suzuki K6A No-VVT". Try selecting this (change trigger 1 to reluctor), leave trigger 2 set to the defaults. Let me know it that works. Firmware 5.6.5.3430.LFM

In the next firmware release there is a new triggermode called "K6A Non-VVT", this engine has a cam sensor only (no crank sensor) and appears to have a similar pattern to yours above. Can you confirm if your signal above is from the camshaft wheel or crankshaft?

Can you confirm in that photo, pin 1 is the right hand end and pin 4 is the left hand end. The correct spark edge is falling for these coils, if you’re coils are getting hot when the engine isn’t running then you most likely have the pinout wrong.

Our 350Z base map has injector deadtimes and ignition dwell times for the stock injectors and coils. I have notes that the injector flowrate on our car was 284cc @ 345Kpa, which was the base fuel pressure. The fuel system type is returnless.

HP Academy have a decent webinar on the subject. A USD$20 membership will give you access to their webinar library. https://www.hpacademy.com/previous-webinars/049-setting-up-knock-control-link-g4-vipec/

Hi Josh, its a bit hard to read the text in your screenshots but from your proposal it sounds like a good way to achieve this. Obviously you can get more complex by "stacking" virtual auxes to get more conditions or incorporate timers etc if needed. You can also change to a GP PWM aux output if you want a 3D table to map the on/off conditions.

The G3 doesnt have OBD2. I think you will need to upgrade to G4 firmware to get anything useful out of it. In G3 firmware you have very few options for display (apart from a laptop). With G4 there are many CAN options as well as serial and USB options such as realdash:

The factory solenoid has two wires. one goes to +12V ignition switched, the other goes to the ECU aux output (Aux 8, ecu pin 25).

Most looks ballpark except for the gains. Set all to 1 initially.

I think you will need to upgrade the G3 to G4 firmware as I dont see any way to configure the CAN output in the old G3 software. There is a cost associated with this, you need to purchase an "upgrade code" from a dealer, to give you an idea it is about NZD$230 in NZ. Your ecu will also most likely need a small hardware mod to enable the CAN. We can send you instructions to get it done locally or you maybe able to do it yourself if you are capable with a soldering iron (or it is a free of charge service if you want to send back to us in NZ). Note also the G4 doesnt have any CAN receive capability (only transmit) so you will be able to send data to the dash for display but you want be able to use the Toucan touchscreen "buttons" to activate anything in the ECU.

You cant connect a wideband sensor directly to the ECU, you will need some kind of wideband controller in between. CAN bus type of analog output type can be used, Link have a CAN bus option: http://dealers.linkecu.com/can-lambda Your car should already have a factory fitted wastegate solenoid, the most common method is to remove the factory solenoid, then connect the new solenoid to the existing wiring that went to the factory solenoid.

The proportional for the 1JZ vvt mode is 6.0 when set to default PID mode. This works ok for most 1J/2J's but I have seen a couple recently need lower P. I dont know if it is related to wear of the hardware, oil viscosity/pressure, or some other variable.

From its datasheet here: https://www.milspecwiring.com/DATA SHEETS/RG/RG_SPEC-0016 Fluid Temp Sensor.pdf its calibration is similar to the Delphi ECT but not an exact match, it will read about 5deg out if you use that. It will be best to create your own cal table for it.

The mxs stream is in the 5.6.6 firmware which is not out yet. Set your ecu CAN to transmit generic dash stream.

Yep, see attached. Thunder with Mounting holes.pdf

Hi Mark, I suspect the problem is your oil temp sensor being on a AV input is not actually assigned to the "oil temp" parameter but rather a "GP Temp" parameter that is not sent in the standard generic dash stream. Attached below is a configurable version of the generic dash stream where I have replaced "oil temp" with AN 8 - Oil temp. MarkHellier.lcs For any others that want it I will also attach an un-modified configurable generic dash stream. Configurable Generic Stream.lcs

I have sent you a PM.

How sure are you that this is a magnetic sensor? I wonder if it is an active type sensor. Do you have any testing info in a workshop manual or something that may give us a clue?

Hi Sergey, this is usually done with a circuit external to the ecu. There are aftermarket options available or if you are capable of basic electronics I can give you a simple Op-amp circuit that you can build yourself. Here is one 3rd party option: https://www.haltech.com/product/ht-038001-nissan-attesa-4wd-tps-adaptor/

What settings do you have on the DI and what are you looking at to tell you there is “no response”?

Every engine is potentially different, but in our multi-fuel example map (from our Subaru EJ20 dyno mule engine), it has a value of 14deg for petrol charge cooling and 8deg for ethanol.

attach your ecu tune file and dash config and I will set it up for you.

No, just load one of our basemaps out of the PC Link basemap folder. Note before you "overwrite it" I suggest that you save a copy of the existing protected map as you can always load that back in if you get stuck. Also before overwriting, have a look at the runtimes screen and note down (or take screenshots) what functions are assigned to aux outputs, analog inputs, and DI's like pictured below. Having this info will make it easier to set up the new map.

Also dont forget to turn off the IAT trim table. You may still need two VE tables (as even if all your injector and fuel property data is perfect, VE will still change a little) but at least your individual trims will still work if you need to use two tables now.