I accidently stalled the engine the other day; i had a lot on my mind.
However, it wouldn't restart, the fuel gauge read zero and the trip comp gave a range of 1 mile despite that fact that i'd just half filled the tank.
After a few locks and unlocks it started and the fuel gauge very slowly came back to the correct reading.

Anyone a clue to what went on? Another member of the failed FL2 clutch/DMF club, twice.

A lot of things could done that along the chain...
The fuel level sender is communicating the fuel level to central junction box (CJB).
From here it is sent over can-bus to the engine ECU and to the instrument cluster.
Because both engine wasn't starting and instrument cluster showed zero, then the information about fuel level on the can-bus, after/broadcasted by the CJB, was non existent, or zero.
So the problem was in one of these places:
- fuel level sensor glitch;
- bad electrical connection at fuel sensor;
- bad electrical connection at CJB;
- software glitch inside CJB.
I tend to belive that was the last one.
So, if I were you, I wont worry.
Yet....

Alex,
Thanks for your thoughts. I can't figure out what went wrong, the car has been fine ever since. What i did find odd is that EMS didn't go into limp mode after restaring the engine as both gauge and trip comp were so low. It took a good 5 minutes for them both to come back to normal readings.
Think i'll check any fault codes but i've a feeling that i wont find any.
Oh, Happy New Year!! Another member of the failed FL2 clutch/DMF club, twice.

Happy New Year to you too!

Pegleg wrote:

What i did find odd is that EMS didn't go into limp mode after restaring the engine as both gauge and trip comp were so low.

You could be right.
Incidently, the low fuel w/l didn't come on, very strange.
Now if i was still working in my professional capacity, i could have given the boys at Gaydon a ring!
Many thanks Alex  Another member of the failed FL2 clutch/DMF club, twice.

A couple of years ago I had a restarting issue occasionally. If I stopped the engine without removing the fob (say, in a traffic jam), it would sometimes not crank when pressing the start button again. I would have to remove and reinsert the keyfob and that would usually solve it. I've had more than one firmware update since and it hasn't been an issue for some time.
As with many similar bugs and glitches, firmware upgrades often sort it.

Today i hit the stop/start button while driving(very slowly) and the fob wouldn't release. Another member of the failed FL2 clutch/DMF club, twice.

I would hope not. If you'd have got the fob out the steering lock solenoid would have kicked in.
I would imagine that the road wheel rotation sensing has to see no rotation at all before you can release the fob - as a safely measure.

Nope, i was stationary at the time. Took several attemps to get the fob out. Another member of the failed FL2 clutch/DMF club, twice.

I see. I read it as though you were still moving.
Have you tried the same experiment with another keyfob? It sounds more like the software was possibly struggling with the fact that the engine was stopped while rolling and took a while to enable keyfob release. Could be a bug - again firmware upgrade might be necessary.