Pages: [1]
Author Topic: EGT Sensor Reading with diagnostics disabled.  (Read 4405 times)
BoobieTrap
Full Member
***

Karma: +3/-0
Offline Offline

Posts: 74


« on: October 25, 2017, 12:01:58 AM »

I have converted my 1.8t narrowband to wideband, originally disabling ECU EGT in the ECU and running an EGT gauge inside the car (with an audible alarm when EGT>900).
I have recently upgraded to a GTX30 and the manifold came with an EGT sensor, so I have wired it in, 12V, 0V and ECU pin 61.

Initially I just want to check how ECU EGT sensor compares to my gauge (they are both located in the manifold). However, when logging tats_w, I get a constant 1,110C. I initially assumed that leaving EGT sensor disabled in the ECU will prevent any fault codes/limp modes etc but still provide me with a valid EGT reading but I see now that it may not be the case.

Am I right in assuming that leaving CDATR, CDATS, CATR disabled and only enabling EGT only via ESKONF will give me valid EGT readings via tats_w? Or should it work regardless and my EGT sensor is toast?
Logged
TijnCU
Hero Member
*****

Karma: +60/-4
Offline Offline

Posts: 690


flying brick


« Reply #1 on: October 25, 2017, 02:36:06 AM »

The oem egt sensor comes with a seperate controller. I assume that you can not wire any generic sensor to this pin for correct readings. Can you elaborate on the type of sensor you are trying to use?
Logged

BoobieTrap
Full Member
***

Karma: +3/-0
Offline Offline

Posts: 74


« Reply #2 on: October 25, 2017, 03:26:18 AM »

Sorry, should have said that I used OEM Audi EGT sensor 06a919529, which came with the controller. I got it second hand so I don't know if it actually works, hence I wanted to check if it gives good readings before enabling all the diagnostics for it in the ECU.
I am using 06A906032HJ ECU which I crossflashed with Audi TT BAM hex file. When I converted to this wideband ECU, I have originally disabled EGT, VVT, Rear o2, CAT etc, and now I am trying to re-introduce the EGT sensor but I need to check that the sensor/controller works correctly first.

Logged
TijnCU
Hero Member
*****

Karma: +60/-4
Offline Offline

Posts: 690


flying brick


« Reply #3 on: October 25, 2017, 05:20:00 AM »

Another possibility is that your HJ ecu does not read on that EGT pin.
Logged

BoobieTrap
Full Member
***

Karma: +3/-0
Offline Offline

Posts: 74


« Reply #4 on: October 25, 2017, 05:36:53 AM »

It's possible, however, I know that that pin is related to heating/cooling in some way. The APX narrowband ECU uses that pin (61) for Air Con pressure switch, and before I realized this I had the fans behaving erratically on start up (constantly going ON and OFF) on the wideband ECU. Once I disconnected the pin and connected it to the EGT controller, the fans started behaving correctly.

I guess what I am asking is whether enabling EGT via ESKONF but disabling the EGT diagnostics via CDATR, CDATS and CATR should result in correct EGT readings being logged via ME7logger?
Logged
fknbrkn
Hero Member
*****

Karma: +185/-23
Offline Offline

Posts: 1454


mk4 1.8T AUM


« Reply #5 on: October 26, 2017, 12:28:19 AM »

y no enable ATR and test?
5min talking
Logged
BoobieTrap
Full Member
***

Karma: +3/-0
Offline Offline

Posts: 74


« Reply #6 on: October 26, 2017, 12:59:09 AM »

Because I am still tweaking MLHFM/KFLF as I've hit ps_w limit and I don't want EGT limp mode to be interfering until I've sorted it.
I think I will just have to wait until I'm happy with those before checking/enabling all EGR functionality.
Logged
prj
Hero Member
*****

Karma: +1072/-480
Offline Offline

Posts: 6035


« Reply #7 on: October 26, 2017, 04:10:21 AM »

The sensor is damaged. Even with the keyword disabled it should still read.
Logged

PM's will not be answered, so don't even try.
Log your car properly - WinOLS database - Tools/patches
BoobieTrap
Full Member
***

Karma: +3/-0
Offline Offline

Posts: 74


« Reply #8 on: October 26, 2017, 04:28:34 AM »

That's useful, thank you.
Do you know if there is a way to bench test the sensor+controller?
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.024 seconds with 16 queries. (Pretty URLs adds 0s, 0q)