[BB_cuda]

I had to reload the app as the old one had stopped working all together. This was the pro version. Anyone seen where units of °C where really more indicative of °F?

I test drove the 335D first. I got reasonable coolant temps of ~82°C but the EGT #1 temp seemed high. Under hard throttle, its showing upwards of 594-599°C. Yikes. That would be a more reasonable value of 599°F. 599F converts to 315C. I should mention my tune is JR 2.0 race.

I then switched over to our recently purchased and deleted 2013 X5D. Tune is JR 2.8. I got almost same result for the EGT#1 parameter under hard throttle. After chilling out and letting things cool off, at idle we see around 125°C.

The rpm matches the tach, oil temp is not too far off the coolant temp. I'm just seeing wrong units (my opinion anyway) for the EGT #1.

Thoughts please. My old version of the carly app had correct units and was in never any higher than 340°C for EGT #1. thanks

[TDIwyse]

Originally Posted by BB_cuda

I had to reload the app as the old one had stopped working all together. This was the pro version. Anyone seen where units of °C where really more indicative of °F?

I test drove the 335D first. I got reasonable coolant temps of ~82°C but the EGT #1 temp seemed high. Under hard throttle, its showing upwards of 594-599°C. Yikes. That would be a more reasonable value of 599°F. 599F converts to 315C. I should mention my tune is JR 2.0 race.

I then switched over to our recently purchased and deleted 2013 X5D. Tune is JR 2.8. I got almost same result for the EGT#1 parameter under hard throttle. After chilling out and letting things cool off, at idle we see around 125°C.

The rpm matches the tach, oil temp is not too far off the coolant temp. I'm just seeing wrong units (my opinion anyway) for the EGT #1.

Thoughts please. My old version of the carly app had correct units and was in never any higher than 340°C for EGT #1. thanks

I tried logging with iCarly a few times many years ago, but I found it too slow to be of much value ... but I did find an old log from early 2015 that had EGT data for some normal driving around and then a hard pull. I don't recall what I configured iCarly (BMWhat back then) for units, but the EGT's in this log are in F based on what I see in Torque and TestO. Showing graphs of a couple parameters (rpm, boost, egt).

[dixy2k]

The app is pretty unstable.
It often gets a bunch of errors with the values. You would think you are somewhere in space and pilot an interstellar spacecraft according to the values shown on the screen.

In the past it lost the parameters I set to monitor. Empty screen, had to reload them 3-4 times.

[BB_cuda]

Thanks TDI and dixy. TDI, your plot from many years ago showing close to 1000F when RPM spiked to ~4300 rpm. Was that with normal DPM still in operation? I just never recall seeing anything higher than like 350C in old version of Carly. Not in denial here but surprised. I will say the data observed is consistent for both the 335 and X5 M57s. I will go look again with the boost pressure set point but not today. We are getting freezing rain here pretty soon. H-town is shutting down.

[TDIwyse]

Originally Posted by BB_cuda

... TDI, your plot from many years ago showing close to 1000F when RPM spiked to ~4300 rpm. Was that with normal DPM still in operation? I just never recall seeing anything higher than like 350C in old version of Carly. Not in denial here but surprised. ...

Did you mean DPF?

This was from almost exactly 3 years ago, so this was with full deletes, but oem turbos, and at full fueling it was very smokey and low AFR's... Low AFR's will drive EGT's high on a diesel.

iCarly was only able to log one sample every 1.5-2 seconds, which is really poor...

Any reason you're not using Torque or TestO for watching parameters or logging data?

[BB_cuda]

Originally Posted by TDIwyse

Did you mean DPF?

This was from almost exactly 3 years ago, so this was with full deletes, but oem turbos, and at full fueling it was very smokey and low AFR's... Low AFR's will drive EGT's high on a diesel.

iCarly was only able to log one sample every 1.5-2 seconds, which is really poor...

Any reason you're not using Torque or TestO for watching parameters or logging data?

Not that it's a good reason but i don't have an Android product for Torque? I have an iphone.