Resistance on many mods tends to fluctuate, so any temp control has to be re-adjusted from time to time. What TC mode does it "assume" that the initial resistance is set right (to what temperature is it even supposed to be cooled down?) and that the resistance reading is consistent and exact enough (it isn't) Without locking the resistance, TC can't work correctly, because it aims for target resistance, assuming that's when the temperature is reached. You also need to know things like TCR, TFR, and in theory you should also know what the resistance of the "non heating" part of the current path is. What we get is Snake oil. So I propose we get a completely different mode for vaping To see what I mean: 1) set power to a level you would be comfortable vaping in VW mode 2) set temperature much higher (300 C or so) 3) vape and watch what the temperature reading does 4) it will more or less stop at one point (it will heat much much slower) - that's the point where juice is rapidly evaporating and thus cooling the coil. At this point the temperature is probably a bit too high for someone looking for TC. Firmware could either detect this point or let the user stop firing at this point, and so it should be possible to avoid the whole TC resistance-reading mess, and just detect the difference in how fast the resistance rises. How I imagine it would work in firmware First use: 1) while firing, measure how fast the resistance rises 2) when user stops firing, store the speed of resistance/temperature change as a reference for "hot" Subsequent use: 1) set "temperature" on the mod, but not in C scale but something like cooler-hotter (wher the max is what was measured in the 2) before) 2) fire like in TC mode and measure the speed of the temperature change, aim for that speed Benefits: 1) we don't need to know the exact resistance (initial nor target) 2) user doesn't have to fiddle with resistances 3) it should even work across different builds (it would be more dependant on mass) Does this make sense?