I have a portable digital oscilloscope. Does any one know what should be the wave pattern that I should be looking for on the crank sensor?
Volt amplitude?
 
I have a portable digital oscilloscope. Does any one know what should be the wave pattern that I should be looking for on the crank sensor?
Volt amplitude?

I think the sensor just transmits a pulse three times per revolution. The ECU then drives the rev counter. Rev counter should not move when engine is being cranked.
 
Can anyone please help me understand what I did wrong when contacting BBS?

Hi,

I just bought a Nanocom Evolution and I'm trying to read and interpret the faults ridden on a P38 EDC.

I have this fault,

NANOCOM - EDC.APP - EDC faults file

ENGINE SPEED SENSOR INVALID VALUE
Type: INVALID FAULT,MAJOR FAULT,LOGGED,CURRENT,INTERMITTENT
RPM = 0
WATER TEMP = 193
OCCURRANCE = 14
---


That water temp read here is in what scale?
The value occurrence is the number of times this fault has occurred?
The water temp read at this time was: +/- 5ºC

NANOCOM - EDC.APP - EDC inputs GEN file

Water temperature;Air temperature;Boost pressure(kpa);Ambient pressure(kpa);Throttle potentiometer(%);Throttle potentiometer(v);Battery(V);Low Idle value;Cruise status
5.32;20.28;101.19;101.19;0.00;0.4;11.64;819.00;CRUISE ON
4.63;20.28;101.19;101.19;0.00;0.4;11.64;819.00;CRUISE ON


Best regards

Good afternoon

Please go to this link and here you wil find all the ECU Help guides that
have been written to assist customers understanding of the readings

:: Download - Nanocom ::

Kind Regards

Ron Blakey

I already read the EDC document and could not found any details on the faults read. besides the TYPE.
This is why I'm asking for help on details.

Hello

We have equipment that Reads the fault which the ECU manufacturer puts as
a code number and we have a meaning of the fault, we display this on our
equipment as Text.

Other than that information we cannot offer further explanations on what
is causing the fault. Our role is to supply diagnostic equipment and
support issues with the hardware and/or software that we provide. We do
not manufacture the ECU's nor do we program the faults that are triggered.

You need to use other reference material such as Land Rovers Rave or GTR
site for such information

Kind Regards

Ron Blakey



> I already read the EDC document and could not found any details on the
faults read. besides the TYPE.
> This is why I'm asking for help on details.

Hi, Ron,

Clearly I did not explained myself clearly.

I gave as an example the following fault:

---------------------------------------------------------------------------------------------------------
NANOCOM - EDC.APP - EDC faults file

ENGINE SPEED SENSOR INVALID VALUE
Type: INVALID FAULT,MAJOR FAULT,LOGGED,CURRENT,INTERMITTENT
RPM = 0
WATER TEMP = 193
OCCURRANCE = 14
------------------------------------------------------------------------------------------------------------

And what I want to know is:

That "WATER TEMP" read here is in what scale? The water temp read in live data at this time was: +/- 5ºC.
The value "OCCURRANCE" is the number of times this fault has occurred?

Only BBS can give me that information because, has you said, your equipment translate into text the error codes given by the ECU.
I think my question is very pertinent because your P38 EDC document is very vague on this matter and has no example explaining it. That should be helpful.

Regards

Good morning

I understood you perfectly well thank you. What you fail to understand is
that the information we provide as text is derived from the code given by
the manufacturer of the ECU. if they do not provide the information on
what the values are, we also cannot provide them despite your thinking and
the fact that you believe the documentation is vague.

As explained, you need to use other resources to find out HOW you vehicle
works. We are not here to teach you that.

As to your 2 "pertinent" questions, as the boiling point of water is
98.98C and you are getting a reading of WATER TEMP = 193 this would be
common sense to realise that this has to be in fact Fahrenheit despite the
ECU manufacturer not stipulating this. if it were Degrees Celsius then you
would have an extremely serious overheating issue with your vehicle.

As for the question on Occurrences, again common sense would dictate that
this is the number of times the fault has occurred.

Once again I reiterate, we do not write the programming for the ECU's nor
do we repair vehicles.

Regards

Ron Blakey

What did I do wrong?
 
Can be seen as a little unhelpful from BBS....

But as he says, all their unit does is read information stored on the ECU and presents it as text....BBS no not what the results/information presented is/means all their job to do was to display this to the user....

But I would have thought a more helpful and less abrupt response would have been nice from them though!....
 
