Adamw

User stream file attached.  Set up on ID1635, bit rate 1Mbit.  
LF wheel = CAN Freq1
RF = CAN Freq2
LR = CAN Freq3
RR = CAN Freq4.
 
ECU Master CAN Wheel speed G4X ID1635.lcs

The stock fuel pump controller can only do 3 fixed speeds.

You unlikely need to adjust the throttle.  You will need to tune fuel, ignition, and idle control before you can expect a good idle.  

Wall wetting is not active during cranking.  Precrank prime, first crank enrich and crank enrich are what you want to play with if you think startup fuel is not right.  

You can do a test right in the fan settings menu.

Correct, you just want the -20 in there while doing the timing check.  You can right click on the table then do >im port/export>export to file to save a copy of the table before doing the calibration, then import it back in afterwards.

It sounds like the parameter config may be messed up.  Try this:  
 

The main purpose of the update rate table is to account for "transport delay", this is the time it takes for the lambda sensor to sense a change in the fuel mixture and reach a stable value.  To test this you can log injector PW or fuel table number and lambda, hold the engine at a constant RPM and apply a step change of say 10% to the whole fuel table, the transport delay is how long it takes after you have changed the fuel table until the measured lambda reaches the new value corresponding to the change in fuel input (~10%).  The more gas that is moving through the exhaust system, then the faster this delay will be.  So you can update at a faster at higher RPM because more gas is moving through the system so the delay to reach and saturate the sensor is shorter.  Your update rate can be close to the transport delay time.
If your update rate is too fast then you have to use much less gain to prevent oscillation.
The gain is basically how "big of a bite" the CLL system will take at correcting the lambda error.  To tune this I just log CLL trim, Lambda error, lambda target & lambda 1 and watch response while making step changes to the whole fuel table (just multiply the whole table by say 10% or -10% as well as smaller and larger changes).  Then play around with gain to achieve the fastest correction possible without significant overshoot/undershoot or oscillation.  Especially the 3 cells at the left hand end of the gain table are the ones that make the biggest difference.  You can do a pretty good job of this just free revving, holding at constant RPM, you dont really need to be on a dyno or anything.
 

I would set up a new blank page in PC Link with a big digital gauge displaying AN Temp 3 raw voltage, sit the laptop somewhere you can see it then go around the loom and bend/wiggle/yank/stretch anything to do with the oil temp wiring - including where there may be ground splices and especially around the sensor connector and terminals etc.  That will usually find if there is a bad connection anywhere.  If that doesnt find anything then I would probably look at swapping the sensor next.

I would set up a new blank page in PC Link with a big digital gauge displaying AN Temp 3 raw voltage, sit the laptop somewhere you can see it then go around the loom and bend/wiggle/yank/stretch anything to do with the oil temp wiring - including where there may be ground splices and especially around the sensor connector and terminals etc.  That will usually find if there is a bad connection anywhere.  If that doesnt find anything then I would probably look at swapping the sensor next.

With innovate controllers the sensor usually hasnt failed, they just refuse to work when the frequency response gets slower.  If you get error 2 or error 8 the sensor is likely still perfectly fine and will work with any other wideband controller, if you haven't thrown away already, save them as spares for when you have a decent controller.   
Innovate determine oxygen content by driving the sensor completely differently than they were ever designed to be, rather than measuring the actual pump current required to keep the nerst cell near stoich they instead drive the pump at full current all the time, continuously bouncing current backward and forwards, then use the resulting duty cycle to derive how rich or lean it was.  This can give very fast response and works fine when the sensor is new, clean, and its temperature is relatively stable, but age, temperature and deposits effect the timing a lot so the controller then justs reports the sensor has failed if it takes too long to see the response it expects. 
    

Bit rate should be 500K.  I just noticed you had OBD enabled on CAN 1 so turn that off and try again.  

The fuel pump can be connected to different pins depending on region.  Try changing the fuel pump jumper to the alternative option.

I think this is using raw CAN, not OBD2 PID's so PID is really the wrong term that is confusing the question.  Message ID or CAN ID would be more appropriate.  Maybe their app was originally only designed for OBD2 commands.  
What ecu CAN port is the RC device wired to?

Any of the supported CAN options work well.  There are wireless or wired options, both work equally well and setup is pretty much the same.  
https://realdash.net/manuals/supported_can_lin_analyzers.php

Your ECU has 2 CAN ports, you can use either one.  It is fine to connect multiple devices all to the same bus, this is exactly what CAN is designed for. 

Yes, and the "Delphi AC IAT" and "Link IAT 1-8" cal is the same. 

