Disco 2 dies W/ODB2 error

[bmxer06pa]

My 2000 D2 has recently started to just die. I drove it to the store and when I came out it wouldn't start. After cranking for about 10-15 mins it fired right up and I was able to drive it almost all the way home. Just as i entered my neighborhood it died with no warning. It didnt run rough, it just died. I towed it home let it sit for a day or two and it started right up. It idled for about 15 mins before it shut off again.
Every time it has died/won't start I get an error on my ultragauge. The engine temp and intake temp fields display error. I unplugged the ultra gauge and plugged it back in and it was unable to find the vehicle. After a small wait it found the vehicle then my truck would start again.
Through searching I would guess it is a ckps, but I haven't seen much info on the ODB2 issue. Have any of you guys had a similar issue to this?

 

[Dane!]

Just swap the crank sensor first. I feel that's the cause of the running issues.

 

[KyleT]

Check the ground by the coolant bottle by the fender and fuse box.

 

[dcarr1971]

Hey Doug, The other guys have you covered for the serious issue, so let me just say this...my Ultragauge has done the same thing a few times when both my D1 and D2 have failed to start.

I suspect that it's caused by the device running into comm errors over the OBD2 port when it is powered on and the ignition is turned but the truck doesn't actually succeed in starting. (i.e.- It's detecting/reading sensor data in a specific order, if those sensors fail to provide that data to the Ultragauge, it errors them out and continues on. Given the nature of the device, it isn't terribly sophisticated, and doesn't go back to re-test those sensors later...)

Generally it comes right back if I shut the truck off and then successfully restart it or even just turn the key to 'run' and let the gauge fully initialize/boot. (I have had to completely unplug it from the OBD2 port once or twice to let it completely re-initialize as you described above.) I guess what I'm trying to say is that it's nothing to get too excited about, and probably not indicative of a failure of your OBD2 port or ECU...