From what we know, the PQ35 platform doesn’t transmit gearbox oil temperature over the native stream. VCDS can read the temperature, but that is a completely separate communication protocol for the service tool.
You can’t read the 0x390 frame, because that is a frame sent by EMU. This is a gateway frame that EMU is sending when emulation is enabled. You can confirm that by disabling the emulation in the EMU software.
yep, no oil temp in the can by default only if you request it specifically.
There’s an m14x1.5 plug on the gearbox near the heat exchanger you can use as an analog sensor bung instead
If you want to examine the CAN frames sent by the TCM, this is what I suggest:
Connect to the HS CAN and log. I use SavvyCan and you can export the Frame details as a separate log and then use RegEx (or copy/paste) to make a list of the unique CAN-IDs.
Then, disconnect the TCM and power everything back up to log a second time. Make a second list and diff them to find your TCM frame IDs.
Open the first log back up and isolate the frames with your TCM data. Sometimes, I export these frames to a separate log. However, I find that doing so seems to skew my ability to correlate the data to real world events because I don’t find the timestamp function to be accurate or particularly useful in SavvyCan so I use the frame count itself to sequence real world events to the frame data.
I mention this because I was told that the transmission oil temperature is not included in the native stream for the Aisin TF80-SC but I have found an ID containing continual growth sequence between minimum and normal oil temps for the transmission and I highly suspect that this is what it is.
