Flir E4 Thermal imaging camera teardown

[Pauloven]

Hi, I feel as if my photos where out of focus, specially the normal camera. What do you think?

[OrBy]

Hi, I feel as if my photos where out of focus, specially the normal camera. What do you think?

Your doing very wide far away outdoor shots with a camera that has a very low resolution when compared to even a cheap cell phone now a days. It's not going to look great. Try a closer subject to see if you can get more detail.

[OrBy]

Please check my excel sheet, the calculations with atmosphere transmissivity are a great improvement.

Are these improvements able to be made available in your flir.php as well or is to complex for that method or needs to be done another way?

[tomas123]

exiftool can decode this new tags since two days
I will complete the flir.php the next days...

[OrBy]

exiftool can decode this new tags since two days
I will complete the flir.php the next days...

Very good news! 

I look forward to comparing the differences.
I also noticed that the the v2 of your script does not include the panoramic fixes that you posted about here:

I changed flir.php from

Code: [Select]

exec($convert." raw.png -fx \"($B/ln($R1/($R2*(65535*u+$O))+$F)-$Smin)/$Sdelta\" ir.png");
to

Code: [Select]

// check RAW value > |Planck Offset|
// x?y:z  Imagemagick ternary conditional expression, returns value y if x > 0, otherwise z
exec($convert." raw.png -fx \"($B/ln($R1/($R2*((65535*u+$O)?(65535*u+$O):1))+$F)-$Smin)/$Sdelta\" ir.png");


Does this fix make the images some how inferior to the method in your v2 script?

[Pauloven]

Your doing very wide far away outdoor shots with a camera that has a very low resolution when compared to even a cheap cell phone now a days. It's not going to look great. Try a closer subject to see if you can get more detail.

Would you please check these closer ones. The normal camera really looks super cheap.

[OrBy]

Would you please check these closer ones. The normal camera really looks super cheap.

Looks like mine does. I think your fine.
Keep in mind - there are no auto focus optics in the E4 visible light camera like many cell phones have. It's a single focus 640x480 camera like many old web cam's. It's just there to provide extra MSX definition to the even lower spec'ed thermal camera. At 640x480 it has 4 times the pixels then the "upgraded" E4 thermal sensor. If that's not enough it may be time to look into a E40 or better unit.

[tomas123]

I also noticed that the the v2 of your script does not include the panoramic fixes that you posted about here:

you are right, the flir.php is only a template for own adaptations (proof of concept)
... but I collect all infos in my "changes and enhancements"

reading radiometric image with Exiftool + ImageMagick (without flir tools)

changes and enhancements

• see this post for invalid RAW values
  https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg356008/#msg356008
  

[OrBy]

I also noticed that the the v2 of your script does not include the panoramic fixes that you posted about here:

you are right, the flir.php is only a template for own adaptations (proof of concept)
... but I collect all infos in my "changes and enhancements"

reading radiometric image with Exiftool + ImageMagick (without flir tools)

changes and enhancements

• see this post for invalid RAW values
  https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg356008/#msg356008
  

Good to know!

[Yama13]

First post.  I recently bought an E4.  I enjoy reading about the incredible things you guys are doing with the model – kudos to all.

In my case, I don’t plan to hack it (at least for now), because I tried it out as received, and feel it’s good enough for my use (again, for now), which is just to check things around the house – the MSX feature makes it easy to figure out what I’m looking at versus a bunch of fuzz bunnies.  I purchased it knowing it may end up being a 1.21 unit, but I felt it was a good deal anyway.

I just wanted to contribute the info for mine to the “database.”  I ordered it online on February 19.  It was shipped on the 20th (there was no backorder, so it obviously came from existing stock), and I received it on the 25.

To my surprise, here is the info:

Serial 6391 1xxx
E4 1.1
Firmware 1.19.8
Calibration 1/24/14

I do have one question.  I have not hooked it up to Flir Tools as yet, and I have read it phones home when you hook the camera up.  I assume the software doesn’t “force” an update in any way, does it?  I assume if anything, it just notifies me that an update is available, but gives me the option?  I’m not going to do the hack now, but want to keep options open.

KEEP UP THE GREAT WORK!

[RAWebb]

In my case, I don’t plan to hack it (at least for now), because I tried it out as received, and feel it’s good enough for my use (again, for now), which is just to check things around the house – the MSX feature makes it easy to figure out what I’m looking at versus a bunch of fuzz bunnies.  I purchased it knowing it may end up being a 1.21 unit, but I felt it was a good deal anyway.