I suspect the unstable idle is possibly due to the SPWA as the lambda bounces up and down by a whole lot more than the reported effective PW.  You can see his reported Eff PW is bouncing between about 0.5 and 0.6mS (this reported value doesnt include SPWA).  If the injector was perfectly linear then 0.6ms would be 20% more fuel than 0.5ms.  If you add the SPWA figures on to that - at 0.5PW the SPWA is -0.066 and at 0.625PW the SPWA is +0.046 so you actually end up with a final PW of 0.434ms for the commanded 0.5 and final of 0.646 for the 0.6 commanded, or you could say 48% extra fuel/PW.  Obviously those adders are there to compensate for an injector that is not perfectly linear, but perhaps those or the deadtimes are wrong and therefore adding or removing fuel where it doesnt need to be.  
For the wall wetting I know it is disabled during start up so it is unlikely but I thought there could potentially be something triggering it either at shutdown or shortly after starting that causes the flooding.
 
 
 

There are two common types of EGT sensors.  RTD's - these are a resistance based sensor and in laymans terms work similar to a coolant temp sensor.  RTD's can be connected directly to an Analog temp input.  RTD Pros: Simple connection, no amplifier needed, no special wiring needed.  Cons:  Max temp around 900C, generally slower response than TC's.
The 2nd type is a thermocouple.  Thermocouples only generate a tiny voltage (<50mV at max temp), so for connection to an ecu they need an amplifier to increase that voltage output.  TC Pros: Higher temps (~1200C), can be faster response.  Cons: needs an amp, more wiring (amp needs power etc), special cable and connectors required if TC wire needs to be extended.
 
A common RTD is AEM 30-2052.
For EGT amps there are many options, Texense THK 1250 is a nice single channel one or there are many less fancy low cost options. 
 
 
   

Yes, it comes from the same manufacturer as the Link ones by the looks.  Calibration = Link IAT1-8.  

@Brian B I suspect in your case the built-in "Link 3 Bar" calibration in the firmware might be wrong.  At least with the little bit of testing I done today I was getting low values reported by PC Link vs what I calculate from voltage using the manufacturer's transfer function.  I just asked the Firmware team to confirm so I will come back to you when I have an answer. 

With innovate controllers the sensor usually hasnt failed, they just refuse to work when the frequency response gets slower.  If you get error 2 or error 8 the sensor is likely still perfectly fine and will work with any other wideband controller, if you haven't thrown away already, save them as spares for when you have a decent controller.   
Innovate determine oxygen content by driving the sensor completely differently than they were ever designed to be, rather than measuring the actual pump current required to keep the nerst cell near stoich they instead drive the pump at full current all the time, continuously bouncing current backward and forwards, then use the resulting duty cycle to derive how rich or lean it was.  This can give very fast response and works fine when the sensor is new, clean, and its temperature is relatively stable, but age, temperature and deposits effect the timing a lot so the controller then justs reports the sensor has failed if it takes too long to see the response it expects. 
    

You just need to change the Start Position.

With innovate controllers the sensor usually hasnt failed, they just refuse to work when the frequency response gets slower.  If you get error 2 or error 8 the sensor is likely still perfectly fine and will work with any other wideband controller, if you haven't thrown away already, save them as spares for when you have a decent controller.   
Innovate determine oxygen content by driving the sensor completely differently than they were ever designed to be, rather than measuring the actual pump current required to keep the nerst cell near stoich they instead drive the pump at full current all the time, continuously bouncing current backward and forwards, then use the resulting duty cycle to derive how rich or lean it was.  This can give very fast response and works fine when the sensor is new, clean, and its temperature is relatively stable, but age, temperature and deposits effect the timing a lot so the controller then justs reports the sensor has failed if it takes too long to see the response it expects. 
    

With innovate controllers the sensor usually hasnt failed, they just refuse to work when the frequency response gets slower.  If you get error 2 or error 8 the sensor is likely still perfectly fine and will work with any other wideband controller, if you haven't thrown away already, save them as spares for when you have a decent controller.   
Innovate determine oxygen content by driving the sensor completely differently than they were ever designed to be, rather than measuring the actual pump current required to keep the nerst cell near stoich they instead drive the pump at full current all the time, continuously bouncing current backward and forwards, then use the resulting duty cycle to derive how rich or lean it was.  This can give very fast response and works fine when the sensor is new, clean, and its temperature is relatively stable, but age, temperature and deposits effect the timing a lot so the controller then justs reports the sensor has failed if it takes too long to see the response it expects.