PM your email address to me, I will send my FlashBFS folder to you! FW 1.19.8, HW 1.0
Here you can dl the file flir_ex_pn639_v1.18.7_update_pack.zip (http://en.file-upload.net/download-8686493/flir_ex_pn639_v1.18.7_update_pack.zip.html).
The first image seems to have no radiometrical data in it but to my eye that still looks like 80x60.
The second image looks like a "normal" E4 image, 80x60 resolution, radiometrical data and MSX.
I think your camera is not accepting your new config file. In the old config file there is a noise of 135 (whichever unit that may be) added. The new one is not valid or not accepted, so the camera probably assumes a noise value of 0.
Functions like the spot measurement and MSX or saving the radiometrical data in the JPG are enabled via the config file. Invalid config file -> those functions don't get enabled.
Hi folks,
I have an issue with the MSX image alignment. It seems the distance / fine tuning only adjusts the image up and down. I have an issue with the MSX outline image being offset to the right. The further away I am, the more drastic the ghost image is off center.
Do any of you know of a way to calibrate this or adjust the camera image back to the left so it's on center?
This is a 1.19.8 camera upgraded to the E8+ so I really don't want to send it in to FLIR.
Any help would be appreciated.
$ exiftool -offset* FLIR0230.jpg
Offset X : -4
Offset Y : +21
Don't disassemble!
Edit the calibration values for the camera...Code: [Select]$ exiftool -offset* FLIR0230.jpg
Offset X : -4
Offset Y : +21
see my post here for details
http://u88.n24.queensu.ca/exiftool/forum/index.php?topic=4898.msg24156#msg24156
$ cat /FlashFS/system/calib.rsc | grep fusion.leExFOL7
.calib.visual.fusion.leExFOL7 index
.calib.visual.fusion.leExFOL7.C0X double -0
.calib.visual.fusion.leExFOL7.C0Y double 8.3035752
.calib.visual.fusion.leExFOL7.C1X double -11.721635
.calib.visual.fusion.leExFOL7.C1Y double 6.5931212
.calib.visual.fusion.leExFOL7.C2X double 0
.calib.visual.fusion.leExFOL7.C2Y double 0
.calib.visual.fusion.leExFOL7.C3X double 0
.calib.visual.fusion.leExFOL7.C3Y double 0
.calib.visual.fusion.leExFOL7.CT double 0
.calib.visual.fusion.leExFOL7.T0 double 304.34131
.calib.visual.fusion.leExFOL7.fixFusionDistance double 3
.calib.visual.fusion.leExFOL7.isMeasured bool true
.calib.visual.fusion.leExFOL7.magnQuote double 1.3050345
.calib.visual.fusion.leExFOL7.mathVersion int32 100
.calib.visual.fusion.leExFOL7.minPanX double 0
.calib.visual.fusion.leExFOL7.minPanY double 0
.calib.visual.fusion.leExFOL7.minZoom double 1
.calib.visual.fusion.leExFOL7.rotAngle double -0.21724635
.calib.visual.fusion.leExFOL7.type int32 100
.calib.visual.fusion.leExFOL7.visualFocus int32 0
$ exiftool -offset* FLIR0230.jpg
Offset X : xxx
Offset Y : yyy
Looks like it is just a standard 32 bit CRC like used in the ZIP format. Here's a short python script to calculate it for a file:Code: [Select]import sys
import zlib
with open(sys.argv[1], 'r') as fp:
crc = zlib.crc32(fp.read()) & 0xffffffff
print '0x%08x' % crc
Have you checked this with any of the files?
Yep, I tried it on several of the .rsc files. Just have to delete the existing CRC line before using.
With "the first image" I meant the one with the filename FLIR0281.jpg, and the second one with file name FLIR0282.jpg .
If you look at the image info in for example Windows Explorer, you only see the resolution of the JPG file, which is always at 320x240. But crucial is the thermal resolution which you only can see in the FLIR Tools software or on the camera when you open up the gallery, open a picture, push the center button and choose "Information". Then a box appears which shows some information about the picture (especially the thermal resolution). But I'm pretty sure for the file FLIR0281.jpg you won't see the thermal resolution becaus it does not contain any thermal information.
I tried to PM you but it doesen't seem to have worked.
You could upload your own original (EDIT: the one from your initial backup, that came with your camera) conf.cfc here and I'll do the modification of the file for you.
// count lines
$ wc -l FlashFS/system/calib.rsc
801 FlashFS/system/calib.rsc
//print last line
$ tail -n1 FlashFS/system/calib.rsc
# CRC32 ef8f7e0e
//calc a new crc32 for 801-1=800 lines
$ crc32 <(head -n 800 FlashFS/system/calib.rsc)
ef8f7e0e
Code: [Select]$ cat /FlashFS/system/calib.rsc | grep fusion.leExFOL7
.calib.visual.fusion.leExFOL7 index
.calib.visual.fusion.leExFOL7.C0X double -0
.calib.visual.fusion.leExFOL7.C0Y double 8.3035752
.calib.visual.fusion.leExFOL7.C1X double -11.721635
.calib.visual.fusion.leExFOL7.C1Y double 6.5931212
For a given userDistance z the shift d ((x,y)panVal = floor(d)) between visual and thermal image is calculated byCode: [Select]d(z) = c1 + c0/z (1)
with c0 and c1 being constant values that are factory calibrated into your cam. d, c0 and c1 are 2-dimensional (x,y), units are [px] for d and c1, [m] for z and [px*m] for c0. The coordinate system starts with (0,0) in the upper left corner, d is the shift of the visual image relative to the thermal image (see below for example).
The constants c0 and c1 are provided by \FlashFS\system\calib.rsc, here are mine:Code: [Select]...
.calib.visual.fusion.leExFOL7.C0X double -0
.calib.visual.fusion.leExFOL7.C0Y double 8.1835451
.calib.visual.fusion.leExFOL7.C1X double -8.0483421
.calib.visual.fusion.leExFOL7.C1Y double -2.2975248
...
There are more parameters important for MSX (zoom, rotation, ...), but I didn't need to touch them. So I'm only covering horizontal and vertical shift here.
You have at least two options to calculate new constants for your calibration file:
1) You could set these four parameters to zero, copy the resulting file with a new CRC32 back to the cam, overwriting the original one (keep a backup!) and reboot the E4. To recalculate new values for c0 and c1 you need to get at least two MSX images A and B with some distance between them, determine dA(zA) as well as dB(zB) and solve the system of linear equations to:Code: [Select]c0 = (dA - dB)/(1/zA - 1/zB) (2)
c1 = (dA*zA - dB*zB)/(zA - zB) (3)
Hint for the sign of d: if your visual image appears 5px to the top and 3px to the left of your thermal image, then d = (-3px, -5px).
Note that you don't need to configure z in the cams settings for this, with c0=c1=(0,0) while measuring, (x,y)panVal will be 0 for all z as well.
2) I found it easier to use rset to modify xpanVal and ypanVal (see Tauchers post) on my connected E4, until my MSX images looked the way I wanted. You may want to temporarily disable auto calibration while doing this or wait for the cam to settle.
I started with a very distant object, in my case it was a street light about 50m away, a building front with windows will also work. Now you already have c1, because c1 = d for large z. Then you need a second image of a nearby object, it should be small and centered in your image to minimize error. I used my doors peep hole at about 25cm away and adjusted (x,y)panVal and the distance to get a proper fit. Now you can use equation (1) to get c0.
My new calibration file obtained by 2) worked great, at least indoors, distant objects were still off by 3px. Reason: the configurable userDistance in the cams settings ends with ">3" (cam uses z=3m then), which makes it impossible to reach c1 for infinity. I decided to overcorrect my parameters and used my obtained c1 as if it were dA at zA=3m and calculated new constants with (2) and (3). Now I have perfect MSX even for great distances, while indoors my actual z slightly differs from the configured userDistance. However, I think it would be a better solution to have additional menue entries for greater distances (e.g. ">10").
Another thing worth mentioning: The cam doesn't round() the result for (x,y)panVal, it just chops off everything following the decimal point. So if your dy results to 5.99px at z=3m you'll end up with a 5px shift being used. You may want to adjust the constants to avoid this and could use rls .image.fusion to see the actual values the cam is using.
Query MSX distance from console:
EDIT - Adjusting MSX once somebody played too much with the camera:
fist backup all old values
-> rls .image.fusion
-> write them down, pipe them to file, back them up etc...!
then measure the distance between your camera and some testpattern in cm - set that as MSX distance value
check congruency for the image center AND check if the corners align as well, if not
then adjust xpanVal until the error (if any) is symmetric (keep distance fixed)
zoomFactor and ypanVal should only be touched if you realy understand what you're doing and have to touch them
Never touch the Alpha value, you'll need to powercycle the cam to restore MSX as the value will be auto-zeroed if changed.
Hi all. Got an E4 camera a few days ago and really happy with it so far. One thing I noticed is that after the camera has been on for a few minutes, a small bright spot (maybe 2-3C temperature difference) appears in one part of the image. There is also a similarly sized dark spot nearby. I think someone in this thread mentioned that it might be a speck of dust on the sensor, although I am not sure why the spots only appears after a few minutes. I also noticed that there is a bit of banding in the image -- slightly off-color "stripes" that make the image non-uniform. What I am wondering is how common these problems are. It's pretty easy for me to exchange the camera, but should I expect the new camera to be any better? Do you find that the image on your camera is close to perfect, or are these minor spots / bands expected in this price range? Thanks!
so here the E60 files I used for my E30, pw funzt666
https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg371680/#msg371680
https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg379973/#msg379973
https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg380259/#msg380259
https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg379141/#msg379141
thats all informations, do you need
Why newbies don't use a search before asking?