Vaughan

Oh that's good. Thx for your valve and useful information! Really appreciate.
Jacky

That will all be set automatically when you choose LS2/LS7. I would expect falling on both.

If the idle got rougher and it is showing a leaner afr it seems reasonably likely that it is missing which causes a leaner afr (sensor measures how much unburnt oxygen there is).

Awesome cheers buddy, I am going to use them then but I'll have to run new cables Anyways as they have to go a further distance so mayaswell put new ones in 

ok, thanks very much.

Worked well. 
Arming and disarming with DI1.
Speed Lockout set to 1. (If i leave it on 0 - launch won't engage)
Launch disarmed when DI1 goes off.
 
 
White Ford Fiesta.
RPM 6000
1.6 bar in the intake on the start.

Don't even need bangs to get these stunning results with Link.  
Launch Control

just checked again and yeah, that seems to be right. Though I swear yesterday I checked it was showing all options for all GP outputs without assigning a pin.
Thank you

GP Outputs and GP PWM Outputs don't display the rest of the settings until an output is selected. Do you have a screenshot of a GP Output with an output set but no settings showing?

Something I've done recently is add a knock warning to my CE Light, I used a math block to calculate knock level - threshold and put it through a gp output to get an off delay (hold time) and fed it into the CE Light Aux.
So far I've only used it for playing around with setting up my thresholds (so I can see how often it happens and for a clearer picture of when it happens) but I imagine it will be very useful once I've finished setting u the knock too. It has also been very useful for reviewing Knock stuff in PCLink logs as often the knock stuff happens too fast to be caught by PCLink but the knock light status can be used to see when it occurs without needing to actually see the knock level above the threshold.
 

Something I've done recently is add a knock warning to my CE Light, I used a math block to calculate knock level - threshold and put it through a gp output to get an off delay (hold time) and fed it into the CE Light Aux.
So far I've only used it for playing around with setting up my thresholds (so I can see how often it happens and for a clearer picture of when it happens) but I imagine it will be very useful once I've finished setting u the knock too. It has also been very useful for reviewing Knock stuff in PCLink logs as often the knock stuff happens too fast to be caught by PCLink but the knock light status can be used to see when it occurs without needing to actually see the knock level above the threshold.
 

Thank you sir

You guys are absolutely shit hot!!! Thanks alot for your help, that explained everything!!! 

To confirm Vaughan's comment, the lockouts just control the point at which closed loop control takes over.  Outside of the lockouts the idle valve will be in open loop mode and will just follow whatever is in the base position table.  The help file explains how most of these functions work.

Thanks. I'm waiting for the G4X Fury so can't test but it looks like I have options for VTC.

coworker has made the comment that you might be better of switching around math block 1 and 2 there as that would mean the LH End calculation would happen immediately before the lower threshold calulation which uses it instead of using the value from the last round of calculations, I doubt you would be able to see a difference but it would be more technically correct.

Try this, seems to work from a quick play on the desk

Great, thanks for the quick response
 

Yes boolean on/off would be excellent. I've played with 3d tables with RPM axis of 999, 1000, 1999, 2000, 4299 and 4300. I need VTC on at 2000rpm at low load but on at 1000rpm at high load with effectively a straight line in between. I thought this would be really easy to do in a 3d map but it actually seems tricky to do with the playing around I've done.
Interesting concept. Yes math block could be a winner to get the different cutoff at varying load. I'll have a play with that option. Thanks.

18 & 52 are the main grounds I believe, 27 & 28 are sensor grounds and 35 is the trigger ground

Make sure Disable Digital Input is set to off or is inactive, if that doesn't work check the knock status runtime

I thought I did, but it seems I did not, as today with some crispy fresh pulls it is working properly. Thanks

My bad, part of the risk of trying to convert basemaps using a custom program. New release will have it corrected to the G4+ axes.

same setup seems to be working for me here, do you want to attach a copy of your basemap?
Also just to clarify did you setup that math block before making that log? The math blocks only work in real time and can't be backdated through logs.

Lights should stay on a short while after turning the key off as the JZX100 has ECU Hold Power (For the idle stepper motor). Does the ECU stay on indefinitely or does it turn off after about 10 seconds? if indefinitely try unplugging it and plugging it back in to power cycle it.

I was using the wrong software. I was under the impression it was a g4+ ECU, as that is what I ordered, and that's what the instruction manual listed it as. It's a g4x ECU. Waiting on the unlock code now, but, the ECU is able to communicate with the PC now.