You are not listening that is what you are doing wrong. You have rev counter jumping on crank. That is not supposed to happen. You have glow warning lamp coming on when cold but obviously no power to glow plugs at times. Just because the ECU lights the glow lamp does not mean there is power to the delay relay. Glow lamp and switching power to delay relay are two separate circuits. Have you checked that there is actually power to the glow plugs when lamp is lit? You have ridiculous temp readings. All these things are computed and controlled by the ECU. Maybe, just maybe, you have a faulty ECU. I would start thinking along those lines.
 
Last edited:
They do not sell 20quid toasters. :frusty:

Common sense... common sense is not very common is it?
My common sense is built by my own ambient, experience, and academic knowledge. It is normal that my own judgment differs from a plumber or a NASA engineer. Common sense is not very common is it?:confused:
 
I don't think that the water temp is in Fahrenheit. I think that it's a decimal issue and is 19.3 C - around ambient on one of our better days.

G~
 
You are not listening that is what you are doing wrong. You have rev counter jumping on crank. That is not supposed to happen. You have glow warning lamp coming on when cold but obviously no power to glow plugs at times. Just because the ECU lights the glow lamp does not mean there is power to the delay relay. Glow lamp and switching power to delay relay are two separate circuits. Have you checked that there is actually power to the glow plugs when lamp is lit? You have ridiculous temp readings. All these things are computed and controlled by the ECU. Maybe, just maybe, you have a faulty ECU. I would start thinking along those lines.

I will monitor power at glow plugs, but I must say that I have the same problem when hot also. Yesterday, everytime I started the engine it was a pain and 2 of them were when hot.
Why do you say my temperature readings are high?
I've been monitoring water temp using nanocom live data and it seems normal.

Here is a recorded reading:

NANOCOM - EDC.APP - EDC inputs GEN file

Water temperature;Air temperature;Boost pressure(kpa);Ambient pressure(kpa);Throttle potentiometer(%);Throttle potentiometer(v);Battery(V);Low Idle value;Cruise status
10.07;14.84;100.05;100.05;0.00;0.4;13.32;;CRUISE ON
14.84;14.84;100.05;100.05;0.00;0.4;13.32;750.75;CRUISE ON
14.84;14.84;100.05;100.05;0.00;0.4;13.32;750.75;CRUISE ON
15.52;14.84;100.05;100.05;0.00;0.4;13.32;750.75;CRUISE ON
16.87;14.84;100.05;100.05;0.00;0.4;13.32;750.75;CRUISE ON
16.87;14.84;100.05;100.05;0.00;0.4;13.32;750.75;CRUISE ON
17.55;14.84;100.05;100.05;0.00;0.4;13.32;750.75;CRUISE ON
18.23;14.84;100.05;100.05;0.00;0.4;13.32;750.75;CRUISE ON
18.92;14.84;100.05;100.05;0.00;0.4;13.32;750.75;CRUISE ON
19.60;14.84;100.05;100.05;0.00;0.4;13.32;750.75;CRUISE ON
19.60;14.84;100.05;100.05;0.00;0.8;13.32;750.75;CRUISE ON
20.28;14.84;103.46;100.05;24.56;1.1;13.32;750.75;CRUISE ON
20.95;15.52;110.28;100.05;24.56;1.1;13.32;750.75;CRUISE ON
20.95;15.52;103.46;100.05;0.00;0.4;13.32;750.75;CRUISE ON
21.63;15.52;101.19;101.19;0.00;0.4;13.32;750.75;CRUISE ON
22.31;15.52;101.19;101.19;0.00;0.4;13.32;750.75;CRUISE ON
23.00;15.52;101.19;101.19;0.00;0.4;13.32;750.75;CRUISE ON
23.68;15.52;101.19;101.19;0.00;0.4;13.32;750.75;CRUISE ON
24.36;15.52;101.19;101.19;0.00;0.4;13.32;750.75;CRUISE ON
25.04;15.52;101.19;101.19;0.00;0.4;13.32;750.75;CRUISE ON
25.71;15.52;101.19;101.19;0.00;0.4;13.32;750.75;CRUISE ON

10ºC seems pretty normal isn't it?

That water "WATER TEMP = 193" being in Fahrenheit i suspect it is wrong. It would not be the first bug found in nanocom!
Live data shows normal values to me. What do you think? I can document it better if needed.
 
I don't think that the water temp is in Fahrenheit. I think that it's a decimal issue and is 19.3 C - around ambient on one of our better days.

G~