The resolution mod is so safe you really ought to do it. Use Taucher's EZCRC01 tool to create one file, e8.cfg, and upload it to the right config directory on the E4 and yer in.

There is a new version of FLIR Tools up (4.1.14052.1001) as of late February, so it may be safest to go the RNDIS route?

Hmmm... Noticed on the FLIR home page at that there's a picture of an E4 inspecting an electrical enclosure. That image on its screen looks awfully clear to be only 80x60. Would FLIR use an "enhanced" E4 on their web page?

[jkrump]

I feel like I've arrived late to the party! I just got my E4, and it will serve my purposes but the higher res sure would've been nice to look at! I'll stay subscribed here just in case anyone posts a breakthrough on 1.21. For posterity's sake, here are the details:

Model: E4 1.1L 63901-0101
Serial: 639149XX
Purchased: 2/20/14 via Amazon
Received: 3/4/14
Programmed: 2/17/14 in Estonia
Version: 1.21.0

[Yama13]

@RAWebb.

About the image of the panel, it looks like what I see when I look at my panel - the MSX pretty much negates (for me, and for now) the need to increase the thermal resolution, as I can readily make out what I'm looking at.  You can tell it's still the 80x60 because of all the pixelation of the background (esp in the blue areas) which you wouldn't get with the higher rez thermal image.

I also notice the ambient lighting also makes a big difference in how everything looks.  The dimmer the ambient lighting, the more pixelated the thermal part looks - and obviously the less detail MSX is able to pick up and integrate.  It appears that the "regular" cam side is not the best at picking up detail at lower ambient light levels.  This would probably be the one reason to make me switch - when the lighting is low, the combined image isn't that great, so a higher rez thermal image from the getgo would definitely make a difference.  And yet, I haven't really found it necessary in my use to be concerned with lower light levels - it's just when playing to learn the limits.

I may end up doing at least the rez mod eventually though - that's why I want to make sure that plugging it in to Flir Tools will not force any kind of updating.

I feel I really lucked out with the 1.19 considering how "late" in the game I was, so don't want to lose that option.

[Rainer]

If you want to test something, you can send me a zip-file and some instructions.

try to copy the attached file e8.cfg to /FlashFS/system/appcore.d/config.d/
reset -> any changes?

I think the menu-hack should work, except zoom.

Sometimes the easy way is the easiest way.

i have tested, but no changes in any option:

first i put the e8cfg in the folder, reset to factory-> no changes
next i delete the old conf.cfc-file, reset to factory->no changes

Should it work, when i put the removed binaries in the TIC?(thomas123 said so)

[tomas123]

try to copy the attached file e8.cfg to /FlashFS/system/appcore.d/config.d/
reset -> any changes?

it's nice, that you generate a valid cfg for his serial number 

but...

first i put the e8cfg in the folder, reset to factory-> no changes
next i delete the old conf.cfc-file, reset to factory->no changes

Should it work, when i put the removed binaries in the TIC?(thomas123 said so)

don't play around with delete/reset - you can seriously brick your camera !!!!

[tomas123]

Should it work, when i put the removed binaries in the TIC?(thomas123 said so)

better idea,

Can you login to telnet?
Try this with binary from old fw

Code: [Select]

\FlashBFS\system>i2c.exe r AE FF
Open I2C device
I2C read command 57 FF returned: FF FF F9 99 40 1 F0 0 0 1 0 0 0 0 0 0 0 0 30 3 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 0 46 4C 49 52 20 45 34 ....and post the result

save your registers and post the zipped rls.txt
no panic, wait a minute

Code: [Select]

> rls -r -l > /FlashIFS/rls.txt

furthermore copy prodapp.exe to /FlashFS/system and try this

Code: [Select]

// start the service mode app
> start prodapp
// wait some seconds and check process list
> ps
// if you see something like
// Process prodapp.EXE     ( 3 threads), id 0x0552005E, loaded at 0x00010000
// try high resolution mode
> rset prod.preparation.command restartHighRes
post your terminal output

post files from FlashFS/tmp like
prod.log

