CVT Temp

[Spunkster]

With everything plugged in and the ignition in the on position, go to the Help menu and click on “send feedback”. Include a detailed description of the issue.

[scofield]

With everything plugged in and the ignition in the on position, go to the Help menu and click on “send feedback”. Include a detailed description of the issue.

send feedback done

[Spunkster]

Torque it never had and will never have as that is a Type R channel. For the temps please post the calibration used and a datalog showing the issue.

[scofield]

Torque it never had and will never have as that is a Type R channel. For the temps please post the calibration used and a datalog showing the issue.

Is this expected behavior? I can actually see the Torque info on the Hondata mobile app, but it is still not showing up in FlashPro Manager.

[scofield]

Torque it never had and will never have as that is a Type R channel. For the temps please post the calibration used and a datalog showing the issue.

lease check the attached calibration (.cal) and datalog (.fpd) files.
The CVT temperature reading appears to be incorrect. After driving for over 10 minutes, while the ECT (Engine Coolant Temp) fluctuated between 8x°C to 100°C, the CVT temp stayed stuck at 74°C without any variation.
I checked other logs where CVT temp was displayed, and the reading stayed static there as well. This doesn't seem normal or realistic. Could you please take a look?

0920a.fpcal

datalog0001.fpdl

[Spunkster]

Record a datalog from a cold start and make sure it records driving and getting up to full temp then post here.

[scofield]

Record a datalog from a cold start and make sure it records driving and getting up to full temp then post here.

Please reference the attached logs regarding the CVT temperature issue.
As shown in the logs, while the ECT rises from start to end, the CVT temp in FlashPro log record at 39°C without any change. However, the Hondata Mobile App clearly showed the CVT temp changing up to 64°C during the same run.

Note: Due to the long-log download failure issue mentioned earlier, I separated this recording into two shorter log files for your review.

datalog0000.fpdl

datalog0001.fpdl