FL2-3.2 turns over but does not start, then a few minutes later it does

New to me 2008 FL-2 3.2 Petrol JDM 156,000km - debugging

So today, pleasant sunny day - 10-12° (C), the FL2 started it up, drove 6 km into the village (40 km/h). I came out 5 minutes later, the engine would crank but not start. As a pushbutton, it turns over a few seconds and then stops. Tried about 10 times. Cranking sounded normal, no struggling battery. Then started pushing various buttons, turning off radio, flipping terrain controls on and off. No joy. Locked the car while sitting inside and reopened. Nothing. Tried again, nothing. Elapsed time about 10 minutes or so, then once more, nothing and again - it fires up like nothing has happened. Drives home fine, started two hours later when I put the OBD on to get readings.

This is the second time, but the first a few days ago, was just a few tries and I wasn't sure it actually was a problem. Now I know it is.

Error Codes

P061A-62 Intermittent = Torque performance of internal control modules. This code is not listed (or I cannot find it) on the FL-2 Error Code list - when I cleared it, it did not come back after starting the engine (but no driving)

U3000-87 Intermittent Control module - LR Manual states:
Control module Missing message Check CJB for DTCs and refer to DTC Index.
For additional information, refer to: Communications Network (418-00 Module Communications Network, Diagnosis and Testing).
Check information and entertainment module for Car Configuration File and MOST network DTCs and refer to relevant DTC Index. Carry out MOST/CAN network tests using the manufacturer approved diagnostic system - when I cleared it, it did not come back after starting the engine (but no driving)

U2101-00 Intermittent - Control module configuration incompatible -
Control Module Configuration Incompatible - No sub type information
Car Configuration File (CCF) information incompatible to Adaptive Front Lighting System (AFS) Control Module
Check the correct Adaptive Front Lighting System (AFS) Control Module is installed to vehicle specification. Refit original or replace the module as required. Refer to the new module/component installation note at the top of the DTC Index

The most significant hint was the reader showing the battery at 12.3 v with the ignition on and the engine off. This is below recommended spec, and like the Jag X350 I recently sold, I know these cars are battery sensitive. But why would it go on strike when warmed up, and then start up after 12-15 tries which generally depletes voltage?

I've done the usual Google searches, but can't find a similar set of symptoms.

If anyone has any thoughts (other than buy a new battery, which I will do tomorrow), I would appreciate it.

Maybe look at the crank sensor, and or it's wiring, also the cam sensor, does this only occur when the engine is hot or after a run, or does it do it from cold start.

Arctic2 said:

Maybe look at the crank sensor, and or it's wiring, also the cam sensor, does this only occur when the engine is hot or after a run, or does it do it from cold start.

Click to expand...

Warm. The car had been sitting for a few days. I decided to take it into the village, about 6 km away, 40 km/h, so enough to warm it up. Then it sat for 5-10 minutes while I did some food shopping.

These vehicles are very power hungry, so having a perfect battery is the first step to reliability. If the standing battery voltage is 12.3V, then it's below specification, and should be replaced with a suitable replacement.

As above, a failing cam sensor can prevent starting when hotter than cold.

+1 for a failing cam sensor causing starting issues, especially when the engine is warm