This is not meant to be a thermometer. It is a relative temperature scanner meant to quickly scan and delineate the boundaries of a temperature gradient. If it performs as specified, it will do this faster, more accurately, and safer than using one's fingers.
Agreed, but then once you've done that you'll want to know the temperature of one of the locations - and it's kinda stupid that it doesn't do it and you have to dig another tool.
The problem with your logic is that you are theorizing how the deltaK works in practice, but I know how it works because I've used it for years.
And so will most of your potential customers, since it's only you who's used it for years Analyzing the theory, trying to project that into practice and evaluating possibilities and usability is one of the main thing engineers do, on an engineer forum you're naturally going to face a lot of that
The reason I don't want to add a numeric absolute temperature display for point measurements is because of cost. The hardware can do it, but I'm leaving that for then open source hackers, or a future version. For scanning mode its useless.
Cross-posted but I edited my post above to say I'd happily pay double if it had a temp readout function, however I won't pay $35 for the scanning alone since I feel while scanning is a good idea having only that makes no sense and I'd also want readout.
Maybe I'm wrong and by using it I'd realize the readout isn't that useful (it will always somewhat be even for non-overlapping use) but that's how it comes to me. But becasue of [previous sentence] I will never know.
To be clear, I would also find it useful to have a numeric display for absolute temperature. Its just a cost thing. But of course it would be more useful than not having it. The deltaK is for finding temperature anomalies in space, not time. I find that usually when I need to measure anomalies in time, it makes alot more sense to have a multimeter style tool with a fixed probe, and in that case, I probably need to know absolute temperature too.
In practice, I do not find that I need to know the absolute temperature of things while scanning circuit boards. It just doesn't seem to come up that often, if ever. And if you do need a quick absolute reference, you can just recal the deltaK on a known surface (2 seconds) and then go back to the anomaly and there you go, the 3 dynamic ranges are well defined and after you use it awhile you can get an idea what the absolute temperatures of things are using this method, just like you can by touching things. I go back to the thermal camera analogy, without absolute temperature data. A heat map tells you a tremendous amount about the thermal state of a surface, without absolute data. And if you want absolute data, just pick a roughly known spot and start the deltaK there.
I dont find alot of thermal noise on circuit boards. Of course, there are an infinite number of circuit board designs out there. And there are of course some situations where thermal data by itself, even from a camera, might be too complex to make conclusions from. But even in that case, you can usually compare known good to device under test and figure things out.
When I troubleshoot circuit boards, I bring the whole calvary, every meter, scope, soldering iron, thermometer, schematics, PCB layout, etc..... basically every tool and document I have and throw it all at the problem on the first go. Its not a situation where there is a benefit to having just-one-tool. The deltaK provides a unique functionality at a very low cost that fills a blank spot in that toolbox. I'm still keeping my Omega thermocouple meter, my point and shoot IR themometer, and if I ever get a thermal camera, that too, and of course the deltaK. They arent exclusive of each other, they compliment each other.