14:17:32 Log restart ProdApp built:Mon Sep 16 13:56:38 2013 by:upalmer@SE-BRYGG5/ALPHA_1.9, build:15,  Detector:*
14:17:33 Found detectortype SB320 ISC0901, selecting detector S
14:17:33 Lens leExFOL7
...
14:17:38 ProdSpec:     0.4X
14:17:39 WARNING: Sensor system.tempsens.TShutterDigFilt2 is indicating 0 K
14:17:41  11 Preparation:All tasks reporting ready
14:17:41  12 Preparation:Image frequency 9
14:17:44 Using .image.flow.detector.TFpa to check tempstable
14:22:33 WARNING: Sensor system.tempsens.TShutterDigFilt2 seems to be frozen at 0

and with successful command restartHighRes you get the 320x240 resolution

01:40:08  13 Preparation:---------------Command restartHighRes received
01:40:10 Using .image.flow.detector.TFpa to check tempstable
01:40:16  15 Preparation:Restarting in high resolution mode/service mode
01:40:16  16 Preparation:Command restartHighRes, result 0

I missed this folder in your FLIR_BACKUP

!! don't delete/change original files !!

[Rainer]

I will check this today (when i'm back from job)

Good to know about bricking my TIC in this way. This Device has some trouble sometimes with flipping/rotating display after start with usb-cord on it or after pressing power for longer than a click(right before i was activating the Network-Mode for the first time) So i will play around a while with this device a send it back on next Weekend.

If there is a solution to see for hack, i change to a new one. Else i want my money back and look for an hackable one.

How does telnet works on the device? Do i need any special software for the Win7-PC?

[tomas123]

I don't believe, that restartHighRes works.
This command generates a "high resolution" config file from a template with an old CRC01 checksum...

for telnet use putty.exe
http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html

step by step

This Device has some trouble sometimes with flipping/rotating display after start with usb-cord on it or after pressing power for longer than a click

this is certainly not a hardware defect
make a photo from this

[mikeselectricstuff]

I will check this today (when i'm back from job)

Good to know about bricking my TIC in this way. This Device has some trouble sometimes with flipping/rotating display after start with usb-cord on it or after pressing power for longer than a click(right before i was activating the Network-Mode for the first time) So i will play around a while with this device a send it back on next Weekend.

If there is a solution to see for hack, i change to a new one. Else i want my money back and look for an hackable one.

How does telnet works on the device? Do i need any special software for the Win7-PC?

Telnet is not installed by default in Win7 but it can be enabled - don;t recall how but googling telnet win7 should find it

[tomas123]

Please check my excel sheet, the calculations with atmosphere transmissivity are a great improvement.

Are these improvements able to be made available in your flir.php as well or is to complex for that method or needs to be done another way?

done 

download new flir.php script here https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg342072/#msg342072

as attachment my two "flir radiometric jpg" 4x4 Pixel samples with 0m and 100m distance to object

Output for Distance = 0m

Code: [Select]

.\php\php flir.php --resize 640x480 -i 4x4-0m.jpg -o result_0m.jpg
...
wrote "result_0m.jpg" with Temp-Range: -15.1 / 129.2 degree Celsius
for 100m with overwritten distance

Code: [Select]

>.\php\php flir.php --resize 640x480 --dist 100 -i 4x4-0m.jpg -o result_100m.jpg
...
wrote "result_100m.jpg" with Temp-Range: -18.0 / 134.4 degree Celsius
or with 100 m embedded distance 

Code: [Select]

>.\php\php flir.php --resize 640x480 -i 4x4-100m.jpg -o result_100m.jpg
...
wrote "result_100m.jpg" with Temp-Range: -18.0 / 134.4 degree Celsius

see here for further informations about calculations
http://u88.n24.queensu.ca/exiftool/forum/index.php/topic,4898.msg27546.html#msg27546

now flir.php calculations are 100% identical with Flir Tools temperature csv export
we need 15 parameters for temperature calculations

Code: [Select]

$ exiftool -Atm* -Planck* -Object* -Emis* -Reflected* -Relativ* 4x4-100m.jpg
Atmospheric Temperature         : 20.0 C
Atmospheric Trans Alpha 1       : 0.006569
Atmospheric Trans Alpha 2       : 0.012620
Atmospheric Trans Beta 1        : -0.002276
Atmospheric Trans Beta 2        : -0.006670
Atmospheric Trans X             : 1.900000
Planck R1                       : 14168.402
Planck B                        : 1386
Planck F                        : 2.5
Planck O                        : -7363
Planck R2                       : 0.026881648
Object Distance                 : 100.00 m
Emissivity                      : 0.95
Reflected Apparent Temperature  : 30.0 C
Relative Humidity               : 50.0 %

[hgg]

Control Panel / Programs and Features / Turn Windows Features On or Off / Tick Telnet Client.

[Rainer]

Should it work, when i put the removed binaries in the TIC?(thomas123 said so)

better idea,

Can you login to telnet?
Try this with binary from old fw

Code: [Select]

\FlashBFS\system>i2c.exe r AE FF
Open I2C device
I2C read command 57 FF returned: FF FF F9 99 40 1 F0 0 0 1 0 0 0 0 0 0 0 0 30 3 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 0 46 4C 49 52 20 45 34 ....and post the result

save your registers and post the zipped rls.txt
no panic, wait a minute

Code: [Select]

> rls -r -l > /FlashIFS/rls.txt

furthermore copy prodapp.exe to /FlashFS/system and try this

Code: [Select]

// start the service mode app
> start prodapp
// wait some seconds and check process list
> ps
// if you see something like
// Process prodapp.EXE     ( 3 threads), id 0x0552005E, loaded at 0x00010000
// try high resolution mode
> rset prod.preparation.command restartHighRes
post your terminal output

post files from FlashFS/tmp like
prod.log

14:17:32 Log restart ProdApp built:Mon Sep 16 13:56:38 2013 by:upalmer@SE-BRYGG5/ALPHA_1.9, build:15,  Detector:*
14:17:33 Found detectortype SB320 ISC0901, selecting detector S
14:17:33 Lens leExFOL7
...
14:17:38 ProdSpec:     0.4X
14:17:39 WARNING: Sensor system.tempsens.TShutterDigFilt2 is indicating 0 K
14:17:41  11 Preparation:All tasks reporting ready
14:17:41  12 Preparation:Image frequency 9
14:17:44 Using .image.flow.detector.TFpa to check tempstable
14:22:33 WARNING: Sensor system.tempsens.TShutterDigFilt2 seems to be frozen at 0

and with successful command restartHighRes you get the 320x240 resolution

01:40:08  13 Preparation:---------------Command restartHighRes received
01:40:10 Using .image.flow.detector.TFpa to check tempstable
01:40:16  15 Preparation:Restarting in high resolution mode/service mode
01:40:16  16 Preparation:Command restartHighRes, result 0

I missed this folder in your FLIR_BACKUP

!! don't delete/change original files !!

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------

Hello tomas

telnet was fine:
copy i2c and get this back:

Code: [Select]

\FlashBFS\system>i2c.exe r AE FF
Open I2C device
I2C read command 57 FF returned: CA 54 31 39 38 32 38 33 0 0 0 32 30 31 33 36 30 31 36 0 0 31 31 0 0 0 0 0 0 0 0 ED 9C FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF A F4 3C 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 46 F4 54 31 39 38 33 30 34 0 0 0 36 33 38 31 33 38 30 38 0 0 30 31 0 0 FF FF FF FF FF FF F2 9F 50 0 3C 0 0 1 0 0 0 0 0 0 0 0 8C 1 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 0 46 4C 49 52 20 45 34 0 0 0 0 0 0 0 0 0 0 0 0 0 36 33 39 30 31 2D 30 31 30 31 0 0 0 0 0 0 36 33 39 31 34 37 35 32 0 0 32 30 31 34 2D 30 32 2D 31 33 0 0 30 31 0 0

(is in attached i2c.txt)

next i do this rls-thing. file is attached rls.txt

last i do your prodapp-instructions an after a couple of minutes, there was a new tmp-folder with the log-File.

2014-03-04 20:38:40 Log restart ProdApp built:Mon Sep 16 13:56:38 2013 by:upalmer@SE-BRYGG5/ALPHA_1.9, build:15, Core:63813808, Detector:*
2014-03-04 20:38:40 Found detectortype SB320 ISC0901, selecting detector S
2014-03-04 20:38:40 Lens leExFOL7
2014-03-04 20:38:40 Found osimgkit ASCO OS image, selecting Cameratype Z, Web-Addon Z3
2014-03-04 20:38:40 WARNING Failed to update \FlashBFS\system/web/inc for Z3
2014-03-04 20:38:40 ERROR: No Configuration name found. Bad camera serial number ??[64]
2014-03-04 20:38:40 Configuration name: ""
2014-03-04 20:38:41 Deleted 0 \FlashIFS\tmp\*.fff files
2014-03-04 20:38:41
2014-03-04 20:38:41 FLIR E4       63901-0101     63914752 
2014-03-04 20:38:41 --- Software combinations ---
2014-03-04 20:38:41 swcombination    1.21.0
2014-03-04 20:38:41 appkit           1.0.16     10-Jan-2014
2014-03-04 20:38:41 confkit         E4 1.1L     25-Oct-2013
2014-03-04 20:38:41 osimgkit        16.0.12     2013-11-26
2014-03-04 20:38:41 prodkit               0     12-Feb-2014
2014-03-04 20:38:41 --- Software components ---
2014-03-04 20:38:41 AppCore         22.0.0.1     01-Dec-2013      upalmer@SE-BRYGG5/ALPHA_1.9   
2014-03-04 20:38:41 AppServices     22.0.0.1     23-Apr-2013      upalmer@SE-BRYGG5/ALPHA_1.9   
2014-03-04 20:38:41 Bootloader      16.1.5.0     -                FLIR                         
2014-03-04 20:38:41 ResMon          22.0.0.1     23-Apr-2013      upalmer@SE-BRYGG5/ALPHA_1.9   
2014-03-04 20:38:41 WinCE            6.0.0.0     2005             Microsoft                     
2014-03-04 20:38:41 appcore_dll      1.9.0.1     23-Apr-2013      upalmer@SE-BRYGG5             
2014-03-04 20:38:41 common_dll       1.9.0.7     10-Jan-2014      upalmer@SE-BRYGG5             
2014-03-04 20:38:41 facet_core      22.0.0.1     25-Nov-2013      upalmer@SE-BRYGG5/ALPHA_1.9   
2014-03-04 20:38:41 facet_ui_qml    22.0.0.1     25-Nov-2013      upalmer@SE-BRYGG5/ALPHA_1.9   
2014-03-04 20:38:41 fvd            16.0.47.0     Oct  8 2013      upalmer@SE-BRYGG4             
2014-03-04 20:38:41 --- Firmware components ---
2014-03-04 20:38:41 IRDM             0.0.1.0     -                -                             
2014-03-04 20:38:41 POLLUX           0.1.0.0     20-Sep-2013      FLIR                         
2014-03-04 20:38:41 POLLUX_FPGA     8.1.25.0     -                FLIR                         
2014-03-04 20:38:41 --- Configuration ---
2014-03-04 20:38:41                       
2014-03-04 20:38:41 ProdSpec:     0.51
2014-03-04 20:38:41 Calibration:  1.22 2014-02-07 11:18:55
2014-03-04 20:38:41 Torrent version:
2014-03-04 20:38:41 Release: 22
2014-03-04 20:38:41
2014-03-04 20:38:41 No \FlashFS\system\prodresult.rsc found
2014-03-04 20:38:41 No ResLogList found
2014-03-04 20:38:41 Information: Unable to Open ".prodSpec.general.config.PPrDir" retcode ab010008
2014-03-04 20:38:41 WARNING: Sensor system.tempsens.TShutterDigFilt2 is indicating 0 K
2014-03-04 20:38:46  13 Preparation:All tasks reporting ready
2014-03-04 20:38:46  14 Preparation:Image frequency 9
2014-03-04 20:38:50 Using .image.flow.detector.TFpa to check tempstable
2014-03-04 20:39:53  15 Preparation:---------------Command restartHighRes received
2014-03-04 20:39:53  16 Preparation:Target noise set to 0
2014-03-04 20:40:00  17 Preparation:Restarting in high resolution mode/service mode
2014-03-04 20:40:00  18 Preparation:Command restartHighRes, result 0
2014-03-04 20:43:40 WARNING: Sensor system.tempsens.TShutterDigFilt2 seems to be frozen at 0
2014-03-04 20:57:30 Battery: 34 % remaning, Charging off

 Last thing: i shot a thermal foto with full 320x240 , but lost the MSX-Option

[stefbeer]

One thing I noticed in the prod.log:

2014-03-04 20:38:40 ERROR: No Configuration name found. Bad camera serial number ??[64]
2014-03-04 20:38:40 Configuration name: ""

@ Rainer: Did you put the original conf.cfc back or is it still missing? Maybe that's why the MSX option is missing.
Or does it only disappear after you enable high resolution mode?

[Rainer]

conf.cfc is right in place.

MSX-Option was working fine until to the high-Res-Mode activation.

[granz]

Anyone interested in getting an E4 with the 1.19.8 firmware in the US, I just got one today (shipped immediately when ordered) please PM me.  I don't want to post a link, because people have started to buy them all up and then resell them on eBay for a profit, and that makes me angry