I guess the only way will be to build a table and cross the live data temp with the fault reading temp.
 
Can be seen as a little unhelpful from BBS....

But as he says, all their unit does is read information stored on the ECU and presents it as text....BBS no not what the results/information presented is/means all their job to do was to display this to the user....

But I would have thought a more helpful and less abrupt response would have been nice from them though!....

Hi!

I really don´t found very "professional" (for what I understand) BBS did not answer what "units" is the water temp.
This was a simple question.
And sorry, I don´t believe they just "copy- past" the soft, and did not try to understand the readings (and confirm).... (perhaps its just me who is seeing wrong).


I think this kind of help, is what makes for example people from rr.net (USA) not to be happy with them, and do not advise to buy BBS.

But, I understand in other way they provide a tool, and are not mechanics.

rfsimoes, the next time the RR do not start, try this.
put in 1º or 2 second gear, and try to start the engine (be careful of course), just I little "touch", and then try again.
This is a tip that I friend of mine give to me, (when my other car start to have the same problem, more in hot).
Don´t know/understand why, but works until the crank sensor was replaced ....
 
I will monitor power at glow plugs, but I must say that I have the same problem when hot also. Yesterday, everytime I started the engine it was a pain and 2 of them were when hot.
Why do you say my temperature readings are high?
I've been monitoring water temp using nanocom live data and it seems normal.

Here is a recorded reading:



10ºC seems pretty normal isn't it?

That water "WATER TEMP = 193" being in Fahrenheit i suspect it is wrong. It would not be the first bug found in nanocom!
Live data shows normal values to me. What do you think? I can document it better if needed.

Since when have Germans who made the ECU used F as a temp value. I maybe wrong but everything is pointing to glitches in the ECU. Usually if intermittent caused by poor connections either in the ECU or to sensors. If the live data is showing sensible readings then at the time of the fault logging something has either lost signal or the ECU has glitched. You have to find out which one of those is causing your problems.
 
Last edited:
Hi!

I really don´t found very "professional" (for what I understand) BBS did not answer what "units" is the water temp.
This was a simple question.
And sorry, I don´t believe they just "copy- past" the soft, and did not try to understand the readings (and confirm).... (perhaps its just me who is seeing wrong).


I think this kind of help, is what makes for example people from rr.net (USA) not to be happy with them, and do not advise to buy BBS.

But, I understand in other way they provide a tool, and are not mechanics.

rfsimoes, the next time the RR do not start, try this.
put in 1º or 2 second gear, and try to start the engine (be careful of course), just I little "touch", and then try again.
This is a tip that I friend of mine give to me, (when my other car start to have the same problem, more in hot).
Don´t know/understand why, but works until the crank sensor was replaced ....

If it's an auto and the engine cranks in 1st or 2nd gear you have yet another problem. :)
 
You may find the temp reading is not a physical value at all and more a Data value...i.e 0-255 ..... 0 being Hot and 255 being Cold or vice versa

If you consider the Temp gauge on the dash reads 0-50 in the first third, 51-100 in the second third and 101-150 in the last third....

with some maths you could see if the 193 data value has credit!
 
You may find the temp reading is not a physical value at all and more a Data value...i.e 0-255 ..... 0 being Hot and 255 being Cold or vice versa

If you consider the Temp gauge on the dash reads 0-50 in the first third, 51-100 in the second third and 101-150 in the last third....

with some maths you could see if the 193 data value has credit!

So, open circuit should show one end of the scale and a short the opositor end. If I sort tais out, that prat is going to listen some good ones...
 
You may find the temp reading is not a physical value at all and more a Data value...i.e 0-255 ..... 0 being Hot and 255 being Cold or vice versa

If you consider the Temp gauge on the dash reads 0-50 in the first third, 51-100 in the second third and 101-150 in the last third....

with some maths you could see if the 193 data value has credit!
Exactly right, the reading is not Centograde or Farenheight, it's a decimal number converted form the Hexadecimal output of the A to D convertor, and as Saint rightly says 0 represents too fecking hot and 255 represents very cold.:) don't waste your time on maths, the output of the sensor is not linear.
 
Exactly right, the reading is not Centograde or Farenheight, it's a decimal number converted form the Hexadecimal output of the A to D convertor, and as Saint rightly says 0 represents too fecking hot and 255 represents very cold.:) don't waste your time on maths, the output of the sensor is not linear.
Bloody non-linear log10 based or something equally complex really screws with my theory...but atleast we know now :D
 

Similar threads