Can "Core Temperature" be available as a Telemetry option

[0crap]

For logging purposes, on the Taranis radio, it would be nice to have Core Temperature available as a Telemetry option.

The Tmp1 sensor I can get now doesn't make sense.
Maybe replace that for Core Temperature?

[klutvott123]

Tmp1 is used for flight modes and arming status. The number 3 to the left is just a counter. The lua script uses it to detect if there's a telemetry connection, but it doesn't care about the values it contains. If it's used for something other than that i don't know. If it's for logging purposes, maybe it would make more sense to have the blackbox log it(maybe it's already capable of it, i don't know)?

[mikeller]

We can have both. debug_mode = ADC_INTERNAL will log the temperature into debug field 0. Also, we have more than one temperature slots available, we can send the core temperature in a free one.

[0crap]

Thx for the comments!

Didn't think of blackbox, I'll check that.
However it would be better to have it on Telemetry, that way you can also make nice alarms for high temp on the Taranis. (Using logical switches.)

I tried debug_mode = ADC_INTERNAL however that gives an error. (On MATEKF405 @ BF 3.5.4)
There is something like debug_mode = core_temp but that doesn't do anything with the "Tmp1" sensor.

[mikeller]

@0crap: Did you try set debug_mode = ADC_INTERNAL?

There is something like debug_mode = core_temp but that doesn't do anything with the "Tmp1" sensor.

debug_mode = core_temp is news to me. My suggestion about using a Tmp sensor for this was meant as 'we'd have to implement this first'.

[0crap]

@0crap: Did you try set debug_mode = ADC_INTERNAL?

There is something like debug_mode = core_temp but that doesn't do anything with the "Tmp1" sensor.

debug_mode = core_temp is news to me. My suggestion about using a Tmp sensor for this was meant as 'we'd have to implement this first'.

Ahhh, well since you and all devs have your hands full on getting 4.0 done, I'm not going to ask anything. :-)

[mikeller]

Drats. That got renamed between 3.5 and 4.0, and I was looking at 4.0.
set debug_mode = core_temp is what you want, the temperature value will be in debug field 0.

[0crap]

Perfect! I'm going to try that.
Usually debug_mode = gyro_scaled, for me to play with BB and Plasmatree.

I sure hope it will end up some day as a Telemetry sensor. 👍

[mikeller]

@0crap: Who knows, it's Christmas. ;-)

[mikeller]

Merry Christmas!

#7278:

[0crap]

Merry Christmas!

Fantastic looking picture with the Tmp1 sensor. 👍
For sure one to turn on for logging in the Taranis and make some nice Temp alarms.
Can't wait to test it out when it becomes available as a nightly build.

I'll test it and let you know!
Thx again for the hard work.

[klutvott123]

Nice! I'll try it out later. Merry Christmas!

[0crap]

I tested Development build # 1312
Unfortunately it didn't work on my setup.

After flashing I first take a look at the existing sensors.
I noticed that VFAS showed ---
So I did a delete all sensors and discover new sensors.
At that point VFAS was no longer available.
The Tmp1 sensor was still doing the same as in the picture in my fist post.

Flashed Development build # 1311 and all back to normal. (VFAS sensor back again.)

Let me know if you need more info on my setup for troubleshooting this!

[mikeller]

@0crap: Did you have a look at the comments in #7278? If you're using SmartPort, you're going to have to disable some other sensors to be able to see this one, as the telemetry link seems to be overloaded - or just move to FPort that doesn't have this problem.

[0crap]

Sorry, no I did not.
Currently I'm on SmartPort and only use/log a few sensors on my Taranis. (Deleted all sensors I don't want.)
Like this:

I would love to switch to FPort but that is a bit hard because of all the inversion crap on my F405 controller. And the lack of a decent inversion hack on the XSR-E receiver.

So I think from #7278 I need to give a CLI command to use the sensors I need and include Tmp1 for the core temp, right?