As a feedback. I get hang on if I try interpolation x4 and I have to kill the application.
I run windows 10
x2 can be selected.
This issue is consistent.
I've noticed a discrepancy between reported Flir temperature (through the Flir app) and the Thermovision software. This from an 'enhanced' E4
The first picture is via Thermovision and shows a peak temperature in the bounding box of 40.7C. The second picture shows Flir App reporting 45.1C. Both programs are of course using the exact same Flir captured file then downloaded to the pc.
How does Thermovision determine the temperature for both spot/box? What information from the file does it use and why the discrepancy?
Panning spot around inside the box shows the same 40.7C, so it is a consistent difference in reported reading.
Interestingly the Flir 'temp bar on the right' shows 41.1C at the top (which I though was max temp). Maybe the Flir app is at fault?
thanks,
george.
I wonder if the 0.1C variation is just a rounding/truncation issue - seems possible to me ??
You should create a paypal button (or similar) on your development page for folk to buy you a beer or pizza or etc...
Hi Joe,
I tried to play with the latest TermoVision_JoeC 1.4.0.0
1. I am not able to connect to the camera using Extern tab
2. I get consistent hang if I press interpolation x4 in the Image Processing window or in Illustration tab
3. I get hang if I enable the tick for the Sharpen filter
4. After a few hangs/kill/start of the TermoVision_JoeC I am not able to connect to the camera anymore. When this happen I still see i3system USB Device in Windows Device Manager (and it appears/disappear if I plug unplug the camera) but I don't hear the typical sound Windows play on enumeration of a new USB device. The only solution I found is to restart the PC.
5. I don't see any affect (in MainIR) if I click on Median, Gauss Blur, Temperature Offset and adjusting the parameters in the whole range.
6. If I see live stream using Intern -> Stream I tried the new feature Visual Blending (moved the slider) but I don't see any effect in MainIR. In fact the only thing which reflect my MainIR is the 'corners' effect.
7. More general I find hard time understanding what some of the options are supposed to do. I understand that this is a free software so no much resources for documentation but in my opinion having a small wiki or user guide for ThermoVision_JoeC will be very useful.
Have a happy New Year
Dimitar
Do you recommend using "Zadig (WinUSB) driver" with Thermovision_JoeC and Thermal Expert Q1?
From your explanation I feel this is the case?
When I save an image (x1, x2), jpg, bmp the Hot and Cold spots are missing inside the measurement box.
I assume some kind of bug?
1. Should I bother with Cal_Low/Hi_TE_Frame for now?
2. Create new Go-Map. Is this an alternative to the Slope Offset parameters?
What distance to the cold, hot surface is recommended. Should it be uniform temperature? How do you use those frames?
3. Slope Offset. Can you explain what is this exactly? I tried to use it so get correct temperatures (for a typical scene in my room)
and I got values: Slope 0.001, Offset 10. Are those values looks plausible to you?
4. I see sometimes the histogram is filled black, sometimes it has only contour what does this represent?
How to make it wide? I was not able to do it whatever I do.
5. related with question 4. Whatever I do I get stream with to low temperature dynamic range even in the cases I point my camera to the hot soldering iron. I see the iron clearly but still the histogram is short.
In addition the soldering tip temperature appears too low, so I think I messed up something with the slope/offset
... with i3 original drivers the image is much more intuitive compared to the one I managed to get from Zadig driver
Quote from: dpenev on Yesterday at 11:08:50 PMQuote1. Should I bother with Cal_Low/Hi_TE_Frame for now?this should be normaly a really simple thing:
1. Klick on "Create new GO-Maps"
2. point to the cold surface and hit the blue "get low frame"
3. point to the hot surface and hit the red "get hi frame"
4. now the "load" button have to be green. now make a right mouse click on the temperature scale and use "autoscale".
Now you should see a clear image
Quote from: dpenev on Yesterday at 11:08:50 PMQuote2. Create new Go-Map. Is this an alternative to the Slope Offset parameters?
What distance to the cold, hot surface is recommended. Should it be uniform temperature? How do you use those frames?no, the GO Map ist for the image quality, the Slope Offset are for the temperature.
practically the GO Map is the same calculation like the Slope Offset for each pixel. But i have this two ways to can fix temperature calibration more easier and without a full uniform heated surface.
Quote from: dpenev on Yesterday at 11:08:50 PMQuote3. Slope Offset. Can you explain what is this exactly? I tried to use it so get correct temperatures (for a typical scene in my room)
and I got values: Slope 0.001, Offset 10. Are those values looks plausible to you?this are the Values for a 2 Point Calibration, see here:
https://learn.adafruit.com/calibrating-sensors/two-point-calibration
and no, with my Camera i have something like that:
Slope: 0.056373
Offset: -365.030
Quote from: dpenev on Yesterday at 11:08:50 PMQuote4. I see sometimes the histogram is filled black, sometimes it has only contour what does this represent?
How to make it wide? I was not able to do it whatever I do.if the histogram shows a solid black, than you have many holes between the values.
For Example... you have a really small Thermal image with 3x3 Pixels
25,25,26,
26,27,27,
27,29,29
the Histogram will count following:
25 = 2
26 = 2
27 = 3
28 = 0
29 = 2
and the zero on 28°C will get from the curve to the base line and back to the curve for the next value.
This indicate that you have temperature steps inside your image.
To the Usage... the Histogram will be refreshed on each new frame. if you want to analyze, stop the stream.
with the left mouse you can drag the curve. with right mouse you get a standard context menu.
And with the middle mouse you can mark a field to zoom inside. With mouse wheel you can zoom too.
Quote from: dpenev on Yesterday at 11:08:50 PMQuote5. related with question 4. Whatever I do I get stream with to low temperature dynamic range even in the cases I point my camera to the hot soldering iron. I see the iron clearly but still the histogram is short.it sounds normal for the i3 Driver (intern), not for the WinUSB Driver "Extern".
Have you seen this while using the "Extern" Streaming?
Quote from: dpenev on Yesterday at 11:08:50 PMQuote... with i3 original drivers the image is much more intuitive compared to the one I managed to get from Zadig driverthe "Intern" image from the DLL seems to be enhanced with auto gain. this cause more holes and a "black" histogram, but the image looks better. And you don't have to work with thinks like calibration.
My Load button is not green after GO-Maps procedure, see the Zadig picture.
Can this be related to my low color dynamic range issue?
...
I think I have some issue with GO-Maps which doesn't work in my case.
...
P.S. Now I've noticed that on my root folder I have files Cal_Hi_Frame.dat and Cal_Lo_Frame.dat,
not Cal_Hi_TE_Frame.dat and Cal_Lo_TE_Frame.dat.
If I understood what you are describing is the typically way the histogram is represented - 'stem' kind of plot.
For the stem plot I would expect almost all histograms being black (as the temperature should be mostly spatially continuous, so no holes)
However this doesn't explain for example the histogram I have on the zadig.png.
So I guess you are not doing a typical stem plot?
What temperature difference between wall and hand references do you recommend.
Should those objects be close to the camera, I guess they need to cover the full view?
Should those objects have uniform surface temperature?
I have moved ThermoVision_JoeC_V1.4.0.0RelFE on my C:\ and after the Create GO Maps Load greens if it pressed.
Previously I had the program extracted at "C:\projects\Thermal Expert\ThermoVision_JoeC_V1.4.0.0RelFE" probably
it doesn't tolerate spaces in the path name?
My main problem however seems to be related with the camera dead pixels. I guess 'Extern' mode doesn't deal
with the dead pixels?
On my images I have one relatively big dead zone which represents on my current images as 12degC. My scene is at 27DegC with variance 7degC. In this case the histogram auto scale process makes all my usefully image shifted and compressed in the hot end, histogram become short. The Median filter removes/mitigates the outlayer (I am referring to one big dead pixel group I have) and I have much better image now (thought still not as good as with the i2system driver, but probably this is a Median filter effect)
I am attaching my dead pixels image for a comments. Are those amount of dead pixels normal?
... However this was not reflected on my histogram.
... my histogram was not reflecting my change. Am I missing something?