BECM setting for Cruise = Not Set. Always has been.

That cruise error has always been there, although now I think about it I cannot remember if the rpm and water temp ones have or not. Doesn't matter how many times I clear the fault, engine running or not, go back in and there it is.

Then look to Keiths scenario. The Nanocom is sometimes to cleaver for it's own good and will have you chasing shadows. At what period in it's operation is the engine doing 33 RPM?
 
BECM setting for Cruise = Not Set. Always has been.

That cruise error has always been there, although now I think about it I cannot remember if the rpm and water temp ones have or not. Doesn't matter how many times I clear the fault, engine running or not, go back in and there it is.
Try setting cruise, shut down the Nanocom and the BECM, then go and change it back to Not Set. Sometimes there can be strange outputs from memory chips, re-writing the info can cure it.
 
That's what I figured, hence why I've always ignored it in the past. :)

I think this is where I came in!
 
Try setting cruise, shut down the Nanocom and the BECM, then go and change it back to Not Set. Sometimes there can be strange outputs from memory chips, re-writing the info can cure it.

OK. Will give it a go when I get back. I kind of assumed it happened to everyone without cruise control or maybe without and with lowline BECM.
 
Incidentally, some time back there was another thread where I mentioned my BECM was set to Late EDC and I was surprised given it was an early 1995 car. Rick-the-Pick said it depended on what the engine was monitoring. Well, I tried setting it to Early EDC but then it wouldn't start so switched it back. Meant to update the other thread but had lost it.

Makes you wonder when it switched to Late EDC. Started P38 production in 1994? Wonder if you can tell from the chassis number which number yours was off the production line?
 
Incidentally, some time back there was another thread where I mentioned my BECM was set to Late EDC and I was surprised given it was an early 1995 car. Rick-the-Pick said it depended on what the engine was monitoring. Well, I tried setting it to Early EDC but then it wouldn't start so switched it back. Meant to update the other thread but had lost it.

Makes you wonder when it switched to Late EDC. Started P38 production in 1994? Wonder if you can tell from the chassis number which number yours was off the production line?

You and that Nanocom are like a bloody kid playing with a live grenade. One day the pin will fall out. :D:D
 
I'm saving this thread so I can be ready with an "I told you so" when the car goes pop!

IIRC Jules, your Nanocom says my cruise is not set, when I do have it fitted.

I've switched it on and off and it didn't seem to make any difference.
 
Last edited:
You and that Nanocom are like a bloody kid playing with a live grenade. One day the pin will fall out.

:) Have to try to learn. Burnt hand teaches best, as they say. Besides, what could possibly go wrong with the guiding hands of Wammers and Datatek leading me?

Try setting cruise, shut down the Nanocom and the BECM, then go and change it back to Not Set. Sometimes there can be strange outputs from memory chips, re-writing the info can cure it.

No, no difference but not worried as I think that it is working normally.

IIRC Jules, your Nanocom says my cruise is not set, when I do have it fitted.
I've switched it on and off and it didn't seem to make any difference.

That's odd. Maybe worth raising with BBox then. May already be; not checked for an update for a while.

Think we're done here. No unusual faults. Timing modulation is varying too much and is way too high indicating worn chain / sprockets on lower chain. Only other option is timing electronics itself is getting cranky. Job done.
 
Incidentally, I've noticed that when you look at the reading in live time the timing modulation variation is only a few percent, much as the manual suggests. It is only when you record a trace over a reasonable time that the higher variation is apparent. I'm not sure these extreme readings are entirely reliable.
 
Incidentally, I've noticed that when you look at the reading in live time the timing modulation variation is only a few percent, much as the manual suggests. It is only when you record a trace over a reasonable time that the higher variation is apparent. I'm not sure these extreme readings are entirely reliable.

Are you driving around and recording these traces. What part of baselines are read at IDLE with an HOT engine do you not understand?
 
No, done at idle on a warm engine.

I was just making the point that characteristics were different depending on the manner in which you were measuring it. I think that's worth knowing.
 
No, done at idle on a warm engine.

I was just making the point that characteristics were different depending on the manner in which you were measuring it. I think that's worth knowing.

The distance between two points can vary greatly depending how far you stretch your elastic tape measure. Just take the visual readings from the Nanocom. Anything else has you asking silly questions. :D:D:D
 
Go into settings you will see a lot of boxes with numbers in them. DO NOT change any other value other than the idle speed setting if it is needed. That should be 128. Change only by one or two points. Lower number lowers idle speed, higher number raises idle speed. Think you had better read the instructions again it is all explained in there. Personally at 82% i would be checking chains for wear if one snaps you are up ****s creek without a paddle. If pump modulation is up at 82% cam timing will also be out. If bottom chain is worn enough to give 82% on modulation top chain that drives cam will also likely be on its way home.
Wammers on. Mine when I go into this I have lots of boxes but there's no value in any except the idle which is 128.is this how it should be?
 

Similar threads