Thread: Puma 2.2 random oil temp reading

My nanocom does the same.

Mine does the Same. Must be a bug!
Lindsay.

Does anyone out there with a code reader get an believable/normal oil temp reading?

Marty90 & Oldyella 76 do you have similar vintage to my 2012 model?
I'm wondering if we are unlucky or if we got a bad batch of senders or something? Keen to get to the bottom of it!!

Mine's a 2013. I'd be interested to know what you find.I assumed it was the nanocom.

Yep mine is a 2012 model.
Lindsay.

Hiya All

Thanks to Marty90 for pointing me to this thread on the new CSV viewer thread.

http://www.aulro.com/afvb/showthread.php?p=2511383

Unfortunately, like all diagnostic systems that connect via the OBDII socket, the Nanocom cannot directly read any sensor value.

All it can do is send a numerical request (Parameter ID or PID) to the vehicles ECU that the sensor is connected to and if the PID is supported by the ECU, it will send back a numerical value that then has to be converted. Of course knowing what PID Number is for what information and how to convert the resultant reply into an understandable value such as Volts, RPM, MPH or KPH, Centigrade, Degrees or Percentage requires quite a lot of figuring out.

To create a live display of any given Parameter(s) such as the instrument mode, you simply create a repetative loop that re requests the PID from the Vehicle ECU and displays the converted result on the screen.

However, it is possible to start requesting PID's at a rate that the ECU cannot quite keep up with and so sometimes it can reply with incorrect values or not reply at all which causes a communication loss error.
If a sensor really were faulty the Vehicle ECU would more likely log a Fault Code.

As a part of our preparation for the imminant release of the new CSV viewer, and our continued striving to improve our software, we have substantially re worked and standardised the code and timings involved that provides this display for all CAN BUS ECU's like the Puma Defender, including adding new Parameters and hope that this may well result in the Puma EMS ECU.

At the very least it will provide a new ability to record the data and determine differences between regular values and such abnormal ones and easily send us CSV files showing any such problems.

Hi Colin,
Thanks for the information. Unfortunately ,I'm not as computer literate as many others on the forum so I'm not any the wiser as to how to rectify the problem. From what you're saying, if I'm reading it correctly, the sensor is likely not to be the problem and the problem seems to be a communication fault between the vehicles ECU and the Nanocom. Am I correct in that there is to be a software update to rectify this. When I purchased the Nanocom I had a fault code stating"too many codes to read".When I contacted your office I was directed to the forum where the solution was to download the latest software update,but because I have an apple I first had to download an app to allow this to happen. Unsurprisingly, this didn't work.Looking at your other thread I see there's another update due to be released.If this is the case,I'd rather send the unit back to you for the updates.

"However, it is possible to start requesting PID's at a rate that the ECU cannot quite keep up with and so sometimes it can reply with incorrect values or not reply at all which causes a communication loss error.
If a sensor really were faulty the Vehicle ECU would more likely log a Fault Code."

Hi Colin,

Thanks for the reply. Mine was logging at P0198 "Oil Temp high intermittent"
That apparently relates to a short in the circuit or a faulty sensor. Is it possible this code is being generated by the Nanocom trying to read it and the ECU not being able to or do I actually have a short or sensor problem?

Thanks

J