sr20

ah right @confused got you! Sounds like a plan @adamw, will give that a go and post back Thanks both!

Thanks sir, yes I see it, screenshot attached, and at 4.96v the oil temp reads zero, so as you mentioned in an earlier thread I think in addition to diagnosis I need to reverse the error high/low values too

Ok I finally managed to capture the error, it happened twice today, once on the outbound journey, once on the return so seems to be becoming more prevalent, ambient temperature outside about 21C, log uploaded, let me know if you need anything else! Thanks! PC Datalog - 2023-07-23 12;12;15 pm.zip

Thanks for the response, actually just the opposite, the first time we saw this it was an unusually hot month here in the UK, I think it was 33C on the day we got it, and all other times its been a very hot ambient temperature too, that said we have driven it on even hotter days and never got the errors. I guess my concern is If the configuration is wrong that doesn't really explain why we have only just started getting the errors after 2 years of perfect operation

Done! thanks for reminding me! savedtune.pclx

Many thanks for your prompt response and apologies for not replying sooner, I've been trying to capture the errors as they are happening in a live log but haven't been able to reproduce them so attached is a log captured after I started seeing the errors (albeit the errors didn't actually occur during this logging session) Also attached are some screenshots of the IAT temp and oil temp ECU settings showing the high and low values (captured today - engine wasn't running)

Had the ECU for a couple of years, everything has been fine but very recently started seeing the engine management light coming on whilst driving which relates to these codes Sporadically I see the IAT temp high error and then some days later the oil temp high error, nothing has changed on the ECU, some days of driving though we see no errors at all We clear the code during the drive and it never comes back on that drive, car running perfectly, then on the next drive we may get one or the other code which we clear and again doesn't come back on that drive When we look at current temps after the event, everything looks fine and within error high values Anything to be concerned about? Thanks in advance PS can attach recent logs but have never managed to catch the error during a logging session

Yes really hoping this is implemented in the software, the logging is actually very rich but am coming to Link from Nistune which had the ability to use gauges with log playback which as mentioned is really useful so assumed it was possible to do the same in PCLink, is it possible to request this as a feature request?