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?
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?
Datatek
Well-Known Member
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.
Datatek
Well-Known Member
That is also a possibility, mine has cruise so not the same.
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?
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.
tomcat59alan
Well-Known Member
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? No, no difference but not worried as I think that it is working normally.
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.
My tractor has done double the miles yours has and will still be running when your liners drop onto the tarmac and the pistons bevel our bonnet!
My tractor has done double the miles yours has and will still be running when your liners drop onto the tarmac and the pistons bevel our bonnet!
I hope so!
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?
tomcat59alan
Well-Known Member
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.
Rangeroverbass
Member
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?
The first box top left should be 8 all the rest should be 128.
Rangeroverbass
Member
Would this be causing any issues do you think? I'll set it to what you say today see what happens
