Thread: vague auto cruise control in d2

I am running the latest version of the software but could not record unless I had an external power source connected to the usb adaptor on the right hand side of the unit.

You picked a good time to pass through, its looking really nice here at the minute, could do with a rain here shortly though, ( I'm a farmer!) hope you're enjoying your travels.


cheers james

I wouldn't mind comparing autobox logs with if you manage to get it going,
mine seems to go almost straight from third to fourth lockup, its quite noticeable as you drive along and the engine drops so many revs so quickly.

cheers james

Originally Posted by OffTrack

The LR Topix site also has diagnostic flows for all the P codes although most are obviously V8 specific.

cheers
Paul

Do you have a subscription to topix? If so, any chance you could look up the same information for a code for my V8 LR3/D3 ? I'm getting an intermittent code P0026. Everything seems to point to VVT solenoid, but I'm curious if there is any addtional troubleshooting from Land Rover.

Thanks! (and sorry to hijack the thread for a bit)

Originally Posted by jafir

Do you have a subscription to topix? If so, any chance you could look up the same information for a code for my V8 LR3/D3 ? I'm getting an intermittent code P0026. Everything seems to point to VVT solenoid, but I'm curious if there is any addtional troubleshooting from Land Rover.

Thanks! (and sorry to hijack the thread for a bit)

I just buy single model, single year 24hr hour access when needed. It will cost you about $12. You can also purchase 1 hour access blocks for about $7-8.

Originally Posted by shack

I wouldn't mind comparing autobox logs with if you manage to get it going,
mine seems to go almost straight from third to fourth lockup, its quite noticeable as you drive along and the engine drops so many revs so quickly.

cheers james

The recording issues appear to be known bug that a few people have verified, and isn't related to powering as far as I can tell. I can connect to the ECU and monitor the values on screen without any dramas. The problem is that when you click the save icon then try to enter a filename the onscreen keyboard doesn't work correctly. The "keyboard" responds as if the previous screens buttons are active behind the keyboard display, so if you tap in the correct places the OK, Cancel, and file browser break through the keyboard. It's a bit weird, but BBS aren't going to look into it until they get the D3/D4/RRS support released. Reported it just before xmas 2012, I'm hoping BBS might release a fix before xmas 2013 but not holding my breath.

As far as I'm aware it only causes problems on the Autobox > Inputs > General and SLABS > Inputs > ABS Inputs save screens.

Have you updated to v1.12 since you got the Nanocom? BBS don't ship the Nanocom's with the latest firmware installed, so unlikely to be running the latest version out of the box.

cheers
Paul

Hi Paul

That's a useful work around kludge to know. Many thanks!!

I also managed to get the auto instrument recording going recently by selecting an existing file name and overwriting that, however it was fussy about which csv file I selected.

I can understand Black Box delaying new feature additions to the firmware while they focus on a new vehicle module, but it would be nice if known bugs were still rectified at least in a semi periodic manner or a workaround provided.

Cheers
Steve

PS I dimly seem to recall that the bug surfaced in the V1.12 firmware but could be wrong.

Originally Posted by Rok_Dr

Hi Paul

That's a useful work around kludge to know. Many thanks!!

I also managed to get the auto instrument recording going recently by selecting an existing file name and overwriting that, however it was fussy about which csv file I selected.

I can understand Black Box delaying new feature additions to the firmware while they focus on a new vehicle module, but it would be nice if known bugs were still rectified at least in a semi periodic manner or a workaround provided.

Cheers
Steve

PS I dimly seem to recall that the bug surfaced in the V1.12 firmware but could be wrong.

Steve,

I'm pretty sure it appeared in V1.12 too. That was why I asked the question about firmware versions.

Thanks for the tip re using existing files. I guess you could create a blank file on the card before trying to record. I noticed yesterday when I was double checking after reinstalling the firmware that you could pick existing files when I accidentally tapped on one in the keyboard screen. I hadn't followed that through any further.

cheers
Paul