Flir E40 Upgrade & Configuration - Page 1
Forum section: electronics / general

author: ElectroTuna
author_rank: Contributor
timestamp: November 20, 2014, 04:39:47 am
content: The thread regarding the E4 camera is now nearly at 400 pages with many useful information from helpful users. I have spent about an hour reading through it, but unfortunately information about upgrading the E40 camera is rather old. I have one unit which I recently got with firmware Version 3.18.0 (E40 1.0).If someone can post a quick instruction on this model, I would really appreciate it and I promise to report back and provide a detailed instruction with any issues I encountered.Thank you!

author: Pinkus
author_rank: Frequent Contributor
timestamp: November 20, 2014, 08:08:26 am
content: Edit: Section removed as pointed to the wrong threadYou do not need to read all 400 pages. Mike put all the important links on the first page.Basically the E40 acts the same a the E4, there is nothing special.... oh, and make a backup first!For the first time you will need some time if you work carefully and concentrated (including backup etc. you will need 3 hours) - so make sure nobody disturbs you.

author: tomas123
author_rank: Frequent Contributor
timestamp: November 20, 2014, 11:13:47 am
content: there is no point-to-click hack for the Exxthe first post from mikehttps://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/referencedhttps://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg342072/#msg342072and go to19 "Resolution upgrade Flir E30/E40/E50 to E60 and i3/i5 to i7"if you have a newer firmware/hardware, then you must help to hack ita nice history from E30 (without WLAN) to E60 (with WLAN)https://www.eevblog.com/forum/profile/?area=showposts;u=89829---------I will give no futher reply in this thread.

author: ElectroTuna
author_rank: Contributor
timestamp: November 20, 2014, 03:53:35 pm
content: Thanks, I will make an effort and will report to this post with issues/findings.If anyone else has any input, I would appreciate it. If successful, I will make a detailed reports.

author: ElectroTuna
author_rank: Contributor
timestamp: November 30, 2014, 03:42:31 am
content: As promised, I have been working on documenting the step-by-step procedure to upgrade the E40. I have everything figured out except for the fact that the new E40's, aren't shipped with all the files like the old firmware.As a result, I need the files which comes with the E60 in order to be able to make the modifications.Can someone please post their E60 files (like an image of the instrument files) and I will create a nice package for everyone who would like to do the same.Thanks guys!

author: ElectroTuna
author_rank: Contributor
timestamp: December 01, 2014, 05:01:44 am
content: Is there anyone out there who can help?

author: tomas123
author_rank: Frequent Contributor
timestamp: December 01, 2014, 10:25:17 am
content: Quote from: tomas123 on November 20, 2014, 11:13:47 amdo you have succesfull enhanced the resolution of the E40 to 320x240?what do you need else?please post your config file of the unpatched E40

author: mikeselectricstuff
author_rank: Super Contributor
timestamp: December 01, 2014, 10:32:02 am
content: The changes are just a few parameters - look at the E4 stuff, most of it will be the same.

author: ElectroTuna
author_rank: Contributor
timestamp: December 02, 2014, 02:13:44 am
content: Thank you mikeselectricstuff and tomas123, I appreciate your responses.On this forum, I found a template for a modified E40 config files as a guide on what I need to change on my unit. My unit's config file in directory \FlashFS\system\kits.d:# confkit.rev# This file contains revision information for all loaded# files in a kit# Do not editNAME userconfVERSION E40 1.0DATE 16-Oct-2013# format: FILE <filename> <size> <CRC32># or: FILE <filename> undefinedFILE flashfs\system\appcore.d\config.d\conf.cfg undefinedFILE flashfs\system\appcore.d\factory.d\adjust.rsc 113 568770501FILE flashfs\system\appcore.d\factory.d\intensity.rsc 145 2456191835FILE flashfs\system\appcore.d\factory.d\laser.rsc 143 2190380121FILE flashfs\system\appcore.d\factory.d\palette.rsc 268 767855916FILE flashfs\system\appcore.d\factory.d\pathimages.rsc 139 4242760020FILE flashfs\system\appcore.d\factory.d\power.rsc 333 1829598383FILE flashfs\system\appcore.d\factory.d\time.rsc 128 3305292736FILE flashfs\system\appcore.d\factory.d\usb.rsc 114 2394224369FILE flashfs\system\kits.d\confkit.rev undefinedFILE flashfs\system\service\appcore.d\config.d\conf.cfg undefinedFILE flashfs\system\service\appcore.d\factory.d\bw.rsc 258 4267495318FILE flashfs\system\service\appcore.d\factory.d\rndis.rsc 84 1796347983FILE flashfs\system\services.d\config.d\conf.cfg undefinedFILE flashfs\system\services.d\factory.d\dcim.rsc 119 4038415784FILE flashfs\system\services.d\factory.d\no_wzctool.rsc 60 2262041015FILE flashfs\system\ui.d\config.d\conf.cfg undefinedBut for example, the E60 file I need to replace this with looks like this:# confkit.rev# This file contains revision information for all loaded# files in a kit# Do not editNAME userconfVERSION E60 0.10DATE 28-Apr-2011# format: FILE <filename> <size> <CRC32># or: FILE <filename> undefinedFILE \flashfs\system\appcore.d\config.d\conf.cfg undefinedFILE \flashfs\system\appcore.d\factory.d\adjust.rsc 113 568770501FILE \flashfs\system\appcore.d\factory.d\intensity.rsc 145 2456191835FILE \flashfs\system\appcore.d\factory.d\laser.rsc 143 2190380121FILE \flashfs\system\appcore.d\factory.d\palette.rsc 267 3727757887FILE \flashfs\system\appcore.d\factory.d\power.rsc 333 1829598383FILE \flashfs\system\appcore.d\factory.d\time.rsc 128 3305292736FILE \flashfs\system\appcore.d\factory.d\usb.rsc 114 195315524FILE \flashfs\system\arctic.pal 2037 747452631FILE \flashfs\system\bw.pal 3192 1681767566FILE \flashfs\system\iron.pal 3112 2395977639FILE \flashfs\system\kits.d\confkit.rev undefinedFILE \flashfs\system\lava.pal 3645 3268586420FILE \flashfs\system\rainbow.pal 3095 986361025FILE \flashfs\system\rainhc.pal 3081 336971817FILE \flashfs\system\service\appcore.d\config.d\conf.cfg undefinedFILE \flashfs\system\service\appcore.d\factory.d\bw.rsc 258 4267495318FILE \flashfs\system\service\appcore.d\factory.d\rndis.rsc 84 1796347983FILE \flashfs\system\services.d\config.d\conf.cfg undefinedFILE \flashfs\system\services.d\factory.d\dcim.rsc 119 4038415784FILE \flashfs\system\services.d\factory.d\no_wzctool.rsc 60 2262041015FILE \flashfs\system\ui.d\config.d\conf.cfg undefinedFILE \flashfs\system\ui.d\factory.d\320_240.rsc 119 3416508497FILE \flashfs\system\ui.d\factory.d\autofusion.rsc 260 727783077FILE \flashfs\system\ui.d\factory.d\pipfusion.rsc 267 532069858FILE \flashfs\system\ui.d\factory.d\regional.rsc 182 2653315878FILE \flashfs\system\ui.d\factory.d\save_direct.rsc 139 3237695249FILE \flashfs\system\ui.d\factory.d\sim_save.rsc 131 1198853717FILE \flashfs\system\ui.d\factory.d\tfsdir.rsc 312 3781116346The problem is that I don't have most of those files on my E40. I guess the newer firmware don't put those files in by default...And this is my problem. Anything you can do to help would be much appreciated.

author: ixfd64
author_rank: Frequent Contributor
timestamp: December 02, 2014, 02:53:33 am
content: This post may be of interest:https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg561266/#msg561266

author: ElectroTuna
author_rank: Contributor
timestamp: December 02, 2014, 03:00:14 am
content: Quote from: ixfd64 on December 02, 2014, 02:53:33 amThanks. The problem is that units with # ID 490xxxxx, have all the files already on the camera. The newer units don't have all the files and therefore these changes will then point to non-existing files as my previous post shows.

author: Pinkus
author_rank: Frequent Contributor
timestamp: December 02, 2014, 08:09:34 am
content: Quote from: ElectroTuna on December 02, 2014, 03:00:14 amOlder units (without MSX) are using a different software than the newer ones with MSX. Because of this, you CANNOT use the E4 (always comes with MSX) instructions here 1:1 on an older E40 (without MSX).... and vice versa.I assume you have a newer E40 with MSX (because your confkit.rev is from Oct 2013), so you CANNOT use the E60 files from the forum, as the Exx used here, always were older ones without MSX.The Exx files in this forum will only work on older E40 (without MSX).If you have an older, non-MSX version (which I doubt, as the file date from October 2013 shows, you are using the newer version), look here:https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg561266/#msg561266

author: ElectroTuna
author_rank: Contributor
timestamp: December 02, 2014, 02:21:59 pm
content: Quote from: Pinkus on December 02, 2014, 08:09:34 amThank you Pinkus,So the now the question is, given that I have the new E40, with serial numbers that start with 6 instead of 4, what do I do to get all the features, including pallets... I am sorry if my question seems primitive again, but I thought I had it figured out!

author: tomas123
author_rank: Frequent Contributor
timestamp: December 02, 2014, 03:31:07 pm
content: I asked foryour config file!You posted only files from this forum (best known old Exx without MSX).We can't help you, if you don't give us your file structure.PS: to update the resolution you need to edit only the config file (one file)Quote from: tomas123 on December 04, 2013, 02:23:30 pm

author: tomas123
author_rank: Frequent Contributor
timestamp: December 02, 2014, 04:02:24 pm
content: as sample the path and critical content for the old E40 (without MSX)Code:>type \FlashFS\system\appcore.d\config.d\conf.cfg....caps.config.name text "app E40".caps.config.revision text "0.10".caps.config.image.settings.enabled bool true.caps.config.image.settings.downsample bool true.caps.config.image.settings.resIR int32 160.caps.config.image.targetNoise entry.caps.config.image.targetNoise.enabled bool true.caps.config.image.targetNoise.targetNoiseMk int32 60...you can copy and edit the file (update crc), but watch for the alphabetically order !!!!Quote from: mikeselectricstuff on February 02, 2014, 09:12:38 pmfirmware differences in Exx P/N:490xx to Exx P/N:645xx (with MSX)old Exx (Late 2012) firmware feed:Last Updated: April 23, 2013: FLIR Exx P/N:490xx (2.23.14) Update Packhttp://support.flir.com/SwDownload/app/RssSWDownload.aspx?ID=127Code:> dir fpg*06.12.2011 17:23 592.029 fpga.bin02.02.2012 17:57 797.881 fpga_c4_55.bin06.12.2011 17:00 798.274 fpga_c55.binmy old Exx has the sensor "SB320 ISC0601" (see /FlashFS/tmp/prod.log or "rls .image.flow.detector")new Exx with MSX: (Late 2013)Last Updated: November 21, 2014: FLIR Exx P/N:645xx / 646xx (4.9.0) Update Packhttp://support.flir.com/SwDownload/app/RssSWDownload.aspx?ID=194Code:> dir fpg*28.04.2014 16:26 807.922 fpga_B2CO3.bin17.12.2013 08:18 805.703 fpga_C4_55.binunzip the E2qtcomb_v4.9.0.fifFlir changed the file structure from \Flashfs\system\*.exe to \FlashBFS\system\*.exe (like the Ex)but the path for the config file is the samewe need to see if your config file is encrypted (cfg / cfc)PS: I listed the fpga firmware, because the MSX feature is part of fpga.Nobody attempt to hack the old Exx (late 2012) with the newer fimwareoff topic: fgpa of ExQuote from: tomas123 on November 21, 2014, 10:41:16 am

author: ElectroTuna
author_rank: Contributor
timestamp: December 03, 2014, 03:41:24 am
content: Dear tomas123,I appreciate your thorough and detailed responses, it must be the efficient German genes!I have attached two config files from my camera. Aside from the resolution, what would be great is if I could get the other functions like the zoon and Thermal Fusion.Again, thank you for helping me this far. Please take a moment and look at the config files:FlashFS/system/services.d/config.d/cof.cfg:Code:## Appservices wlan configuration#.caps entry.caps.config entry.caps.config.name text "srvs E40".caps.config.revision text "1.0".caps.config.wlan entry.caps.config.wlan.enabled bool true.caps.config.bluetooth entry.caps.config.bluetooth.enabled bool true# ID 645XXXXXFlashFS/system/appcore.d/config.d/conf.cfgCode:## Generated at 2013-10-16 09:16:10#.caps entry.caps.config entry.caps.config.name text "app E40".caps.config.revision text "1.0".caps.config.segment text "handheld".caps.config.direction entry.caps.config.direction.sensorAccel entry.caps.config.direction.sensorAccel.enabled bool true.caps.config.direction.compass entry.caps.config.direction.compass.enabled bool false.caps.config.direction.lcdAccel entry.caps.config.direction.lcdAccel.enabled bool true.caps.config.image entry.caps.config.image.framegrab entry.caps.config.image.framegrab.fusion entry.caps.config.image.framegrab.fusion.enabled bool true.caps.config.image.framegrab.fusion.pip entry.caps.config.image.framegrab.fusion.pip.enabled bool true.caps.config.image.framegrab.fusion.hcf entry.caps.config.image.framegrab.fusion.hcf.enabled bool true.caps.config.image.sensor entry.caps.config.image.sensor.enabled bool true.caps.config.image.services entry.caps.config.image.services.store entry.caps.config.image.services.store.enabled bool true.caps.config.image.services.store.radiometric entry.caps.config.image.services.store.radiometric.enabled bool true.caps.config.image.services.store.incompatible entry.caps.config.image.services.store.incompatible.enabled bool false.caps.config.image.services.store.incompatible.level int32 0.caps.config.image.settings entry.caps.config.image.settings.enabled bool true.caps.config.image.settings.downsample bool true.caps.config.image.settings.resIR int32 160.caps.config.image.sysimg entry.caps.config.image.sysimg.alarms entry.caps.config.image.sysimg.alarms.enabled bool true.caps.config.image.sysimg.alarms.measfunc entry.caps.config.image.sysimg.alarms.measfunc.enabled bool true.caps.config.image.sysimg.alarms.measfunc.maxCount int32 3.caps.config.image.sysimg.alarms.humidity entry.caps.config.image.sysimg.alarms.humidity.enabled bool false.caps.config.image.sysimg.alarms.humidity.maxCount int32 1.caps.config.image.sysimg.alarms.insulation entry.caps.config.image.sysimg.alarms.insulation.enabled bool false.caps.config.image.sysimg.alarms.insulation.maxCount int32 1.caps.config.image.sysimg.irMarkers entry.caps.config.image.sysimg.irMarkers.enabled bool false.caps.config.image.sysimg.irMarkers.spot entry.caps.config.image.sysimg.irMarkers.spot.enabled bool false.caps.config.image.sysimg.irMarkers.spot.maxCount int32 0.caps.config.image.sysimg.irMarkers.arrow entry.caps.config.image.sysimg.irMarkers.arrow.enabled bool true.caps.config.image.sysimg.irMarkers.arrow.maxCount int32 0.caps.config.image.sysimg.irMarkers.box entry.caps.config.image.sysimg.irMarkers.box.enabled bool false.caps.config.image.sysimg.irMarkers.box.maxCount int32 0.caps.config.image.sysimg.measureFuncs entry.caps.config.image.sysimg.measureFuncs.enabled bool true.caps.config.image.sysimg.measureFuncs.diff entry.caps.config.image.sysimg.measureFuncs.diff.enabled bool true.caps.config.image.sysimg.measureFuncs.diff.maxCount int32 1.caps.config.image.sysimg.measureFuncs.diff.calcMask int32 65526.caps.config.image.sysimg.measureFuncs.isotherm entry.caps.config.image.sysimg.measureFuncs.isotherm.enabled bool true.caps.config.image.sysimg.measureFuncs.isotherm.calcMask int32 20.caps.config.image.sysimg.measureFuncs.isotherm.dual bool false.caps.config.image.sysimg.measureFuncs.isotherm.fixScale bool false.caps.config.image.sysimg.measureFuncs.isotherm.interval bool true.caps.config.image.sysimg.measureFuncs.isotherm.invInterval bool false.caps.config.image.sysimg.measureFuncs.isotherm.maxCount int32 1.caps.config.image.sysimg.measureFuncs.mbox entry.caps.config.image.sysimg.measureFuncs.mbox.enabled bool true.caps.config.image.sysimg.measureFuncs.mbox.calcMask int32 1924.caps.config.image.sysimg.measureFuncs.mbox.maxCount int32 3.caps.config.image.sysimg.measureFuncs.mcircle entry.caps.config.image.sysimg.measureFuncs.mcircle.enabled bool false.caps.config.image.sysimg.measureFuncs.mcircle.calcMask int32 1924.caps.config.image.sysimg.measureFuncs.mcircle.maxCount int32 1.caps.config.image.sysimg.measureFuncs.mline entry.caps.config.image.sysimg.measureFuncs.mline.enabled bool false.caps.config.image.sysimg.measureFuncs.mline.calcMask int32 1924.caps.config.image.sysimg.measureFuncs.mline.maxCount int32 0.caps.config.image.sysimg.measureFuncs.reftemp entry.caps.config.image.sysimg.measureFuncs.reftemp.enabled bool true.caps.config.image.sysimg.measureFuncs.reftemp.calcMask int32 1924.caps.config.image.sysimg.measureFuncs.reftemp.maxCount int32 1.caps.config.image.sysimg.measureFuncs.script entry.caps.config.image.sysimg.measureFuncs.script.enabled false.caps.config.image.sysimg.measureFuncs.script.maxCount int32 0.caps.config.image.sysimg.measureFuncs.spot entry.caps.config.image.sysimg.measureFuncs.spot.enabled bool true.caps.config.image.sysimg.measureFuncs.spot.calcMask int32 514.caps.config.image.sysimg.measureFuncs.spot.maxCount int32 3.caps.config.image.sysimg.visualMarkers entry.caps.config.image.sysimg.visualMarkers.enabled bool false.caps.config.image.sysimg.visualMarkers.spot entry.caps.config.image.sysimg.visualMarkers.spot.enabled bool false.caps.config.image.sysimg.visualMarkers.spot.maxCount int32 0.caps.config.image.sysimg.visualMarkers.arrow entry.caps.config.image.sysimg.visualMarkers.arrow.enabled bool false.caps.config.image.sysimg.visualMarkers.arrow.maxCount int32 0.caps.config.image.sysimg.visualMarkers.box entry.caps.config.image.sysimg.visualMarkers.box.enabled bool false.caps.config.image.sysimg.visualMarkers.box.maxCount int32 0.caps.config.image.targetNoise entry.caps.config.image.targetNoise.enabled bool true.caps.config.image.targetNoise.targetNoiseMk int32 55.caps.config.image.zoom entry.caps.config.image.zoom.enabled bool true.caps.config.image.zoom.maxFactor double 2.caps.config.ui entry.caps.config.ui.archive entry.caps.config.ui.archive.enabled bool true.caps.config.ui.archive.export entry.caps.config.ui.archive.export.enabled bool true.caps.config.ui.archive.sketch entry.caps.config.ui.archive.sketch.enabled bool true.caps.config.ui.archive.text entry.caps.config.ui.archive.text.enabled bool true.caps.config.ui.archive.voice entry.caps.config.ui.archive.voice.enabled bool true.caps.config.ui.fusion entry.caps.config.ui.fusion.enabled bool true.caps.config.ui.fusion.PIP entry.caps.config.ui.fusion.PIP.enabled bool true.caps.config.ui.fusion.PIP.locked bool true.caps.config.ui.laser entry.caps.config.ui.laser.enabled bool true.caps.config.ui.laser.positionMarker bool true.caps.config.ui.image entry.caps.config.ui.image.startMode text "IR".caps.config.ui.measure entry.caps.config.ui.measure.externWindow entry.caps.config.ui.measure.externWindow.enabled bool true# ID 645XXXXXFlashFS/system/ui.d/config.d/conf.cfgCode:## Generated at 2013-10-16 09:16:11#.caps entry.caps.config entry.caps.config.name text "GUI E40".caps.config.revision text "1.0".caps.config.ui entry.caps.config.ui.archive entry.caps.config.ui.archive.enabled bool true.caps.config.ui.archive.export entry.caps.config.ui.archive.export.enabled bool true.caps.config.ui.archive.sketch entry.caps.config.ui.archive.sketch.enabled bool true.caps.config.ui.archive.text entry.caps.config.ui.archive.text.enabled bool true.caps.config.ui.archive.voice entry.caps.config.ui.archive.voice.enabled bool true.caps.config.ui.fusion entry.caps.config.ui.fusion.enabled bool true.caps.config.ui.fusion.PIP entry.caps.config.ui.fusion.PIP.enabled bool true.caps.config.ui.fusion.PIP.locked bool true.caps.config.ui.laser entry.caps.config.ui.laser.enabled bool true.caps.config.ui.laser.positionMarker bool true.caps.config.ui.image entry.caps.config.ui.image.startMode text "IR".caps.config.ui.measure entry.caps.config.ui.measure.externWindow entry.caps.config.ui.measure.externWindow.enabled bool true# ID 645XXXXXCheers,

author: tomas123
author_rank: Frequent Contributor
timestamp: December 03, 2014, 08:33:58 am
content: Do you have deleted the last line?I need information about the CRC.if the last line inFlashFS/system/appcore.d/config.d/conf.cfgbegins withCode:CRC01then you must only edit this two linesCode:.caps.config.image.settings.resIR int32 160...caps.config.image.targetNoise.targetNoiseMk int32 55toCode:.caps.config.image.settings.resIR int32 320...caps.config.image.targetNoise.targetNoiseMk int32 0and generate a new CRC01use tutorial and CRC01.exe from Mikehttps://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg321956/#msg321956same good hints:- make a backup from conf.cfg- see the Flir E4 thread about editors and line breaks !! (notepad++works fine)- watch for the alphabetical order trap in folder FlashFS/system/appcore.d/config.d/https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg380267/#msg380267- test your editor and the crc01.exe:first remove the last line "CRC01 xyz" (Make sure there is exactly one CRLF at the end of the file)and then use the crc01.exe keygen for restoring the original crc(compare the result with known crc)if you habe trouble, use a hexeditor to check your CRLF- don't copy config files from another camera to your E40I don't know, why you have opened a new thread.This is exact the same (generic) process several times described in this forum (editing the config and not copying another files to the Flir camera)you can check your loaded configuration with telnetold ExxCode:> rls .registry.caps.config.image.settingsr------------- 0 root root <b> downsample falser------------- 0 root root <b> enabled truer------------- 0 root root <i> resIR 320>rls .caps.config.image.targetNoiseenabled truetargetNoiseMk 0it's possible, that you have the new pathes like Exthen you can search in your whole config withCode:rls -r -l > filename_with_path_to_your_sd_cardwait a minute until completed and open the (large) filename_with_path_to_your_sd_card in your editorPS: some users prefer to switch off the noise generatorCode:.caps.config.image.targetNoise.enabled bool false

author: ElectroTuna
author_rank: Contributor
timestamp: December 03, 2014, 06:41:01 pm
content: Thanks. I will try this and report back. I assume also that I can get the Thermal Fusion and maximum zoom by changing the appropriate fields:.caps.config.image.zoom.maxFactor double 2and.caps.config.ui.fusion.PIP.locked bool trueI have the CRC01 fields in my config files, which means they are not encrypted I guess. I will back everything up and try it.Are the latest Firmwares encrypted? I assume that I should NOT upgrade my firmware.

author: ElectroTuna
author_rank: Contributor
timestamp: December 04, 2014, 04:42:27 am
content: I got the resolution to work!But no Thermal Fusion...I thought I was changing the right field, but alas, it doesn't show up...I also have another strange issue. I have one bad pixel on the screen (Which was there from the beginning). This pad pixel is always at the same temperature (27C) which means when I am looking at cold surfaces, my spot measurement always jumps to it as the highest temperature on the screen... Very annoying issue.My thought was to perhaps modify the calibration file, but I am not able to open it. I know it is in some kind of image format, but I have no idea how to read it. My bad pixel is at (235,147) pixel, and I thought by adding it to the calibration file as another bad pixel, the camera will begin to ignore it and this problem would go away...Does anyone else have this issue?Cheers,

author: tomas123
author_rank: Frequent Contributor
timestamp: December 04, 2014, 08:56:00 am
content: bad pixel:Quote from: mrflibble on November 10, 2013, 07:46:59 pmyou can see severals clustersyou can simple readout your calibration mapping imageslook for *.fff files in threadhttps://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardownlike ds250C_we_ap_fi_le_static.fff and ds250C_we_ap_fi_le_static.ganhttps://www.google.de/#q=site:eevblog.com%2Fforum%2Ftestgear%2Fflir-e4-thermal-imaging-camera-teardown+ds250C_we_ap_fi_le_staticyou can convert this *.fff files with exiftool to png and count your bad pixelsrls helpsseehttps://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/?action=dlattach;attach=84060Code:.calib.detector.deadPixMap: (2)rw-dr---r---np 0 root root <x> ds250C_we_ap_fi_lerw-dr---r---np 0 root root <x> ds_we_ap_fi_le.calib.detector.deadPixMap.ds250C_we_ap_fi_le: (2)rw--rw-------p*0 root root <a> fileName "ds250C_we_ap_fi_le_static.gan"rw--rw-------p*0 root root <i> type 100.calib.detector.deadPixMap.ds_we_ap_fi_le: (2)rw--rw-------p*0 root root <a> fileName "ds_we_ap_fi_le.dpx"rw--rw-------p*0 root root <i> type 100

author: ElectroTuna
author_rank: Contributor
timestamp: December 04, 2014, 09:15:16 am
content: Thanks Tomas, I'll take a look.Still not able to get Thermal Fusion... I know I've troubled you a lot already, but do you know which field needs to change for Thermal Fusion to show up?

author: tomas123
author_rank: Frequent Contributor
timestamp: December 04, 2014, 09:18:18 am
content: do you mean MSX?the current E40 hardware (late 2013) has MSX on boardhttp://www.flir.com/uploadedFiles/Thermography_USA/Products/Product_Literature/flir-e-series-datasheet.pdfyou wroteQuote from: ElectroTuna on November 20, 2014, 04:39:47 amyour E40 ref 1.0 fw 3.18.0 (Late 2013) with MSXmy E40 ref 0.10 fw 2.23.14 (Late 2012) without MSXI thought, that the last firmware for old E40 hardware (without MSX) is 2.23.14Quote from: tomas123 on December 02, 2014, 04:02:24 pmfor old E40 I activated fusion and pdf inCode:\flashfs\system\ui.d\config.d\conf.cfg....caps.config.mode.radiometricVideo bool true.caps.config.fusion.thermal.enabled bool true.caps.config.fusion.thermal.auto bool true.caps.config.fusion.thermal.interval bool true.caps.config.fusion.thermal.above bool true.caps.config.fusion.thermal.below bool true.caps.config.report.createPdf bool true...look for this strings in your config filesbest entry isCode:rls -r -land grep fusionwith rls you can find hidden unknown switches but not all workshere is the corresponding part for the file above (old E40)\flashfs\system\ui.d\config.d\conf.cfgCode:.ui.caps.config.fusion: (3)rw--r--------- 0 root root <e> PIPr---r--------- 0 root root <b> enabled truerw--r--------- 0 root root <e> thermal.ui.caps.config.fusion.PIP: (2)r---r--------- 0 root root <b> enabled truer---r--------- 0 root root <b> locked true.ui.caps.config.fusion.thermal: (5)r---r--------- 0 root root <b> above falser---r--------- 0 root root <b> auto falser---r--------- 0 root root <b> below falser---r--------- 0 root root <b> enabled falser---r--------- 0 root root <b> interval false.ui.caps.config.mode: (5)r---r--------- 0 root root <b> enabled truer---r--------- 0 root root <b> panorama falser---r--------- 2 root root <b> program falser---r--------- 0 root root <b> radiometricVideo falser---r--------- 2 root root <b> video true.ui.caps.config.report: (2)r---r--------- 0 root root <b> createPdf falser---r--------- 0 root root <b> enabled truewatch for the syntax of the config filesyou must go every step with "entry"!!

author: tomas123
author_rank: Frequent Contributor
timestamp: December 04, 2014, 11:30:19 am
content: Quote from: ElectroTuna on December 04, 2014, 04:42:27 amPlease take the time and write a good tutorial for upgrading the E40 Late 2013 and link it in the first post of this threadthank you

author: ElectroTuna
author_rank: Contributor
timestamp: December 04, 2014, 06:10:11 pm
content: Quote from: tomas123 on December 04, 2014, 11:30:19 amI will.By the way, by thermal fusion, I mean like this:https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg426832/#msg426832I'll try the changes you suggested above to see if I can get this feature.

author: tomas123
author_rank: Frequent Contributor
timestamp: December 04, 2014, 10:36:45 pm
content: in your config files I seeCode:.caps.config.image.framegrab.fusion.pip entry.caps.config.image.framegrab.fusion.pip.enabled bool trueandCode:.caps.config.ui.fusion.PIP entry.caps.config.ui.fusion.PIP.enabled bool true.caps.config.ui.fusion.PIP.locked bool trueas entry point for fusionwatch my post above for syntax detailsPS: do you really want to use fusion instead of MSX ?

author: ElectroTuna
author_rank: Contributor
timestamp: December 04, 2014, 11:31:52 pm
content: Quote from: tomas123 on December 04, 2014, 10:36:45 pmThomas, sorry, I am confused. You are really familiar with the details of this stuff, but some of this stuff is foreign to me.I was under the impression that Thermal Fusion will be an added option in the image type selection, and it won't replace MSX. After all, why can't you have both?Unfortunately, I am still not sure which fields I must change to enable that... I don't know what 'rls' actually is.As for calibration, I found a way (thanks to your comments) to read my cal files with Matlab. I plan to add a new 'dead pixel' to my cal file and hope that the camera will then remove that annoying dead pixel from my images. Once I am successful I will post a tutorial for that too along with everything else (and credit you as well of course).

author: ElectroTuna
author_rank: Contributor
timestamp: December 05, 2014, 07:07:41 am
content: Tomas,Do the calibration image files have some kind of checksum? I modified the field for the deadpixel, but then I lose the whole calibration completely... I have to restore the original files before it goes back to normal.

author: tomas123
author_rank: Frequent Contributor
timestamp: December 05, 2014, 08:22:46 am
content: Quote from: ElectroTuna on December 04, 2014, 11:31:52 pmYes you can have both, but do you need thermal fusion (feature junkie)?simple edit the lines, as described aboveQuote from: ElectroTuna on December 05, 2014, 07:07:41 amplease describe exactly, what do you have modified and the result of lost calibrationthe is calibration of temperature parametersfor details see my excel sheet herehttp://u88.n24.queensu.ca/exiftool/forum/index.php/topic,4898.msg27546.html#msg27546Quote from: tomas123 on December 04, 2013, 02:23:30 pm...and a bad pixel mapping

author: Fraser
author_rank: Super Contributor
timestamp: December 05, 2014, 12:17:12 pm
content: Thanks to all for another very interesting thermal camera thread. I am a long term owner of an E4 but the comments on modifying the bad pixel map is of great interest in case it is needed in the future. I own a TEST 880-1 that has three dead pixels visible so I will be taking a look at that cameras software soon to see if its map is accessible. Different camera but hopefully the same principles fro dead pixel mapping. Keep up the good work.Aurora

author: tomas123
author_rank: Frequent Contributor
timestamp: December 05, 2014, 01:49:07 pm
content: Quote from: ElectroTuna on December 05, 2014, 07:07:41 amalle config-txt-files have checksumsconfig files uses CRC32sample in bashCode:a crc32 sample on command line// count lines$ wc -l FlashFS/system/calib.rsc801 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)ef8f7e0eor search crc32 inhttps://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown

author: tomas123
author_rank: Frequent Contributor
timestamp: December 05, 2014, 02:03:35 pm
content: Quote from: Aurora on December 05, 2014, 12:17:12 pmFirmware_FlirE4\FlashFS\system\calib.rscCode:.calib.detector.deadPixMap entry.calib.detector.deadPixMap.ds250C_we_ap_fi_le index.calib.detector.deadPixMap.ds250C_we_ap_fi_le.fileName text "ds250C_we_ap_fi_le_static.gan"\FlashFS\system\maps\ds250C_we_ap_fi_le_static.ganuse exiftool and imagemagickCode:>exiftool ds250C_we_ap_fi_le_static.ganExifTool Version Number : 9.75File Name : ds250C_we_ap_fi_le_static.ganDirectory : .File Size : 151 kBFile Type : FLIRMIME Type : application/unknownCreator Software :Gain Dead Map Image Width : 320Gain Dead Map Image Height : 240Gain Dead Map Image Type : TIFFGain Dead Map Image : (Binary data 153804 bytes, use -b option to extract)> exiftool -b -GainDeadMapImage ds250C_we_ap_fi_le_static.gan > 1.tif>identify 1.tif1.tif TIFF 320x240 320x240+0+0 16-bit Grayscale Gray 154KB 0.000u 0:00.000> convert 1.tif -depth 8 1.pngthe next step is trickysee the exiftool documenationhttp://cpansearch.perl.org/src/EXIFTOOL/Image-ExifTool-9.76/lib/Image/ExifTool/FLIR.pmthe embedded image is a 16 bit raw binaryexiftool add a tif header to the raw datas (uncompressed 16 bit tif)the best way is to poke the additional bad pixels direct to ds250C_we_ap_fi_le_static.gan with a hexeditor- open the tif in an image editor and edit the additional pixels- save as (uncompressed) 16 bit tif (or use imagemagick convert)- find the binary differences of the pixels and poke them with an hexeditor to ds250C_we_ap_fi_le_static.gan

author: Fraser
author_rank: Super Contributor
timestamp: December 05, 2014, 02:10:43 pm
content: @tomas123,Thank youAurora

author: ElectroTuna
author_rank: Contributor
timestamp: December 05, 2014, 06:29:43 pm
content: Tomas,I did exactly what you said a few days ago as well.But there are some interesting additional issues:1) In my 'map' directory, I have three files which the camera seems to use for calibration and bad pixel. One of them has the term '120C' and the other '650C' both with .gan extensions. There is also a third file, with a .dpx extension.2) Flir Tools can open ALL these files and you can see dead pixels. I can also read them with Matlab or with a hex editor.3) My .dpx file is identical to the '120C' file, but the '650C' file has much more bad pixels in it. It looks like the calibration matrix is difference when the camera is set to different temperature ranges. Although I am not 100% sure yet what the purpose of the .dpx file is.4) I tried changing the field which corresponds to my bad pixel and modified it in all three files. But after I saved the files, the camera lost all calibration and many bad pixels showed up. I had to restore it back to original.This is where I am now. So it seems there is more to it than just changing the fields.In the EXIF documentation, I see the following:Code:# set file type if reading from FFF or SEQ file ($tagTablePtr will not be defined)$et->SetFileType($type eq 'FFF' ? 'FLIR' : 'SEQ') unless $tagTablePtr;# FLIR file header (ref 3)# 0x00 - string file format ID = "FFF\0"# 0x04 - string file creator: seen "\0","MTX IR\0","CAMCTRL\0"# 0x14 - int32u file format version = 100# 0x18 - int32u offset to record directory# 0x1c - int32u number of entries in record directory# 0x20 - int32u next free index ID = 2# 0x24 - int16u swap pattern = 0 (?)# 0x28 - int16u spares# 0x34 - int32u reserved# 0x3c - int32u checksumThe last line hints at a checksum. Perhaps after 'poking' the dead pixel, a new checksum is needed, otherwise the camera assumes the file is corrupt and this destroys the calibration procedure. Had I not saved a backup of my calibration files, I would have ruined it.

author: tomas123
author_rank: Frequent Contributor
timestamp: December 06, 2014, 02:19:27 am
content: sorry, I forgot it because the checksum is ignored by flir tools and exiftoolsas attachment the document for calculating the checksumCode:unsigned long dwChecksum; /* Data checksum 4 32 bytes */dwChecksum is checksum of tag data block. It may be set to0 when not used.When used, 2 types of checksums are allowed:1) Type 1 for longword aligned data:dwChecksum & 0xC0000000 == 0x80000000.Checksum is calculated as the sum of all 32-bit longwords in thetag data block given by dwDataPtr and dwDataSize modulo 0x20000000or'ed with 0x8000 0000 (MSB always set, MSB-1 always 0).2) For possible odd number of bytes in tag data, algorithm 2 exists:dwChecksum & 0xC0000000 == 0x40000000.Checksum is calculated as the sum of all bytes in thetag data block given by dwDataPtr and dwDataSize modulo 0x20000000or'ed with 0x4000 0000 (MSB always set, MSB-1 always 0).*/but first tryCode:"Checksum may be set to 0 when not used."the different map file names comes from range:E4 250 °C temp. rangeE40 120 and 650°C temp. rangePS: on shell there is a interesting commandQuote

author: tomas123
author_rank: Frequent Contributor
timestamp: December 06, 2014, 02:33:12 am
content: Do have tried the service menu of E40?http://192.168.64.1/service/index.asplogin: flirpw: 3vligthen activate Service Modethere you can also map the dead pixelPS: I never used the EEPROM unlock password: 1235fast way to count the mapped bad pixel:first convert ds120C_we_ap_fi_le_static.gan with exiftool and IMthenCode:$ identify -verbose ds120C.gifHistogram:17: ( 0, 0, 0) #000000 black76783: (255,255,255) #FFFFFF whiteColormap: 256

author: tomas123
author_rank: Frequent Contributor
timestamp: December 06, 2014, 03:20:31 am
content: ah I see, that the current fw of E40 Late 2013v4.9.0has no service menuthe important files for mapping bad pixels from old E40 FW 2.23.14Code:$ ls flir_exx_pn490_v2.23.14_update_pack/E2comb_v2.23.14.fif/FlashFS/system/web/service/ImgCorrActivateDigFilters.aspGainMapResult.aspOperability.aspStaticMap.aspStaticMapResult.aspGainMap.aspGainMapSelCase.aspOperabilityLog.aspStaticMapCalc.aspStaticMapWarm.aspGainMapCalc.aspGainMapWarm.aspPixKill.aspStaticMapCold.aspgainmapcalcGF.aspGainMapCold.aspImgCorrSelCase.aspShutterMap.aspStaticMapPrepare.aspindex.aspsee here for links to this fileshttps://www.eevblog.com/forum/testgear/flir-e40-upgrade-configuration/msg561542/#msg561542you can simple read the html files of the old FW and make the same steps on the shell (setResourceValue = rset)sample:search for activating the service mode in Web GUI (file nameHighRes.asp = full resolution):Code:$ cd flir_exx_pn490_v2.23.14_update_pack/E2comb_v2.23.14.fif/FlashFS/system/web$ grep -i -r highres *service/Diag/HighRes.asp: restree.setResourceValue( "prod.preparation.command", "restartHighRes" );service/inc/servicemenu.inc:menuRow("Activate Service Mode", "/service/Diag/HighRes.asp", "submenu1", selectedMenu == "mnuDiagResolution");service/index.asp: <FORM ACTION=diag\HighRes.asp METHOD="POST">we getCode:restree.setResourceValue( "prod.preparation.command", "restartHighRes" );and this is the same command on the shellCode:#start HighRes Modus>rset prod.preparation.command restartHighReson the old E40 the commandrestartHighResperform following 2 steps:(1) copy service config files and folders from/FlashFS/system/service/appcore.dto/Temp/appcore.dand calculate a new CRC01 checksum for the copied config files (it's aintegrated crc01 keygen)(2) boot Exx to full resolution over restartapp.batCode:$ cat flir_exx_pn490_v2.23.14_update_pack/E2comb_v2.23.14.fif/FlashFS/system/restartapp.batset PATH=\windows;\FlashFS\system\;rset .watchdog.enable falserset .services.log.active falseps -k Prodps -k prodps -k uicoreps -k Guips -k MediaServerps -k appcoreps -k AppServicesps -k Resmonps -k Bitps -k syslogps -k Camps -k camps -k genips -k digps -k Digps -k watchps -k Watchps -k RTPps -k fwaps -k progressps -k Meddelay 1start appcoredelay 10start prodappNot all listed processes are running!for better understanding of the restartapp.bat I will illuminatethe Exx boot process:(1) start the windows ce (NK.bin)(2) over a windows registry entry CE starts the flir batch file FlashFS/system/applaunch.dat(3) applaunch.dat start the appcore.exe(4) appcore.exe start the Flir binaries (like the Flir GUI)after booting we get this process listCode:\>psProcess NK.EXE (87 threads), id 0x00400002, loaded at 0x88190000Process udevice.exe ( 1 threads), id 0x01550002, loaded at 0x00010000Process udevice.exe ( 2 threads), id 0x01630002, loaded at 0x00010000Process udevice.exe ( 1 threads), id 0x01F20002, loaded at 0x00010000Process udevice.exe ( 1 threads), id 0x03BF0002, loaded at 0x00010000Process servicesd.exe (18 threads), id 0x04030002, loaded at 0x00010000Process cmd.exe ( 1 threads), id 0x05000006, loaded at 0x00010000Process appcore.exe (35 threads), id 0x05530006, loaded at 0x00010000Process AppServices.exe (17 threads), id 0x070D0006, loaded at 0x00010000Process Resmon.exe (12 threads), id 0x07260006, loaded at 0x00010000Process MediaServer.exe (15 threads), id 0x07380006, loaded at 0x00010000Process uicore.exe ( 9 threads), id 0x07850006, loaded at 0x00010000Process CMD.EXE ( 1 threads), id 0x090C0046, loaded at 0x00010000Process ps.EXE ( 1 threads), id 0x04C1001E, loaded at 0x00010000i.e. the command "ps -k uicore" from restartapp.bat kills the process uicore.exeapplaunch.dat old E40 FW v2.23.14Code:$ cat flir_exx_pn490_v2.23.14_update_pack/E2comb_v2.23.14.fif/FlashFS/system/applaunch.dat# Show intro bootlogo and start progressprogressapp -f \flashfs\system\bootlogo.bmp# Start command shell on the RS-232 portcmd /R# Register a default userdefaultusr# Start appcore. Appcore starts other necessary processesappcoreand now with some new CRC checks in FWv4.9.0against hacking in E40 Late 2013Code:$ cat flir_exx_pn645_pn646_v4.9.0_update_pack/E2qtcomb_v4.9.0.fif/FlashBFS/system/applaunch.dat# Show intro bootlogo and start progressprogressapp -f \flashbfs\system\bootlogo.bmp -d1# Start command shell on the RS-232 portcmd /R# Register a default userdefaultusr# Start appcore. Appcore starts other necessary processesappcore# doCRC FlashBFS\system\appcore.exe 1819648 214275933# doCRC FlashBFS\system\common_dll.dll 1225216 3648436271# doCRC FlashBFS\system\appcore_dll.dll 708608 3728193282# doCRC FlashBFS\system\progressapp.exe 29184 4017170338# doCRC FlashBFS\system\defaultusr.exe 5120 1997273047# doCRC FlashBFS\system\chargeapp.exe 32768 1583842125# doCRC FlashBFS\system\ui.d\design_ui_E2.xml 54099 4047603580# doCRC FlashBFS\system\ui.d\facet_E2.rcc 861107 3311570564# doCRC FlashBFS\system\ui.d\toolbar-config_E2.xml 6522 1692081231# doACRC FlashBFS\system\appcore.exe 1819648 2566311456# doACRC FlashBFS\system\common_dll.dll 1225216 1513280386# doACRC FlashBFS\system\appcore_dll.dll 708608 3192873875# doACRC FlashBFS\system\progressapp.exe 29184 3808303586# doACRC FlashBFS\system\defaultusr.exe 5120 2154779382@ ElectroTunaContains your FW3.18.0(E40 1.0) in applaunch.dat also the anti hack doACRC part??If not, then you still have the web front end with the service menu and my explanation was unnecessaryQuote from: Taucher on February 05, 2014, 06:18:35 pmPS: I hope you have now enough informations for understanding and hacking a E40

author: ElectroTuna
author_rank: Contributor
timestamp: December 06, 2014, 05:06:10 am
content: Jesus Tomas! You should write a book!I have the resolution enabled, the magnifying ability up to X4 (from X2) and I have turned the noise off. I still don't have that stupid Thermal Fusion. I will try a few other things.I am also working on a simple way of injecting bad pixels manually and either regenerating the CRC or using that ignore CRC option.I don't seem to have the files for the web access. I did use Telnet to connect to the camera and I do see the processes running with 'ps'.

author: ElectroTuna
author_rank: Contributor
timestamp: December 06, 2014, 05:14:33 am
content: These lines added to both config files did NOT enable thermal fusion:.caps.config.ui.fusion.thermal entry.caps.config.ui.fusion.thermal.enabled bool true.caps.config.ui.fusion.thermal.auto bool true.caps.config.ui.fusion.thermal.interval bool true.caps.config.ui.fusion.thermal.above bool true.caps.config.ui.fusion.thermal.below bool true

author: ElectroTuna
author_rank: Contributor
timestamp: December 06, 2014, 05:28:45 am
content: This is my header for my calibration file: (In hex)Code:46 46 46 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 64 00 00 00 40 00 00 00 0e00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 02 5a 20 00 00 00 00 e0 b5 cc a100 05 00 02 00 00 00 64 00 00 00 01 00 00 02 0000 02 58 20 00 00 00 00 00 00 00 00 ba de ee fe00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0002 00 40 01 f0 00 00 00 00 00 00 00 3f 01 00 00ef 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00Which hex segments are the CRC?! Man, I am going crazy!

author: tomas123
author_rank: Frequent Contributor
timestamp: December 06, 2014, 11:19:21 am
content: Quote from: ElectroTuna on December 06, 2014, 05:14:33 amI can't guess, what do you make wrong, if you only post snippets.There are some syntax restrictions and CRC pitfalls.You must learn to check the loaded configuration with "rls"!see my post abovehint from old E40:The fastet way to load configurations is using temp path for config files and the script restartapp.batAfter full reboot the camera is restored to standard configurationYou don't give me the asked informations about your firmware!clone your filesystem with ftp and post the directory listingor post appkit.rev and prodkit.rev

author: tomas123
author_rank: Frequent Contributor
timestamp: December 06, 2014, 11:22:09 am
content: Quote from: ElectroTuna on December 06, 2014, 05:28:45 amI'm disappointed64 Byte HeaderQuote from: ElectroTuna on December 05, 2014, 06:29:43 pm0x00: 46 46 46= FFF0x3c: e0 b5 cc a1and the next checksum is in the 32 Byte indexsee pdf aboveCode:typedef struct tagFLIRFILEINDEX-> ba de ee feedit:first try zeroing the checksum

author: ElectroTuna
author_rank: Contributor
timestamp: December 07, 2014, 04:32:45 am
content: Sorry Tomas, I was too haste in my questions.Unfortunately setting the CRC field (ba de ee fe) to (00 00 00 00) does not work. I guess the CRC needs to be re-calculated.

author: ElectroTuna
author_rank: Contributor
timestamp: December 07, 2014, 06:18:03 am
content: I am working on re-calculating the CRC based on this:Code:Type 1 for longword aligned data:dwChecksum & 0xC0000000 == 0x80000000.Checksum is calculated as the sum of all 32-bit longwords in thetag data block given by dwDataPtr and dwDataSize modulo 0x20000000 or'ed with 0x80000000 (MSB always set, MSB-1 always 0).This means taking data from positon 0x200 in the file all the way to the end in 32-bit chunks and summing them all up. Then the final sum value is modulo 0x20000000 and finally or'ed with 0x80000000 which sets the MSB to 1.But the CRC I get is not the same as the one in the file...

author: tomas123
author_rank: Frequent Contributor
timestamp: December 07, 2014, 10:52:26 am
content: Quote from: ElectroTuna on December 07, 2014, 06:18:03 amnot to the end - look for dwDataSizeadd longword (4 Byte) as you wroteCode:00 05 Type FFF_TAGID_GainDeadMap = 5,00 02 wSubType00 00 00 64 dwVersion00 00 00 01 dwIndexID00 00 02 00 dwDataPtr 0x0000020000 02 58 20 dwDataSize 0x0002582000 00 00 00 dwParent00 00 00 00 dwObjectNrba de ee fe dwChecksum 0xBADEEEFE

author: ElectroTuna
author_rank: Contributor
timestamp: December 07, 2014, 08:02:10 pm
content: Tomas,The initial index, plus the data size takes us to the very end of the file. 0x25820 is 153,6832 bytes, which is 32 bytes more than the resolution in 16-bit numbers (320*240*2).I am using Matlab:QuoteRemember that Matlab array indexes start from 1.

author: tomas123
author_rank: Frequent Contributor
timestamp: December 07, 2014, 09:44:22 pm
content: Phil (Exiftool) and I both reengineered all the known Flir stuff last two years.I haven't enough time check the algorithm but I'm absolute sure that the pdf is the right key.I suggest first hack the dwChecksum of tagFLIRFILEHEAD (the Head & index checksum )there are only a few byteCode:46 46 46 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 64 00 00 00 40 00 00 00 0e00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 02 5a 20 00 00 00 00 00 00 00 0000 05 00 02 00 00 00 64 00 00 00 01 00 00 02 0000 02 58 20 00 00 00 00 00 00 00 00 00 00 00 00flir sometimes use a reversed byte order in the data stream (usSwapPattern)see herehttps://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg348398/#msg348398

author: tomas123
author_rank: Frequent Contributor
timestamp: December 08, 2014, 09:42:38 am
content: I also can't calculate the checksum of the headersee attachmentyou have not posted your file listappkit.revandprodkit.revnext tryhttps://www.eevblog.com/forum/testgear/flir-e40-upgrade-configuration/msg563460/#msg563460Code:>rset prod.preparation.command xyz

author: tomas123
author_rank: Frequent Contributor
timestamp: December 08, 2014, 10:04:10 am
content: on my PC I found the old FW v3.12.7 for your E40 Late 2013 ( FLIR Exx P/N:645xx / 646xx )flir_exx_pn645_pn646_v3.12.7_update_pack.zipand there are all files for WebGUI insideCode:> dir flir_exx_pn645_pn646_v3.12.7_update_pack\E2qtcomb_v3.12.7\FlashBFS\system\web\service\Calib21.08.2013 20:23 2.331 AccMeas.asp21.08.2013 20:23 9.743 AccMeasMeasure.asp21.08.2013 20:23 515 AccMeasProtocol.asp21.08.2013 20:23 4.725 AccMeasRemove.asp21.08.2013 20:23 10.017 AccMeasSelect.asp21.08.2013 20:23 8.231 AccMeasSetObjpar.asp12.09.2013 12:01 4.203 CalibAcc.asp21.08.2013 20:23 1.067 index.asp21.08.2013 20:23 3.427 SysCalib.asp21.08.2013 20:23 7.762 SysCalibActivate.asp21.08.2013 20:23 6.841 SysCalibAddLensCase.asp21.08.2013 20:23 12.181 SysCalibCalculate.asp21.08.2013 20:23 13.272 SysCalibEditLimits.asp21.08.2013 20:23 9.292 SysCalibEditMeas.asp21.08.2013 20:23 6.244 SysCalibEnaDisa.asp21.08.2013 20:23 3.954 SysCalibFarFocus.asp21.08.2013 20:23 8.372 SysCalibMeasure.asp21.08.2013 20:23 513 SysCalibProtocol.asp21.08.2013 20:23 6.154 syscalibRangeEnaDisa.asp21.08.2013 20:23 9.998 SysCalibSelect.asp21.08.2013 20:23 5.895 SysCalibSwitch.asp21.08.2013 20:23 12.171 transmission.asp22 Datei(en), 146.908 BytesCode:> dir flir_exx_pn645_pn646_v3.12.7_update_pack\E2qtcomb_v3.12.7\FlashBFS\system\web\service\ImgCorr21.08.2013 20:23 7.123 ActivateDigFilters.asp21.08.2013 20:23 2.882 GainMap.asp21.08.2013 20:23 9.935 GainMapCalc.asp21.08.2013 20:23 5.588 gainmapcalcGF.asp21.08.2013 20:23 5.819 GainMapCold.asp21.08.2013 20:23 9.655 GainMapResult.asp21.08.2013 20:23 2.385 GainMapSelCase.asp21.08.2013 20:23 2.689 GainMapWarm.asp21.08.2013 20:23 6.803 ImgCorrSelCase.asp21.08.2013 20:23 1.566 index.asp21.08.2013 20:23 5.246 Operability.asp21.08.2013 20:23 1.684 OperabilityLog.asp04.09.2013 12:22 47.416 PixKill.asp21.08.2013 20:23 5.660 ShutterMap.asp21.08.2013 20:23 1.558 StaticMap.asp21.08.2013 20:23 5.138 StaticMapCalc.asp21.08.2013 20:23 7.070 StaticMapCold.asp21.08.2013 20:23 3.144 StaticMapPrepare.asp21.08.2013 20:23 8.810 StaticMapResult.asp21.08.2013 20:23 3.864 StaticMapWarm.asp20 Datei(en), 144.035 Bytesas attachment the relevant part (file size limit here is 1mb)rename to zipwatch for the full file list of the firmware v3.12.7 in folder kits.d (appkit.revandprodkit.rev)some screenshots from the bad pixel mapping procedureQuote

author: tomas123
author_rank: Frequent Contributor
timestamp: December 08, 2014, 11:32:49 am
content: wow,I found a menu, where you canreplace single dead pixels!the page only work with internet explorer ( no firefox or chrome)Select a methodshow all bad pixels (currently mapped)kill a single bad pixel

author: Fraser
author_rank: Super Contributor
timestamp: December 08, 2014, 12:07:14 pm
content: Tomas123,Excellent findings Sir !Hopefully the E4 Service Menu operates in a similar manner. Being able to kill individual bad pixels, as they occur, is an excellent capability to have. Microbolometers are qhite relaible but, just like a CCD cell, you can suffer individual pixel failures over time.Reference Blackbodies...... I have been looking at making some as the commercial units are very expensive and even then, teh chepaer types using hot air and flat plate radiators are a pretty uneven surface for calibration. Ok for checking accuracy though. Whne searching for "Blackbody" on ebay or Google I was presented with all manner of interesting imagesI suggest serches on "IR calibration source" is a safer optionAurora

author: Chanc3
author_rank: Frequent Contributor
timestamp: December 09, 2014, 01:05:51 pm
content: If it helps, I have both the E60 2012 and 2014 model, so I can share the files if anyone needs them.I know this thread is just for the Exx range, but the pixel correction/service menu also works on the T6xx and SC6xx range of IR cameras.

author: tomas123
author_rank: Frequent Contributor
timestamp: December 09, 2014, 03:55:01 pm
content: greatPlease post the config files from your E60 (2014)Which firmware do you have?the original config files from E60 (2012) we got last year from user funzt (he rent a E60)Quote from: funzt on November 28, 2013, 04:35:43 pmhe killed the serial in the filesCode:# ID 490xxxxx# CRC01 xxxxxxxx

author: Chanc3
author_rank: Frequent Contributor
timestamp: December 09, 2014, 04:09:32 pm
content: Quote from: tomas123 on December 09, 2014, 03:55:01 pm

author: ElectroTuna
author_rank: Contributor
timestamp: December 09, 2014, 05:46:01 pm
content: Last when I tried, I could not get the website to work. I will also post my files as Tomas requested. I have been busy, I'll take a look again tonight. I really need to get the dead-pixel removed, it really makes the camera's temperature cursor useless.

author: Chanc3
author_rank: Frequent Contributor
timestamp: December 09, 2014, 08:39:48 pm
content: Quote from: ElectroTuna on December 09, 2014, 05:46:01 pmWhen you say you cannot get it to work, what have you tried?Camera in Network mode (RSNVC or something like that)Plug into PCThen you normally connect to 192.168.0.2 - if this doesn't work, go to Run > CMD. Type ipconfig /all and it should list the network adaptors currently connected. You should see you camera in there, find the default gateway IP for it, then plug that into internet explorer.

author: tomas123
author_rank: Frequent Contributor
timestamp: December 09, 2014, 10:21:41 pm
content: my experience:connect Exx over a router with wlan, it's a bulletproof method (instead USB RNDIS and driver)

author: Chanc3
author_rank: Frequent Contributor
timestamp: December 11, 2014, 09:15:58 am
content: Still waiting for my colleague to get back with the E60 2012 model. Surprisingly, whilst it doesn't have MSX, it has more measurement features than the newer model...

author: ElectroTuna
author_rank: Contributor
timestamp: December 12, 2014, 05:52:35 am
content: Hi Tomas,Thanks for posting your web files! I am one step closer to get this thing working. I copied your web directly and over-wrote my own. I replaced no other files.Please see attached screenshot.The web pages take forever to load, and as you can see I am missing the necessary service to be able to perform this task. I also posted the other files you requested.Thanks again for continuing to help me out. I am sure we can get this camera to work!

author: tomas123
author_rank: Frequent Contributor
timestamp: December 12, 2014, 03:38:21 pm
content: Do you activated the service mode in the menu?Read the html code and try some commands on telnetAs I wrote above, I think that not all rset commands are implemented in your firmwarehttps://www.eevblog.com/forum/testgear/flir-e40-upgrade-configuration/msg563460/#msg563460

author: ElectroTuna
author_rank: Contributor
timestamp: December 13, 2014, 09:26:42 pm
content: Quote from: tomas123 on December 12, 2014, 03:38:21 pmI followed the links from the webpage to get to the Pixel Kill page, but as you said some services may not have started. I can try digging through the HTML code like you suggested...Did you have a chance to look at the files I posted?Thanks,

author: tomas123
author_rank: Frequent Contributor
timestamp: December 14, 2014, 12:20:12 pm
content: Quote from: ElectroTuna on December 13, 2014, 09:26:42 pmyesAs presumed, your FW v3.18.0 iscrippledfor security reasons.the old firmware v3.12.7 contains all necessary partsQuote from: tomas123 on December 08, 2014, 10:04:10 amsome compares of appkit.rev between FW v3.12.7 and v3.18.0Code:$ grep "FILE" v3.12.7/appkit.rev | cut -d" " -f1-2 > v3.12.7/appkit.trim$ grep "FILE" v3.18.0/appkit.rev.txt | cut -d" " -f1-2 > v3.18.0/appkit.trim$ diff v3.12.7/appkit.trim v3.18.0/appkit.trim$ diff -y v3.12.7/appkit.trim v3.18.0/appkit.trim# format:# format:##FILE \flashbfs\system\appcore.d\factory.d\default_params.rscFILE \flashbfs\system\appcore.d\factory.d\default_params.rscFILE \flashbfs\system\appcore.d\factory.d\fusion_params.rscFILE \flashbfs\system\appcore.d\factory.d\fusion_params.rscFILE \flashbfs\system\appcore.d\factory.d\ui_archive.rscFILE \flashbfs\system\appcore.d\factory.d\ui_archive.rscFILE \flashbfs\system\appcore.d\factory.d\ui_control.rscFILE \flashbfs\system\appcore.d\factory.d\ui_control.rscFILE \flashbfs\system\appcore.d\factory.d\ui_display.rscFILE \flashbfs\system\appcore.d\factory.d\ui_display.rscFILE \flashbfs\system\appcore.d\factory.d\ui_fusion_always.rsFILE \flashbfs\system\appcore.d\factory.d\ui_fusion_always.rsFILE \flashbfs\system\appcore.d\factory.d\ui_noantialias.rscFILE \flashbfs\system\appcore.d\factory.d\ui_noantialias.rscFILE \flashbfs\system\appcore.d\factory.d\ui_pipfusion.rscFILE \flashbfs\system\appcore.d\factory.d\ui_pipfusion.rscFILE \flashbfs\system\appcore.d\factory.d\ui_remove_uicore_guFILE \flashbfs\system\appcore.d\factory.d\ui_remove_uicore_guFILE \flashbfs\system\appcore.d\factory.d\ui_start_facet.rscFILE \flashbfs\system\appcore.d\factory.d\ui_start_facet.rscFILE \flashbfs\system\appcore.exeFILE \flashbfs\system\appcore.exeFILE \flashbfs\system\appcore_dll.dllFILE \flashbfs\system\appcore_dll.dllFILE \flashbfs\system\applaunch.datFILE \flashbfs\system\applaunch.datFILE \flashbfs\system\appservices.exeFILE \flashbfs\system\appservices.exeFILE \flashbfs\system\arctic.palFILE \flashbfs\system\arctic.palFILE \flashbfs\system\battest.exeFILE \flashbfs\system\battest.exeFILE \flashbfs\system\bootlogo.bmpFILE \flashbfs\system\bootlogo.bmpFILE \flashbfs\system\bt.exeFILE \flashbfs\system\bt.exeFILE \flashbfs\system\bw.palFILE \flashbfs\system\bw.palFILE \flashbfs\system\cecompat6.dllFILE \flashbfs\system\cecompat6.dllFILE \flashbfs\system\cemgrc.exe<FILE \flashbfs\system\cerdisp.exe<FILE \flashbfs\system\cetlstub.dll<FILE \flashbfs\system\chargeapp.exeFILE \flashbfs\system\chargeapp.exeFILE \flashbfs\system\clientshutdown.exe<FILE \flashbfs\system\cmaccept.exe<FILE \flashbfs\system\colorize.exeFILE \flashbfs\system\colorize.exeFILE \flashbfs\system\combtabs.d\combtab.appkitFILE \flashbfs\system\combtabs.d\combtab.appkitFILE \flashbfs\system\common_dll.dllFILE \flashbfs\system\common_dll.dllFILE \flashbfs\system\common_unittest.exe<FILE \flashbfs\system\conmanclient2.exe<FILE \flashbfs\system\conmanclient3.exe<FILE \flashbfs\system\dbtest.exeFILE \flashbfs\system\dbtest.exeFILE \flashbfs\system\defaultusr.exeFILE \flashbfs\system\defaultusr.exeFILE \flashbfs\system\devicedma.dll<FILE \flashbfs\system\dumpcoff.exe<FILE \flashbfs\system\edbgtl.dll<FILE \flashbfs\system\facet_core.dllFILE \flashbfs\system\facet_core.dllFILE \flashbfs\system\facet_exe.exeFILE \flashbfs\system\facet_exe.exeFILE \flashbfs\system\facet_ui_qml.dllFILE \flashbfs\system\facet_ui_qml.dllFILE \flashbfs\system\fmqping.exe<FILE \flashbfs\system\fpga_b2co3.binFILE \flashbfs\system\fpga_b2co3.binFILE \flashbfs\system\fpga_c4_55.binFILE \flashbfs\system\fpga_c4_55.binFILE \flashbfs\system\freeze.exeFILE \flashbfs\system\freeze.exeFILE \flashbfs\system\ftest.exeFILE \flashbfs\system\ftest.exeFILE \flashbfs\system\fvd.dllFILE \flashbfs\system\fvd.dllFILE \flashbfs\system\fvd.exe<FILE \flashbfs\system\gethwtype.exeFILE \flashbfs\system\gethwtype.exeFILE \flashbfs\system\i2c.exe<FILE \flashbfs\system\imageformats\qgif4.dllFILE \flashbfs\system\imageformats\qgif4.dllFILE \flashbfs\system\iron.palFILE \flashbfs\system\iron.palFILE \flashbfs\system\kitcrc.exeFILE \flashbfs\system\kitcrc.exeFILE \flashbfs\system\kits.d\appkit.revFILE \flashbfs\system\kits.d\appkit.revFILE \flashbfs\system\kits.exeFILE \flashbfs\system\kits.exeFILE \flashbfs\system\lava.palFILE \flashbfs\system\lava.palFILE \flashbfs\system\level.exeFILE \flashbfs\system\level.exeFILE \flashbfs\system\mediaserver.exeFILE \flashbfs\system\mediaserver.exeFILE \flashbfs\system\mp4.dllFILE \flashbfs\system\mp4.dllFILE \flashbfs\system\nuc.exeFILE \flashbfs\system\nuc.exeFILE \flashbfs\system\palette.exeFILE \flashbfs\system\palette.exeFILE \flashbfs\system\pmic.exe<FILE \flashbfs\system\progressapp.exeFILE \flashbfs\system\progressapp.exeFILE \flashbfs\system\qtcore4.dllFILE \flashbfs\system\qtcore4.dllFILE \flashbfs\system\qtdeclarative4.dllFILE \flashbfs\system\qtdeclarative4.dllFILE \flashbfs\system\qtgui4.dllFILE \flashbfs\system\qtgui4.dllFILE \flashbfs\system\qtnetwork4.dllFILE \flashbfs\system\qtnetwork4.dllFILE \flashbfs\system\qtscript4.dllFILE \flashbfs\system\qtscript4.dllFILE \flashbfs\system\rainbow.palFILE \flashbfs\system\rainbow.palFILE \flashbfs\system\rainhc.palFILE \flashbfs\system\rainhc.palFILE \flashbfs\system\rclone.exeFILE \flashbfs\system\rclone.exeFILE \flashbfs\system\rcreate.exeFILE \flashbfs\system\rcreate.exeFILE \flashbfs\system\rdelete.exeFILE \flashbfs\system\rdelete.exeFILE \flashbfs\system\rdump.exeFILE \flashbfs\system\rdump.exeFILE \flashbfs\system\recall.exeFILE \flashbfs\system\recall.exeFILE \flashbfs\system\regsvrce.exe<FILE \flashbfs\system\resmon.exeFILE \flashbfs\system\resmon.exeFILE \flashbfs\system\restool.exeFILE \flashbfs\system\restool.exeFILE \flashbfs\system\restree.dllFILE \flashbfs\system\restree.dllFILE \flashbfs\system\rfind.exeFILE \flashbfs\system\rfind.exeFILE \flashbfs\system\rls.exeFILE \flashbfs\system\rls.exeFILE \flashbfs\system\rpatch.exeFILE \flashbfs\system\rpatch.exeFILE \flashbfs\system\rreload.exeFILE \flashbfs\system\rreload.exeFILE \flashbfs\system\rsctest.exeFILE \flashbfs\system\rsctest.exeFILE \flashbfs\system\rset.exeFILE \flashbfs\system\rset.exeFILE \flashbfs\system\rsubscr.exeFILE \flashbfs\system\rsubscr.exeFILE \flashbfs\system\rverify.exeFILE \flashbfs\system\rverify.exeFILE \flashbfs\system\sensor.d\ex845.dllFILE \flashbfs\system\sensor.d\ex845.dllFILE \flashbfs\system\sensor.d\ml2.dllFILE \flashbfs\system\sensor.d\ml2.dllFILE \flashbfs\system\sensor.d\mo297.dllFILE \flashbfs\system\sensor.d\mo297.dllFILE \flashbfs\system\services.d\factory.d\dcf.rscFILE \flashbfs\system\services.d\factory.d\dcf.rscFILE \flashbfs\system\services.d\factory.d\dcim.rscFILE \flashbfs\system\services.d\factory.d\dcim.rscFILE \flashbfs\system\services.d\factory.d\no_wzctool.rscFILE \flashbfs\system\services.d\factory.d\no_wzctool.rscFILE \flashbfs\system\services.d\factory.d\wlan_nosort.rscFILE \flashbfs\system\services.d\factory.d\wlan_nosort.rscFILE \flashbfs\system\services.d\sql.d\default.sqlFILE \flashbfs\system\services.d\sql.d\default.sqlFILE \flashbfs\system\services.d\sql.d\defaulttextfield.sqlFILE \flashbfs\system\services.d\sql.d\defaulttextfield.sqlFILE \flashbfs\system\span.exeFILE \flashbfs\system\span.exeFILE \flashbfs\system\sqlite.dllFILE \flashbfs\system\sqlite.dllFILE \flashbfs\system\stopapp.batFILE \flashbfs\system\stopapp.batFILE \flashbfs\system\store.exeFILE \flashbfs\system\store.exe>FILE \flashbfs\system\suid.exeFILE \flashbfs\system\supv.exeFILE \flashbfs\system\supv.exeFILE \flashbfs\system\syslog.exeFILE \flashbfs\system\syslog.exeFILE \flashbfs\system\taskmgr.exeFILE \flashbfs\system\taskmgr.exeFILE \flashbfs\system\tcpconnectiona.dll<FILE \flashbfs\system\tcpipc.dll<FILE \flashbfs\system\tprls.exeFILE \flashbfs\system\tprls.exeFILE \flashbfs\system\treeproxy.dllFILE \flashbfs\system\treeproxy.dllFILE \flashbfs\system\ui.d\design_ui_e2.xmlFILE \flashbfs\system\ui.d\design_ui_e2.xmlFILE \flashbfs\system\ui.d\facet_e2.rccFILE \flashbfs\system\ui.d\facet_e2.rccFILE \flashbfs\system\ui.d\fonts\gulim.ttfFILE \flashbfs\system\ui.d\fonts\gulim.ttfFILE \flashbfs\system\ui.d\fonts\mingliu.ttfFILE \flashbfs\system\ui.d\fonts\mingliu.ttfFILE \flashbfs\system\ui.d\fonts\msgothic.ttfFILE \flashbfs\system\ui.d\fonts\msgothic.ttfFILE \flashbfs\system\ui.d\fonts\simsun.ttfFILE \flashbfs\system\ui.d\fonts\simsun.ttfFILE \flashbfs\system\ui.d\languages\strings_cs.qmFILE \flashbfs\system\ui.d\languages\strings_cs.qmFILE \flashbfs\system\ui.d\languages\strings_da.qmFILE \flashbfs\system\ui.d\languages\strings_da.qmFILE \flashbfs\system\ui.d\languages\strings_de.qmFILE \flashbfs\system\ui.d\languages\strings_de.qmFILE \flashbfs\system\ui.d\languages\strings_el.qmFILE \flashbfs\system\ui.d\languages\strings_el.qmFILE \flashbfs\system\ui.d\languages\strings_en.qmFILE \flashbfs\system\ui.d\languages\strings_en.qmFILE \flashbfs\system\ui.d\languages\strings_es.qmFILE \flashbfs\system\ui.d\languages\strings_es.qmFILE \flashbfs\system\ui.d\languages\strings_fi.qmFILE \flashbfs\system\ui.d\languages\strings_fi.qmFILE \flashbfs\system\ui.d\languages\strings_fr.qmFILE \flashbfs\system\ui.d\languages\strings_fr.qmFILE \flashbfs\system\ui.d\languages\strings_hu.qmFILE \flashbfs\system\ui.d\languages\strings_hu.qmFILE \flashbfs\system\ui.d\languages\strings_it.qmFILE \flashbfs\system\ui.d\languages\strings_it.qmFILE \flashbfs\system\ui.d\languages\strings_ja.qmFILE \flashbfs\system\ui.d\languages\strings_ja.qmFILE \flashbfs\system\ui.d\languages\strings_ko.qmFILE \flashbfs\system\ui.d\languages\strings_ko.qmFILE \flashbfs\system\ui.d\languages\strings_nb-no.qmFILE \flashbfs\system\ui.d\languages\strings_nb-no.qmFILE \flashbfs\system\ui.d\languages\strings_nl.qmFILE \flashbfs\system\ui.d\languages\strings_nl.qmFILE \flashbfs\system\ui.d\languages\strings_pl.qmFILE \flashbfs\system\ui.d\languages\strings_pl.qmFILE \flashbfs\system\ui.d\languages\strings_pt.qmFILE \flashbfs\system\ui.d\languages\strings_pt.qmFILE \flashbfs\system\ui.d\languages\strings_ru.qmFILE \flashbfs\system\ui.d\languages\strings_ru.qmFILE \flashbfs\system\ui.d\languages\strings_sv.qmFILE \flashbfs\system\ui.d\languages\strings_sv.qmFILE \flashbfs\system\ui.d\languages\strings_tr.qmFILE \flashbfs\system\ui.d\languages\strings_tr.qmFILE \flashbfs\system\ui.d\languages\strings_zh-chs.qmFILE \flashbfs\system\ui.d\languages\strings_zh-chs.qmFILE \flashbfs\system\ui.d\languages\strings_zh-cht.qmFILE \flashbfs\system\ui.d\languages\strings_zh-cht.qmFILE \flashbfs\system\ui.d\presets.d\preset_centerhotcoldspotFILE \flashbfs\system\ui.d\presets.d\preset_centerhotcoldspotFILE \flashbfs\system\ui.d\presets.d\preset_centerspot.rscFILE \flashbfs\system\ui.d\presets.d\preset_centerspot.rscFILE \flashbfs\system\ui.d\presets.d\preset_coldspot.rscFILE \flashbfs\system\ui.d\presets.d\preset_coldspot.rscFILE \flashbfs\system\ui.d\presets.d\preset_deltaspot.rscFILE \flashbfs\system\ui.d\presets.d\preset_deltaspot.rscFILE \flashbfs\system\ui.d\presets.d\preset_deltatemp.rscFILE \flashbfs\system\ui.d\presets.d\preset_deltatemp.rscFILE \flashbfs\system\ui.d\presets.d\preset_fivespots.rscFILE \flashbfs\system\ui.d\presets.d\preset_fivespots.rscFILE \flashbfs\system\ui.d\presets.d\preset_hotcoldspot.rscFILE \flashbfs\system\ui.d\presets.d\preset_hotcoldspot.rscFILE \flashbfs\system\ui.d\presets.d\preset_hotspot.rscFILE \flashbfs\system\ui.d\presets.d\preset_hotspot.rscFILE \flashbfs\system\ui.d\presets.d\preset_threespots.rscFILE \flashbfs\system\ui.d\presets.d\preset_threespots.rscFILE \flashbfs\system\ui.d\presets.d\preset_twohotspots.rscFILE \flashbfs\system\ui.d\presets.d\preset_twohotspots.rscFILE \flashbfs\system\ui.d\toolbar-config_e2.xmlFILE \flashbfs\system\ui.d\toolbar-config_e2.xmlFILE \flashbfs\system\version.exeFILE \flashbfs\system\version.exeor only the differencesCode:$ diff -y v3.12.7/appkit.trim v3.18.0/appkit.trim | grep '<\|>'FILE \flashbfs\system\cemgrc.exe<FILE \flashbfs\system\cerdisp.exe<FILE \flashbfs\system\cetlstub.dll<FILE \flashbfs\system\clientshutdown.exe<FILE \flashbfs\system\cmaccept.exe<FILE \flashbfs\system\common_unittest.exe<FILE \flashbfs\system\conmanclient2.exe<FILE \flashbfs\system\conmanclient3.exe<FILE \flashbfs\system\devicedma.dll<FILE \flashbfs\system\dumpcoff.exe<FILE \flashbfs\system\edbgtl.dll<FILE \flashbfs\system\fmqping.exe<FILE \flashbfs\system\fvd.exe<FILE \flashbfs\system\i2c.exe<FILE \flashbfs\system\pmic.exe<FILE \flashbfs\system\regsvrce.exe<>FILE \flashbfs\system\suid.exeFILE \flashbfs\system\tcpconnectiona.dll<FILE \flashbfs\system\tcpipc.dll<your FW missed some binaries

author: tomas123
author_rank: Frequent Contributor
timestamp: December 14, 2014, 12:20:26 pm
content: and some compares of prodkit.rev between FW v3.12.7 and v3.18.0Code:$ grep "FILE" v3.12.7/prodkit.rev | cut -d" " -f1-2 > v3.12.7/prodkit.trim$ grep "FILE" v3.18.0/prodkit.rev.txt | cut -d" " -f1-2 > v3.18.0/prodkit.trim$ diff -y v3.12.7/prodkit.trim v3.18.0/prodkit.trim# format:# format:##FILE \flashbfs\system\bitapp.exe|FILE flashbfs\system\combtabs.d\combtab.prodkitFILE \flashbfs\system\camtorrent.exe|FILE flashbfs\system\kits.d\prodkit.revFILE \flashbfs\system\combtabs.d\combtab.prodkit|FILE flashbfs\system\web\ctrlcam.aspFILE \flashbfs\system\kits.d\prodkit.rev|FILE flashbfs\system\web\images\flirtrans.gifFILE \flashbfs\system\prodapp.exe|FILE flashbfs\system\web\inc\camtype.incFILE \flashbfs\system\prodisapi.dll|FILE flashbfs\system\web\inc\restree.incFILE \flashbfs\system\restartapp.bat|FILE flashbfs\system\web\inc\sitewidgets.incFILE \flashbfs\system\torrenterrorcodes.xml|FILE flashbfs\system\web\inc\usermenu.incFILE \flashbfs\system\torrenterrorcodes.xsd|FILE flashbfs\system\web\inc\versions.incFILE \flashbfs\system\torrenterrorcodes.xsl|FILE flashbfs\system\web\index.aspFILE \flashbfs\system\web\black-240x320.mov|FILE flashbfs\system\web\rtp.aspFILE \flashbfs\system\web\ctrlcam.asp|FILE flashbfs\system\web\smallcam.aspFILE \flashbfs\system\web\images\a2.jpg|FILE flashbfs\system\web\styles\flirweb.cssFILE \flashbfs\system\web\images\a320.gif|FILE flashbfs\system\web\sysinfo.aspFILE \flashbfs\system\web\images\cross.gif|FILE flashbfs\system\web\webcam.aspFILE \flashbfs\system\web\images\cross_1.gif|FILE flashbfs\system\web\webpopup.aspFILE \flashbfs\system\web\images\cross_2.gif<FILE \flashbfs\system\web\images\cross_3.gif<FILE \flashbfs\system\web\images\dotted_16x12.gif<FILE \flashbfs\system\web\images\e2.jpg<FILE \flashbfs\system\web\images\e2qt.jpg<FILE \flashbfs\system\web\images\e3.jpg<FILE \flashbfs\system\web\images\e3qt.png<FILE \flashbfs\system\web\images\fenix.jpg<FILE \flashbfs\system\web\images\flirtrans.gif<FILE \flashbfs\system\web\images\ghost.gif<FILE \flashbfs\system\web\images\infracam.gif<FILE \flashbfs\system\web\images\noimage.jpg<FILE \flashbfs\system\web\images\p-remote.gif<FILE \flashbfs\system\web\images\pt-cam.jpg<FILE \flashbfs\system\web\images\redcross_1.gif<FILE \flashbfs\system\web\images\redcross_2.gif<FILE \flashbfs\system\web\images\redcross_3.gif<FILE \flashbfs\system\web\images\t-cam.gif<FILE \flashbfs\system\web\images\thermacamp640.gif<FILE \flashbfs\system\web\images\z-cam.gif<FILE \flashbfs\system\web\images\z3_astra.jpg<FILE \flashbfs\system\web\inc\camtype.inc<FILE \flashbfs\system\web\inc\restree.inc<FILE \flashbfs\system\web\inc\sitewidgets.inc<FILE \flashbfs\system\web\inc\usermenu.inc<FILE \flashbfs\system\web\inc\versions.inc<FILE \flashbfs\system\web\index.asp<FILE \flashbfs\system\web\results.css<FILE \flashbfs\system\web\results.xsl<FILE \flashbfs\system\web\rtp.asp<FILE \flashbfs\system\web\service\calib\accmeas.asp<FILE \flashbfs\system\web\service\calib\accmeasmeasure.asp <FILE \flashbfs\system\web\service\calib\accmeasprotocol.asp <FILE \flashbfs\system\web\service\calib\accmeasremove.asp <FILE \flashbfs\system\web\service\calib\accmeasselect.asp <FILE \flashbfs\system\web\service\calib\accmeassetobjpar.asp <FILE \flashbfs\system\web\service\calib\calibacc.asp<FILE \flashbfs\system\web\service\calib\index.asp<FILE \flashbfs\system\web\service\calib\syscalib.asp<FILE \flashbfs\system\web\service\calib\syscalibactivate.asp <FILE \flashbfs\system\web\service\calib\syscalibaddlenscase.a <FILE \flashbfs\system\web\service\calib\syscalibcalculate.asp <FILE \flashbfs\system\web\service\calib\syscalibeditlimits.as <FILE \flashbfs\system\web\service\calib\syscalibeditmeas.asp <FILE \flashbfs\system\web\service\calib\syscalibenadisa.asp <FILE \flashbfs\system\web\service\calib\syscalibfarfocus.asp <FILE \flashbfs\system\web\service\calib\syscalibmeasure.asp <FILE \flashbfs\system\web\service\calib\syscalibprotocol.asp <FILE \flashbfs\system\web\service\calib\syscalibrangeenadisa. <FILE \flashbfs\system\web\service\calib\syscalibselect.asp <FILE \flashbfs\system\web\service\calib\syscalibswitch.asp <FILE \flashbfs\system\web\service\calib\transmission.asp <FILE \flashbfs\system\web\service\caminfo\accprot.asp<FILE \flashbfs\system\web\service\caminfo\calibprot.asp<FILE \flashbfs\system\web\service\caminfo\components.asp <FILE \flashbfs\system\web\service\caminfo\index.asp<FILE \flashbfs\system\web\service\caminfo\opspec.asp<FILE \flashbfs\system\web\service\datentime.asp<FILE \flashbfs\system\web\service\diag\bit.asp<FILE \flashbfs\system\web\service\diag\bitcooler.asp<FILE \flashbfs\system\web\service\diag\bitinteractive.asp <FILE \flashbfs\system\web\service\diag\bitselftest.asp<FILE \flashbfs\system\web\service\diag\highres.asp<FILE \flashbfs\system\web\service\diag\index.asp<FILE \flashbfs\system\web\service\diag\noise.asp<FILE \flashbfs\system\web\service\diag\noisemeasure.asp<FILE \flashbfs\system\web\service\diag\noiseresults.asp<FILE \flashbfs\system\web\service\diag\post.asp<FILE \flashbfs\system\web\service\diag\postlog.asp<FILE \flashbfs\system\web\service\diag\servicedue.asp<FILE \flashbfs\system\web\service\diag\statistics.asp<FILE \flashbfs\system\web\service\eeprom\edcaminfo.asp<FILE \flashbfs\system\web\service\eeprom\edcomp.asp<FILE \flashbfs\system\web\service\eeprom\edlens.asp<FILE \flashbfs\system\web\service\eeprom\index.asp<FILE \flashbfs\system\web\service\focus\alignment.asp<FILE \flashbfs\system\web\service\focus\alignmentpt.asp<FILE \flashbfs\system\web\service\focus\alignmentvisvis.asp <FILE \flashbfs\system\web\service\focus\focus.asp<FILE \flashbfs\system\web\service\focus\focussd.asp<FILE \flashbfs\system\web\service\focus\index.asp<FILE \flashbfs\system\web\service\focus\laser.asp<FILE \flashbfs\system\web\service\focus\lensdist.asp<FILE \flashbfs\system\web\service\imgcorr\activatedigfilters. <FILE \flashbfs\system\web\service\imgcorr\gainmap.asp<FILE \flashbfs\system\web\service\imgcorr\gainmapcalc.asp <FILE \flashbfs\system\web\service\imgcorr\gainmapcalcgf.asp <FILE \flashbfs\system\web\service\imgcorr\gainmapcold.asp <FILE \flashbfs\system\web\service\imgcorr\gainmapresult.asp <FILE \flashbfs\system\web\service\imgcorr\gainmapselcase.asp <FILE \flashbfs\system\web\service\imgcorr\gainmapwarm.asp <FILE \flashbfs\system\web\service\imgcorr\imgcorrselcase.asp <FILE \flashbfs\system\web\service\imgcorr\index.asp<FILE \flashbfs\system\web\service\imgcorr\operability.asp <FILE \flashbfs\system\web\service\imgcorr\operabilitylog.asp <FILE \flashbfs\system\web\service\imgcorr\pixkill.asp<FILE \flashbfs\system\web\service\imgcorr\shuttermap.asp <FILE \flashbfs\system\web\service\imgcorr\staticmap.asp<FILE \flashbfs\system\web\service\imgcorr\staticmapcalc.asp <FILE \flashbfs\system\web\service\imgcorr\staticmapcold.asp <FILE \flashbfs\system\web\service\imgcorr\staticmapprepare.as <FILE \flashbfs\system\web\service\imgcorr\staticmapresult.asp <FILE \flashbfs\system\web\service\imgcorr\staticmapwarm.asp <FILE \flashbfs\system\web\service\inc\accmeasprottempl.inc <FILE \flashbfs\system\web\service\inc\calibprottempl.inc <FILE \flashbfs\system\web\service\inc\eepromlock.inc<FILE \flashbfs\system\web\service\inc\errorcodes.inc<FILE \flashbfs\system\web\service\inc\servicemenu.inc<FILE \flashbfs\system\web\service\inc\serviceutils.inc<FILE \flashbfs\system\web\service\index.asp<FILE \flashbfs\system\web\service\ppr.asp<FILE \flashbfs\system\web\service\ppri.htm<FILE \flashbfs\system\web\service\tdrift\curcomp.asp<FILE \flashbfs\system\web\service\tdrift\index.asp<FILE \flashbfs\system\web\service\tdrift\logging.asp<FILE \flashbfs\system\web\service\tdrift\sensors.asp<FILE \flashbfs\system\web\smallcam.asp<FILE \flashbfs\system\web\styles\flirweb.css<FILE \flashbfs\system\web\sysinfo.asp<FILE \flashbfs\system\web\web-addon\a-web-addon\inc\camtype.i <FILE \flashbfs\system\web\web-addon\a-web-addon\index_s.asp <FILE \flashbfs\system\web\web-addon\a2-web-addon\inc\camtype. <FILE \flashbfs\system\web\web-addon\a2-web-addon\index_s.asp <FILE \flashbfs\system\web\web-addon\e-web-addon\inc\camtype.i <FILE \flashbfs\system\web\web-addon\e2-web-addon\inc\camtype. <FILE \flashbfs\system\web\web-addon\e2qt-web-addon\inc\camtyp <FILE \flashbfs\system\web\web-addon\e3-web-addon\inc\camtype. <FILE \flashbfs\system\web\web-addon\e3qt-web-addon\inc\camtyp <FILE \flashbfs\system\web\web-addon\fx-web-addon\inc\camtype. <FILE \flashbfs\system\web\web-addon\g-web-addon\inc\camtype.i <FILE \flashbfs\system\web\web-addon\p-web-addon\inc\camtype.i <FILE \flashbfs\system\web\web-addon\prem-web-addon\inc\camtyp <FILE \flashbfs\system\web\web-addon\prem-web-addon\service\in <FILE \flashbfs\system\web\web-addon\pt-web-addon\inc\camtype. <FILE \flashbfs\system\web\web-addon\x-web-addon\inc\camtype.i <FILE \flashbfs\system\web\web-addon\x2-web-addon\inc\camtype. <FILE \flashbfs\system\web\web-addon\z-web-addon\inc\camtype.i <FILE \flashbfs\system\web\web-addon\z3-web-addon\inc\camtype. <FILE \flashbfs\system\web\webcam.asp<FILE \flashbfs\system\web\webpopup.asp<you have not the filesCode:\flashbfs\system\prodapp.exe\flashbfs\system\restartapp.batand therefore you can' start the service modeseehttps://www.google.de/?gws_rd=ssl#q=site:eevblog.com+prodappI post the missed files for the web GUI here:Quote from: tomas123 on December 08, 2014, 10:04:10 am

author: tomas123
author_rank: Frequent Contributor
timestamp: December 14, 2014, 12:33:30 pm
content: A firmware downgrade is possible, but you risk a bricked stone.see E4 thread for experience reports

author: ElectroTuna
author_rank: Contributor
timestamp: December 15, 2014, 03:38:25 pm
content: Quote from: tomas123 on December 14, 2014, 12:33:30 pmTomas,Flir will only fix bad pixels if you send them the camera (no surprises).Maybe downgrading the camera's firmware can be my last option. Will the camera run the service mode if it has the missing files that you mentioned?\flashbfs\system\prodapp.exe\flashbfs\system\restartapp.batLike I said, I am not very familiar with the detailed inner working of this system like you are, if I could get this damn dead-pixel cleared, I would be happy!

author: tomas123
author_rank: Frequent Contributor
timestamp: December 16, 2014, 11:29:21 am
content: I uploaded the original package flir_exx_pn645_pn646_v3.12.7_update_pack.zip heredurability 30 dayshttp://www.filedropper.com/flirexxpn645pn646v3127updatepackand herehttp://www.file-upload.net/download-10007428/flir_exx_pn645_pn646_v3.12.7_update_pack.zip.htmlYou can harmless copy the prodapp.exe and restartapp.bat to your E40 (service mode app, also for Web GUI)seehttps://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg415480/#msg415480and here for using rlshttps://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg400024/#msg400024But a full firmware downgrade is risky.Good luck!

author: tomas123
author_rank: Frequent Contributor
timestamp: December 16, 2014, 11:58:00 am
content: @ElectroTunaread the post herehttps://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg563620/#msg563620I think, your camera was delivered with an open firmware, because your config files are not encrypted.(file name is conf.cfg and not conf.cfc, seehttps://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg403480/#msg403480)But have made an update with the anti-hack firmware.The good news:Your Eeprom is not used as dongle. Therefore you can edit your config file ad libitumI also think, you can run the prodapp.exe but I'm not suggest to downgrade the firmware.google:Code:site:eevblog.com downgrade firmware e4site:eevblog.com downgrade firmware e4 1.19

author: tomas123
author_rank: Frequent Contributor
timestamp: December 18, 2014, 12:10:58 pm
content: Quote from: ElectroTuna on December 07, 2014, 08:02:10 pmI looked in a gain map file and found it's a common CRC32 checksumQuote from: ElectroTuna on December 07, 2014, 06:18:03 amI calculated the CRC32 of the block (size0x25820) with the HxD Hexeditorhttp://mh-nexus.de/de/hxd/it's the sameCode:// truncate 0x25820 bytes$ dd skip=$((0x200)) count=$((0x25820)) bs=1 if=ds250C_we_ap_fi_le_static.gan > truncate.bin153632+0 records in153632+0 records out153632 bytes transferred in 0.233211 secs (658768 bytes/sec)// calc crc32$ crc32 truncate.bin4a2ad6ac// compare with dwChecksum$ dd skip=$((0x5c)) count=4 bs=1 if=ds250C_we_ap_fi_le_static.gan 2>/dev/zero| hexdump0000000 4a 2a d6 acAnd now the bad newssee attachmentCode:Tag section is normally initiated to 14 tag descriptors (size of header + tags is then 512 bytes)....The general header contains a checksum for data+all tags descriptors. (not data blocks)Header and index tag endian order can be in both Little and Big Endian order.The header record contains a flag which indicates endian type.Data tag endian order might be tag type dependent.If you change the CRC above, you must also change the header checksum (my file C2 B6 BD 68 / your file e0 b5 cc a1 )Code:unsigned long dwChecksum; /* Head & index checksum 4 64 bytes */you can verify this trouble, if you compare the header above with your header (there are the same bytes except the both checksumsQuote from: ElectroTuna on December 06, 2014, 05:28:45 ama hint:head size: 64 Byteindex size: 32 BytedwNumUsedIndex = 0xE (marked blue above) = 14-> Head & index: 64 + 14x32=512 Bytebut zeroing the Header CRC (my file C2 B6 BD 68 / your file e0 b5 cc a1 )and calculate the CRC of the first 512 byte gives not the right result

author: tomas123
author_rank: Frequent Contributor
timestamp: December 20, 2014, 11:26:56 am
content: @ ElectroTunayou search a way to map a bad pixelwhy do you don't try out my suggestQuote from: tomas123 on December 06, 2014, 02:19:27 amin ftest.exe are parts for broken CRCs and handling of tags likeCode:$ strings \ e40/flir_exx_pn490_v2.23.14_update_pack/E2comb_v2.23.14.fif/FlashFS/system/ftest.exe | grep -i deadFFF_TAGID_DeadMapFFF_TAGID_GainDeadMap

author: tomas123
author_rank: Frequent Contributor
timestamp: December 23, 2014, 01:48:07 pm
content: Quote from: ElectroTuna on December 07, 2014, 04:32:45 am@ ElectroTunayou are a little bit lazilyQuote from: tomas123 on December 06, 2014, 02:19:27 amI'm tried out my suggest for using ftest.exe to recalculate embedded CRC and it works fine!I used the E4 gain map file from the post aboveas attachment the original gain map file (ds250C_we_ap_fi_le_static.gan) and a crc patched map file (badCRC.gan)from my PC:Quotenow let the camera calculate the CRCfrom telnet to E40:Quoteand now the checksum on my PCQuotesame MD5 like original

author: bretzeljoe
author_rank: Newbie
timestamp: March 02, 2015, 09:41:15 pm
content: Hi tomas123 and Electrotuna,very interesting dialog between you two. I tried to understand your very sophisticated talk now for 3 evening. If could not succeed fully.I have an E40 bx (SN 490 ++++, mfd late 2011) I would like to upgrade the resolution. From my readings I found that it should be quite easy. Only the config.cfg should be changed However I could not find out exact steps. also checked GustavoCampos Tutorial. however it has some flaws. Perhaps you can help.Is there already an upgrade tutorial from ElectroTuna?Best regards.Update:I performed a nightshift and finally succeed in upgrading the E40bx (Serial number: 490xxxxxx)Here the procedure:I used the cfg files for manipulation from user "funzt":https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg338671/#msg338671User "gustavocampos" provided a leaky, but helpful tutorial especially for file the manipulation procedure.https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg561266/#msg561266Important information: ! I did not use his provided cfg files, but his provided Crc01.exe for Crc01 calculation !First time I tried with his cfg files my camera lost zooming functionality and no resolution upgrade was performed. I do not know exactly what was the reason, but just be warned if you use a FLIR E40bx for upgrade.Just add your serial number to the files provided by user "funzt" and calculate the CRC01 for each file as described in detail by gustavocampos.--> addition of this files to their corresponding location via FTP results in full resolution and (hopefully full) E60bx functionality.Always perform a full backup before you start messing with your cam (FlashFS folder)!

author: WEL0058
author_rank: Newbie
timestamp: March 14, 2015, 08:52:16 pm
content: Hi Joe,Curious what you found wrong with Gustavo Campos's instructions? I found the instruction spot on. Had purchase a used E40bx on eBay with sn#490.The FLIR was not always reliable giving IP address 192.168.0.1 so statically assigned it to my computer's RNDIS interface. Now always able to connect to the camera. Using WinSCP for file transfers.First thing after connecting to the camera's file system was to do a complete backup (copy) of the file system to my computers hard drive.Next did the 2.23.14 firmware upgrade then reboot.Used Gustavo's E60.cfg file to modify and replace my conf.cfg.Verified that the resolution was 320 x 240 and it was. Was missing so of the 'bx' features.Did a line by line comparison of the E60 and the original E40bx conf.cfg files. Enable the 'bx' features in the E60 conf.cfg file.Also did the 2.23.14 firmware again.Question:Possible to also added the 650C degree temperature range to the camera's existing 250C temperatureThanks for all help.

author: bretzeljoe
author_rank: Newbie
timestamp: March 16, 2015, 10:11:09 pm
content: Hi WEL0058,I do not really know what went wrong the first time. But know I am quite happy with the cam. Especially 60 Hz.BTW: Does anybody know if there is a (3D Printable) lensholder for the FLIR Exx series for a macro lens like for the E4. Since the FLIR Exx has a built-in lens attachment it should be easy to create one and install it. If anybody knows just let me know.THX a lot.

author: Chanc3
author_rank: Frequent Contributor
timestamp: March 17, 2015, 01:00:19 pm
content: Does anyone still require the files from the E60 2014 model? I have both sitting on my desktop at the moment (2012 and 2014).

author: WEL0058
author_rank: Newbie
timestamp: March 19, 2015, 04:02:04 am
content: Chanc,Would be interested in the files that you have. Interested in seeing the difference between the non-msx and the newer msx model. Any possibility to upgrading earlier Exx with msx feature?Thanks

author: Chanc3
author_rank: Frequent Contributor
timestamp: March 19, 2015, 12:04:36 pm
content: Quote from: WEL0058 on March 19, 2015, 04:02:04 amI don't think it is possible due to the difference in hardware, since the 2012 model has less processing power.I've attached the conf file for the 2014 model, from 3.18.0, albeit as a .txt file. Some differences in the features and a slight change in the noise (35 on 2014 model, 40 on 2012...). If you need a full breakdown of files, I have them from the 3.18.0 firmware and the 4.10.0.

author: rterens
author_rank: Newbie
timestamp: March 26, 2015, 05:25:01 pm
content: I am interested in the e60 files. I have an older e40bx with 2.23.14 firmware I would like to try and update

author: Gasburner
author_rank: Contributor
timestamp: July 07, 2015, 03:28:12 pm
content: ElectroTuna how things working out for your E40 to E60 upgrade ?Reading and learning from you guys.As i got the same model.E40 1.0Serial: 645xxxxxSoftware: 3.18.0So let me know if you need a unedited software version, before i start trying to hack mineAnd we can make all together a nice guide for 645xxxxx version users.

author: Chanc3
author_rank: Frequent Contributor
timestamp: July 07, 2015, 04:17:58 pm
content: Hi Gasburner, apologies for lack of response! Been too busy fixing other IR cameras!I'll dig out my old files for both E60s I have - hopefully they'll help!Sent from my HTC One_M8 using Tapatalk

author: Gasburner
author_rank: Contributor
timestamp: July 07, 2015, 06:48:20 pm
content: Thanks Chanc3, dont worry we all got our daily work lol..My first intention is to only upgrade the resolution to a E60And as it develops to do the rest and do some trial and error on the rest.

author: Gasburner
author_rank: Contributor
timestamp: July 07, 2015, 10:22:17 pm
content: Stupid Question,Maybe i am missing something, but i cannot get it in to open the Gray "diagnostic" screen.According my logic this is the sequence to follow afterwards:- Install Flir Tools- Install Total Comandor- Download Mike's CRC01 Tool (Extract to documents)- Connect E40 let windows install drivers normally- Disconnect your E40- Set your E40 to USB RNDIS mode- Connect your E40 again to PC, let drivers install normally- Run Total Comandor app (And connect to your E40 by FTP)- Copy a back-up to safe locaction of the full folder from your E40- Drag and drop (copy) Conf.cfg to document folder- Start Notepad and insert new codeQuote from: tomas123 on December 03, 2014, 08:33:58 am- Save file (Overwrite)From there page 8 How to upgrade your flir I3 or I5, to I7 small.pdfThanks in advance for the help

author: Chanc3
author_rank: Frequent Contributor
timestamp: July 07, 2015, 10:24:15 pm
content: Quote from: Gasburner on July 07, 2015, 10:22:17 pmGo to camera information and hold the right arrow key for 10-12 secondsSent from my HTC One_M8 using Tapatalk

author: Gasburner
author_rank: Contributor
timestamp: July 07, 2015, 11:22:34 pm
content: Thanks a lot Chanc3,I have put my findings so far in a PDF file. I want to document the complete hack in to a simple guide to help others on this blog as a future reference.bare with me... i try to make this guide as simple as possible for everyone.I ask you guys all small details to make it as smooth possibleMy E40 battery died on my for today, to be continued after rechargeGuide File updated: on 8 july 2015

author: Gasburner
author_rank: Contributor
timestamp: July 22, 2015, 04:55:04 am
content: Hi guys,Got my E40 connected trough RNDIS > FTP with Total Commander, but its hanging on download.It opens the FTP connection and is trying to download, but stays on download window.Hostname= 192.168.0.2Username= flirPassword= 3vligAny ideas, wrong password for this E40 maybe ?Thanks in advanced

author: Chanc3
author_rank: Frequent Contributor
timestamp: July 22, 2015, 06:00:21 am
content: Try using filezilla, had no issues with that.Sent from my HTC One_M8 using Tapatalk

author: reallybigone916
author_rank: Contributor
timestamp: July 22, 2015, 11:16:06 am
content: I'm planning to get a used E40, 2011 model. Is there a different in performance between the newer model?Thanks

author: tomas123
author_rank: Frequent Contributor
timestamp: July 22, 2015, 01:25:48 pm
content: missing live MSX, but you can overlay the thermal and real image with the postprocessing Flir Tools

author: Pinkus
author_rank: Frequent Contributor
timestamp: July 22, 2015, 01:31:28 pm
content: Quote from: reallybigone916 on July 22, 2015, 11:16:06 amThe performance and functionality is similar if you compare old and new Exx. However, MSX is missing in the older models - no chance to update. But don't worry - with the Exx this is not a big deal as the Exx have a very detailed and clean picture, much better than the Ex. Where MSX on an E4/8 is often needed/helpful, in most cases you will not miss it on an E40/60. Why not? Because with an E40/E60 you will see much more details than with an E4/E8 (due to the fact that the lens/sensor is much larger on the Exx).

author: bookaboo
author_rank: Frequent Contributor
timestamp: July 22, 2015, 01:43:16 pm
content: Agree, at 320x240 there's no need for MSX especially with the manual focus of the Exx.

author: Gasburner
author_rank: Contributor
timestamp: July 22, 2015, 03:33:51 pm
content: Thanks Chanc3 that did the trick using FileZilla

author: Gasburner
author_rank: Contributor
timestamp: July 22, 2015, 03:38:56 pm
content: This should be the only things needed for the resolution the upgrade, and generate a new CRC01. Please correct me if wrongi add my conf.cfg as a reference.FlashFS/system/appcore.d/config.d/conf.cfgbegins withCode: CRC01then you must only edit this two linesCode: .caps.config.image.settings.resIR int32 160...caps.config.image.targetNoise.targetNoiseMk int32 55toCode: .caps.config.image.settings.resIR int32 320...caps.config.image.targetNoise.targetNoiseMk int32 0Code:## Generated at 2013-10-16 09:16:10#.caps entry.caps.config entry.caps.config.name text "app E40".caps.config.revision text "1.0".caps.config.segment text "handheld".caps.config.direction entry.caps.config.direction.sensorAccel entry.caps.config.direction.sensorAccel.enabled bool true.caps.config.direction.compass entry.caps.config.direction.compass.enabled bool false.caps.config.direction.lcdAccel entry.caps.config.direction.lcdAccel.enabled bool true.caps.config.image entry.caps.config.image.framegrab entry.caps.config.image.framegrab.fusion entry.caps.config.image.framegrab.fusion.enabled bool true.caps.config.image.framegrab.fusion.pip entry.caps.config.image.framegrab.fusion.pip.enabled bool true.caps.config.image.framegrab.fusion.hcf entry.caps.config.image.framegrab.fusion.hcf.enabled bool true.caps.config.image.sensor entry.caps.config.image.sensor.enabled bool true.caps.config.image.services entry.caps.config.image.services.store entry.caps.config.image.services.store.enabled bool true.caps.config.image.services.store.radiometric entry.caps.config.image.services.store.radiometric.enabled bool true.caps.config.image.services.store.incompatible entry.caps.config.image.services.store.incompatible.enabled bool false.caps.config.image.services.store.incompatible.level int32 0.caps.config.image.settings entry.caps.config.image.settings.enabled bool true.caps.config.image.settings.downsample bool true.caps.config.image.settings.resIR int32 160.caps.config.image.sysimg entry.caps.config.image.sysimg.alarms entry.caps.config.image.sysimg.alarms.enabled bool true.caps.config.image.sysimg.alarms.measfunc entry.caps.config.image.sysimg.alarms.measfunc.enabled bool true.caps.config.image.sysimg.alarms.measfunc.maxCount int32 3.caps.config.image.sysimg.alarms.humidity entry.caps.config.image.sysimg.alarms.humidity.enabled bool false.caps.config.image.sysimg.alarms.humidity.maxCount int32 1.caps.config.image.sysimg.alarms.insulation entry.caps.config.image.sysimg.alarms.insulation.enabled bool false.caps.config.image.sysimg.alarms.insulation.maxCount int32 1.caps.config.image.sysimg.irMarkers entry.caps.config.image.sysimg.irMarkers.enabled bool false.caps.config.image.sysimg.irMarkers.spot entry.caps.config.image.sysimg.irMarkers.spot.enabled bool false.caps.config.image.sysimg.irMarkers.spot.maxCount int32 0.caps.config.image.sysimg.irMarkers.arrow entry.caps.config.image.sysimg.irMarkers.arrow.enabled bool true.caps.config.image.sysimg.irMarkers.arrow.maxCount int32 0.caps.config.image.sysimg.irMarkers.box entry.caps.config.image.sysimg.irMarkers.box.enabled bool false.caps.config.image.sysimg.irMarkers.box.maxCount int32 0.caps.config.image.sysimg.measureFuncs entry.caps.config.image.sysimg.measureFuncs.enabled bool true.caps.config.image.sysimg.measureFuncs.diff entry.caps.config.image.sysimg.measureFuncs.diff.enabled bool true.caps.config.image.sysimg.measureFuncs.diff.maxCount int32 1.caps.config.image.sysimg.measureFuncs.diff.calcMask int32 65526.caps.config.image.sysimg.measureFuncs.isotherm entry.caps.config.image.sysimg.measureFuncs.isotherm.enabled bool true.caps.config.image.sysimg.measureFuncs.isotherm.calcMask int32 20.caps.config.image.sysimg.measureFuncs.isotherm.dual bool false.caps.config.image.sysimg.measureFuncs.isotherm.fixScale bool false.caps.config.image.sysimg.measureFuncs.isotherm.interval bool true.caps.config.image.sysimg.measureFuncs.isotherm.invInterval bool false.caps.config.image.sysimg.measureFuncs.isotherm.maxCount int32 1.caps.config.image.sysimg.measureFuncs.mbox entry.caps.config.image.sysimg.measureFuncs.mbox.enabled bool true.caps.config.image.sysimg.measureFuncs.mbox.calcMask int32 1924.caps.config.image.sysimg.measureFuncs.mbox.maxCount int32 3.caps.config.image.sysimg.measureFuncs.mcircle entry.caps.config.image.sysimg.measureFuncs.mcircle.enabled bool false.caps.config.image.sysimg.measureFuncs.mcircle.calcMask int32 1924.caps.config.image.sysimg.measureFuncs.mcircle.maxCount int32 1.caps.config.image.sysimg.measureFuncs.mline entry.caps.config.image.sysimg.measureFuncs.mline.enabled bool false.caps.config.image.sysimg.measureFuncs.mline.calcMask int32 1924.caps.config.image.sysimg.measureFuncs.mline.maxCount int32 0.caps.config.image.sysimg.measureFuncs.reftemp entry.caps.config.image.sysimg.measureFuncs.reftemp.enabled bool true.caps.config.image.sysimg.measureFuncs.reftemp.calcMask int32 1924.caps.config.image.sysimg.measureFuncs.reftemp.maxCount int32 1.caps.config.image.sysimg.measureFuncs.script entry.caps.config.image.sysimg.measureFuncs.script.enabled false.caps.config.image.sysimg.measureFuncs.script.maxCount int32 0.caps.config.image.sysimg.measureFuncs.spot entry.caps.config.image.sysimg.measureFuncs.spot.enabled bool true.caps.config.image.sysimg.measureFuncs.spot.calcMask int32 514.caps.config.image.sysimg.measureFuncs.spot.maxCount int32 3.caps.config.image.sysimg.visualMarkers entry.caps.config.image.sysimg.visualMarkers.enabled bool false.caps.config.image.sysimg.visualMarkers.spot entry.caps.config.image.sysimg.visualMarkers.spot.enabled bool false.caps.config.image.sysimg.visualMarkers.spot.maxCount int32 0.caps.config.image.sysimg.visualMarkers.arrow entry.caps.config.image.sysimg.visualMarkers.arrow.enabled bool false.caps.config.image.sysimg.visualMarkers.arrow.maxCount int32 0.caps.config.image.sysimg.visualMarkers.box entry.caps.config.image.sysimg.visualMarkers.box.enabled bool false.caps.config.image.sysimg.visualMarkers.box.maxCount int32 0.caps.config.image.targetNoise entry.caps.config.image.targetNoise.enabled bool true.caps.config.image.targetNoise.targetNoiseMk int32 55.caps.config.image.zoom entry.caps.config.image.zoom.enabled bool true.caps.config.image.zoom.maxFactor double 2.caps.config.ui entry.caps.config.ui.archive entry.caps.config.ui.archive.enabled bool true.caps.config.ui.archive.export entry.caps.config.ui.archive.export.enabled bool true.caps.config.ui.archive.sketch entry.caps.config.ui.archive.sketch.enabled bool true.caps.config.ui.archive.text entry.caps.config.ui.archive.text.enabled bool true.caps.config.ui.archive.voice entry.caps.config.ui.archive.voice.enabled bool true.caps.config.ui.fusion entry.caps.config.ui.fusion.enabled bool true.caps.config.ui.fusion.PIP entry.caps.config.ui.fusion.PIP.enabled bool true.caps.config.ui.fusion.PIP.locked bool true.caps.config.ui.laser entry.caps.config.ui.laser.enabled bool true.caps.config.ui.laser.positionMarker bool true.caps.config.ui.image entry.caps.config.ui.image.startMode text "IR".caps.config.ui.measure entry.caps.config.ui.measure.externWindow entry.caps.config.ui.measure.externWindow.enabled bool true# ID 645xxxx# CRC01 1c8c954b

author: Chanc3
author_rank: Frequent Contributor
timestamp: July 22, 2015, 03:50:44 pm
content: I believe it has a few more measurement options:Code:## Generated at 2011-04-28 17:34:36#.caps entry.caps.config entry.caps.config.name text "app E60".caps.config.revision text "0.10".caps.config.image entry.caps.config.image.framegrab entry.caps.config.image.framegrab.fusion entry.caps.config.image.framegrab.fusion.enabled bool true.caps.config.image.sensor entry.caps.config.image.sensor.enabled bool true.caps.config.image.services entry.caps.config.image.services.store entry.caps.config.image.services.store.enabled bool true.caps.config.image.services.store.radiometric entry.caps.config.image.services.store.radiometric.enabled bool true.caps.config.image.services.store.incompatible entry.caps.config.image.services.store.incompatible.enabled bool false.caps.config.image.services.store.incompatible.level int32 0.caps.config.image.settings entry.caps.config.image.settings.enabled bool true.caps.config.image.settings.downsample bool false.caps.config.image.settings.resIR int32 320.caps.config.image.sysimg entry.caps.config.image.sysimg.alarms entry.caps.config.image.sysimg.alarms.enabled bool false.caps.config.image.sysimg.alarms.measfunc entry.caps.config.image.sysimg.alarms.measfunc.enabled bool false.caps.config.image.sysimg.alarms.measfunc.maxCount int32 0.caps.config.image.sysimg.alarms.humidity entry.caps.config.image.sysimg.alarms.humidity.enabled bool false.caps.config.image.sysimg.alarms.humidity.maxCount int32 0.caps.config.image.sysimg.alarms.insulation entry.caps.config.image.sysimg.alarms.insulation.enabled bool false.caps.config.image.sysimg.alarms.insulation.maxCount int32 0.caps.config.image.sysimg.irMarkers entry.caps.config.image.sysimg.irMarkers.enabled bool false.caps.config.image.sysimg.irMarkers.spot entry.caps.config.image.sysimg.irMarkers.spot.enabled bool false.caps.config.image.sysimg.irMarkers.spot.maxCount int32 0.caps.config.image.sysimg.irMarkers.arrow entry.caps.config.image.sysimg.irMarkers.arrow.enabled bool true.caps.config.image.sysimg.irMarkers.arrow.maxCount int32 0.caps.config.image.sysimg.irMarkers.box entry.caps.config.image.sysimg.irMarkers.box.enabled bool false.caps.config.image.sysimg.irMarkers.box.maxCount int32 0.caps.config.image.sysimg.measureFuncs entry.caps.config.image.sysimg.measureFuncs.enabled bool true.caps.config.image.sysimg.measureFuncs.diff entry.caps.config.image.sysimg.measureFuncs.diff.enabled bool true.caps.config.image.sysimg.measureFuncs.diff.maxCount int32 1.caps.config.image.sysimg.measureFuncs.diff.calcMask int32 65526.caps.config.image.sysimg.measureFuncs.isotherm entry.caps.config.image.sysimg.measureFuncs.isotherm.enabled bool true.caps.config.image.sysimg.measureFuncs.isotherm.calcMask int32 20.caps.config.image.sysimg.measureFuncs.isotherm.dual bool false.caps.config.image.sysimg.measureFuncs.isotherm.fixScale bool false.caps.config.image.sysimg.measureFuncs.isotherm.interval bool true.caps.config.image.sysimg.measureFuncs.isotherm.invInterval bool false.caps.config.image.sysimg.measureFuncs.isotherm.maxCount int32 1.caps.config.image.sysimg.measureFuncs.mbox entry.caps.config.image.sysimg.measureFuncs.mbox.enabled bool true.caps.config.image.sysimg.measureFuncs.mbox.calcMask int32 1924.caps.config.image.sysimg.measureFuncs.mbox.maxCount int32 3.caps.config.image.sysimg.measureFuncs.mcircle entry.caps.config.image.sysimg.measureFuncs.mcircle.enabled bool false.caps.config.image.sysimg.measureFuncs.mcircle.calcMask int32 1924.caps.config.image.sysimg.measureFuncs.mcircle.maxCount int32 0.caps.config.image.sysimg.measureFuncs.mline entry.caps.config.image.sysimg.measureFuncs.mline.enabled bool false.caps.config.image.sysimg.measureFuncs.mline.calcMask int32 1924.caps.config.image.sysimg.measureFuncs.mline.maxCount int32 0.caps.config.image.sysimg.measureFuncs.reftemp entry.caps.config.image.sysimg.measureFuncs.reftemp.enabled bool true.caps.config.image.sysimg.measureFuncs.reftemp.calcMask int32 1924.caps.config.image.sysimg.measureFuncs.reftemp.maxCount int32 1.caps.config.image.sysimg.measureFuncs.script entry.caps.config.image.sysimg.measureFuncs.script.enabled false.caps.config.image.sysimg.measureFuncs.script.maxCount int32 0.caps.config.image.sysimg.measureFuncs.spot entry.caps.config.image.sysimg.measureFuncs.spot.enabled bool true.caps.config.image.sysimg.measureFuncs.spot.calcMask int32 514.caps.config.image.sysimg.measureFuncs.spot.maxCount int32 3.caps.config.image.sysimg.visualMarkers entry.caps.config.image.sysimg.visualMarkers.enabled bool false.caps.config.image.sysimg.visualMarkers.spot entry.caps.config.image.sysimg.visualMarkers.spot.enabled bool false.caps.config.image.sysimg.visualMarkers.spot.maxCount int32 0.caps.config.image.sysimg.visualMarkers.arrow entry.caps.config.image.sysimg.visualMarkers.arrow.enabled bool false.caps.config.image.sysimg.visualMarkers.arrow.maxCount int32 0.caps.config.image.sysimg.visualMarkers.box entry.caps.config.image.sysimg.visualMarkers.box.enabled bool false.caps.config.image.sysimg.visualMarkers.box.maxCount int32 0.caps.config.image.targetNoise entry.caps.config.image.targetNoise.enabled bool true.caps.config.image.targetNoise.targetNoiseMk int32 40.caps.config.image.zoom entry.caps.config.image.zoom.enabled bool true.caps.config.image.zoom.maxFactor double 4.caps.config.system entry.caps.config.system.focus entry.caps.config.system.focus.laser entry.caps.config.system.focus.laser.updateFocus entry.caps.config.system.focus.laser.updateFocus.enabled bool false# ID 490xxxxx# CRC01 xxxxxxxxThis was taken from the E4 thread. I'll try and pull the E60 2012 files when it is back from cal.

author: Chanc3
author_rank: Frequent Contributor
timestamp: July 22, 2015, 03:56:58 pm
content: If you also set everything to "true" in the "FlashFS\system\ui.d\config.d\conf.cfg" file you should unlock a few more features!

author: Gasburner
author_rank: Contributor
timestamp: July 22, 2015, 04:12:52 pm
content: All in the conf.cfg, or in some other directory ?Quote from: Chanc3 on July 22, 2015, 03:56:58 pm

author: Chanc3
author_rank: Frequent Contributor
timestamp: July 22, 2015, 04:15:16 pm
content: In the ui.d directory

author: Gasburner
author_rank: Contributor
timestamp: July 22, 2015, 06:15:39 pm
content: Any info which ones someone ?, or you upload them if your E60 comes back Chance3 ?Thanks a lot for all help so farQuote from: Chanc3 on July 22, 2015, 04:15:16 pm

author: Chanc3
author_rank: Frequent Contributor
timestamp: July 22, 2015, 08:59:32 pm
content: Quote from: Gasburner on July 22, 2015, 06:15:39 pmIn the ui.d directory you should just have conf.cfg open that in text editor and change the values to true.This is for the MSX model just so you're aware. I don't have the files for 2012 version until my E60 gets repaired and calibrated.Sent from my HTC One_M8 using Tapatalk

author: Gasburner
author_rank: Contributor
timestamp: July 22, 2015, 09:46:46 pm
content: Where to find the lastest CRC01.exe ?, most links end dead on here.

author: Chanc3
author_rank: Frequent Contributor
timestamp: July 22, 2015, 09:49:06 pm
content: Part of a zip file that Mike put up on the E4 thread (for 1.18.1 firmware hack)Sent from my HTC One_M8 using TapatalkEDIT: I can email over tomorrow if I can find it!

author: encryptededdy
author_rank: Frequent Contributor
timestamp: July 22, 2015, 11:04:30 pm
content: Just looking online, I think the new E40 has much better video recording frame rate. The old Exx would lag when recording video and the resulting file would be lower than 30fps

author: tomas123
author_rank: Frequent Contributor
timestamp: July 23, 2015, 02:38:34 pm
content: there are very few applications, where you need high frame rates with a wide-angle lensI own an E40 from 2012 and the frame rate is fine.On video you have lags from the NUC (shutter) and some ugly overlays (scale, logo).But a really great feature are RAW-videos with Flir Tools.see my post here:https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg377140/#msg377140... stack the frames to superesolution:https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg363213/#msg363213.. or make a panorama (I use single photos)https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg621514/#msg621514

author: Chanc3
author_rank: Frequent Contributor
timestamp: July 23, 2015, 02:49:19 pm
content: Quote from: tomas123 on July 23, 2015, 02:38:34 pmYou can turn off the logo via telnet I believe!Sent from my HTC One_M8 using Tapatalk

author: tomas123
author_rank: Frequent Contributor
timestamp: July 23, 2015, 02:50:20 pm
content: yes, I know// old firmwareCode:rset .ui.userSettings.overlayLogo false

author: tomas123
author_rank: Frequent Contributor
timestamp: July 23, 2015, 02:54:16 pm
content: Quote from: Chanc3 on July 22, 2015, 03:50:44 pmsee here for E60 files version 2012 (pw funzt666)https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg338671/#msg338671

author: Gasburner
author_rank: Contributor
timestamp: July 24, 2015, 12:14:42 am
content: Do i need the CRC01 or CRC03 ? for my E40E40 1.0Serial: 645xxxxxSoftware: 3.18.0

author: Chanc3
author_rank: Frequent Contributor
timestamp: July 24, 2015, 06:44:51 am
content: Quote from: Gasburner on July 24, 2015, 12:14:42 amDoes it say CRC01 after your serial number?I highly doubt it is CRC03Sent from my HTC One_M8 using Tapatalk

author: tomas123
author_rank: Frequent Contributor
timestamp: July 24, 2015, 07:55:19 am
content: you need CRC01 if your configuration files are not encrypted (plain text)but you need CRC03:old E40http://80.77.70.144/SwDownload/app/RssSWDownload.aspx?ID=127FLIR Exx P/N:490xx (Firmware 2.23.14)Last Updated: April 23, 2013this works with CRC01 (self tested)new E40 with MSXhttp://80.77.70.144/SwDownload/app/RssSWDownload.aspx?ID=194FLIR Exx P/N:645xx / 646xx (Firmware 4.10.0)

author: Gasburner
author_rank: Contributor
timestamp: July 24, 2015, 01:15:58 pm
content: Thanks Chance3 and tomas123Its a CRC01 as you can see in my conf.cfg file on the previous page.I copied and paste it directly in to windows Notepad, without any decryptionSo that's interesting, there is also different version in 645xxx i mean CRC01 or CRC03, but i guess its because of the Firmware 3.18.0Anyone knows the difference between 3.18.0 vs 4.10.0, major upgrade ?, what do you advice upgrade or leave it as it is.This is where i am stuck, i can only find tools.zip with CRC03 inside

author: Chanc3
author_rank: Frequent Contributor
timestamp: July 24, 2015, 08:36:04 pm
content: https://www.eevblog.com/forum/index.php?topic=21772.msg321956.msg#321956in the zip fileSent from my HTC One_M8 using Tapatalk

author: Gasburner
author_rank: Contributor
timestamp: July 24, 2015, 10:52:01 pm
content: Thanks a lot Chance3Quote from: Chanc3 on July 24, 2015, 08:36:04 pm

author: Gasburner
author_rank: Contributor
timestamp: July 25, 2015, 01:07:38 am
content: Okay,Just to resume, can one of you confirm i am on the right track- First i made a backup of config.cfg from the camera- Downloaded my conf.cfg file from the E40 to pc- Copied it to same map as where i unzipped the e4hack3c.zip files- I have edit my conf.cfg file, i changed 645xxxx to the original serial number (leaving the old CRC01 number untouched)- Changed my resolution settings:.caps.config.image.settings.resIR int32 320and.caps.config.image.targetNoise.targetNoiseMk int32 0- Take care you have one free line on the end of the text file(CRLF is not \r\n\command ?)- Save file- Run the E8.cfg and on the prompt you receive a new CRC01 number(or do i need to copy paste my file text in to the E8.cfg ?)- Remove the old CRC number in your file, and replace this with the new generated CRC01Do i need to zip the config.cfg file and change it to .fif extension? to run back in too the E40 ?As a few things are different to a E4 in terms explanation, i get a bit unsure, and don't like to end up with a brick as resultI am not very familiar with computers these days, and CD / \ stuff was a long.... time ago. so bare with me guys.

author: Chanc3
author_rank: Frequent Contributor
timestamp: July 25, 2015, 05:37:57 am
content: Quote from: Gasburner on July 25, 2015, 01:07:38 amJust upload the new cfg file and replace on camera (you have a backup). Should either work or not.Sent from my HTC One_M8 using Tapatalk

author: Gasburner
author_rank: Contributor
timestamp: July 25, 2015, 08:36:23 pm
content: Sorry for my ignoranceBut it does not make any sense to me, to call the file E8.cfg in my case..Quote:Save the file as flashfs\system\appcore.d\config.d\e8.cfgCreate a zip file containing the flashfs folder tree and camera.cmdRename the file from .zip to .fifInstall FLIR toolsGo to the install folder\binTurn camera on and plug USB inRun FLIRInstallNetBrowse to your .fif fileClick Run FIFUnplug USB, remove battery and replaceEnjoy!

author: tomas123
author_rank: Frequent Contributor
timestamp: July 26, 2015, 09:30:12 pm
content: do you read this post ?https://www.eevblog.com/forum/testgear/flir-e40-upgrade-configuration/msg561922/#msg561922Don't copy files from forum. Edit your cfg file!

author: reallybigone916
author_rank: Contributor
timestamp: July 31, 2015, 01:01:11 pm
content: Here is a good small program I use to compare the hacked .cfg files (or text files) with the original .cfg files.http://winmerge.org/Enjoy!

author: snakemars
author_rank: Newbie
timestamp: August 19, 2015, 07:48:26 pm
content: I bricked my E50bx HELP!!!!!!!I made a backup of the entire FlashFS and subsequent files and subdirectories and then attempted the hack, but now I just have a black screen with limited menu options.I tried to restore FlashFS/system/ with filezilla but no luck!At this point I just want to restore to original, then I may reattempt the hack.This is 490XXXXXX unit.Any help would be appreciated!

author: reallybigone916
author_rank: Contributor
timestamp: August 20, 2015, 02:04:04 am
content: are you able to access your unit via FTP?limited menu options? what can you do or see?

author: jumbo
author_rank: Contributor
timestamp: August 30, 2015, 07:08:00 am
content: Hello everyone!I bought old Flir E30_bx yesterday, I have small expirience with E4 (hacked 2 times with old and new firmware but with big help from janekivi)my camera have parameters:serial:492xxxxxcatalogue:49001-1901firmware:2.23.14model:E30bx_B1.1without MSXI have laser, LED uncovered and I can use it right now without makings wholes where the Flash light and Camera are located.1.Can I upgrade my E30 like from lgustavocampos post:https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg561266/#msg561266? or my camera is different because of serial 492 not 490 like other?2.What I can get from upgrading? I sure 320x240 but what else?MSX? Wi-Fi? Blue-Tooth? new pallets?Yes, I read all post from this topic but for my English I am never shore if I misunderstand or not, so I write this post to be shore;)I attached oryginal conf and this what I made by my self (by tutorial from lgustavocampos post, with crc, SerialNumber and .cfg format;), but when I put them into my camera I have only 320x240 but I lose a lot of tools.3.I wonder only to make upgrade resolution 320x240 and have wi-fi or BlueTooth to make movies without USB connection.Enybody know solution for this?All best to you;)

author: jumbo
author_rank: Contributor
timestamp: August 30, 2015, 08:40:17 pm
content: Last question, when I'm running comand - crc01.exe "conf.cfg"in my conf.cfg file should I have Serial number, CRC number and empty line? or only Serial number and empty line?

author: tomas123
author_rank: Frequent Contributor
timestamp: August 31, 2015, 03:23:08 pm
content: Quote from: jumbo on August 30, 2015, 07:08:00 aminteresting, I only knowQuote from: tomas123 on July 24, 2015, 07:55:19 ambut your firmware is 2.23.14 -> use hack for P/N:490xx

author: jumbo
author_rank: Contributor
timestamp: August 31, 2015, 08:46:30 pm
content: Quote from: tomas123 on August 31, 2015, 03:23:08 pm

author: simclardy1
author_rank: Newbie
timestamp: November 02, 2015, 01:59:02 pm
content: Ok I am attempting this "upgrade". I used filezilla and accessed my files via usb RANDIS mode. not problem. I saved a copy of all my files and then I edited my config file in appcore. Here is the edited version## Generated at 2011-09-16 15:15:21#.caps entry.caps.config entry.caps.config.name text "app E60".caps.config.revision text "1.1".caps.config.image entry.caps.config.image.framegrab entry.caps.config.image.framegrab.visual entry.caps.config.image.framegrab.visual.enabled bool true.caps.config.image.sensor entry.caps.config.image.sensor.enabled bool true.caps.config.image.services entry.caps.config.image.services.store entry.caps.config.image.services.store.enabled bool true.caps.config.image.services.store.radiometric entry.caps.config.image.services.store.radiometric.enabled bool true.caps.config.image.services.store.incompatible entry.caps.config.image.services.store.incompatible.enabled bool false.caps.config.image.services.store.incompatible.level int32 0.caps.config.image.settings entry.caps.config.image.settings.enabled bool true.caps.config.image.settings.downsample bool true.caps.config.image.settings.resIR int32 320.caps.config.image.settings.resVIS int32 1600.caps.config.image.sysimg entry.caps.config.image.sysimg.alarms entry.caps.config.image.sysimg.alarms.enabled bool false.caps.config.image.sysimg.alarms.measfunc entry.caps.config.image.sysimg.alarms.measfunc.enabled bool false.caps.config.image.sysimg.alarms.measfunc.maxCount int32 0.caps.config.image.sysimg.alarms.humidity entry.caps.config.image.sysimg.alarms.humidity.enabled bool false.caps.config.image.sysimg.alarms.humidity.maxCount int32 0.caps.config.image.sysimg.alarms.insulation entry.caps.config.image.sysimg.alarms.insulation.enabled bool false.caps.config.image.sysimg.alarms.insulation.maxCount int32 0.caps.config.image.sysimg.irMarkers entry.caps.config.image.sysimg.irMarkers.enabled bool false.caps.config.image.sysimg.irMarkers.spot entry.caps.config.image.sysimg.irMarkers.spot.enabled bool false.caps.config.image.sysimg.irMarkers.spot.maxCount int32 0.caps.config.image.sysimg.irMarkers.arrow entry.caps.config.image.sysimg.irMarkers.arrow.enabled bool true.caps.config.image.sysimg.irMarkers.arrow.maxCount int32 0.caps.config.image.sysimg.irMarkers.box entry.caps.config.image.sysimg.irMarkers.box.enabled bool false.caps.config.image.sysimg.irMarkers.box.maxCount int32 0.caps.config.image.sysimg.measureFuncs entry.caps.config.image.sysimg.measureFuncs.enabled bool true.caps.config.image.sysimg.measureFuncs.diff entry.caps.config.image.sysimg.measureFuncs.diff.enabled bool true.caps.config.image.sysimg.measureFuncs.diff.maxCount int32 1.caps.config.image.sysimg.measureFuncs.diff.calcMask int32 65526.caps.config.image.sysimg.measureFuncs.isotherm entry.caps.config.image.sysimg.measureFuncs.isotherm.enabled bool true.caps.config.image.sysimg.measureFuncs.isotherm.calcMask int32 20.caps.config.image.sysimg.measureFuncs.isotherm.dual bool false.caps.config.image.sysimg.measureFuncs.isotherm.fixScale bool false.caps.config.image.sysimg.measureFuncs.isotherm.interval bool true.caps.config.image.sysimg.measureFuncs.isotherm.invInterval bool false.caps.config.image.sysimg.measureFuncs.isotherm.maxCount int32 1.caps.config.image.sysimg.measureFuncs.mbox entry.caps.config.image.sysimg.measureFuncs.mbox.enabled bool true.caps.config.image.sysimg.measureFuncs.mbox.calcMask int32 1924.caps.config.image.sysimg.measureFuncs.mbox.maxCount int32 3.caps.config.image.sysimg.measureFuncs.mcircle entry.caps.config.image.sysimg.measureFuncs.mcircle.enabled bool false.caps.config.image.sysimg.measureFuncs.mcircle.calcMask int32 1924.caps.config.image.sysimg.measureFuncs.mcircle.maxCount int32 0.caps.config.image.sysimg.measureFuncs.mline entry.caps.config.image.sysimg.measureFuncs.mline.enabled bool false.caps.config.image.sysimg.measureFuncs.mline.calcMask int32 1924.caps.config.image.sysimg.measureFuncs.mline.maxCount int32 0.caps.config.image.sysimg.measureFuncs.reftemp entry.caps.config.image.sysimg.measureFuncs.reftemp.enabled bool true.caps.config.image.sysimg.measureFuncs.reftemp.calcMask int32 1924.caps.config.image.sysimg.measureFuncs.reftemp.maxCount int32 1.caps.config.image.sysimg.measureFuncs.script entry.caps.config.image.sysimg.measureFuncs.script.enabled false.caps.config.image.sysimg.measureFuncs.script.maxCount int32 0.caps.config.image.sysimg.measureFuncs.spot entry.caps.config.image.sysimg.measureFuncs.spot.enabled bool true.caps.config.image.sysimg.measureFuncs.spot.calcMask int32 514.caps.config.image.sysimg.measureFuncs.spot.maxCount int32 3.caps.config.image.sysimg.visualMarkers entry.caps.config.image.sysimg.visualMarkers.enabled bool false.caps.config.image.sysimg.visualMarkers.spot entry.caps.config.image.sysimg.visualMarkers.spot.enabled bool false.caps.config.image.sysimg.visualMarkers.spot.maxCount int32 0.caps.config.image.sysimg.visualMarkers.arrow entry.caps.config.image.sysimg.visualMarkers.arrow.enabled bool false.caps.config.image.sysimg.visualMarkers.arrow.maxCount int32 0.caps.config.image.sysimg.visualMarkers.box entry.caps.config.image.sysimg.visualMarkers.box.enabled bool false.caps.config.image.sysimg.visualMarkers.box.maxCount int32 0.caps.config.image.targetNoise entry.caps.config.image.targetNoise.enabled bool true.caps.config.image.targetNoise.targetNoiseMk int32 40.caps.config.image.zoom entry.caps.config.image.zoom.enabled bool true.caps.config.image.zoom.maxFactor double 4.caps.config.system entry.caps.config.system.focus entry.caps.config.system.focus.laser entry.caps.config.system.focus.laser.updateFocus entry.caps.config.system.focus.laser.updateFocus.enabled bool false# ID 490I put my serial number in here.# CRC01 cfa0408eI did not change crc01 number at all and there is a space after the crc line.I replaced the original file in the camera and..........nothing changed! can someone help. Thanks.PS. I am trying to make this thread as long as the e4 thread.

author: Chanc3
author_rank: Frequent Contributor
timestamp: November 02, 2015, 02:07:10 pm
content: You must change the CRC number!If you send me your conf.cfg file I will adjust it for you

author: tomas123
author_rank: Frequent Contributor
timestamp: November 02, 2015, 11:52:28 pm
content: Nice service

author: simclardy1
author_rank: Newbie
timestamp: November 03, 2015, 03:39:50 am
content: Chanc3 and tomas123.....you guys are the best. I am finished! I did it. chanc3 you are right. I had to find the crc01 file. I found it on Mikes original post (thanks mike). So then I managed to get the resolution but no menus.....so I changed the ui.d config. still nothing. I discovered that you can't just change the name of the camera at the top of the script. I imagine if you changed it in every file it would be ok. once I did that my menus started working except fusion and pip. SO I have to credit tomas123. In one of his post he said "don't copy and paste but edit" something like that. (did not copy and paste and I am glad for it) sure enough my framegrab entries are a bit different than mikes file. Mine have a framegrab.visual entry.wow. I feel like I learned a lot about computers. it is a nice feeling.

author: tomas123
author_rank: Frequent Contributor
timestamp: November 03, 2015, 11:46:43 am
content: You're welcome!Please tell us, which Exx hardware version (generation) do you updated.

author: simclardy1
author_rank: Newbie
timestamp: November 04, 2015, 01:19:56 am
content: Tomas123, it is the "E30_B 1.1" made in 2012. I had originally called Flir about a problem with viewing captured pictures on the unit so they had me update the software (this did not help). I don't remember which version it was. Now I have 2.23.14. Thanks to you guys I can preview my pictures......AND VIDEO!One more "shout out" there is a utube video by pspgamr that helped me understand some of the computer stuff, like, using FTP and the command prompt commands. It's not exactly the path I took, but does help. here is the linkhttps://youtu.be/oXJYv_MxIHw

author: tomas123
author_rank: Frequent Contributor
timestamp: November 04, 2015, 03:41:56 pm
content: ok, it's an old Exx P/N:490xx without the MSX featurethis is your firmwarehttp://80.77.70.144/SwDownload/app/RssSWDownload.aspx?ID=127

author: simclardy1
author_rank: Newbie
timestamp: November 04, 2015, 09:10:08 pm
content: yeah that's what I have. Tomas, what computer language is the config.cfg file in? just curious.And, would you expect my bluetooth and wifi to work?

author: tomas123
author_rank: Frequent Contributor
timestamp: November 04, 2015, 11:52:10 pm
content: This is no language, only a config fileThere are different hardware versions of E30But user funzt send a feedback of success (bluetooth and wifi)https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg336470/#msg336470https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg336470/#msg336470

author: simclardy1
author_rank: Newbie
timestamp: November 05, 2015, 11:13:37 am
content: my bad. I was trying to use "wifi device" I needed to use "wlan" and then go into settings. Long story short, it works, I was just not setting it up right. I am guessing bluetooth works but have not tested.cheers

author: cuda12
author_rank: Regular Contributor
timestamp: March 12, 2016, 06:40:07 pm
content: If anyone knows the brand of Bluetooth / wlan adapter used in the Exx series please post it. It's tough to gather all the information on Exx upgrades but this post covered a lot of the little differences pretty good. I have a 2013 e30bx updated to a e60 with all the extras but no bluetooth or wifi because the hardware is not in the later built models.

author: targit
author_rank: Regular Contributor
timestamp: March 18, 2016, 02:57:11 am
content: Hi, I have put my "strip down" images of my E30 on imgur, sorry they are not great quality, I just snapped them with my phone to aid reassembly.http://imgur.com/a/tn8aFyou should be able to see the wireless module/PCB , it's buried pretty deep in the camera and will require almost total strip down to get to.sky@eevblog also made a zip file of the images herehttp://imgur.com/a/tn8aF/zip

author: tomas123
author_rank: Frequent Contributor
timestamp: March 19, 2016, 02:23:20 pm
content: it's impressive how many parts used Flir for the Exx series compared to the new generation Flir One with Lepton chip

author: Pinkus
author_rank: Frequent Contributor
timestamp: March 20, 2016, 03:01:32 pm
content: Quote from: targit on March 18, 2016, 02:57:11 amGreat photos. Thank you for sharing.

author: Bill W
author_rank: Super Contributor
timestamp: March 20, 2016, 03:38:56 pm
content: tomas123>>it's impressive how many parts used Flir for the Exx series compared to the new generation Flir One with Lepton chip<<I would put it more as to that is how many more parts you need to make a free standing camera as opposed to a sensor drive PCB which is all a FLIR One is. The only surprise to me was the use and amount of discrete cable looming.Looks a nice F antenna design used for the wifi unitThe double skin on the camera allows the antenna to sit outside the EMC box and inside the environmental box.Bill

author: hikanio
author_rank: Contributor
timestamp: May 21, 2016, 04:00:16 pm
content: Flir E30 49001-1801 Serial # 492xx Success ReportSuccessfully updated the IR resolution, VIS resolution and E60 menu functions. :-)Just a biit surprised, that the cam saves image files without the vis picture if not in thermal fusion or pip mode.This is a slight discomfort as it prevents any Tools MSX conversion of the picture.Also the 492xx cameras seem to miss the cmmunications board so wifi and bluetooth could not be enabled.If anybody could confirm that the lack of the of the slbwver hw component really means the physical absence of the communications modul, it could save me from further investigation. ;-)If anybody needs help with patching his Exx, you'll be welcome.Cheershikanio

author: cuda12
author_rank: Regular Contributor
timestamp: May 21, 2016, 09:13:43 pm
content: Yea I try to take pictures in both thermal and thermal fusion so that if I want to use msx in flir tools that I have that option but the msx conversion is sometimes not very good and regular thermal looks better, I bought flir tools + and it makes no difference.

author: hikanio
author_rank: Contributor
timestamp: May 22, 2016, 09:22:26 am
content: How to find out, if my E30 49001-1801 is physically missing it's wlan/bluetooth modul?As far as I understood from other postings the absence of the hw component "slbwver" is the indicator that something is missing.In my service menu I can see that instead of any Part #, revision # and Serial # there is only an asterisk "*" in the slbwver row.But... in the EEPROM Menu you can actually set these components manually so the absence of the slbwver data is not enough proof for me that this component is physically absent.In theory it might be just not enabled. (Yeah I know, whishful thinking, but the hope dies last ;-) )Edit: In the Power-On Test Log a related interesting entry shows up: "slbwver rev *, serial * detected"Has anybody played around with these settings yet?CheersHikanio

author: tomas123
author_rank: Frequent Contributor
timestamp: May 22, 2016, 03:46:12 pm
content: from my E40:Code:http://192.168.64.1/SysInfo.aspCameraNamePart #Serial #DateFLIR E4049001-2001490xxxx2012-12-22HardwareNamePart #Revision #Serial #...mainboardT1981330119xxxxxslbwverT1978770419xxxxxslioverT1977131319xxxxxx...and the registry entryCode:\>rls -l....version.hw.slbwver: (3)rw--r---r----- 0 root root <a> article "T197877"rw--r---r----- 0 root root <a> revision "04"rw--r---r----- 0 root root <a> serial "19xxxxx"PS: Don't edit your EEPROM!for E4Quote from: mrflibble on November 30, 2013, 02:48:53 pm

author: tomas123
author_rank: Frequent Contributor
timestamp: May 22, 2016, 08:33:29 pm
content: while googling for your E30 hardware, I saw, that you posted also here ;-)https://www.eevblog.com/forum/testgear/flir-e30-config-and-specs/to your question:A sample for another hardware revision of E30 with ID 490xxxxxQuote from: lgustavocampos on December 01, 2014, 11:58:58 pmand this user used an external bluetooth stickQuote from: uski on March 11, 2014, 02:55:38 pm

author: tomas123
author_rank: Frequent Contributor
timestamp: May 22, 2016, 08:54:29 pm
content: Quote from: hikanio on May 22, 2016, 09:22:26 amhere you find a full teardown of an E30Quote from: targit on March 18, 2016, 02:57:11 am

author: hikanio
author_rank: Contributor
timestamp: May 23, 2016, 05:45:08 am
content: Yes, that last picture is what is tempting me to add the SLBW component to the EEPROM. The data on the sticker is that what is entered in the component record...I still have serious doubts that Flir really set up a different production line just to exclude this cheap little piece of hardware.It looks I have the following options1. Wait until somebody takes his E30 180-1 SN 492xx apart or has an x-ray machine to look into it.2. See if I can find a windows CE component that lists the connected hardware.3. Take my own camera apart or just manually set the EEPROM records.But for now I am still too chicken to try the third option ;-)And for the reason I'd like to have the wlan functionality? :I'd prefer Flir tools on Android without the cable as a remote display for the camera.Thanks for you help so far Tomas :-)CheersHikanio

author: hikanio
author_rank: Contributor
timestamp: May 25, 2016, 09:48:38 am
content: Just another experiment:can sombody with an Exx including wlan please post a thermal picture of the cameras head from above (after operating for a while to warm up its guts) , because the hole for the wlan antenna should leave a distinct thermal signature through the rubber casing.Just like the picture I took this morning below. (sorry for the quality, my second cam is a Flir C2 only ;-) )Perhaps the diffenrence can tell me somethng more about the presence of that antenna or even a difference in the casing.CheersHikanio

author: hikanio
author_rank: Contributor
timestamp: June 13, 2016, 01:09:50 pm
content: Just an interesting observation on "enabling" MSX on my non-MSX E30 models.Using the two lines in conf.cfg (appcore):.caps.config.image.framegrab.fusion.hcf entry.caps.config.image.framegrab.fusion.hcf.enabled bool trueshows the MSX function in the Camera menu but only displays a visible cam picture (Tomas123 mentioned this somewhere before).It still might be be helpful as it does show the visible picture in the same FOV as the thermal image and it can also show the tools on top of the picture.I.e. you can see the hot/cold markers of a box on the visible picture.When saving the picture from this mode, it is stored like a "real" MSX picture and what I found quite surprising is if you display the picture in "play" mode, it is already the "real" MSX picture and displayed as such. :-)So the camera does obviously have all the software for creating these MSX pictures, but for now it just doesn't display the picture in realtime.CheersHikanio

author: Chanc3
author_rank: Frequent Contributor
timestamp: June 13, 2016, 08:31:19 pm
content: From speaking with my contact at flir, I was told that it is the hardware that prevents you from using MSX on older models. The newer versions have a better image processor, which enables realtime MSX.Sent from my iPad using Tapatalk

author: tomas123
author_rank: Frequent Contributor
timestamp: June 13, 2016, 09:17:17 pm
content: I can confirm this "crippled MSX" feature with old Exx hardware.I found my old postQuote from: tomas123 on March 16, 2014, 10:59:50 am

author: reallybigone916
author_rank: Contributor
timestamp: July 22, 2016, 04:04:05 am
content: It's confirmed.....Not able to "connect" to Bluetooth or wifi due to missing the communication board on my E30 (S/N 492020XX)Quote from: hikanio on May 21, 2016, 04:00:16 pm

author: tomas123
author_rank: Frequent Contributor
timestamp: September 06, 2016, 02:17:49 pm
content: for information and archiving:FLIR E40 S/N:645XXXXXX F/W:4.11.0Quote from: xbnipx on September 05, 2016, 01:55:44 pm

author: nongken
author_rank: Newbie
timestamp: December 04, 2016, 04:49:11 pm
content: Quote from: tomas123 on September 06, 2016, 02:17:49 pmThank You "tomas123"

author: tomas123
author_rank: Frequent Contributor
timestamp: December 04, 2016, 05:39:50 pm
content: You are welcome!

author: layws
author_rank: Contributor
timestamp: January 04, 2017, 07:45:14 am
content: Thanks this form and everbody. I upgrade E40 with 320x240SN: 645xxxxxxfirmware: 3.12B.7 -> 4.10Q1:Everybody know how to login E40 (2014) service menu?I am try user:flir pwd: 3vlig can not login web service menu.Q2:Where to buy lens plastic cover, please see the attach image.Thanks a lot.

author: Chanc3
author_rank: Frequent Contributor
timestamp: January 04, 2017, 09:14:02 am
content: Quote from: layws on January 04, 2017, 07:45:14 amRE: Q1: in the latest firmware they removed the web service menu. I think they completely removed it. I do still have a backup of the previous firmware, so if someone who has greater expertise wants to compare, then let me know.

author: layws
author_rank: Contributor
timestamp: January 04, 2017, 03:02:07 pm
content: Quote from: Chanc3 on January 04, 2017, 09:14:02 amMaybe you are right ?!I use WIFI connect to E40 and copy files, please see the attached file.No need use USB cable/service folder all empty.

author: Chanc3
author_rank: Frequent Contributor
timestamp: January 04, 2017, 03:07:30 pm
content: Can you try and copy it over?

author: layws
author_rank: Contributor
timestamp: January 04, 2017, 03:09:39 pm
content: Quote from: Chanc3 on January 04, 2017, 03:07:30 pmService menu function, only folder not have any files.

author: Chanc3
author_rank: Frequent Contributor
timestamp: January 04, 2017, 03:35:39 pm
content: I'll see if I can find the files on the older 2012 model of the E60.

author: tomas123
author_rank: Frequent Contributor
timestamp: January 04, 2017, 08:50:11 pm
content: here I posted the web fileshttps://www.eevblog.com/forum/thermal-imaging/flir-e40-upgrade-configuration/msg564687/#msg564687and the config files of my E40 2012https://www.eevblog.com/forum/thermal-imaging/flir-e40-upgrade-configuration/msg565342/#msg565342but read the post from Electrotuna - it doesn't workQuote from: ElectroTuna on December 12, 2014, 05:52:35 am

author: Chanc3
author_rank: Frequent Contributor
timestamp: January 05, 2017, 10:43:45 am
content: Do you not think those files could be transferred over also?

author: tomas123
author_rank: Frequent Contributor
timestamp: January 05, 2017, 12:49:32 pm
content: I think, the binary is crippled in newer firmwaresold pathCode:\Flashfs\system\prodapp.exenew pathCode:\flashbfs\system\prodapp.exe

author: layws
author_rank: Contributor
timestamp: January 05, 2017, 01:26:05 pm
content: Dear tomas123Thanks your help. I used your link about flir web site firmware link.By use E2comb_v2.23.14.fif change ext file name to E2comb_v2.23.14.zipAnd copy E2comb_v2.23.14.zip\FlashFS\system\web\ all folder *.asp and *.inc to E40It can work some function. Pixel Replacement can not work. Electrotuna - it doesn't work, the same resultYou can use WIFI, direct connect to E40. No need hack and use USB cable.I am try reset "Usage statistics" function as well.

author: tomas123
author_rank: Frequent Contributor
timestamp: January 05, 2017, 02:46:23 pm
content: greatcan you make some noise tests?Quote from: tomas123 on December 04, 2013, 11:25:32 pm

author: layws
author_rank: Contributor
timestamp: January 06, 2017, 12:10:49 am
content: Dear tomas123Q1: How to check Temporal noise data? I can try to do a test. ThanksQ2: Would you have 3.12.7 flir firmware? I want to test \web\ *.asp to tryMy data.caps.config.image.services.store.incompatible.enabled bool false.caps.config.image.services.store.incompatible.level int32 0.caps.config.image.settings.downsample bool false.caps.config.image.settings.resIR int32 320.caps.config.image.targetNoise.enabled bool true.caps.config.image.targetNoise.targetNoiseMk int32 5

author: tomas123
author_rank: Frequent Contributor
timestamp: January 06, 2017, 06:08:51 pm
content: Q1: run the noise test in your service menu (look at your screenshot)Q2: if have an old E40 without MSX (P/N:490xx) with firmware 2.23.14 from year 2013http://support.flir.com/SwDownload/app/RssSWDownload.aspx?ID=127Flir never updated the firmware of this "old" cameramy data, but for what?Code:.caps.config.image.services: (1)rw--r--------- 0 root root <e> store.caps.config.image.services.store: (3)r---r--------- 0 root root <b> enabled truerw--r--------- 0 root root <e> incompatiblerw--r--------- 0 root root <e> radiometric.caps.config.image.services.store.incompatible: (2)r---r--------- 0 root root <b> enabled falser---r--------- 0 root root <i> level 0.caps.config.image.services.store.radiometric: (1)r---r--------- 0 root root <b> enabled truethis means, that you add 5mK fake noise to your images.caps.config.image.targetNoise.targetNoiseMk int32 5look at my full dump aboveCode:rset .caps.config.image.targetNoise.targetNoiseMk 60 (MilliKelvin)results in:Code:Temporal noise MilliKelvinPixel Noise 61.28

author: layws
author_rank: Contributor
timestamp: January 07, 2017, 01:45:07 am
content: Sorry no response, maybe 2.23.14 can not copy for 4.10.0

author: Chanc3
author_rank: Frequent Contributor
timestamp: January 08, 2017, 09:26:19 am
content: I have a number of other firmwares for other FLIR cameras, maybe those can help? Unfortunately none of them are from cameras which had MSX.Sent from my iPad using Tapatalk

author: layws
author_rank: Contributor
timestamp: January 08, 2017, 01:58:19 pm
content: Quote from: Chanc3 on January 08, 2017, 09:26:19 amI try those again, T4***, T6*** series firmware still can not use.

author: layws
author_rank: Contributor
timestamp: May 10, 2017, 05:20:02 am
content: FLIR Exx P/N:645xx / 646xx (4.13.0) Update PackWould you have good idea?http://support.flir.com/SwDownload/app/RssSWDownload.aspx?ID=194

author: Chanc3
author_rank: Frequent Contributor
timestamp: May 10, 2017, 06:18:00 am
content: I'd try and not update firmware. The older the better, really.Sent from my ONE A2003 using Tapatalk

author: Fraser
author_rank: Super Contributor
timestamp: September 04, 2017, 01:52:07 pm
content: I finally got around to upgrading my E40 today. It is a MK1 model from 2012 and it had an early firmware installed. IIRC it was V1.3x.I decided to carry out the upgrade over FTP using the USB port, rather than via Wi-Fi, as I needed to know the process in order to help an E30 owner.All went well but after the upgrade the measurement crosshairs were located in the top left quadrant of the screen. I had read about this somewhere else on this forum and I think the owner edited a configuration file X/Y co-ordinate entry to solve it.Remember, I was on an earlier firmware version than recommended for the upgrade files. I chose not to update the firmware first in order to see if the earlier firmware played nicely with the upgrade. It appears that the measurement cross hairs position was the only issue.I carried out the recommended firmware update for a MK1 camera, and all proceeded well. The upgraded configuration files are unchanged by the firmware update and the update stuck. No problems at all. Having checked the dates on the configuration files involved in the E60 upgrade, none are changed by the firmware update process. The measurement cross hair returned to its normal position in the middle of the screenMy E40(E60) is performing flawlessly and is now even more impressive with its increased resolutionNow to help a non IT confident E30 owner update his camera via a conference call. Wish me luck !Fraser

author: HighVoltage
author_rank: Super Contributor
timestamp: September 05, 2017, 09:58:14 am
content: I am about to buy a used E40 tomorrow from a guy and when I have it, I want to upgrade it to E60.Q1:Anything I need to look out for, when I inspect the E40 before I buy it?I guess, if an older FW is installed it is ok but if the newest one is installed it is bad?Q2:What is the recommended FW version for doing an upgrade?Thanks

author: Fraser
author_rank: Super Contributor
timestamp: September 05, 2017, 10:56:09 am
content: @Highvoltage,I am no expert on the Exx series but when I was looking for one, I considered the following when selecting a unit to purchase used.1. Hardware version - forgetting revision numbers here, there are at least four versions of the E40 camera. An easy way to spot them follows. The earliest MK1 version has a solid X-Y navigation pad, the later MK1 has individual navigation buttons but in the same format as the earlier model. The final MK1 version has the individual pad buttons plus rubber port covers on the sides rather than hinged plastic doors. The MK2 E40 is the facelifted version that looks similar to the Ex series in that that it uses the rubberised solid X-Y pad. It also has MSX, unlike its predecessors.Which hardware version is best ? If you desire. MSX you have to buy the MK2. Otherwise they are all very similar. I actively sought out a late MK1 version. I am uncertain whether the earliest MK1 units have Wi-Fi and Bluetooth. Worth checking as it's useful.2. Firmware versions - Forgive me but I do not have a list of firmware versions or specific details of each.I am aware that the MK1 units are not the same firmware as the MK2. The good news is that development of the MK1 firmware was well formed but stopped with the release of the MK2. Why is this good? The MK1 firmware is complete and was never countermeasures against the upgrade. The final version is available on the FLIR web site. My MK1 came with FW 1.3x and I easily upgraded it to FW 2.xx. Nothing was lost in terms of facilities. The service menu is present and accessible via theUSB port.The MK2 firmware contains support for the MSX feature that the hardware supports. The firware has been slightly crippled though. The Service menu has been removed so no service features are available. These include all manner of performance tests, calibration and a dead pixel map updating utility. I wanted the service menu but cared little about MSX so went for the late MK1 model. Updating the dead pixel map can be a real bonus to those who intend to keep the camera for a long time and do not wish to send it to FLIR for calibration etc.To the best of my knowledge, all MK1 and MK2 firmware releases are capable of having their resolution upgraded to 320 x 240. The MK1 can definitely have more advanced menus enabled and these are more than the E60 normally provides ! I am uncertain whether the menu's may be enabled on the MK2 cameras firmware so you need to hear from someone who achieved such themselves.Which model is best ? I personally wanted a solid performer with the Service manual present. Others may prefer the MK2 due to the presence of MSX. I bought an 'as new' E40 from a research company as excess inventory and got it for £1200. I was happy with the model and price. You need to consider the physical condition of the camera (has it been abused), the version (MK1 or MK2), its Wi-Fi status (present or not on early MK1), battery condition as they cost around 100 Euro each !, screen condition (it's a touch screen so not easily replaced if scratched), and price. Do not overpay. There are some quite good used prices on the E40 these days. I have seen $1500 as about average on eBay. Condition seriously effects price though. Mine was mint so I think I got a nice deal.Software ? Some Pro camera owners bought professional image reporting or analysis software such as ResearchIR. The software can be very expensive (thousands of Euros) so getting that with a used camera can be a great bonus. Ensure the activation codes or HASP dongle is present though. If not wanted, the software can be sold separately to recover some money on the deal.Hope this helpsFraser

author: tomas123
author_rank: Frequent Contributor
timestamp: September 05, 2017, 11:01:07 am
content: Quote from: Fraser on September 04, 2017, 01:52:07 pmI can confirm this.The configuration saves the cross hair position at the absolut x/y position.Therefore the cross hair position moves after a change of the resolution.Over the menu you can simple set (and save) a cross hair at the center positionAfter a reset of a configuration (FW update) the cross hair also moves to the center...

author: Fraser
author_rank: Super Contributor
timestamp: September 05, 2017, 11:05:21 am
content: Just remembered..... make sure the charger is present. It uses a weird power connector that I have yet to track down. Some cameras come with the optional charging dock as well. This normally costs around 150 Euros. If you are very lucky, some cameras come with other accessories such as the tripod adapter and shade hood for the LCD. Cameras with optional lenses usually cost far more so are rare at good prices. All accessories for the Exx are very expensive as is common in this market segment. Even the LCD shade costs around 50 Euros.Fraser

author: Fraser
author_rank: Super Contributor
timestamp: September 05, 2017, 11:06:51 am
content: @tomas123,Thanks for the information on the cross hairs position issueFraser

author: Fraser
author_rank: Super Contributor
timestamp: September 05, 2017, 11:29:03 am
content: This may have already been covered, so sorry if it has.When upgrading my E40 I had a set of configuration files provided by a fellow forum member, complete with my unique CRC01 entries (he kindly calculated them for me before sending the files) I chose not to use the files as I wanted to do the upgrade process from scratch in order to talk another forum member through the exact process.I used the original E60 file capture as the source of the configuration files I used. I ended up with a hassle free upgrade to standard E60 spec. All good so farLast night I decided to try the files provide by my fellow forum member as they had more functions enabled in the menu's. Whilst the change to the enhanced menu configuration appeared to go well, I did notice a weird problem. At this point I should say that the menu configuration files appeared to have everything enabled and there were even two additional line entries. The camera appeared to behave normally and even included the useless MSX selection menu option !Now the problem. I saved images and the camera seemed to carry out the IR and VIS save just fine with the small thumbnail image briefly appearing at the top of the screen. I did notice a flash of noise across the screen when initially pressing the save trigger though. After multiple saves I did get one Save Error warning.Upon using the playback button I could see that whilst my image files existed, only the visible images were present. The IR imagescontained only the Overlay and cross hair data, no image data. Weird ! All were the same. This only happened after installing the 'fully loaded' configuration files.I am thinking that it is possible to enable too many features for the MK1 camera hardware to cope with ? I know that this firmware resides in more capable camera models and the functions that have been enabled in the fully loaded configuration files are intended for those more powerful platforms. They may work, but their presence could be causing issues with the Exx series camera ?Has anyone experience of this issue ?I have re-installed my original vanilla E60 configuration files for now and normal operation is restored. Images save just fine. I have to change the target noise generator setting to zero though. It is currently set to 40mK.I will be selecting only certain useful additional menu features in my own custom configuration files and hopefully the image save issue will not be triggered by them.I should state that the camera worked perfectly in every other respect when the image save issue was present. Thank goodness it is so easy to change out the configuration filesFraser

author: Fraser
author_rank: Super Contributor
timestamp: September 06, 2017, 11:28:55 am
content: Well I have carefully studied the "fully loaded" configuration files that caused my E40 to not store the IR image data in saved image files. The only thing that looks possibly responsible for the issue is the addition of two configuration lines to the image fusion section. I suspect that they may be MSX related ? As my MK1 camera cannot provide MSX, they are spurious. There is also the fact that I applied the configuration files of a later firmware to an early 1.33 firmware. That may not have been such a good ideaWow there are a lot of options for image measurement and analysis that are not activated in the standard E60 configuration. I suspect these are used in the T6xx cameras as more advanced thermography tools. I shall be considering which of the functions I actually need and will activate them. I certainly do not need the health screening options ! Enabling options that are not actually needed can make the menu's too 'busy'.When I updated the firmware on my camera from 1.33 to 2.23 all went without a hitch. The update produces a comprehensive, commented, log of its activities during the process. That made interesting reading. None of the configuration files that we changed to upgrade to an E60 spec are changed by the firmware update. Hence why the resolution hack sticks even after a FW update. It is interesting that the firmware update clearly identifies my camera as an E40 model before starting the update though. The fact that the configuration files are identified as E60 makes no difference. I suspect that the camera model is held in an eeprom along with the serial number, as in the E4. No need to mess with that though. The camera does not care.This is the first time I have actively delved into the Exx series file system. It has been interesting. If anyone wants to see the firmware update log, I will upload it. It is purely for interest as it just shows the various checks and balances that the irmware updated carries out before actually changing anything, and its final checks before rebooting the camera. It looks a pretty robust firmware update system to avoid bricking cameras. It even checks if the camera is on external power or has enough battery charge to proceed !Fraser

author: Fraser
author_rank: Super Contributor
timestamp: September 06, 2017, 11:35:57 am
content: Whilst reading through this E40 thread I saw some configuration files that people were uploading to upgrade the resolution. The files still had the target noise generator set active and at level 40. I hope all of you who upgraded your cameras changed this setting to inactive (false) and set the level to 0 (not strictly necessary as the false setting disables the noise generator).Changing this configuration entry removes 40mK of false noise from your camera and improves the image quality, especially at small temperature spans.I thought I would just mention this in case no one had done so previously in this thread.Fraser

author: Pinkus
author_rank: Frequent Contributor
timestamp: September 07, 2017, 09:13:38 pm
content: Thank you for all the input here Fraser!I remember you were trying to get a tripod adapter for the E40 and that you were not satisfied with the original Flir adapter. I did not see the outcome of it - I might have missed it. May I ask if you found a solution for Exx and tripod? Thanks!

author: Fraser
author_rank: Super Contributor
timestamp: September 07, 2017, 09:56:54 pm
content: Hiya,No I have yet to create a tripod adapter with which I am satisfied. The issue is that unless the adapter grips the sides of the camera, it is possible for the camera to rotate around the single M5 mounting screw that FLIR elected to use. They could have designed a far better mount point, like the Picatinny rail.I was given the official FLIR mount by a friend who no longer needed it. So I do have a means to attach the camera to a tripod. I shall continue to develop a better solution though.Fraser

author: tomas123
author_rank: Frequent Contributor
timestamp: September 08, 2017, 08:08:43 am
content: Quote from: Fraser on September 06, 2017, 11:35:57 amYes, two years ago we had a hard discussion in this forum about this topic.with bash/cmd set noise to zeroCode:rset .caps.config.image.targetNoise.targetNoiseMk 0 (MilliKelvin)... and compare my E40 (without MSX) with your E40(25°C room temperature)service menu / diagnostic / noise testCode:Temporal noise MilliKelvin Digital UnitsPixel Noise 19.85 3.93Row Noise 6.39 1.26Column Noise 8.64 1.71Spatial noise MilliKelvin Digital UnitsPixel Noise 18.98 3.76Row Noise 4.70 0.93Column Noise 5.54 1.10Uniformity 210.23 41.63Total noise MilliKelvin Digital UnitsPixel Noise 28.96 5.73Row Noise 5.76 1.14Column Noise 7.66 1.52compare with 60mk noiseQuote

author: tomas123
author_rank: Frequent Contributor
timestamp: September 08, 2017, 08:17:53 am
content: Quote from: Fraser on September 06, 2017, 11:28:55 amAs far as I remember, my E40 (non MSX) had the same behavior with activated msx over a configuration file.I think, the computation-intensive MSX overlay is coded in hardware by a DSP.Therefore the MSX feature can't added by a software update.

author: Fraser
author_rank: Super Contributor
timestamp: September 09, 2017, 10:26:58 pm
content: An update on the upgrade of my E40 camera.I have now enabled just about all of the extended features on this camera. It now has many features not normally found on the standard E60The enablement of the features created no problems for the camera at all and it is working very well.The two configuration files that I have been working with are attached for readers interest. They are simple to set up but not all the features appear to actually appear on the cameras menu's.Has anyone managed to use the following features on their Exx camera please ?GUI configuration file1. Panorama mode. No menu option appears in the camera mode menu that contains Camera, Video and Program options.2. Fastshoot mode No idea what this mode can actually do.3. PIP locked ? No idea what that actually is intended to do.4. Presets - User presets for measurements (macro's if you prefer) I have the Preset menu option but no preset configuration entry in the setup menu.Fraser

author: Fraser
author_rank: Super Contributor
timestamp: September 10, 2017, 09:15:27 pm
content: I have now finalised my APP and GUI configuration files to provide all useful functions on my camera.I ended up disabling the weird cryptic settings as they are not needed. I also disabled the User Presets as they cannot be configured with the current menu structure. Some functions invoke menu 'buttons' whilst I believe some of the more exotic functions would need 'buttons' to be added to the standard Menus with further file modifications, as with the E4.I attach my two configuration files in case anyone has need of them. I have basically enabled all that is available to use on the E40 camera and it is working perfectly as an E60+. I am very pleased with the upgraded cameras capabilities and performanceThe PIP lock function did what it says ... it prevented moving and resizing of the PIP thermal overlay image. Not a desirable option to activate. Sadly Radiometric video recording also proved to not be available even if activated in the configuration.Fraser

author: HighVoltage
author_rank: Super Contributor
timestamp: September 11, 2017, 12:03:34 pm
content: Thank you Fraser for the feedback and buyers guide to the E40.How about theE40bxCan it also be hacked the same way?The only difference between the E40 and the E40bx seems to be the temperature range, right?- E40 =up to 1202 °F (650 °C)- E40bx =up to 248 °F (120 °C)Anything else, that speaks for or against the E40bx?Thank for any feedback.

author: Zucca
author_rank: Unknown
timestamp: September 11, 2017, 12:33:54 pm
content: HighVoltageaccording to my quick investigation it can be hacked.Also the Thermal Sensitivity is different <0.045°C vs <0.07°C (not bx versions)...The 120°C spec could be a limit for soldering/preheating... I would prefer the 250°C like the E4...PS:, Good luck!

author: Fraser
author_rank: Super Contributor
timestamp: September 11, 2017, 01:01:43 pm
content: Thermal sensitivity on these cameras is a product of the microbolometer, lens and the FLIR false noise generator. The microbolometer and lens remain the constant with FLIR tweaking the added noise for each model spec. The noise generator gets switched off as part of the upgrade so you have the best available NETD that the hardware can provide. Calibration is unaffected.Fraser

author: Fraser
author_rank: Super Contributor
timestamp: September 11, 2017, 01:09:55 pm
content: Highvoltage,As Zucca stars, the E40bx can be upgraded to E60bx specification and beyond. It cannot have its temperature range simply increased though as the factory did not calibrate the higher temperature mode.The bx has some building thermography specific modes enabled but these are easily enabled on a standard camera as well.Fraser

author: Pinkus
author_rank: Frequent Contributor
timestamp: September 11, 2017, 01:53:49 pm
content: Quote from: Fraser on September 11, 2017, 01:09:55 pmMmmmh - I read the above statement several times in different threads and I was always wondering, where this information came from, as my modded E30bx is able to work with higher temperatures. I just need to change the settings (at menu'settings, temperature range'from -40°C - +120°C to the setting 0°C - 650°CLook at my examples. I attached 2 files:1) JBC soldering iron set to 360°C (bottom: reflection from the working area)2) hot air reworking station (air exit) set to 500°C (which is the maximum I can set it to).The E30bx (after modding it is reporting E60bx) works like a charm.Should I call me lucky that Flir did calibrate my unit? Maybe this is the case as my unit also contains Wifi and Bluetooth modules which were not working when it was a E30bx but which are working now after modding it to a E60. Does other units do not have this temperature selection menu available?Please note: the information "FOV 45°" (lower left corner) is wrong in this case. I did not install the wide-angle lens and forgot to change the setting at the camera (unfortunately the Flir cannot detect a lens change automatically).

author: Zucca
author_rank: Unknown
timestamp: September 11, 2017, 02:37:41 pm
content: Well in the first picture the closest number I see to 360 is "Max 347", in the second one is "Max. 502" regarding the 500.As there is so much going on with metal surface and emissivity coeff. I would not trust your experiments as proof everything is working like a charm.As I know you need a thermocouple and a black surface hot body to do a proper test.Anyway good to know there is a temp. range setting you can change.Now I step back and let the experts tell their opinions on this.

author: Fraser
author_rank: Super Contributor
timestamp: September 11, 2017, 02:51:31 pm
content: From what I understand, the bx series is shipped with an accurate calibration table for range 1 but range 2 calibration table is at default settings. These are correction tables so even the default values will likely not be miles out, but they will be unclaibrated values.A significant cost in thermal camera production is the calibration of each camera. No two cameras are identical so quality cameras are individually calibrated in a large multi-Black body calibration rig. Each calibration run takes time so by missing out the range 2 calibration cycle, time and money is saved. From FLIR's perspective, why calibrate a range that is not normally accessible ? It is not like the bulk production of a single PCB for multiple versions of a camera.I am very pleased that you have proven that the bx does actually permit the second range to be selected. I will be helping a bx owner upgrade their camera soon and was unsure whether the second range would be available for him to select.IIRC Chanc3 reported that he sent an upgraded bx camera for calibration checking. It failed calibration checks because the second range was enabled and so checked by the calibration house. It was found to be inaccurate, leading to a calibration check fail. Chanc3 may have more insight into the level than f temperature error that was found.I would never want to mislead anyone into thinking that enabling a non calibrated temperature range will provide correct imaging or measurements. Working uncalibrated is something the user needs to carefully consider. If 'just' an image is needed, I do not see any great problems. If reasonably accurate temperature readings are needed in an uncalibrated range, I would recommend a simple calibration check at various temperatures using a variable temperature soldering iron with dull tip and a thermocouple thermometer monitoring surface temperature. Soldering iron tip temperatures are not known for high accuracy unless carefully calibrated on the base station.In summary, I am really pleased to hear that the second temperature range is available on the bx. Is it's accuracy predictable ? I suspect not, but happy to be proved wrong. FLIR use decent Microbolometers so the baseline default calibration table entries may be pretty close to those after formal calibration.There is, of course the matter of the SERVICE MENU and what it can do for youBut that's another storyFraser

author: Fraser
author_rank: Super Contributor
timestamp: September 11, 2017, 02:58:37 pm
content: Some pictures of the calibration rigs at FLIR. I saw one with a row of E2's lined up for calibration but I can't find a picture of it to upload.Fraser

author: Pinkus
author_rank: Frequent Contributor
timestamp: September 11, 2017, 03:01:50 pm
content: For me, usually the temperaturedifferenceis important as the Flir is not very accurate anyway (±2°C or ±2% of reading according to the datasheet). At 500°C this makes plus/minus 10°C. I would not use a thermal camera for checking if the soldering iron is having the correct temp.

author: Pinkus
author_rank: Frequent Contributor
timestamp: September 11, 2017, 03:07:54 pm
content: I think that the E30with Wifimodule might be calibrated. I suspect that Flir at one time produced the cameras in batches for stock and then -depending on the market need- just reinstalled the needed configuration files for E30, E30bx, E40, etc. up to E60. If somebody tolds me where the configuration files are (I have no time right now for searching), I can try to upload it here. Then it should be easy to check it against others to see if there is a common default file or if they are all different.

author: HighVoltage
author_rank: Super Contributor
timestamp: September 11, 2017, 03:45:20 pm
content: Very good information on the bx version, thank you everyone.Especially that the temperature range can be changed is very helpful.The one that was offered to me by another company has the serial number 4903xxxxand is allegedly from 2013 with FW 2.19 installedOn the Flir download site I see different firmware updates for the following ranges:- P/N 785xx-xxxx- P/N 490xx-xxxx- P/N 645xx-xxxx- P/N 646xx-xxxxSince the one offered to me falls right in to the second category, is that good, bad or may be does not matter?

author: Zucca
author_rank: Unknown
timestamp: September 11, 2017, 03:54:33 pm
content: According to here:https://www.eevblog.com/forum/thermal-imaging/flir-e40-upgrade-configuration/msg561542/#msg561542it's the one without MSX, me and Fraser like these ones more then the MSX others.FW can go up to 2.23.14 if I understood correctly.The bx is not for me. I mean I have already a calibrated E4, a Exxbx would be a step back at the end.Of course if you just need an rough idea where the temperatures are, then a bx with the high range selected can do the job,Pinkusis right.

author: Fraser
author_rank: Super Contributor
timestamp: September 11, 2017, 03:55:25 pm
content: The firmware is the key here. My MK1 E40 came with firmware 1.33 that I updated to the last available for the MK1, that was version 2.23. Firmware 2.23 is complete and not messed about with by FLIR. Firmware update is painless and uses an SD card loaded with the firmware update file.The firmware sets what can, and cannot be done to the cameras configuration. Even the MK2 can be upgraded to E60 spec, but it lacks the service menu. You should be fine with firmware 2.19. FLIR did not mess around with the Exx firmware as they have with the more common E4.There are three versions of the MK1 that I know of. The final version has plastic/rubber side doors that hingle forward rather than up. My MK1 Gen 2 has the original "gull wing" side door design.Fraser

author: Fraser
author_rank: Super Contributor
timestamp: September 11, 2017, 03:59:42 pm
content: To come from me shortly in this thread......1. An explanation of the various options that may be enabled in the Exx firmware. They are all listed in the configuration files but do you all know what they are ? For those who do not, I will try to explain. Some do remain a mystery though!2. Close-up lenses and the Exx camera series. Can a close-up lens be easily attached to the Exx and is there vignetting ? We will find outFraser

author: Fraser
author_rank: Super Contributor
timestamp: September 11, 2017, 05:55:51 pm
content: Test of some close-up lenses mounted on the E40(E60+) completedNot surprisingly the professional Inframetrics and Agema/FLIR lenses performed best but then they are almost 60mm diameter of high quality Germanium ! They also cost a small fortune. I include them as a reference only and not a serious proposition for many Exx camera owners.Mounting a close-up lens on the Exx series :Fortunately the Exx series standard 18mm lens has a parallel lens barrel plus a rubber grip sleeve that extends beyond the lens barrel chassis. There is no threaded section inside the lens barrel. There are many options for mounting an auxilliary lens to such a lens barrel but the two that come to mind are:a) A friction fit inside the rubber lens surround.b) A slip on type lens holder that mimics the fitting of the rubber lens cap. Many sizes of rubber and plastic push on lens caps are available on ebay for very little money. Look for binocular lens caps as well as camera lens caps. Binoculars tend to use push on lens caps more often that cameras do. The close-up lens may then be mounted directly into a suitable hole cut into the lens cap, or first mounted into a threaded lens holder before that is fitted into the lens cap hole. This is my preferred mounting method for auxiliary lenses. Suitable threaded lens holders for 19mm and 20mm lenses can often be found on ebay as they are a vintage photographic accessory. They are often cheap.I elected to make a cardboard lens holder tat was pushed into the rubber lens surround. It worked a treat but I would likely go down the lens cap rout for a more long term solution.The test piece for the images :I wanted a simple test piece that had at least one small SMD component that presented a decent target for the camera and that was representative of what would be imaged on the test bench. I found an old ADSL USB modem that fitted the bill nicely.The chosen component on it was a nice warm 5 pin SMD device for which I will provide dimensions. I will also provide the dimensions of the whole PCB as a reference. I will also provide other images of the PCB and an overall image taken with the E60 at closest manual focus with no close-up lens fitted.The lenses tested:1. 20mm diameter 100mm (4") FL ZnSe Planar Convex from China. Normally used in CO2 Laser cutters.2. Inframetrics 60mm diameter 300MM (12") FL Close-up lens - Germanium3. Inframetrics 60mm diameter 150MM (6") FL Close-up lens - Germanium4. Agema/FLIR 55mm diameter 150mm (6") FL Close-up lens - Germanium5. EEV ARGUS 2 rear Germanium lens element - Spec unknown. Aperture 25mm6. EEV ARGUS 2 front Germanium lens element - Spec unknown. Aperture 20mmTest PCB Dimensions: 98mm x 63mm5 pin SMD (PCB ID: U7) component dimensions :Plastic case : 2.94mm x 1.7mmAcross full width of pins: 3.16mmResistor (PCB ID: R8) DimensionsCase including solder areas 3.24mm x 1.55mmPictures to follow .... time for my tea nowFraser

author: Fraser
author_rank: Super Contributor
timestamp: September 11, 2017, 05:58:20 pm
content: Lens 1 - 20mm diameter 100mm FL Znse

author: Fraser
author_rank: Super Contributor
timestamp: September 11, 2017, 06:01:31 pm
content: Lens 2 - Inframetrics 60mm diameter 300mm FL Germanium

author: Fraser
author_rank: Super Contributor
timestamp: September 11, 2017, 06:03:49 pm
content: Lens 3 - Inframetrics 60mm diameter 150mm FL Germanium

author: Fraser
author_rank: Super Contributor
timestamp: September 11, 2017, 06:07:06 pm
content: Lens 4 - Agema/FLIR 55mm diameter 300mm FL Germanium

author: Fraser
author_rank: Super Contributor
timestamp: September 11, 2017, 06:09:54 pm
content: Lens 5 - EEV Argus 2 rear Germanium lens

author: Fraser
author_rank: Super Contributor
timestamp: September 11, 2017, 06:13:59 pm
content: Lens 6 - EEV Argus 2 front Germanium lens

author: Chanc3
author_rank: Frequent Contributor
timestamp: September 11, 2017, 06:42:12 pm
content: @Fraser spotted your mention! Yes, when we sent a camera back to FLIR for full calibration (not a check), I turned an extra temperature range on (not an original one) , to see what they would do. When I got it back, they had turned it off again!In a second instance of my playing around with a P620, I had left a higher, uncalibrated range on. It then went off for a calibration check, and low and behold, it failed spectacularly! Must have been out by 60° or so.We now have two 6" fluke blackbody calibration sources at the office and I will be happy to check out the accuracy of a bx model and if possible, calibrate the higher range. If any one wants to send theirs in and pay return postage, I'll happily do this for free. Please bear in mind that we're UK based.Fraser, when you updated the firmware, did you lose access to the service menu?

author: Fraser
author_rank: Super Contributor
timestamp: September 11, 2017, 06:47:18 pm
content: Chanc3,Thanks for the clarification on the ranges issue.My upgrade to firmware 2.23 did not disable my service menu. All is well on that frontFraser

author: Fraser
author_rank: Super Contributor
timestamp: September 11, 2017, 06:58:54 pm
content: A final thermal image that I took of the PCB using the E60 set at close focus without any auxiliary lens fitted.

author: HighVoltage
author_rank: Super Contributor
timestamp: September 11, 2017, 07:09:15 pm
content: Quote from: zucca on September 11, 2017, 03:54:33 pmInteresting!Why do you think the Exxbx is a step back over the E4So you would prefer the E4 to E8 mod over a E40bx to E60bx mod?If so, why?Thanks for a feedback

author: Fraser
author_rank: Super Contributor
timestamp: September 11, 2017, 07:13:42 pm
content: Highvoltage,I think Zucca is referring to the E4 250C max temp Vs the E60bx official 120C max temp.Fraser

author: Fraser
author_rank: Super Contributor
timestamp: September 11, 2017, 08:17:47 pm
content: Apologies, the IR pictures got a little mixed up in my previous posts for the Close-up test. Now all corrected. I re-took the Inframetrics and Agema lens pictures as I had them mixed up. Poor preparation and record keeping on my partFraser

author: Fraser
author_rank: Super Contributor
timestamp: September 11, 2017, 08:55:28 pm
content: OK, its time for a conclusion to the Close-up lens test.The E40 is pretty god at PCB imaging using its manual focus lens. Not good enough for detailed analysis of small components though. The standard 100mm FL ZnSe lens was a bit of a surprise. I expected more vignetting but instead I found its focus distance to be a bit too close for everyday use. It starts getting into thermal microscope territory ! This is too much when just wanting to carry out a thermal survey of SMD components on a PCB. The Inframetrics and Agema dedicated close-up lenses provided the sort of field of view that is useful when surveying a PCB. Just enough to provide useful information on each component. The EEV Argus 2 lenses were also interesting. The rear lens has too shrt an FL and I found it hard to get close enough to the PCB in order to get any sort of acceptable focus. The front lens was excellent though. A good close-up lens for nice detail of small components. A very crisp image was produced as well. Sadly that EEV front lens is in very short supply as it is the one that gets corroded whilst in service on the ARGUS 2 fire fighting camera.So interestingly, the 100mm FL ZnSe lens, when used on the Exx series 18mm standard lens, is really too close an FL and provides too narrow a field of view for optimum use. Sadly the 100mm FL is about the longest FL that can be bought cheaply.Fraser

author: Pinkus
author_rank: Frequent Contributor
timestamp: September 11, 2017, 09:50:13 pm
content: Quote from: Fraser on September 11, 2017, 08:55:28 pmThere are ZnSe lenses available with e.g. 7.5" FL (~200mm) for not too much money (approx. 30-50 Euro), though only with 20 or 25mm diameter. Would you think these would work or would the diameter be too small?

author: Zucca
author_rank: Unknown
timestamp: September 11, 2017, 10:04:18 pm
content: Quote from: Fraser on September 11, 2017, 07:13:42 pmCorrect

author: Fraser
author_rank: Super Contributor
timestamp: September 11, 2017, 11:13:35 pm
content: Pinkus,I like using a 100mm FL lens with my E4 as I get the FOV that I am comfortable with for PCB surveys.The Ex series have a 45 degree FOV. The Exx series standard 18mm lens has a 25 degree FOV.Some simple maths suggests that for a close-up lens on the Exx camera to provide the same PCB coverage as the wider FOV E4 setup, It will need an FL of 1.8 times that used on the E4. Or to be more precise it will need a close-up lens of FL 180mm (7.2").A 7 to 7.5" FL would be close enough really. Some users prefer the 63mm FL lens on the E4. They would want a 100mm (4") lens as tested here. I personally would use such only for investigation of single components. Too small a PCB coverage for my personal needs.As to diameter. The lens on the Exx is around 25mm diameter. Not all of it is necessarily active however. The FOV is a relatively tight 25 Degrees so it should be possible to get away with a 20 to 25mm close-up lens positioned as close to the cameras objective as possible. My 20mm lens was some distance away and there were definitely losses towards the edges. The main area of interest tends to be central in the image so some vignetting is often permissible. Microscopes produce circular images after allCost is the issue with increasing the lens diameter. The ZnSe lenses used for CO2 laser focus are now mass produced, so very inexpensive. Anything else is likely to be from a more specialist supplier for lab use and so more expensive. It comes down to what you need, what you can live with and what you can afford really. I am very lucky to have the large Inframetrics and Agema close-up lenses. They will not be the easiest to mount on an Exx camera though as they are quite heavy. I will likely work up with a ZnSe Close-up lens solution for my Exx camera. A 25mm diameter 7.5" FL lens would be a great start. 35mm diameter would be even better, but that gets expensive.Hope this helps. Take a look at the two sets of images provided by the Inframetrics and Agema 150mm FL lenses. That is very close to what a 7.5" FL lens would provide. Such a lens us halving the minimum focus distance of the Exx camera so it is basically a X2 magnification factor at minimum focus.I will post some quick and dirty vignetting pictures I took when using the 20mm diameter lens. That will have to wait until tomorrow though. Time for sleep nowFraser

author: Bud
author_rank: Super Contributor
timestamp: September 20, 2017, 01:28:15 am
content: Quote from: Fraser on September 09, 2017, 10:26:58 pmNot on E40 but this is User Presets from a doctored E4.Here we have a Average Box and a Line measurements. Having a Line also produces a graph of the thermal profile (at the screen bottom) along that line as you point to objects.Panorama did not work,Video did not work.Can't remember seeing Fastshoot or PIP locked features.

author: Serpiph
author_rank: Contributor
timestamp: October 31, 2017, 09:06:04 am
content: Hello to everyone!I got my E40bx (ID: 645xxxxxxx, FW: 4.13.0) camera with some features activated by previous owner. I read E4 upgrade thread and this thread also. First of all I change config files to enable all potential features. During my tests with E40bx I found some interesting things.1. I found blend mode which I don't see on FW4.11.0. It works fine.2. Some features are hidden in menus by simply removing lines from xml files. For example multiple selection, sketching, PDF creation, preview mode, timelapse, screening, adding lines with histogram, circles during edit mode.3. Some features I can't activate: panorama mode, five point preset, adding points, boxes, lines and so on during measurement, user preset mode.4. Some presets are not visible even when I activate needed config parameters and rls shows them activated.5. Unfortunatelly PDF creation and sketching don't work when I try to use them.Panorama mode needs .caps.config.image.framegrab.panorama parameter but I can't understand how to create it. I try to enter line into conf.cfg and try to use rcreate/rset programs but get nothing. Also I try to create .caps.config.image.framegrab.panorama.enabled bool parameter and also fail.Please help me with xml config files you have especially those from E60. As I think PDF and sketching don't work because of signal interaction absence.

author: Serpiph
author_rank: Contributor
timestamp: October 31, 2017, 09:39:55 am
content: Quote from: Fraser on September 09, 2017, 10:26:58 pmHello!1. I can't activate panorama mode also but I find parameters referred to it. I still searching info how to activate it.2. Fastshoot mode I don't yet research. I think it means quickly save image without preview edit.3. If you unlock PIP, you can move and resize PIP window. To test select PIP mode, touch PIP window as you touch spot or mbox measurement tool, then PIP options window opens and you can do what you need.4. This is the strangest mode. I try but yet get nothing with it.By the way my camera is HW1.1 (newer).

author: Serpiph
author_rank: Contributor
timestamp: October 31, 2017, 02:28:08 pm
content: It becomes more interesting.1. I add video type to menu (CSQ or MPEG) but receive video record error in CSQ mode. MPEG mode restores normal video mode. It seems to be codec absence in camera.2. Sketch menu is activated but not yet correctly filled with data. So I have to hard reset to exit the sketch mode

author: Bud
author_rank: Super Contributor
timestamp: October 31, 2017, 03:24:53 pm
content: Panorama may require compass/accelerometer hardware be present. If your camera does not have that hardware installed, panorama will not work. It makes sense, the camera should somehow know that you turn around and in which direction when taking a shot.

author: Fraser
author_rank: Super Contributor
timestamp: October 31, 2017, 03:26:15 pm
content: Interesting stuff, keep it comingI have enabled sketch mode and it is working fine on my MK1 camera. I just enabled it in the configuration. I am thinking that some of the features in the configuration menu also require the oresence or at least enablement of linked files elsewhere in the cameras firmware. I am no expert though. I need to talk to Bud as he is happily enabling all manner of functionality in the 2017 model E4 camera !I did not think I would use sketch or text annotation modes but they are good for reminding me of am issue in an image when I later revisit the stored images.From memory, Panorama mode just places a set of grid lines on the screen to help maintain horizontal panning of a scene. Nothing more clever than that. I was hoping for sequential capture and auto stitchingI will need to dive inside my cameras firmware again in order to help someone upgrade an E30. I shall revisit the additional functionality then.Fraser

author: Serpiph
author_rank: Contributor
timestamp: October 31, 2017, 07:12:26 pm
content: Quote from: Bud on October 31, 2017, 03:24:53 pmI found interesting thing: parameter '.caps.config.ui.mode.panorama' exists, but program tries to find parameter '.caps.config.image.framegrab.panorama'. And I can't create the last one. Maybe an error in firmware? Compass existense is not required if firmware can compare shots to find intersections. Ordinal stiching programs does not need compass info, just give them the right image sequence.

author: Serpiph
author_rank: Contributor
timestamp: October 31, 2017, 07:29:12 pm
content: Quote from: Fraser on October 31, 2017, 03:26:15 pmCould you send me your xml config files to compare with mine?By the way, I look into update pack for Kx5 cameras and found full web access to service functions. Maybe it will be interesting to you. Unfortunately E75/85/95 cameras use debian on board and are useless to compare with previous series.

author: Fraser
author_rank: Super Contributor
timestamp: October 31, 2017, 07:33:06 pm
content: I have a MK1 and it has full service menu accessThat Is why I purchased a MK1 rather than a Mk2. I have the full functionality including dead pixel map update.Can you direct me to the XML config files you desire please ?Fraser

author: Serpiph
author_rank: Contributor
timestamp: October 31, 2017, 07:42:26 pm
content: Quote from: Fraser on October 31, 2017, 07:33:06 pmMy files are \FlashBFS\system\ui.d\design_ui_e2.xml and \FlashBFS\system\ui.d\toolbar-config_e2.xml. Your files may exist under \FlashFS.

author: Serpiph
author_rank: Contributor
timestamp: October 31, 2017, 07:57:04 pm
content: Here my exercises are shown

author: Serpiph
author_rank: Contributor
timestamp: October 31, 2017, 08:02:53 pm
content: And my configuration parameters in camera menu

author: mikhail076
author_rank: Contributor
timestamp: November 15, 2017, 07:46:33 pm
content: pls can anybody shareflir_exx_pn645_pn646_v3.12.7_update_pack.ziponce again?thx

author: Fraser
author_rank: Super Contributor
timestamp: January 13, 2018, 04:44:26 pm
content: New firmware release for Exx series MK1An I nteresting development..... So FLIR released an updated firmware for the old Exx MK1 series in September 2017 !Me thinks that unusual as they have ignored the earlier Exx series for yearsUnder no circumstances install firmware 2.26 if you are intending to upgrade. It very likely has some nasty surprises inside it.Anyone interested in this new firmware can download it on the FLIR support site.http://flir.custhelp.com/app/account/fl_download_softwareFraser

author: Chanc3
author_rank: Frequent Contributor
timestamp: January 13, 2018, 04:46:15 pm
content: I'll give this a go on our E60 - see what happens! Will verify if I get locked out of the backend.

author: Fraser
author_rank: Super Contributor
timestamp: January 13, 2018, 04:50:04 pm
content: Cheers Chanc3It seems strange that FLIR would release any form of upgrade on such an old platform. I have to wonder whether it contains anti-upgrade 'devices' or deletion of the service menu.I await your findings with interestFraser

author: Chanc3
author_rank: Frequent Contributor
timestamp: January 13, 2018, 04:50:37 pm
content: Quote from: Chanc3 on January 13, 2018, 04:46:15 pmI'm not sure if FLIR include release notes or change log? Does anyone know?As a general rule of thumb I never upgrade firmware/software unless there is a relatively detailed one!

author: Fraser
author_rank: Super Contributor
timestamp: January 13, 2018, 04:53:00 pm
content: The only comments I have received from FLIR on a particular firmware update was"Minor bug fixes plus some housekeeping stuff"The "housekeeping stuff" was actually changes made to make the upgrade harder for us !Fraser

author: Fraser
author_rank: Super Contributor
timestamp: January 14, 2018, 03:05:14 pm
content: In case anyone needs it, I have uploaded Mk1 Exx firmware 2.23 here:http://www.filedropper.com/flirexxpn490v22314updatepack1Fraser

author: Paw85
author_rank: Regular Contributor
timestamp: February 23, 2018, 07:08:24 pm
content: I hope I'm posting this in the correct thread as I was unable to find a general Exx thread.I'm working on a "ful-hack" as we swedes call it, an ugly but working solution to a problem.It removes Flir logo and set jpg quality to 100% after coldboot automagically.This ful-hack is designed for Exx v1.0 and v1.1 (P/N:490xx) with firmware 2.23.14 or earlier.The only way found to do this that I had found previously was to boot camera, connect via telenet and manually input the commands, EVERY time cold-booting the imager.Noticed that it was possible for us with a Exx v1.0 and v1.1 to edit the applaunch files and finding that out, made it possible to launch a batch file located on the root of the SD card.This made it possible to get the camera to cold-boot, and load the commands to remove logo and set jpg quality, without an external computer.It's also possible to exchange the batch file on the SD card after the imager has finished running the commands in it, so no need to FTP stuff to it to change the commands either.Please note that these are "beta" files, they have worked every single time on my imager, but I do not know how they act on other individuals, but you can open the files yourself in notepad and inspect them, they do not contain any commands that should damage the camera.Also, if you decide you dont want to run the batch file for the time being, you dont need to edit the applaunch, just rename or remove the batch file from SD card, and applaunch will just fail to start it without any issues following.Warning: Do NOT do this if you got a Exx v2.0 P/N:645xx (with MSX), and dont hold me responsible if you mess things up pleaseInstallation:* Connect via RNDIS and FTP to camera, make a backup of your own applaunch file in FlashFS/system/ and replace the applaunch file attached (Or just add the following command at the end of your own applaunch file: "cmd /C \StorageCard\boot_inject.cmd"* Place the "boot_inject.cmd" file in the root of your SD card.* Done!Now simply cold-boot the imager by either removing the battery or holding the power button for ~15 sec, and then start it again.You will notice that the keypad start flashing after ~30-40 seconds, this is to show a confirmation that the batch file has loaded and is running as it should.Future update?Are there any other rset commands you folks usually use on your imager that you wish could be launched every single time you coldboot your Exx?I'm willing to try more things, but the logo and jpg quality is so far the ones I've managed to find most useful.

author: Spirit532
author_rank: Frequent Contributor
timestamp: February 23, 2018, 07:23:56 pm
content: Quote from: Paw85 on February 23, 2018, 07:08:24 pmA biiiiiiit late on that oneI'm working on a full hack menu that will support the Ex/Exx/Txxx series cameras, which includes both of your features already.Take a look here:https://www.eevblog.com/forum/thermal-imaging/flir-t440bx-hacking-firmware-investigation-possible-ultramax-support-for-exx/25/I'm looking for people to test it on the Exx, so PM me your Skype username if you want to join.

author: Fraser
author_rank: Super Contributor
timestamp: February 23, 2018, 07:44:47 pm
content: Paw85,Many thanks for developing this option for the Exx series. It is much appreciated. These are likely the only additional upgrades I would want on my camera so it is a good fit for my use. I will test it as soon as I return from a short trip away.On the multi parallel thread development front for these cameras, I actually like the fact that people develop their own modifications as this generates both user choice and potentially different upgrades and techniques.Paw85 is coming up with some excellent projects for Exx owners. I, for one, thank him for this effort, as I do anyone who offers their time to develop code and processes for the rest of us. Keep it upFraser

author: Paw85
author_rank: Regular Contributor
timestamp: February 23, 2018, 07:49:53 pm
content: Quote from: Spirit532 on February 23, 2018, 07:23:56 pmYes, I have seen pictures of the menu but believe there are difference.This solution is available right now and is fully transparent to the user on how it works as the code is easily viewed with a simple text editor and can be edited if the user wishes to add more rset commands upon boot.I'm probably damaged from a previous bad experience running a "hack" application on a device that bricked it, a bit early for me to try your solution, but once the source code is released and can be reviewed and software proven to work I may give it a go.I do appreciate your efforts on developing the hack menu though, as it works on several devices, not just the early Exx models that my little code work onQuote from: Fraser on February 23, 2018, 07:44:47 pmLet me know how it goes! Since we have almost identical devices it hopefully should not be any issues as boot sequence running the same firmware should be identical.

author: Spirit532
author_rank: Frequent Contributor
timestamp: February 23, 2018, 08:14:15 pm
content: I'm not planning on releasing the source code(at least publicly), mostly to prevent it being stolen and/or sold(see eBay for dozens $100+ upgrade listings and E4s sold as E8s).As for safety, it should be completely safe because I'm limiting the hack to only use native WinCE 5.0 features(the cameras run 6.0) and to only do runtime changes - nothing is permanently changed in flash, so if something goes wrong it's just a matter of rebooting the camera.The camera features are set the same way as the batch file, via rset, as there is no easy other way to do it(would involve reverse-engineering and uncertainty across FW versions).Right now it's been tested to work on an early(2012) T440bx and the latest liberated(Wi-Fi) E4.I won't be releasing it publicly until it's tested to work with the Exx series, as the T440bx->E4 port required some modification.The invitation was to test under supervision to ensure compatibility, but fair enough.

author: Paw85
author_rank: Regular Contributor
timestamp: February 23, 2018, 10:15:36 pm
content: Fraser;I used your config files for the Exx, but never managed to get the graph with line measurement to work properly, the lower part of the screen turned dark, numbers changed to the left, but there was no graph drawn.Are you experiencing the same?I did find a solution that got it working on mine at least unit, in appcore config, change setting .caps.config.image.sysimg.measureFuncs.mline.maxCount int32 to value 1 instead of 5.Doing this got the graph displayed, and all other functionality appear intact as well.Do you know the reason this was set to 5 in the config, and is it working in your unit set to 5?(All other measurement settings are working well with your config, even the other ones that are set to 5 like circle, spot and box)EDIT:Have now found out that if adding as many lines as the maxCount, I can now get graphs of the lines, but they all display the same graph, and it's all the last in count (so basically graphs are set to display the values from line 5, if not having 5 lines, it will display nothing, no matter to which line they belong.At least on my unit, appears best to just set it to 1 to get graph functionality, not sure when Ill have use of more than 1 line measurement

author: Fraser
author_rank: Super Contributor
timestamp: February 23, 2018, 11:59:43 pm
content: Paw85,Yes I had the same issue but did not investigate it further and got distracted. Thank you for looking into this. I think the 5 was the default value in the configuration and I did not change it. I just assumed that this function, like some others, did not work on the Exx hardware. I will change mine to 1 as well.Another mode that I tried but later disabled, was panorama. This just puts up guide lines to assist the user when panning the camera in order to maintain the 'horizon' position. I enabled it but no lines appeared so I suspect a change is needed in another system file for the overlay function. No great loss though. There was a function called 'fast... something that no one seems to know much about. It also failed to do anything when enabled.Many thanks for your work on the Exx. It is one of my favourite thermal cameras. I still need to design some lens mounting adapters to adapt my Fluke Tele2 X2 afocal lens bayonet mount to the Exx bayonet socket. That is still a priority once other important jobs are completed on other projects.Fraser

author: tomas123
author_rank: Frequent Contributor
timestamp: February 24, 2018, 11:14:46 pm
content: @Paw85thanks for sharing your concept of a boot_inject.cmd with the startup valuesCode:rset .image.services.store.quality 100rset .ui.userSettings.overlayLogo false

author: hikanio
author_rank: Contributor
timestamp: February 28, 2018, 02:01:27 pm
content: As an E30 user, I'd really like to see the this new idea of extended menu functions to provide the ability to record thermal videos (not just mp4) on the Exx series.It was already proven possible in general by using command line by tomas123 (as far as I remember) , so it shouldn't be too difficult to implement.That'd be a motivator to get me trying this hack. :-)CheersHikanio

author: Spirit532
author_rank: Frequent Contributor
timestamp: February 28, 2018, 03:09:20 pm
content: Quote from: hikanio on February 28, 2018, 02:01:27 pmFrom my tests I've determined that it's either impossible or extremely close to impossible.A 320x240x30fps video ends up being 18.4MB/s of data, which the hardware inside the camera can't do on the software end(WinCE).tomas123's approach records to RAM until it's either full(and crashes the camera in some cases), or for only about a second(the Ex, Exx, and T4xx cameras seem to have around 25-30MB of RAM free), and then dumps it out onto the SD card or internal flash.I haven't looked into lossless compression yet, but I suspect that's also impossible due to the tiny amounts of computational power available.

author: Zucca
author_rank: Unknown
timestamp: March 12, 2018, 01:41:32 pm
content: Quote from: reallybigone916 on July 22, 2016, 04:04:05 amI can NOT 100% confiirm this:https://www.eevblog.com/forum/testgear/flir-e30-config-and-specs/msg1450104/#msg1450104A unit with PN 49001-1801 has the wifi board, SN is 490217xx. So maybe the theory SN 490xxxxx has the WIFI is correct.

author: Zucca
author_rank: Unknown
timestamp: March 29, 2018, 04:05:27 am
content: So I started to play on my new used E30 condom special version... you will understand why.Here the Details:SN 490214xxPN 49001-1801FW 1.36.23Model E30_B 1.1already upgraded to FW 2.23.14.Hope to get WIFI, I did a picture before doing the hack...it looks to me already 320x240...

author: Fraser
author_rank: Super Contributor
timestamp: March 29, 2018, 10:32:42 am
content: Zucca,Prepare to be very impressed once you have done the hackYour camera automatically interpolates the 160 x 120 pixel image to 320 x 240 to fit the LCD Screen.Your sample image needs to be viewed in FLIR Tools where the true Thermal Resolution is detailed in the image information. Your sample image is 160 x 120 thermal resolution.Your sample image is actually quite poor for what an Exx series camera can produceYes I did say poor ! Once you upgrade the camera you will have four times the number of thermal image pixels plus the awful false noise injection will be removed. FLIR inject varying levels of false noise depending upon the model. The E30 has the highest level of false noise injection to deliberately degrade its image. IIRC it is set at 60mK or 70mK of injected noise !After the upgrade you will see a very nice, detailed and low noise imageDo the full E60 hack and prepare to be impressed with the resultFraser

author: Pinkus
author_rank: Frequent Contributor
timestamp: March 29, 2018, 12:04:24 pm
content: Quote from: Fraser on March 29, 2018, 10:32:42 amA huge difference indeed. See attached pic for the difference (I guess also a firmware update was made according to the changed display layout - but I cannot remember).Edit: before you ask: the two pictures are showing two different windows

author: Zucca
author_rank: Unknown
timestamp: March 29, 2018, 01:48:07 pm
content: Quote from: Fraser on March 29, 2018, 10:32:42 amHi brothers Fraser and Pinkus, ah ah it makes sense now. Somehow I remember my E8+ to be sooo much better, but I was not sure...Thanks, stay tuned I will need your support again I am sure.

author: Fraser
author_rank: Super Contributor
timestamp: March 29, 2018, 04:21:10 pm
content: Congratulations on the upgrade. The amount of artificial noise injected into the E30 image is staggering ! That is the FLIR Marketing team at work, making sure the lower spec/cost cameras in the series provide far inferior imaging to the more expensive models. The Service Menu gives you access to a noise self test feature where the camera calculates the system noise level. That can be interesting to run as you get the noise readout of your microbolometerFor the Exx series it's nice and lowThe larger manual focus lens also improves the real world noise figure of the system when compared to the Ex series that is somewhat limited by its inferior fixed focus lens.Fraser

author: Fraser
author_rank: Super Contributor
timestamp: March 29, 2018, 04:24:04 pm
content: I think your E30 will only have the lower temperature range enabled. If so you can enable range 4 that extends up to 650C. You activate Range 2 via the service menu as I think is detailed recently in this thread. If not, I will find the details for you.Fraser

author: Zucca
author_rank: Unknown
timestamp: March 29, 2018, 05:26:31 pm
content: Quote from: Fraser on March 29, 2018, 04:24:04 pmNo I have two ranges out of the box, which means they are also calibrated.... YES! this is really the ultimate E8+ upgrade, finger crossed for WIFI.That's also why I was suspecting I had an already hacked unit.I contacted the previous owner and he doesn't know what I am talking about.It's funny how many people sell those wonderful toys without knowing the Exx cameras true secret power.Good for us!

author: Fraser
author_rank: Super Contributor
timestamp: March 29, 2018, 05:46:27 pm
content: My mistake, it does have two ranges but, according to FLIR, Range 2 is limited to 350C rather than 650C. It would be worth your time to look into enabling the full range capability via the Service menu.http://www.flir.co.uk/cs/display/?id=41959https://www.ivytools.com/v/vspfiles/assets/images/flir-e30-data-49001-1801.pdfFraser

author: Zucca
author_rank: Unknown
timestamp: March 29, 2018, 05:58:44 pm
content: Ah ah, it's not your mistake.PN 49001-1601 E30 has one range: -20°C to +250°C (see data sheet attached)PN 49001-1801 E30 has two ranges: –20°C to +120°C and 0°C to +350°C

author: Fraser
author_rank: Super Contributor
timestamp: March 29, 2018, 06:01:20 pm
content: Take a look at this thread for all the info on the range changes via the Service Menuhttps://www.eevblog.com/forum/thermal-imaging/just-got-an-e30bx-have-the-usual-questions/I was wrong about the E30 noise injection..... it is set to 90mK in the E30 !Fraser

author: Zucca
author_rank: Unknown
timestamp: March 29, 2018, 06:14:59 pm
content: Quote from: Fraser on March 29, 2018, 06:01:20 pmPrintig money SW machine...The PN 49001-1801 E30bx has just the first range enabled.Those FLIR marketing guys deserved this Hack!On the side I found the technical drawings, useful if we have to make some 3D print things...https://www.tme.eu/pl/Document/4c91ec07e961c92226a3919fcc80768a/1196960_en_51.pdf

author: Fraser
author_rank: Super Contributor
timestamp: March 29, 2018, 10:35:01 pm
content: I wish I could get my hands on technical drawings of the lens bayonet part that mates with the camera. I will be using my trusty digital calliper to design an adapter to fit that type of bayonet mount. I have a project on hold at the moment to adapt a Fluke Tele2 lens to the Exx camera mount. I will either 3D print the adapter, or cut it out of Aluminium on my lathe. Maybe bothFraser

author: Vipitis
author_rank: Frequent Contributor
timestamp: March 29, 2018, 11:04:13 pm
content: I have printed and designed then printed, lens adapters. They work, but need a little bit of help with sanding some parts.But I wouldn't use them as a solution, unless you glue them in, I am too worried to just have my lens drop out.It's great for prototyping.

author: Zucca
author_rank: Unknown
timestamp: March 30, 2018, 05:25:10 am
content: Going into the jungle of hacking... already made a backup of everything I could read out.This is my hack reference:https://www.eevblog.com/forum/thermal-imaging/flir-e4-thermal-imaging-camera-teardown/msg561266/#msg561266Now... I would like to use those Fraser config:https://www.eevblog.com/forum/thermal-imaging/flir-e40-upgrade-configuration/msg1299159/#msg1299159because he is the best on the marketHere where I'm not sure:1) Difference between my APPconf.txt and Fraser's one, see attachments.I don't care if the values are different, but a few parameters/lines are missing.2) Here my \FlashFS\system\kits.d\confkit.revQuoteshould I modify the line VERSION like thisQuote?Same story with GUIconf.txt see attachment.I have a bad feeling about it.Thanks gentleman.

author: Zucca
author_rank: Unknown
timestamp: March 30, 2018, 05:44:38 am
content: https://www.eevblog.com/forum/testgear/flir-e30-config-and-specs/msg946297/#msg946297EDIT:It looks likeI have WIFI... see below...finger double crossed.

author: Fraser
author_rank: Super Contributor
timestamp: March 30, 2018, 11:42:57 am
content: Hiya,Do not modify anything in that 'kit' file. There is no need. Note that the files that are altered in the update are stated as being "undefined" which is goodThere is no requirement to change the references to E30, they have no effect on on the configuration or operation of the camera. They are just detailing the file identity. The file identity in the updated files is changed and this is seen when looking at the camera information. It becomes an E60 in the camera type details.The ".cfg" configuration files are all that need to be changed for the upgrades and there are many options that are available. I enabled those that worked fir me. Note that the graphing mode in my configuration did not work correctly. It turns out that the associated configuration line needs to be set to a value of 5.IIRC you will be adding a configuration file that provides the Wi-Fi configuration and enablement. I forget whether that folder even existed on the E30. I think I had to add it from the E60 image that I was using. It should all be detailed in the E30 upgrade instructions.IIRC, the camera will be identified by FLIR Tools as its original model, in your case, an E30. This effects nothing as it is just read out of the eeprom and is not used by FLIR Tools to set any paremeters. IIRC, the camera ID can be changed in the Service Menu. I personally did not bother as I am not trying to pass the camera off as an E60 in my usage. Some users may want the camera ID to read "E60" in the file metadata.Playing with the .cfg fires is both easy and relatively safe to do. Just make sure to double check the CRC01 calculation each time and keep the. Andra in RNDIS mode until,all playing is completed. That way you can always load the previous working .cfg file if required. It is possible to play with the various .rsc files as well but I have not needed to do that to date. You need CRC32 for their checksum calculation.This is all from memory so take it as my best recollection rather than hard facts.Fraser

author: Fraser
author_rank: Super Contributor
timestamp: March 30, 2018, 12:37:48 pm
content: Just thinking about the "E30" ID. I seem to recall the entry in the kit list DOES set what is seen in the cameras information page. As stated, this is just cosmetic and makes no difference to the cameras operation.You can set your various configuration files to read E60 if you like, just be sure to recalculate the CRC01 if you change a file that has such listed at the bottom.The additional Wi-Fi support configuration is held in the Services.d folder as detailed in the E30 upgrade instructions you referenced. Just use the E60 file and all should be fine.There is much that can be experimented with in this easily edited firmwareI enabled everything that worked in my configuration files and there is plenty of added functionality to enjoy.As a word of warning, including the later Exx (MK2) series MSX entries in the configuration file caused my camera to misbehave. It saved only blank images. Removal of the MSX related lines returned the camera to normal operation.Fraser

author: Fraser
author_rank: Super Contributor
timestamp: March 30, 2018, 12:47:44 pm
content: Zucca,I am happy to send you my cameras complete back-up file set if it is of any interest/help.Let me know if you need it. It is, of course, basically just an E60 build plus a few additional configuration options enabled.Fraser

author: Zucca
author_rank: Unknown
timestamp: April 04, 2018, 05:45:43 am
content: Hack timeRegarding this file:QuoteI was missing these lines:Quotefrom Fraser conf.cfgI modified only the last one, bringing the numer to 3200Quotebecause my default conf.cfg wasQuoteso with the caps.config.image.settings.resIR upgrade to 320, I did the same proportional thing to .caps.config.image.settings.resVIS .I also left this to default:Quoteand did not change to Fraser one:Quotebecause maybe those missing lines are somehow interpreted in the v1.1 config, it should be just a text so just cosmetic I hope.for this puppy:QuoteI used theFraserone as reference but I didn't touched the caps.config.revision text and left the value "1.1" theresame story withQuoteFinally I did change theQuotewith the following:Quotebecause I paid for a E60 not a smelly E30B.Quote from: Fraser on March 30, 2018, 12:37:48 pmYes, I can confirm this.Here the result...before:after with range 0 to 350 Cafter with range -20 to 120 CMuch less noise in this range, expected? I think yes.Please also notice I upgraded the digital camera...beforeafternow it's bed time... will continue to play tomorrow.No I can't go sleep I need to check the radio board...WIFI is there!So in 2 units E30 PN 49001-1801 with serial number 4902XXXX, we have the radio board there. I can also confirm theslbwverinfo in the service menu theory about WIFI.ah... I will never sleep tonight... regarding the second T range, it's interesting... here what i got:beforeafterfunny I can select now the range 200 to 1200 CI am pretty sure it is not calibrated butWe just need to service it and calibrate it...Here the calibration protocol on the service menu:QuoteI went back to 2 ranges and disabled the 200 to 1200 C, because the camera in this range was not working properly. it was just showing >80C all the time but the infrared image was there

author: Fraser
author_rank: Super Contributor
timestamp: April 04, 2018, 11:51:01 am
content: My comments......Great work !1. Yes the changes you made in the Vis settings removes the resolution restriction from the visible light camera. Its is now the full 3.2MP2. The higher the temperature range, the lower the thermal sensitivity. This is normal and shown in the E60 specifications when it switches between Range 1 and Range 2. Perfectly normal and not a problem. The reason is that the bias voltages on the microbolometer are changed to allow the sensor array to cope with higher temperatures. The most highest sensitive of the sensor array is at lower temperatures where the bias voltages are carefully set to provide best performance. As the temperature capability rises, the bias voltages are moved away from that optimum performance setting. Just a fact of life with Microbolometers.3. I was not aware that your camera range options were limited to a maximum capability of 350C. I thought there would be a 650C available but having never looked in that menu for an E30 I was not sure.4. Range 3 is the optional (chargeable) high temperature range. In your camera is was not calibrated, hence its failure to provide sensible temperature measurements. I suspect this range is only calibrated if you buy the high temperature option you have the physical high temperature filter and the camera is calibrated to take account of its characteristics. There is certainly. High temperature filter listed on the accessories list.5. Very pleased to see your camera contains the wireless module. The E30bx I upgraded had no module details listed in the hardware list. When I enabled the Wi-Fi, the menu for it appeared and I could activate it, but there was no SSID emitted and it could not see my router SSID. No module present on that unit. Bluetooth could not be activated, it just flipped back to 'off' whenever I switched it on. The BT module is an integral part of the Wi-Fi module.Fraser

author: Fraser
author_rank: Super Contributor
timestamp: April 04, 2018, 12:10:02 pm
content: With regard to adding any extra lines to the configuration files. Only the MSX lines are likely to cause issues as the camera tries to obey them without having the required hardware performance to cope with such.Adding missing lines from an E60 is otherwise very safe to do. I tried enabling all of the lines in the configuration file that would provide additional functionality. Some worked, some added nothing as there are other changes are needed to enable a function. The camera at no time crashed as a result of my changes. You are just activating functions already in the firmware.... if they have the required support files, they work. If the support files or other settings are missing, they do not work, simpleif you stick with the contents of a Mk1 E60 configuration file contents, you are very safeNote that some options in the configuration file actually restrict the cameras functionality so do not activate PiP lock or anything that appears to be restriction. Some of the config lines that are either already a active (True) or that you make active have a line below them with the ending 'Int' these set the valuecassociated with the function above. In the case of measurement functions, this setting can set the number of spot temperatures or measurement boxes you can have on the screen. Take a look at my configuration file and compare your "Int" values. I have multiple spot and box measurements. I also enabled circle measurement areas and special functions like the Sketch capability that lets you use the touch screen to draw on a saved image to highlight a point of interest when doing a survey. I enabled image editing and any other useful features I found. Take a close look at my configuration file. You can actually use my complete configuration file in your camera provided you edit the serial number and calculate the CRC01 for your serial number and configuration file.Once you get used to editing the configuration files, you can have great fun with them at low risk to to the camera. Just keep the camera set to RNDIS mode whilst playing as any issues are easily corrected in that mode using FileZilla and your file back-ups.Have fun.Fraser

author: Zucca
author_rank: Unknown
timestamp: April 04, 2018, 03:16:26 pm
content: Quote from: Fraser on April 04, 2018, 11:51:01 amMany many thanks! This is a game changer information for me. I always understood the bigger the range the better it is but I was not considering the noise factor.If I understood it correctly the 0-350 have less noise than the 0-650. If this is the case then I prefer the 0-350 as I don't need every day the >350 range, but I need less noise as possible! It's a trade off.Regarding the calibration parameters I found this:http://u88.n24.queensu.ca/exiftool/forum/index.php?topic=4898.60which is cool!Don't want to go up to 1200 C, I am scared to melt the camera... the 1200 range is for the Flir TXX Cameras.Anyway the service menu is bombastic! You can add lens, modify calibrations add ranges.... do want you want! Now I understood why the FW is the key!I will play with video and with all your settingsFraserstay tuned!

author: Fraser
author_rank: Super Contributor
timestamp: April 04, 2018, 04:36:26 pm
content: Hi Zucca,There are normally three microbolometer bias voltage sets used to cover low, medium and high temperature ranges on thermal cameras capable of such.I forget the switch points but Range 1 usually tops out at around 120C and Range 2 usually covers up to around 650C, as found on the E60. Range 3 usually extends coverage up to around 1000C. Range 3 has pretty low sensitivity figures due to the less than optimal bias voltages on the pixels.In your case I do not know whether FLIR set the range 2 bias voltages for a 650C maximum temperature, and calibrated to 350C, or whether they tuned the Range 2 Bias voltages to be optimum for a 350C maximum. A check of the difference between Range 1 and Range 2 sensitivity on the E60 and E30 may suggest what FLIR has done. The increased noise injection on the E30 spec hopefully does not muddy the waters too much. We are looking at Delta Sensitivity here. I will take a look.Fraser

author: Fraser
author_rank: Super Contributor
timestamp: April 04, 2018, 04:44:09 pm
content: Hmmmm FLIR choose to not detail the difference in sensitivity on the different ranges. That is unhelpful. Agilent provide that data on their camera specs.Fraser

author: Zucca
author_rank: Unknown
timestamp: April 04, 2018, 05:04:22 pm
content: Quote from: Fraser on April 04, 2018, 04:36:26 pmSo if the bias voltage is the same, also the noise is the same? In this case if the same bias is used in the 0-350 and 0-650 then the noise is the same in the two ranges... oh well... I really don't need the 650 range...

author: Fraser
author_rank: Super Contributor
timestamp: April 04, 2018, 06:19:36 pm
content: YesFraser

author: joe-c
author_rank: Frequent Contributor
timestamp: April 04, 2018, 07:01:23 pm
content: Hey Guys,i am not finish with my observations about the Config stuff, but i have some info's...i never used the Webpanel to activate Calibration cases, i use thecalib.rscdirectly.Therefore my E40bx has all 3 Cases, one of them need a Filter, see here:https://www.infraredcamerawarehouse.com/flir-high-temperature-option-1200-c-2192-f-t197000/Additional you can adjust the Digital Filter settings, for the old Exx you need to adjust the Noise generator setting there... i also make some changes about the Spartial Filter and the Temporal filter... the Temporal filter will incase the Quality but make the framerate a bit lower.Maybe you just have to look what you prefer (try with EX-Tools on the "Setup" Tabs).See here a Comparison between Ex, Exx and Bxx, all enhanced to 320x240, the Exx has default filter setting, the Bxx has adjusted Setting, see resultsbest wishesAdditional: you can just add some *.pal files in default folder. They are added to menu after restart and you have to add the name you want in:FlashFS\system\ui.d\tml\languages\strings.en.xml

author: Fraser
author_rank: Super Contributor
timestamp: April 04, 2018, 08:18:43 pm
content: Joe-C,Thanks, as always, for the helpful inputDo you have the values you settled upon for the filters ? I may have a play with those as your 'tweaked' pictures are very niceIt would be useful to know what you settled on in terms of filtering as a comparison with any experimentation I do with such.I saw the high temperature upgrade advertised but could not see a physical filter shown. I also note in your referenced page that the shipping weight is zero. It is possible to bias a microbolometer to work up to 1200C so I have to wonder whether this is actually a payment for FLIR to enable and calibrate that range.On the PAL file front ..... thanks for the tip. I intend to add some PAL files at some point and wondered about how I get them recognised by the system. Now I knowFraser

author: Zucca
author_rank: Unknown
timestamp: April 04, 2018, 08:47:09 pm
content: Thanksjoe-cfor the input,Using the web service menu I was able to get this too:The problem is the calibration. If that range was not calibrated at factory I see no use in activating the uncalibrated range.I don't have the 650 range, but just the 350 calibrated. FYI Some user reported the 650 range calibrated in the E3x device but not activated, it´s another story.A DIY calibration is out of dicussion for me. TrustedFraserreported here in this therad some pics from FLIR calibrations labs...so, I am not going in that direction.when you select the 1200 range do you get readings which make sense? in other words, is the 200-1200 range on your device calibrated?Anyway I don´t need the 0-650, my E8+ had 250 max, now I have 350 totally happy with that.My todo list:https://www.eevblog.com/forum/thermal-imaging/flir-e40-upgrade-configuration/msg564687/#msg564687https://www.eevblog.com/forum/thermal-imaging/flir-e40-upgrade-configuration/25/and thisSpirit532Menu hack (.jpg quality 100%, removeflir logo):https://www.eevblog.com/forum/thermal-imaging/flir-t440bx-hacking-firmware-investigation-possible-ultramax-support-for-exx/msg1421638/#msg1421638also your SW and the tomas123`s onetripod mount...https://www.eevblog.com/forum/thermal-imaging/fraser-has-bought-his-new-favourite-daily-use-camera-the-flir-exx-love-it/msg1450338/#msg1450338lens ... and so on...

author: joe-c
author_rank: Frequent Contributor
timestamp: April 04, 2018, 09:15:26 pm
content: Quote from: Fraser on April 04, 2018, 08:18:43 pmShure, here my last settings:.calib.nrdp.ds120C_we_ap_fi_le.alt.0.noiseGen.level int32 0.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial.bilateral.sigma double 30.calib.nrdp.ds120C_we_ap_fi_le.alt.0.temporal.level int32 16.calib.nrdp.ds120C_we_ap_fi_le.alt.0.temporal.threshold int32 16my regardings... rise the Sigma value will reduce the noise on uniform surfaces, but loose details.rise the Temporal level will lower the noise, but add some "ghost Effect".all other was just shortly tried and leaved as is.for the other ranges use:.calib.nrdp.ds650C_we_ap_fi_le.alt.0.noiseGen.level int32 0the full set is:Code:.calib.nrdp.ds120C_we_ap_fi_le.alt.0.noiseGen.enabled bool true.calib.nrdp.ds120C_we_ap_fi_le.alt.0.noiseGen.level int32 0.calib.nrdp.ds120C_we_ap_fi_le.alt.0.qualityRanking int32 1.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial entry.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial.bilateral entry.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial.bilateral.enabled bool true.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial.bilateral.sigma double 30.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial.column entry.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial.column.enabled bool true.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial.column.threshold int32 50.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial.column.thresholdPix int32 80.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial.edge entry.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial.edge.enabled bool false.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial.edge.gain double 0.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial.offsetPixel entry.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial.offsetPixel.altThreshold int32 0.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial.offsetPixel.altThresholdArea int32 0.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial.offsetPixel.altThresholdDiff int32 0.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial.offsetPixel.apr bool false.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial.offsetPixel.enabled bool false.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial.offsetPixel.threshold int32 0.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial.offsetPixel.thresholdArea int32 0.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial.offsetPixel.thresholdDiff int32 0.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial.offsetPixel.thresholdPix int32 0.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial.row entry.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial.row.enabled bool false.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial.row.threshold int32 0.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial.row.thresholdPix int32 0.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spr entry.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spr.enabled bool false.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spr.threshold int32 0.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spr.thresholdTemp int32 0.calib.nrdp.ds120C_we_ap_fi_le.alt.0.temporal entry.calib.nrdp.ds120C_we_ap_fi_le.alt.0.temporal.enabled bool true.calib.nrdp.ds120C_we_ap_fi_le.alt.0.temporal.level int32 16.calib.nrdp.ds120C_we_ap_fi_le.alt.0.temporal.threshold int32 16.calib.nrdp.ds120C_we_ap_fi_le.alt.0.temporalRow entry.calib.nrdp.ds120C_we_ap_fi_le.alt.0.temporalRow.enabled bool false.calib.nrdp.ds120C_we_ap_fi_le.alt.0.temporalRow.level int32 14.calib.nrdp.ds120C_we_ap_fi_le.alt.0.temporalRow.limit int32 10250.calib.nrdp.ds120C_we_ap_fi_le.alt.0.temporalRow.threshold int32 20.calib.nrdp.ds120C_we_ap_fi_le.alt.0.type int32 100.calib.nrdp.ds120C_we_ap_fi_le.calcNoise entry.calib.nrdp.ds120C_we_ap_fi_le.calcNoise.factor double 286.calib.nrdp.ds120C_we_ap_fi_le.calcNoise.temporalMkDefault double 20.calib.nrdp.ds120C_we_ap_fi_le.measureInfo entry.calib.nrdp.ds120C_we_ap_fi_le.measureInfo.spatialDu double 4.2782106.calib.nrdp.ds120C_we_ap_fi_le.measureInfo.spatialMk double 20.633417.calib.nrdp.ds120C_we_ap_fi_le.measureInfo.temporalDu double 4.6188022.calib.nrdp.ds120C_we_ap_fi_le.measureInfo.temporalMk double 22.276059

author: tomas123
author_rank: Frequent Contributor
timestamp: April 04, 2018, 09:59:22 pm
content: I'm looking for the old firmware 2.23.14 (Exx without MSX) .The old link goes to current FW 2.27.16.http://support.flir.com/SwDownload/app/RssSWDownload.aspx?ID=127Can anybody upload the fileflir_exx_pn490_v2.23.14_update_pack.zipfrom FLIR Exx P/N:490xx (2.23.14) Update Pack ?Thanks for help.

author: Pinkus
author_rank: Frequent Contributor
timestamp: April 04, 2018, 10:01:16 pm
content: Send me your email address as a PM and I will send it to you.

author: Zucca
author_rank: Unknown
timestamp: April 05, 2018, 03:19:37 am
content: Quote from: tomas123 on April 04, 2018, 09:59:22 pmhttps://www.eevblog.com/forum/thermal-imaging/just-got-an-e30bx-have-the-usual-questions/msg1400320/#msg1400320

author: Zucca
author_rank: Unknown
timestamp: April 05, 2018, 03:41:03 am
content: Quote from: Fraser on April 04, 2018, 12:10:02 pmI have all the above functions,but i can not get the MIN values in lines,box or circles etc.. Only the MAX values are showing up. Moreover i spent 30minute to add the graph under the line like the one below but no luck. Something wrong with my config? Sorry I can't send a screenshot because this orrible ipad don't have the sd card reader....

author: Zucca
author_rank: Unknown
timestamp: April 05, 2018, 04:02:26 pm
content: https://www.eevblog.com/forum/thermal-imaging/flir-e40-upgrade-configuration/msg1434799/#msg1434799forgot to change the .caps.config.image.sysimg.measureFuncs.mline.maxCount int32 to value 1 instead of 5...still don´t know why I got only MAX Value and no graph at all under the line, box or circle. needs investigation... maybe the .caps.config.revision text "1.1" need to be .caps.config.revision text "0.1"

author: Paw85
author_rank: Regular Contributor
timestamp: April 05, 2018, 06:25:03 pm
content: Quote from: zucca on April 05, 2018, 04:02:26 pmGood you found my previous post to set that value correctly.Regarding only MAX and no graph, are you aware of the menu  -> [Adjust tools] and scroll to the tool you have on your screen and press OK, there you should be able to toggle things like Graph, Max, Min, Avrage, Markers, Alarm.Let me know if you cant find the menu

author: tomas123
author_rank: Frequent Contributor
timestamp: April 05, 2018, 09:37:52 pm
content: Quote from: zucca on April 05, 2018, 03:19:37 amThe link works fine.Thank you

author: Zucca
author_rank: Unknown
timestamp: April 06, 2018, 03:28:50 am
content: My pleasuretomas123, now I need to learn all your SW... you did so much.Paw85cheers!Sorry I did not RTFM.

author: Zucca
author_rank: Unknown
timestamp: April 06, 2018, 10:09:26 pm
content: Can't believe I have this...https://archive.org/embed/FlirE60BxIrInfraredThermalImagingCamera/FlirE60BxIrInfraredThermalImagingCamera.mp4Do you know if it is possible to videostream the IR image on the E60+ screen over WIFI? Should I just use the app?

author: tomas123
author_rank: Frequent Contributor
timestamp: April 06, 2018, 11:53:06 pm
content: We have not yet reversed engineered the WiFi stream.All known hacks for streaming are for a USB connection.

author: Spirit532
author_rank: Frequent Contributor
timestamp: April 07, 2018, 09:43:20 am
content: The WiFi stream seems to be RTSP or RTP, depending on your settings, and it seems to be visual-only, but without the overlay.I may be wrong about this.

author: tomas123
author_rank: Frequent Contributor
timestamp: April 07, 2018, 03:04:26 pm
content: yes, but this is a regular video and not a 16 bit thermal streamfrom my old notes (year 2013):Quicktime playeropen addressrtsp://192.168.64.1ca. 350Kb/sec Frame rate: 19.2480 × 360from manual:rset.qualityEncoding quantization level. Range 1-31. Default value = 7. A low value means higher quality picture. Encoding quality is also dependent on the maximum bit rate allowed.you can change the quality during a running stream:>rset rtp.quality 1-> ca. 500 KB/sec (quality is visible better) Frame rate: 8.0

author: kaz911
author_rank: Super Contributor
timestamp: April 24, 2018, 08:43:57 am
content: got my self a E50bx Mk 1 late 2012 with the 45deg/10mm lens at a reasonable price.Now liberated - to thanks to all! Did update via FTP w/ Fraser's App/Gui codes - so thanks to Mike, Thomas, Gustavo? & Fraser for all their work! and everybody else here.The E50bx 10mm lens is calibrated from factory and have both -20-120 & 0-650 rangeBut the built in lens is only calibrated to -20-120 - so I guess i have to play with files to enable the 0-650 range.But quality of the -20-120 range is super! And I tried it against my old E4 libaratio - and there is so much more detail in the E50bx files. But I do miss the MSX...

author: Zucca
author_rank: Unknown
timestamp: April 24, 2018, 12:57:57 pm
content: Welcome to the club, the EXX is a natural evolution of E4... very impressive indeed.It looks like the EXXbx model can be open to the 0-650 range but there are no much information regarding the calibration of that second range.I got a E30 which is only 0-350 with no further calibration.

author: Fraser
author_rank: Super Contributor
timestamp: April 24, 2018, 01:46:39 pm
content: Kaz911,The second temperature range is enabled via the cameras Service Menu and not in the configuration files. You only need to enter the service menu via a web browser, enter the 3vlig and 1235 passwords and you can add range 2. Hopefully your camera has the required calibration tables present.Fraser

author: kaz911
author_rank: Super Contributor
timestamp: April 24, 2018, 02:48:23 pm
content: Quote from: Fraser on April 24, 2018, 01:46:39 pmI was trying to conveythat I have calibration for the 0-650 ONLY when I add the 10mm lens. There I have calibration for -20 to 120 and 0 to 650The 0-650 calibration is not there for the normal ?18mm lens (the standard lens) - so standard lens only have the calibration for -20 to 120.so currently I can only do 0-650 when I put the 10mm lens on.I have looked in the "service menu" which confirms the above - 3 ranges calibrated - 2 for the 10mm and 1 for the built in lens./k

author: Zucca
author_rank: Unknown
timestamp: April 24, 2018, 03:00:46 pm
content: Interesting

author: Fraser
author_rank: Super Contributor
timestamp: April 24, 2018, 04:37:56 pm
content: Kaz911,Ah, apologies, I did not realise that you had already looked at the service menu.Your situation is unusual. It is not uncommon for early MK1 'bx' suffix cameras to only have range 1 calibration tables, but I had not heard of FLIR providing Range 2 calibration for a supplementary lens on such a camera. I suspect their automated calibration rig just generates the calibration files for Range 1 and 2, no matter which camera is attached to the supplementary lens at the time of testing.It is possible to calibrate the camera for any Range using the service menu, but the correct high and low temperature Black Body thermal sources are needed.As a side not on calibration..... Interestingly, whilst working on an early i5 recently, I found the production log for its calibration. It was clear that the camera had undergone an automated calibration routine that obeyed a set of 'on-board' camera 'descriptors' in order to produce only the required resolution and ranges. Thankfully I do not think the Exx series used such a calibration process and just the service menu is needed for calibration.Fraser

author: Jorkah
author_rank: Newbie
timestamp: May 10, 2018, 01:07:19 pm
content: Quote from: tomas123 on April 04, 2018, 09:59:22 pmI have the same problem, the link also links to the newer firmware (2.27.16). Can anybody please re-upload it?Thanks!

author: Zucca
author_rank: Unknown
timestamp: May 10, 2018, 01:15:53 pm
content: Just look above

author: Jorkah
author_rank: Newbie
timestamp: May 10, 2018, 02:02:07 pm
content: I already tried the link (filedropper) posted by Fraser, but it doesn’t work anymore.14-5-2018 Update:I've got my E40bx upgraded with all the functions!I would like to thank tomas123, Frazer and Paw85 for their input, real good work you did, very interesting! Special thanks to Pinkus, who provided me the necessary firmware!Jorkah

author: Zucca
author_rank: Unknown
timestamp: May 15, 2018, 04:55:16 pm
content: I uploaded the FW hereftp://ftp.xdevs.com/Flir/Exx/FW/flir_exx_pn490_v2.23.14_update_pack.zipthanks toTiNftp server, here how to connect:https://doc.xdevs.com/contact/Z

author: Garry2
author_rank: Newbie
timestamp: May 23, 2018, 02:39:03 am
content: I have a e30 and have followed all the steps I can find on the thread, but can not get "thermal fusion" and "picture in picture" to work. The options are shown in the menu, but grayed out and can not be selected. I got this camera pre modified and do not have access to the original files. This is what I have for my conf files. I have redone my crc values. On firmware 2.23.14appcodeCode:.caps entry.caps.config entry.caps.config.name text "app E60".caps.config.revision text "0.10".caps.config.image entry.caps.config.image.framegrab entry.caps.config.image.framegrab.fusion entry.caps.config.image.framegrab.fusion.enabled bool true.caps.config.image.sensor entry.caps.config.image.sensor.enabled bool true.caps.config.image.services entry.caps.config.image.services.store entry.caps.config.image.services.store.enabled bool true.caps.config.image.services.store.radiometric entry.caps.config.image.services.store.radiometric.enabled bool true.caps.config.image.services.store.incompatible entry.caps.config.image.services.store.incompatible.enabled bool false.caps.config.image.services.store.incompatible.level int32 0.caps.config.image.settings entry.caps.config.image.settings.enabled bool true.caps.config.image.settings.downsample bool false.caps.config.image.settings.resIR int32 320.caps.config.image.sysimg entry.caps.config.image.sysimg.alarms entry.caps.config.image.sysimg.alarms.enabled bool true.caps.config.image.sysimg.alarms.measfunc entry.caps.config.image.sysimg.alarms.measfunc.enabled bool true.caps.config.image.sysimg.alarms.measfunc.maxCount int32 2.caps.config.image.sysimg.alarms.humidity entry.caps.config.image.sysimg.alarms.humidity.enabled bool true.caps.config.image.sysimg.alarms.humidity.maxCount int32 2.caps.config.image.sysimg.alarms.insulation entry.caps.config.image.sysimg.alarms.insulation.enabled bool true.caps.config.image.sysimg.alarms.insulation.maxCount int32 2.caps.config.image.sysimg.irMarkers entry.caps.config.image.sysimg.irMarkers.enabled bool true.caps.config.image.sysimg.irMarkers.spot entry.caps.config.image.sysimg.irMarkers.spot.enabled bool true.caps.config.image.sysimg.irMarkers.spot.maxCount int32 2.caps.config.image.sysimg.irMarkers.arrow entry.caps.config.image.sysimg.irMarkers.arrow.enabled bool true.caps.config.image.sysimg.irMarkers.arrow.maxCount int32 2.caps.config.image.sysimg.irMarkers.box entry.caps.config.image.sysimg.irMarkers.box.enabled bool true.caps.config.image.sysimg.irMarkers.box.maxCount int32 2.caps.config.image.sysimg.measureFuncs entry.caps.config.image.sysimg.measureFuncs.enabled bool true.caps.config.image.sysimg.measureFuncs.diff entry.caps.config.image.sysimg.measureFuncs.diff.enabled bool true.caps.config.image.sysimg.measureFuncs.diff.maxCount int32 2.caps.config.image.sysimg.measureFuncs.diff.calcMask int32 65526.caps.config.image.sysimg.measureFuncs.isotherm entry.caps.config.image.sysimg.measureFuncs.isotherm.enabled bool true.caps.config.image.sysimg.measureFuncs.isotherm.calcMask int32 20.caps.config.image.sysimg.measureFuncs.isotherm.dual bool true.caps.config.image.sysimg.measureFuncs.isotherm.fixScale bool false.caps.config.image.sysimg.measureFuncs.isotherm.interval bool true.caps.config.image.sysimg.measureFuncs.isotherm.invInterval bool false.caps.config.image.sysimg.measureFuncs.isotherm.maxCount int32 5.caps.config.image.sysimg.measureFuncs.mbox entry.caps.config.image.sysimg.measureFuncs.mbox.enabled bool true.caps.config.image.sysimg.measureFuncs.mbox.calcMask int32 1924.caps.config.image.sysimg.measureFuncs.mbox.maxCount int32 5.caps.config.image.sysimg.measureFuncs.mcircle entry.caps.config.image.sysimg.measureFuncs.mcircle.enabled bool true.caps.config.image.sysimg.measureFuncs.mcircle.calcMask int32 1924.caps.config.image.sysimg.measureFuncs.mcircle.maxCount int32 5.caps.config.image.sysimg.measureFuncs.mline entry.caps.config.image.sysimg.measureFuncs.mline.enabled bool true.caps.config.image.sysimg.measureFuncs.mline.calcMask int32 1924.caps.config.image.sysimg.measureFuncs.mline.maxCount int32 5.caps.config.image.sysimg.measureFuncs.reftemp entry.caps.config.image.sysimg.measureFuncs.reftemp.enabled bool true.caps.config.image.sysimg.measureFuncs.reftemp.calcMask int32 1924.caps.config.image.sysimg.measureFuncs.reftemp.maxCount int32 1.caps.config.image.sysimg.measureFuncs.script entry.caps.config.image.sysimg.measureFuncs.script.enabled false.caps.config.image.sysimg.measureFuncs.script.maxCount int32 0.caps.config.image.sysimg.measureFuncs.spot entry.caps.config.image.sysimg.measureFuncs.spot.enabled bool true.caps.config.image.sysimg.measureFuncs.spot.calcMask int32 514.caps.config.image.sysimg.measureFuncs.spot.maxCount int32 5.caps.config.image.sysimg.visualMarkers entry.caps.config.image.sysimg.visualMarkers.enabled bool true.caps.config.image.sysimg.visualMarkers.spot entry.caps.config.image.sysimg.visualMarkers.spot.enabled bool true.caps.config.image.sysimg.visualMarkers.spot.maxCount int32 5.caps.config.image.sysimg.visualMarkers.arrow entry.caps.config.image.sysimg.visualMarkers.arrow.enabled bool true.caps.config.image.sysimg.visualMarkers.arrow.maxCount int32 5.caps.config.image.sysimg.visualMarkers.box entry.caps.config.image.sysimg.visualMarkers.box.enabled bool true.caps.config.image.sysimg.visualMarkers.box.maxCount int32 5.caps.config.image.targetNoise entry.caps.config.image.targetNoise.enabled bool false.caps.config.image.targetNoise.targetNoiseMk int32 0.caps.config.image.zoom entry.caps.config.image.zoom.enabled bool true.caps.config.image.zoom.maxFactor double 8.caps.config.system entry.caps.config.system.focus entry.caps.config.system.focus.laser entry.caps.config.system.focus.laser.updateFocus entry.caps.config.system.focus.laser.updateFocus.enabled bool falseuiCode:.caps entry.caps.config entry.caps.config.name text "GUI E60".caps.config.revision text "0.10".caps.config.IIG entry.caps.config.IIG.enabled bool true.caps.config.IIG.DC int32 1.caps.config.IIG.IR int32 1.caps.config.IIG.canvasSketches int32 0.caps.config.IIG.IRImageSketch bool false.caps.config.IIG.DCImageSketch bool false.caps.config.IIG.textAnnotations int32 1.caps.config.IIG.videos int32 1.caps.config.IIG.voiceAnnotations int32 1.caps.config.IIG.objects int32 5.caps.config.image entry.caps.config.image.enabled bool true.caps.config.image.adjust entry.caps.config.image.adjust.enabled bool true.caps.config.image.adjust.auto bool true.caps.config.image.adjust.interval bool true.caps.config.image.adjust.above bool false.caps.config.image.adjust.below bool false.caps.config.fusion entry.caps.config.fusion.enabled bool true.caps.config.fusion.thermal entry.caps.config.fusion.thermal.enabled bool true.caps.config.fusion.thermal.auto bool true.caps.config.fusion.thermal.interval bool true.caps.config.fusion.thermal.above bool true.caps.config.fusion.thermal.below bool true.caps.config.fusion.PIP entry.caps.config.fusion.PIP.enabled bool true.caps.config.fusion.PIP.locked bool false.caps.config.laser entry.caps.config.laser.enabled bool true.caps.config.laser.positionMarker bool true.caps.config.measure entry.caps.config.measure.enabled bool true.caps.config.measure.emissivityTable entry.caps.config.measure.emissivityTable.enabled bool true.caps.config.measure.externWindow entry.caps.config.measure.externWindow.enabled bool true.caps.config.measure.localObjectParams entry.caps.config.measure.localObjectParams.enabled bool false.caps.config.measure.screening entry.caps.config.measure.screening.enabled bool false.caps.config.mode entry.caps.config.mode.enabled bool true.caps.config.mode.program bool false.caps.config.mode.panorama bool false.caps.config.mode.video bool true.caps.config.mode.radiometricVideo bool false.caps.config.menu entry.caps.config.menu.enabled bool true.caps.config.menu.presets bool false.caps.config.save entry.caps.config.save.enabled bool true.caps.config.save.simultaneous bool true.caps.config.save.fastShoot bool false.caps.config.report entry.caps.config.report.enable bool true.caps.config.report.createPdf bool true

author: Jorkah
author_rank: Newbie
timestamp: May 25, 2018, 10:06:18 am
content: I have used the following code, everything is working fine.appcode:Code:## Generated at 2011-04-28 17:34:36#.caps entry.caps.config entry.caps.config.name text "app E60".caps.config.revision text "0.10".caps.config.image entry.caps.config.image.framegrab entry.caps.config.image.framegrab.fusion entry.caps.config.image.framegrab.fusion.enabled bool true.caps.config.image.framegrab.fusion.hcf entry.caps.config.image.framegrab.fusion.hcf.enabled bool true.caps.config.image.sensor entry.caps.config.image.sensor.enabled bool true.caps.config.image.services entry.caps.config.image.services.store entry.caps.config.image.services.store.enabled bool true.caps.config.image.services.store.radiometric entry.caps.config.image.services.store.radiometric.enabled bool true.caps.config.image.services.store.incompatible entry.caps.config.image.services.store.incompatible.enabled bool false.caps.config.image.services.store.incompatible.level int32 0.caps.config.image.settings entry.caps.config.image.settings.enabled bool true.caps.config.image.settings.downsample bool false.caps.config.image.settings.resIR int32 320.caps.config.image.sysimg entry.caps.config.image.sysimg.alarms entry.caps.config.image.sysimg.alarms.enabled bool true.caps.config.image.sysimg.alarms.measfunc entry.caps.config.image.sysimg.alarms.measfunc.enabled bool true.caps.config.image.sysimg.alarms.measfunc.maxCount int32 2.caps.config.image.sysimg.alarms.humidity entry.caps.config.image.sysimg.alarms.humidity.enabled bool true.caps.config.image.sysimg.alarms.humidity.maxCount int32 2.caps.config.image.sysimg.alarms.insulation entry.caps.config.image.sysimg.alarms.insulation.enabled bool true.caps.config.image.sysimg.alarms.insulation.maxCount int32 2.caps.config.image.sysimg.irMarkers entry.caps.config.image.sysimg.irMarkers.enabled bool true.caps.config.image.sysimg.irMarkers.spot entry.caps.config.image.sysimg.irMarkers.spot.enabled bool true.caps.config.image.sysimg.irMarkers.spot.maxCount int32 2.caps.config.image.sysimg.irMarkers.arrow entry.caps.config.image.sysimg.irMarkers.arrow.enabled bool true.caps.config.image.sysimg.irMarkers.arrow.maxCount int32 2.caps.config.image.sysimg.irMarkers.box entry.caps.config.image.sysimg.irMarkers.box.enabled bool true.caps.config.image.sysimg.irMarkers.box.maxCount int32 2.caps.config.image.sysimg.measureFuncs entry.caps.config.image.sysimg.measureFuncs.enabled bool true.caps.config.image.sysimg.measureFuncs.diff entry.caps.config.image.sysimg.measureFuncs.diff.enabled bool true.caps.config.image.sysimg.measureFuncs.diff.maxCount int32 2.caps.config.image.sysimg.measureFuncs.diff.calcMask int32 65526.caps.config.image.sysimg.measureFuncs.isotherm entry.caps.config.image.sysimg.measureFuncs.isotherm.enabled bool true.caps.config.image.sysimg.measureFuncs.isotherm.calcMask int32 20.caps.config.image.sysimg.measureFuncs.isotherm.dual bool true.caps.config.image.sysimg.measureFuncs.isotherm.fixScale bool false.caps.config.image.sysimg.measureFuncs.isotherm.interval bool true.caps.config.image.sysimg.measureFuncs.isotherm.invInterval bool false.caps.config.image.sysimg.measureFuncs.isotherm.maxCount int32 5.caps.config.image.sysimg.measureFuncs.mbox entry.caps.config.image.sysimg.measureFuncs.mbox.enabled bool true.caps.config.image.sysimg.measureFuncs.mbox.calcMask int32 1924.caps.config.image.sysimg.measureFuncs.mbox.maxCount int32 5.caps.config.image.sysimg.measureFuncs.mcircle entry.caps.config.image.sysimg.measureFuncs.mcircle.enabled bool true.caps.config.image.sysimg.measureFuncs.mcircle.calcMask int32 1924.caps.config.image.sysimg.measureFuncs.mcircle.maxCount int32 5.caps.config.image.sysimg.measureFuncs.mline entry.caps.config.image.sysimg.measureFuncs.mline.enabled bool true.caps.config.image.sysimg.measureFuncs.mline.calcMask int32 1924.caps.config.image.sysimg.measureFuncs.mline.maxCount int32 1.caps.config.image.sysimg.measureFuncs.reftemp entry.caps.config.image.sysimg.measureFuncs.reftemp.enabled bool true.caps.config.image.sysimg.measureFuncs.reftemp.calcMask int32 1924.caps.config.image.sysimg.measureFuncs.reftemp.maxCount int32 1.caps.config.image.sysimg.measureFuncs.script entry.caps.config.image.sysimg.measureFuncs.script.enabled false.caps.config.image.sysimg.measureFuncs.script.maxCount int32 0.caps.config.image.sysimg.measureFuncs.spot entry.caps.config.image.sysimg.measureFuncs.spot.enabled bool true.caps.config.image.sysimg.measureFuncs.spot.calcMask int32 514.caps.config.image.sysimg.measureFuncs.spot.maxCount int32 5.caps.config.image.sysimg.visualMarkers entry.caps.config.image.sysimg.visualMarkers.enabled bool true.caps.config.image.sysimg.visualMarkers.spot entry.caps.config.image.sysimg.visualMarkers.spot.enabled bool true.caps.config.image.sysimg.visualMarkers.spot.maxCount int32 5.caps.config.image.sysimg.visualMarkers.arrow entry.caps.config.image.sysimg.visualMarkers.arrow.enabled bool true.caps.config.image.sysimg.visualMarkers.arrow.maxCount int32 5.caps.config.image.sysimg.visualMarkers.box entry.caps.config.image.sysimg.visualMarkers.box.enabled bool true.caps.config.image.sysimg.visualMarkers.box.maxCount int32 5.caps.config.image.targetNoise entry.caps.config.image.targetNoise.enabled bool false.caps.config.image.targetNoise.targetNoiseMk int32 0.caps.config.image.zoom entry.caps.config.image.zoom.enabled bool true.caps.config.image.zoom.maxFactor double 8.caps.config.system entry.caps.config.system.focus entry.caps.config.system.focus.laser entry.caps.config.system.focus.laser.updateFocus entry.caps.config.system.focus.laser.updateFocus.enabled bool falseui:Code:## Generated at 2011-04-28 17:34:36#.caps entry.caps.config entry.caps.config.name text "GUI E60".caps.config.revision text "0.10".caps.config.IIG entry.caps.config.IIG.enabled bool true.caps.config.IIG.DC int32 1.caps.config.IIG.IR int32 1.caps.config.IIG.canvasSketches int32 3.caps.config.IIG.IRImageSketch bool true.caps.config.IIG.DCImageSketch bool true.caps.config.IIG.textAnnotations int32 1.caps.config.IIG.videos int32 1.caps.config.IIG.voiceAnnotations int32 1.caps.config.IIG.objects int32 5.caps.config.image entry.caps.config.image.enabled bool true.caps.config.image.adjust entry.caps.config.image.adjust.enabled bool true.caps.config.image.adjust.auto bool true.caps.config.image.adjust.interval bool true.caps.config.image.adjust.above bool true.caps.config.image.adjust.below bool true.caps.config.fusion entry.caps.config.fusion.enabled bool true.caps.config.fusion.thermal entry.caps.config.fusion.thermal.enabled bool true.caps.config.fusion.thermal.auto bool true.caps.config.fusion.thermal.interval bool true.caps.config.fusion.thermal.above bool true.caps.config.fusion.thermal.below bool true.caps.config.fusion.PIP entry.caps.config.fusion.PIP.enabled bool true.caps.config.fusion.PIP.locked bool false.caps.config.laser entry.caps.config.laser.enabled bool true.caps.config.laser.positionMarker bool true.caps.config.measure entry.caps.config.measure.enabled bool true.caps.config.measure.emissivityTable entry.caps.config.measure.emissivityTable.enabled bool true.caps.config.measure.externWindow entry.caps.config.measure.externWindow.enabled bool true.caps.config.measure.localObjectParams entry.caps.config.measure.localObjectParams.enabled bool true.caps.config.measure.screening entry.caps.config.measure.screening.enabled bool false.caps.config.mode entry.caps.config.mode.enabled bool true.caps.config.mode.program bool true.caps.config.mode.panorama bool false.caps.config.mode.video bool true.caps.config.mode.radiometricVideo bool false.caps.config.menu entry.caps.config.menu.enabled bool true.caps.config.menu.presets bool false.caps.config.save entry.caps.config.save.enabled bool true.caps.config.save.simultaneous bool true.caps.config.save.fastShoot bool false.caps.config.report entry.caps.config.report.enable bool true.caps.config.report.createPdf bool true

author: Garry2
author_rank: Newbie
timestamp: May 28, 2018, 03:31:23 am
content: Thanks Jorkah, that added an additional option in the menu, "MSX", but all 3 are grayed out. I can still only select thermal and digital. I am wondering if my camera is missing the files that point to those options.

author: eKretz
author_rank: Frequent Contributor
timestamp: June 07, 2018, 07:21:16 am
content: Quote from: zucca on May 15, 2018, 04:55:16 pmMight need this soon but tried to download and it's asking for username and password.

author: Zucca
author_rank: Unknown
timestamp: June 07, 2018, 08:30:53 am
content: WelcomeDevovto the club, well done!Z

author: eKretz
author_rank: Frequent Contributor
timestamp: June 07, 2018, 11:49:24 am
content: Anybody have a working link to the 2.23 firmware?

author: Zucca
author_rank: Unknown
timestamp: June 07, 2018, 12:14:57 pm
content: https://doc.xdevs.com/contact/Quote from: zucca on May 15, 2018, 04:55:16 pm

author: eKretz
author_rank: Frequent Contributor
timestamp: June 07, 2018, 12:28:03 pm
content: Not working for me, some kind of error - says site down. Will try again later.

author: eKretz
author_rank: Frequent Contributor
timestamp: June 07, 2018, 05:53:06 pm
content: Still dead. Anyone else?

author: Jorkah
author_rank: Newbie
timestamp: June 07, 2018, 09:45:41 pm
content: I will put it up tomorrow for you if needed.

author: eKretz
author_rank: Frequent Contributor
timestamp: June 08, 2018, 12:15:00 am
content: Thanks. Will update if I get the other link to work or not.

author: eKretz
author_rank: Frequent Contributor
timestamp: June 08, 2018, 05:22:28 am
content: Still no dice on that firmware. The site keeps giving the same error message, have tried it probably 15 times today throughout the day.

author: eKretz
author_rank: Frequent Contributor
timestamp: June 08, 2018, 05:33:57 am
content: BTW, saw that someone mentioned testing the 2.27.16 firmware to see if it was okay...did anyone ever give it a go?

author: Jorkah
author_rank: Newbie
timestamp: June 08, 2018, 07:47:44 am
content: http://www.filedropper.com/flirexxpn490v22314updatepack

author: eKretz
author_rank: Frequent Contributor
timestamp: June 08, 2018, 08:38:17 am
content: Thank you much kind sir! I am in your debt.

author: Jorkah
author_rank: Newbie
timestamp: June 08, 2018, 07:58:39 pm
content: Just helping someone like I was helped when I needed it.

author: ksilabs
author_rank: Regular Contributor
timestamp: July 16, 2018, 05:23:18 am
content: Any luck with getting thatflir_exx_pn645_pn646_v3.12.7_update_pack.zipupdate?I've just bought a new (NOS, still in original packaging and factory sealed) E40 and it came with 3.18.0 firmware so I need those missing files to get the full functionality.I can host files on mywww.ksilabs.comsite if needed. It is my own web site, not hosted anywhere, running on my own server farm so no stupid banners/registration/limits/whatever. I can also setup ftp and git servers if needed. The latter, IMHO, is the best way to keep track of all changes and be able to roll back to any point if needed.All my servers run on Fedora, nothing is hosted anywhere -- I only buy Internet connectivity -- so I have full control over everything.

author: jumbo
author_rank: Contributor
timestamp: July 22, 2018, 10:31:36 am
content: Hello, I have Flir E30bx with serial number 49202XXX.I made hack like 2-3 years ago, then it was nothing better then this instruction:https://www.eevblog.com/forum/thermal-imaging/flir-e4-thermal-imaging-camera-teardown/msg561266/#msg561266I turn on temperatures 0-650st.CI turn on temperatures 200-1200st.C (but camera shows only >80st.C)But now I see a lot of work with E30-E60 cameras, great to see it. Maybe I can help some how?1. - WiFiI have few question about my model, I tried to change "slbwver" values to turn on wifi, but after update they are going to "*".I put only random numbers there, because I dont know what values should it be in the box: Part, Revision, Serial for "slbwver"2. - Range 200-1200st.CI turn on temperatures 200-1200st.C but there is no RBF. I would like to try to calibrate camera in this range, my friend work in laboratory and there they have "black body"/"calibration owen" in a range to 2000st.C or how I should call it. But they use it for another reason and dont know nothing about Flir cameras. So if somebody can explain me how to calibrate camera only in this one range 200-1200st.C without touching old calibration it will be great.3. - new featuresI last time touch my files in the camera in 2014 or 2015, I even dont remember when. Now I see a lot of work on Exx files. Could somebody correct my files or explain me what I should change? I dont whant to change signature like name "E30bx", serial number and other really basic information. I am looking only for better resolution, quality and if its possible MSX. Yes, my camera is actually without MSX. I didn't upload on my camera any extra files, I only changed this files below.FlashFS\system\appcore.d\config.dCode:## Generated at 2011-09-16 15:13:31#.caps entry.caps.config entry.caps.config.name text "app E30bx_B".caps.config.revision text "1.1".caps.config.image entry.caps.config.image.framegrab entry.caps.config.image.framegrab.fusion entry.caps.config.image.framegrab.fusion.enabled bool true.caps.config.image.framegrab entry.caps.config.image.framegrab.visual entry.caps.config.image.framegrab.visual.enabled bool true.caps.config.image.sensor entry.caps.config.image.sensor.enabled bool true.caps.config.image.services entry.caps.config.image.services.store entry.caps.config.image.services.store.enabled bool true.caps.config.image.services.store.radiometric entry.caps.config.image.services.store.radiometric.enabled bool true.caps.config.image.services.store.incompatible entry.caps.config.image.services.store.incompatible.enabled bool false.caps.config.image.services.store.incompatible.level int32 0.caps.config.image.settings entry.caps.config.image.settings.enabled bool true.caps.config.image.settings.downsample bool true.caps.config.image.settings.resIR int32 320.caps.config.image.settings.resVIS int32 1600.caps.config.image.sysimg entry.caps.config.image.sysimg.alarms entry.caps.config.image.sysimg.alarms.enabled bool true.caps.config.image.sysimg.alarms.measfunc entry.caps.config.image.sysimg.alarms.measfunc.enabled bool true.caps.config.image.sysimg.alarms.measfunc.maxCount int32 3.caps.config.image.sysimg.alarms.humidity entry.caps.config.image.sysimg.alarms.humidity.enabled bool true.caps.config.image.sysimg.alarms.humidity.maxCount int32 1.caps.config.image.sysimg.alarms.insulation entry.caps.config.image.sysimg.alarms.insulation.enabled bool true.caps.config.image.sysimg.alarms.insulation.maxCount int32 1.caps.config.image.sysimg.irMarkers entry.caps.config.image.sysimg.irMarkers.enabled bool false.caps.config.image.sysimg.irMarkers.spot entry.caps.config.image.sysimg.irMarkers.spot.enabled bool false.caps.config.image.sysimg.irMarkers.spot.maxCount int32 0.caps.config.image.sysimg.irMarkers.arrow entry.caps.config.image.sysimg.irMarkers.arrow.enabled bool true.caps.config.image.sysimg.irMarkers.arrow.maxCount int32 0.caps.config.image.sysimg.irMarkers.box entry.caps.config.image.sysimg.irMarkers.box.enabled bool false.caps.config.image.sysimg.irMarkers.box.maxCount int32 0.caps.config.image.sysimg.measureFuncs entry.caps.config.image.sysimg.measureFuncs.enabled bool true.caps.config.image.sysimg.measureFuncs.diff entry.caps.config.image.sysimg.measureFuncs.diff.enabled bool true.caps.config.image.sysimg.measureFuncs.diff.maxCount int32 1.caps.config.image.sysimg.measureFuncs.diff.calcMask int32 65526.caps.config.image.sysimg.measureFuncs.isotherm entry.caps.config.image.sysimg.measureFuncs.isotherm.enabled bool true.caps.config.image.sysimg.measureFuncs.isotherm.calcMask int32 20.caps.config.image.sysimg.measureFuncs.isotherm.dual bool false.caps.config.image.sysimg.measureFuncs.isotherm.fixScale bool false.caps.config.image.sysimg.measureFuncs.isotherm.interval bool true.caps.config.image.sysimg.measureFuncs.isotherm.invInterval bool false.caps.config.image.sysimg.measureFuncs.isotherm.maxCount int32 1.caps.config.image.sysimg.measureFuncs.mbox entry.caps.config.image.sysimg.measureFuncs.mbox.enabled bool true.caps.config.image.sysimg.measureFuncs.mbox.calcMask int32 1924.caps.config.image.sysimg.measureFuncs.mbox.maxCount int32 5.caps.config.image.sysimg.measureFuncs.mcircle entry.caps.config.image.sysimg.measureFuncs.mcircle.enabled bool false.caps.config.image.sysimg.measureFuncs.mcircle.calcMask int32 1924.caps.config.image.sysimg.measureFuncs.mcircle.maxCount int32 0.caps.config.image.sysimg.measureFuncs.mline entry.caps.config.image.sysimg.measureFuncs.mline.enabled bool false.caps.config.image.sysimg.measureFuncs.mline.calcMask int32 1924.caps.config.image.sysimg.measureFuncs.mline.maxCount int32 0.caps.config.image.sysimg.measureFuncs.reftemp entry.caps.config.image.sysimg.measureFuncs.reftemp.enabled bool true.caps.config.image.sysimg.measureFuncs.reftemp.calcMask int32 1924.caps.config.image.sysimg.measureFuncs.reftemp.maxCount int32 1.caps.config.image.sysimg.measureFuncs.script entry.caps.config.image.sysimg.measureFuncs.script.enabled false.caps.config.image.sysimg.measureFuncs.script.maxCount int32 0.caps.config.image.sysimg.measureFuncs.spot entry.caps.config.image.sysimg.measureFuncs.spot.enabled bool true.caps.config.image.sysimg.measureFuncs.spot.calcMask int32 514.caps.config.image.sysimg.measureFuncs.spot.maxCount int32 5.caps.config.image.sysimg.visualMarkers entry.caps.config.image.sysimg.visualMarkers.enabled bool true.caps.config.image.sysimg.visualMarkers.spot entry.caps.config.image.sysimg.visualMarkers.spot.enabled bool false.caps.config.image.sysimg.visualMarkers.spot.maxCount int32 0.caps.config.image.sysimg.visualMarkers.arrow entry.caps.config.image.sysimg.visualMarkers.arrow.enabled bool false.caps.config.image.sysimg.visualMarkers.arrow.maxCount int32 0.caps.config.image.sysimg.visualMarkers.box entry.caps.config.image.sysimg.visualMarkers.box.enabled bool false.caps.config.image.sysimg.visualMarkers.box.maxCount int32 0.caps.config.image.targetNoise entry.caps.config.image.targetNoise.enabled bool true.caps.config.image.targetNoise.targetNoiseMk int32 5.caps.config.image.zoom entry.caps.config.image.zoom.enabled bool true.caps.config.image.zoom.maxFactor double 4.caps.config.system entry.caps.config.system.focus entry.caps.config.system.focus.laser entry.caps.config.system.focus.laser.updateFocus entry.caps.config.system.focus.laser.updateFocus.enabled bool true# ID 49202# CRC01FlashFS\system\services.d\config.dCode:## Appservices wlan configuration#.caps entry.caps.config entry.caps.config.name text "srvs E30bx_B".caps.config.revision text "1.1".caps.config.wlan entry.caps.config.wlan.enabled bool true.caps.config.bluetooth entry.caps.config.bluetooth.enabled bool true# ID 49202# CRC01FlashFS\system\ui.d\config.dCode:## Generated at 2011-09-16 15:13:32#.caps entry.caps.config entry.caps.config.name text "GUI E30bx_B".caps.config.revision text "1.1".caps.config.IIG entry.caps.config.IIG.enabled bool true.caps.config.IIG.DC int32 1.caps.config.IIG.IR int32 1.caps.config.IIG.canvasSketches int32 0.caps.config.IIG.IRImageSketch bool false.caps.config.IIG.DCImageSketch bool false.caps.config.IIG.textAnnotations int32 1.caps.config.IIG.videos int32 1.caps.config.IIG.voiceAnnotations int32 1.caps.config.IIG.objects int32 5.caps.config.image entry.caps.config.image.enabled bool true.caps.config.image.adjust entry.caps.config.image.adjust.enabled bool true.caps.config.image.adjust.auto bool true.caps.config.image.adjust.interval bool true.caps.config.image.adjust.above bool false.caps.config.image.adjust.below bool false.caps.config.fusion entry.caps.config.fusion.enabled bool true.caps.config.fusion.thermal entry.caps.config.fusion.thermal.enabled bool true.caps.config.fusion.thermal.auto bool true.caps.config.fusion.thermal.interval bool true.caps.config.fusion.thermal.above bool true.caps.config.fusion.thermal.below bool true.caps.config.fusion.PIP entry.caps.config.fusion.PIP.enabled bool true.caps.config.fusion.PIP.locked bool false.caps.config.laser entry.caps.config.laser.enabled bool true.caps.config.laser.positionMarker bool true.caps.config.measure entry.caps.config.measure.enabled bool true.caps.config.measure.emissivityTable entry.caps.config.measure.emissivityTable.enabled bool true.caps.config.measure.externWindow entry.caps.config.measure.externWindow.enabled bool true.caps.config.measure.localObjectParams entry.caps.config.measure.localObjectParams.enabled bool false.caps.config.measure.screening entry.caps.config.measure.screening.enabled bool false.caps.config.mode entry.caps.config.mode.enabled bool true.caps.config.mode.program bool false.caps.config.mode.panorama bool false.caps.config.mode.video bool true.caps.config.mode.radiometricVideo bool false.caps.config.menu entry.caps.config.menu.enabled bool true.caps.config.menu.presets bool false.caps.config.save entry.caps.config.save.enabled bool true.caps.config.save.simultaneous bool true.caps.config.save.fastShoot bool false.caps.config.report entry.caps.config.report.enable bool true.caps.config.report.createPdf bool true# ID 49202# CRC01

author: ksilabs
author_rank: Regular Contributor
timestamp: July 22, 2018, 08:31:31 pm
content: Quote from: tomas123 on December 08, 2014, 10:04:10 amThe problem is there is no attachmentDo you still have thatflir_exx_pn645_pn646_v3.12.7_update_pack.ziparchive somewhere? Would you share it so it would've been possible to get fully working service menu in 4.13.0 firmware?It isNOTjust those *.asp web files required for service menu to work; there are also 2 apps one of which is prodapp.exe that those *asp files call to perform their functions and those apps are also missing in 3.18.0 and any newer firmware.Those *.asp files from 2.x.x firmware would probably mostly work in 4.13.0 but prodapp might not -- 3.x.x and newer versions are Qt-based while 2.x.x used some other toolkit so it might not work in 3.x.x/4.x.x. This is why it is important to get that ENTIREflir_exx_pn645_pn646_v3.12.7_update_pack.zipto cherrypick ALL required parts.Does anybody have that update he could share? It doesn't have to be 3.12.7, an earlier 3.x.x version would also work.Maybe somebody got that attachment somewhere if there was any?Maybe someone still has a camera with 3.12.7 (or earlier 3.x.x) firmware and can post his /FlashBFS and /FlashFS directories copy?

author: eKretz
author_rank: Frequent Contributor
timestamp: July 22, 2018, 09:02:45 pm
content: Quote from: jumbo on July 22, 2018, 10:31:36 amYou already have the resolution upgraded, but I would also switch the intentional noise entry off. Can't help on the wifi, not familiar with those settings, my E40 came with wifi working already. AFAIK any entry you see with a "false" flag can be changed to "true" without hurting anything. That's what I did, just changed them a few at a time and any that didn't work or weren't useful to me I set back to "false" again.I have been playing with the lens calibration function in the service menu also but haven't got a good black body so I haven't completed the process.

author: Zucca
author_rank: Unknown
timestamp: July 23, 2018, 06:59:07 am
content: Quote from: jumbo on July 22, 2018, 10:31:36 amIt is terribly simple: there is a separate board in the Flir Exx which does the radio communication (WIFI and Bluetooth). If in your model there is not that board, no SW hack can help.SorryjumboI don't have the flir_exx_pn645_pn646_v3.12.7_update_pack.zip you are looking for. You colud PM some guys here.

author: eKretz
author_rank: Frequent Contributor
timestamp: July 23, 2018, 11:38:59 am
content: Also, I don't think there's any way to enable MSX for the earlier Exx cameras that didn't originally come with it "in-camera" so you can view it on the camera LCD, but you can still use it in FLIR Tools if you want. You'll need to take the image in one of the blended modes, so photos with both the visual and IR cameras are taken. Then you can just click the MSX button on the toolbar in FLIR Tools and it will convert it.

author: ksilabs
author_rank: Regular Contributor
timestamp: July 29, 2018, 05:12:08 am
content: Quote from: tomas123 on December 16, 2014, 11:29:21 amDoes anybody have this archive? Would you share, PLEASE?Even just prodapp.exe from 3.xx.xx version earlier than 3.18.0 would be VERY VERY helpful.Guys, PLEASE!, share that archive!!!I simply can't believe nobody have it somewhere anymore...

author: ksilabs
author_rank: Regular Contributor
timestamp: July 29, 2018, 05:43:32 am
content: Quote from: Chanc3 on January 04, 2017, 09:14:02 amDo you STILL have a copy of that previous firmware? I am VERY VERY interested in that. PLEASE PLEASE tell you still have it!

author: ksilabs
author_rank: Regular Contributor
timestamp: July 29, 2018, 06:17:49 am
content: Quote from: zucca on June 07, 2018, 12:14:57 pmIt is not there anymore...

author: ksilabs
author_rank: Regular Contributor
timestamp: July 29, 2018, 06:18:44 am
content: Quote from: Jorkah on June 08, 2018, 07:47:44 amNot working...

author: Chanc3
author_rank: Frequent Contributor
timestamp: July 29, 2018, 07:14:35 am
content: Quote from: ksilabs on July 29, 2018, 05:43:32 amI don't have the firmware pack, but all the files from the camera using that version. Happy to send over. Just let me know where to send it, in PM.

author: ksilabs
author_rank: Regular Contributor
timestamp: July 29, 2018, 08:14:28 am
content: PM sent.

author: Jorkah
author_rank: Newbie
timestamp: August 01, 2018, 07:16:55 am
content: I uploaded it again, so it will work for 30 days again.http://www.filedropper.com/flirexxpn490v22314updatepack

author: ksilabs
author_rank: Regular Contributor
timestamp: August 01, 2018, 02:49:37 pm
content: Quote from: Jorkah on August 01, 2018, 07:16:55 amGot it, thanks.

author: ksilabs
author_rank: Regular Contributor
timestamp: August 03, 2018, 04:58:10 am
content: Quote from: ksilabs on July 29, 2018, 05:12:08 amOK, so far no results...There were 2 guys here who supposedly had 3.12.7 update pack or backup from camera with that firmware. It turned out they don't have it anymore. The prodapp.exe binary from 2.xx.x versions won't start on 64xxxx Exx cameras. Binary from T420 won't start either. That means prodapp.exe from any earlier 3.xx.x version is needed.I can't believe nobody has an earlier update or backup anywhere.I would even pay a reasonable price for it if somebody has it but don't want to share. Please send me a PM or email if you happened to have that treasure.

author: ksilabs
author_rank: Regular Contributor
timestamp: August 03, 2018, 10:55:37 pm
content: Btw, the interesting thing is that there were multiple software releases after 3.12.B7 that followed the same new pattern (3.12B.7 was the last one after which that started.)Forst release was 3.13 followed by 3.14..3.18, 4.1..4.13. What Flir officially released were X.YZ.0 versions (e.g. my 3.18.0 or current 4.13.0) thatALLhave one thing in common -- theyALLhad version 0 prodkit that is essentially the same bare minimum with all good stuff removed. All of them, starting with 3.13.0 and all the way to current 4.13.0.HoweverEACH AND EVERYof those releases also had a NON-ZERO minor number version that was kinda inconsistent within 3.13..3.18 (it was .8, .9, .10, .11, 12 for 3.xx series) but then it became .13 for all releases between 4.1 and 4.6 and switched to .14 for everything up to latest 4.13. That minor version is exactly the same as the minor version of NON-ZERO version prodkits included into particular release that was 4.0.0.X for all 3.xx software versions and became 4.1.0.x starting software version 4.1. For example, the latest publicly released crippled 4.13.0 software has itsFULLsibling, version 4.13.14 that includes 4.1.0.14 prodkit instead of that mere version 0 stub in 4.13.0. The infamous 3.18.0 had 3.18.12 sibling with 4.0.0.12 prodkit.I wonder where all those non-zero minor number versions are and had some of those somehow leaked?Have you guys ever seenANYExx software after 3.12B.7 (which was right after 3.12.7) withNON-ZEROminor (third) number? Any of 4.XX.13 and especially 4.XX.14 versions would beEXTREMELYdesirable as they contain latest versions of prodkits. 3.18.12 is the version of ubiquitous 3.18.0 but with all service functions ("Service Menu" and the rest of goodies) included.I would've paid a substantial amount for 4.13.14 firmware had somebody had one for sale...

author: ksilabs
author_rank: Regular Contributor
timestamp: August 04, 2018, 12:03:22 am
content: Quote from: ksilabs on August 03, 2018, 10:55:37 pmBTW, methinks that's what they do at the factory -- first camera is installed with non-zero full version, calibrated and tested, then they truncate that prodkit.rev file to the bare minimum, change its revision to 0 and run something like "kitcrc -u -d" to remove the files that are no longer in kits files. I didn't try 4.13.0 but that seems to be exactly the case in 3.18.0 as their web files areNOTmodified properly, they simply delete most of those so "Service" menu isSTILLthere from root index.asp but whatever it pointed to is deleted so there is still the service menu link but clicking it results in 404 "Page not found" error, not in some message that it is not available or whatever as it would've been the case if that web menu had been properly re-written. Prodkit also contains some torrent pieces that might indicate how their software is installed/reinstalled or changed in production.I do also think that some of their DLLs explicitly checks the prodkit version and refuses to run anything not included there if it has 0 version. The applaunch.dat file in 4.13.0 isSIGNEDwith some cryptographic key to make any changes to common_dll.dll and appcore_dll.dll impossible so one could not be able to use a hacked one. The signature clearly shows up as new applaunch.sgn file that was not present in earlier versions.They might also have some kind of marker in their non-zero prodkit.rev file. It is nowhere to be found so it is impossible to tell if it is actually the case so it is just a wild guess.

author: Bud
author_rank: Super Contributor
timestamp: August 04, 2018, 05:34:51 am
content: Quote from: ksilabs on August 04, 2018, 12:03:22 amThat measure was defeated in E4 series time ago on this forum, might be possible for E40 too.

author: ksilabs
author_rank: Regular Contributor
timestamp: August 04, 2018, 08:38:34 pm
content: It is not all that important. The most important thing is getting a proper prodkit. This does not apply to E4 because it never had that service menu in the first place.Turning on full 320x240 resolution and all "advanced" E60 features (and some more) is trivial and works even with 4.13.0.

author: Bud
author_rank: Super Contributor
timestamp: August 04, 2018, 10:08:27 pm
content: I am talking about defeated signature verification. In E4 that allowed to proceed with upgrading the resolution and unlocking a bunch of features. You can use it for a different purpose.

author: ksilabs
author_rank: Regular Contributor
timestamp: August 04, 2018, 10:35:22 pm
content: Of course you can. But does it matter?BTW, T420/T440 and T6xx use very similar firmware. Filesystem layout is identical, most of the files are also identical. TheyDIDhave 3 releases with version 0 prodkit some time ago but then they dropped it and several latest releases do include the full featured non-zero version prodkit. Looks like they tried then decided it is not a very good idea and dropped that practice.Furthermore, there is no sign of any anti-hack protection in those firmwares. The latest T6xx, v.5.17.7, still have the very short applaunch.dat that doesn't have any "DoACRC" and even no "DoCRC" lines. Everything is fully open so it might be possible to assemble some chimera update pack using Exx and T420/T440/T6xx firmware packs.They even use that very same eFLIRInstall.exe program unchanged since 2013 for update install.

author: ksilabs
author_rank: Regular Contributor
timestamp: August 06, 2018, 04:47:17 pm
content: You only need to edit your configuration files. There is not much you can do other than getting full resolution, 4x zoom and a coule of other features from E60. Service menu doesn't work as of now as all X.Y.0 firmwares have the entire web server part for that menu removed and, most important, the prodapp.exe application missing. Web part is easy and some parts of it still work but the most valuable ones like calibration, dead pixel replacement etc. won't as they require prodapp.exe.I'm still trying to get prodapp.exe from late T6xx/T440 work on E40 but no luck so far -- there are no debugging tools available, WinCE 6.0 development stuff seems to be unobtainium so it is difficult to find out why that prodapp.exe refuses to run. No error messages, no logs of any kind, just won't run.

author: Devov
author_rank: Contributor
timestamp: August 09, 2018, 12:43:45 am
content: I got it working. Most of the problems I was having were due to the computer I was using, worked fine on my other workstation.For any new-comers who want a quick summary of how to unlock settings on devices running the 04.11.0 firmware, this is what I did:Enable USB RNDIS Mode (Go to 'Camera Information' menu in the settings menu, hold down 'right' (->) button for 15 seconds until additional settings menu appears)Connect to computer, use an FTP program like WinSCP to connect to the camera. 192.168.0.2 username: flir password: 3vligBack up everythingLocate your config file \FlashFS\system\appcore.d\config.dFor 320x240 resolution adjust this line to read as follows: .caps.config.image.settings.resIR int32 320Adjust this line to read as follows: .caps.config.image.targetNoise.targetNoiseMk int32 0For 4X digital zoom option adjust this line to read as follows: .caps.config.image.zoom.maxFactor double 4Feed your new config file into EzCRC01 (downloadable elsewhere in these threads)Zip the contents of the resulting files, change the file type to .fifWith the camera connected to the computer run FLIRInstallNet from the FLIR Tools directory: C:\Program Files (x86)\FLIR Systems\FLIR Tools\bin\FLIRInstallNet.exeFLIRInstallNet should auto connect to the camera (192.168.0.2)Browse for the .fif file you created using EzCRC01 and click 'RunFIF'Once the update is completed, power down your camera, remove and reinstall the batteries. You should now have full resolution and digital zoom capability.Change the USB setttings back to UVC and MSDI printed a lens holder for a cheap ZnSe macro lens. I need really tight resolution for a project I'm working on. The print is ugly, but it was quick and works pretty well. Results are attached.Edit: I've also attached images taken at the closest possible focus setting with the FLIR 45 and 15 degree addon lenses in case anyone else is curious about their FOV. (I got a good deal on these as FLIR was discontinuing these models)

author: Fraser
author_rank: Super Contributor
timestamp: August 15, 2018, 05:11:14 pm
content: A FLIR E40bx has joined my other thermal camerasI will be releasing it's full E60+ functionality and hopefully enabling the full E60 temperature range. It is a Mk1 facelifted model from 2011 with the metal "gull wing" side doors but separate navigation pad buttons. I need to come up with a repair for the side doors as both catch assemblies are missing. I will be contacting my friends at FLIR to establish the current availability and cost of replacement doors for the Mk1 model. If there is an option to retro fit the later rubber doors, they would be my preference.Fraser

author: Zucca
author_rank: Unknown
timestamp: August 15, 2018, 05:18:06 pm
content: Congratulations! Hopefully you have all the ranges calibrated, keep us posted.

author: Fraser
author_rank: Super Contributor
timestamp: August 15, 2018, 06:12:54 pm
content: Hi Zucca,My resolve to stop buying thermal cameras buckled briefly as the price and condition was too good to missFraser

author: Zucca
author_rank: Unknown
timestamp: August 15, 2018, 09:11:05 pm
content: Hi Fraser, no worries I am like you... Everything is good.You did well, please continue to unleash the Exx devices to E60+, the world needs your service.

author: peppy88
author_rank: Regular Contributor
timestamp: August 24, 2018, 08:26:54 pm
content: Quote from: ksilabs on August 06, 2018, 04:47:17 pmI own a T640. Do you need just the prodapp.exe?

author: ksilabs
author_rank: Regular Contributor
timestamp: August 24, 2018, 11:17:29 pm
content: Thanks for the offer but T640 prodapp.exe fails to start on Exx. I do have a full backup of T640. As a matter of fact it is still included into regular Flir firmware update package.I'm waiting for my i.MX25 development kit shipped today from Slovakia to start hacking. I do have full WinCE 6.0R3, Platform Builder, and whatever else needed. It is going to be very deep hacking so I want a devkit to develop a procedure of un-bricking a bricked camera that I will definitely brick several times in the process. It involves building and installing U-Boot instead of default bootloader and fully re-working nk.bin making a Exx BSP/SDK in the process.BTW, even the latest 4.13.0 still carries very old nk.bin (WinCE proper) built for i.MX27 CPU. It might be totally counter-intuitive but i.MX25 isNEWERprocessor built after i.MX27, mostly compatible with the latter. Freescale/NXP even has an appnote on upgrading/porting from i.MX27 to i.MX25

author: caipiao
author_rank: Contributor
timestamp: September 05, 2018, 07:13:01 pm
content: Recently got an E50 (and have been bothering Fraser our forum expert on a few things - big shout out to him for all the help!).Question to everyone: it runs 3.18.0- should I upgrade it to 4.13.0 before I jailbreak it or not a good idea?FOLLOW UP: forget it - jailbroken easily as per guide posted here. Question is then whether the upgrade brings anything useful?

author: samboman
author_rank: Newbie
timestamp: September 17, 2018, 10:35:57 pm
content: A couple things.First, someone asked a while back "BTW, saw that someone mentioned testing the 2.27.16 firmware to see if it was okay...did anyone ever give it a go?" and I didn't see any response to that. So...did anyone try it? What's the verdict?I just got an E40 (HW E40 0.10 and FW 2.19.10) and was about to upgrade the firmware, but it tried pushing me to the 2.27.16 firmware. Since nobody has tried it, I want to upgrade to 2.23.14 instead, to be safe, but all the mirrors are dead.Can someone please upload it again? Thanks so much!!EDIT: I found it here:https://doc.xdevs.com/docs/Flir/Exx/fw/and was able to install it and get everything working perfectly. I'll just avoid the newer firmware, since (most likely) nobody has tried it. Thanks

author: Serpiph
author_rank: Contributor
timestamp: October 01, 2018, 12:37:52 am
content: Hello to everybody again!I find that EXX cameras with 645XXX have new version 5.2.0. I install it and then I make some test with config files. I found something interesting inside the camera. First of all the upgade program replaces my interface files with the its own ones. I compare them and then I move my corrections into the new firmware. Also I find that new firmware has a medical palette and now I can choose it for my purposes. Also the camera has the sport mode and SuperResolution mode but I don't yet know what do they mean. My changes:1) I remove design_ui_e2.xml and toolbar_config_e2.xml tests in appkit.rev:Code:FILE FlashBFS\system\ui.d\design_ui_e2.xml undefined...FILE FlashBFS\system\ui.d\toolbar-config_e2.xml undefined2) I edit file \FlashBFS\system\appcore.d\config.d\conf.cfg:Code:.caps.config.image.flow entry.caps.config.image.flow.digitalFilter entry.caps.config.image.flow.digitalFilter.liveNuc entry.caps.config.image.flow.digitalFilter.liveNuc.enabled bool true....caps.config.image.services.store.superResolution entry.caps.config.image.services.store.superResolution.enabled bool true....caps.config.ui.measure.sport entry.caps.config.ui.measure.sport.enabled bool true3) I edit file \FlashBFS\system\service\appcore.d\config.d\conf.cfg:Code:.caps.config.image.flow entry.caps.config.image.flow.digitalFilter entry.caps.config.image.flow.digitalFilter.liveNuc entry.caps.config.image.flow.digitalFilter.liveNuc.enabled bool true....caps.config.image.services.store.superResolution entry.caps.config.image.services.store.superResolution.enabled bool true4) I edit files *.xml (in attachment).Please remember that sketching mode is not working yet, I try to make it live.What's new to my previous parameters with 4.13.0:1) selectable frame rate for video2) selectable video type (unfortunately csq type is not working yet)3) selectable image resolution (not working yet)4) new medical palette5) many parameters including graphs in image edit mode in preview mode6) sketch mode in preview mode (not working, to exit you have to switch off hard your camera)7) time lapse modesport mode

author: Serpiph
author_rank: Contributor
timestamp: October 01, 2018, 12:42:01 am
content: Quote from: caipiao on September 05, 2018, 07:13:01 pmI found blending mode in 4.13.0 and 5.2.0 for 645XXXX cameras. The cameras mixes IR and digital camera pictures together. it it similar to MSX mode but without edges enhancing.

author: Nicosrap
author_rank: Newbie
timestamp: October 04, 2018, 07:27:01 pm
content: Dear as I can update or install new firmware.http://subirimagen.me/uploads/20181004142641.25

author: cq-317
author_rank: Contributor
timestamp: October 15, 2018, 12:11:11 pm
content: I just got an E30BX with 490XXXXX, I want to liberate it, I upgraded the firmware to 2.23.14 according to the tutorial. But after I upgraded the firmware I found a problem with my visible light camera.I can't store visible photos normally.1. I used a 2GB TF card (class 4) and the file system is FAT32.2. When I unplug the battery and then cold start, the camera can store about 6 pictures normally. After that ,Only the upper part of the stored photos is normal, and the lower part is still the last normal photo. It looks like it is stitched.3.Only the visible photos is wrong,the IR photo doesn't has the same problemI made some attempts1. I continued to liberate it and I got most of the features, included Bluetooth and WiFi, photo storage is still not normal. The only difference is that the resolution of the photo before liberation is 1664*1228, and the resolution of the photo after liberation is 2048*1536.2. I can shoot the video normally and store it in the TF card. So I think the TF card is not wrong.3. I used a higher speed TF card, but the problem remains.4, I used a U disk for storage, but the problem remains.Does anyone encountered such a problem? Can someone help me?Thanks!

author: cuda12
author_rank: Regular Contributor
timestamp: October 27, 2018, 03:03:17 pm
content: On the touch screen in the upper right corner is there a ? mark, if there is push it then choose ok to sync the stored data. In a similar problem when all options are enabled on my e30 if at the same time I take a photo right when the camera was doing it's shutter reset thing it is like the processor is over loaded and only the top half of the picture is saved but it warns me that it was not saved. I have learned to slow down with my movements and pull the trigger slowly and solid like and it does not happen.

author: cq-317
author_rank: Contributor
timestamp: October 31, 2018, 02:54:19 am
content: QuoteYes, I choosed the button to save the data synchronously. When the camera is cold-started, a few pictures can be taken normally, then all of the pictures have only the upper part. But storing video is normal, which is really confusing.

author: t.AM
author_rank: Newbie
timestamp: November 01, 2018, 05:50:00 pm
content: Flir E40When updating the firmware, the battery is low.Now the camera does not start.In FLIR Tools not visible, but can see a USB flash drive on computer.How can I fix the camera?

author: Fraser
author_rank: Super Contributor
timestamp: November 01, 2018, 07:17:19 pm
content: Did that camera actually shut down during the firmware update ?If it did, that is pretty much a worst case scenario that is often highlighted by manufacturers as irrecoverable without a return to the service agent. The reason is that, unlike a controlled firmware installation failure, where the firmware updates can reverse the update if it detects a problem, a power failure during the writing to flash memory basically creates a totally corrupted firmware build with no 'back out' path.In cases such as this, on embedded computers, if the boot loader remains intact, some clever IT bods install a new firmware image. Sadly I do not think such is so straight forward with the Exx series though. You need to be able to access the operating system and to access that you either need to change the USB mode for FTP communications, or directly access the OS via an RS232 engineering port within the camera. You cannot take someone else's camera firmware and clone it onto your camera as each firmware build is effectively camera specific with file CRC's and unique factory calibration data.I am sorry to say, I think this will require return to FLIR for a new firmware installation using their production utilities.Fraser

author: t.AM
author_rank: Newbie
timestamp: November 07, 2018, 06:19:30 pm
content: To change the resolution I need inFlashFS/system/appcore.d/config.d/conf.cfgCode:.caps.config.image.settings.resIR int32 160...caps.config.image.targetNoise.targetNoiseMk int32 55toCode:.caps.config.image.settings.resIR int32 320...caps.config.image.targetNoise.targetNoiseMk int32 0?Is that all ? or need something else?after replacing the file, pictures taken with new settings, does not work :"(

author: miami123
author_rank: Newbie
timestamp: January 18, 2019, 02:29:44 am
content: Hi, I bought FLIR e40 from 2014 software version 3.18.0 with MSX. How to make an upgrade to 320x240. Do I have to update the software to version 4.13 first ?? Can anyone give some advice to the E40 with MSX with software 3.18.0thx

author: Chanc3
author_rank: Frequent Contributor
timestamp: January 18, 2019, 07:29:14 am
content: Quote from: t.AM on November 07, 2018, 06:19:30 pmDid you read the rest of the guide where you need to regenerate the CRC code?

author: Chanc3
author_rank: Frequent Contributor
timestamp: January 18, 2019, 07:30:02 am
content: Quote from: miami123 on January 18, 2019, 02:29:44 amRead this thread fully. Yes it can be upgraded. No don't update.

author: Pinkus
author_rank: Frequent Contributor
timestamp: February 20, 2019, 11:21:43 pm
content: In case you are interested, I here added some useful information and a STL file for 3D printing for a Exx macro lens:https://www.eevblog.com/forum/thermal-imaging/znse-lenses-on-ebay/msg2214507/#msg2214507

author: netpac
author_rank: Contributor
timestamp: February 23, 2019, 10:16:56 am
content: Can anybody shareflir_exx_pn645_pn646_v3.12.7_update_pack.zip or flir_exx_pn645_pn646_v3.18.0_update_pack.zipPlease and thank you

author: Chanc3
author_rank: Frequent Contributor
timestamp: February 23, 2019, 10:48:09 am
content: Quote from: netpac on February 23, 2019, 10:16:56 amI might have these, will check on Monday when I'm back in the office.

author: netpac
author_rank: Contributor
timestamp: February 23, 2019, 11:40:05 am
content: That would be very helpful. Many Thanks

author: netpac
author_rank: Contributor
timestamp: February 26, 2019, 10:58:37 am
content: @Chanc3please and thank you.

author: Chanc3
author_rank: Frequent Contributor
timestamp: February 26, 2019, 09:24:48 pm
content: Sent you a PM with a link to my stash.

author: netpac
author_rank: Contributor
timestamp: February 28, 2019, 11:31:54 am
content: FLIR Exx P/N:645xx / 646xx Firmware List:ZIP-File: OS: App: Prodkit:flir_exx_pn645_pn646_v3.0.1_update_pack.zip 17.5.0 4.0.0 4.0.0.1flir_exx_pn645_pn646_v3.1.1_update_pack.zip 17.5.0 4.0.1 4.0.0.1flir_exx_pn645_pn646_v3.2.1_update_pack.zip 17.6.2 4.0.2 4.0.0.1flir_exx_pn645_pn646_v3.3.2_update_pack.zip 17.6.3 4.0.3 4.0.0.2flir_exx_pn645_pn646_v3.4.2_update_pack.zip 17.6.3 4.0.4 4.0.0.2flir_exx_pn645_pn646_v3.5.2_update_pack.zip 17.6.4 4.0.4 4.0.0.2flir_exx_pn645_pn646_v3.6.3_update_pack.zip 17.6.4 4.0.5 4.0.0.3flir_exx_pn645_pn646_v3.7.4_update_pack.zip 17.6.4 4.0.6 4.0.0.4flir_exx_pn645_pn646_v3.8A.4_update_pack.zip 17.6.4 4.0.7 4.0.0.4flir_exx_pn645_pn646_v3.8.4_update_pack.zip 17.6.6 4.0.7 4.0.0.4flir_exx_pn645_pn646_v3.8.5_update_pack.zip 17.6.6 4.0.7 4.0.0.5flir_exx_pn645_pn646_v3.8B.5_update_pack.zip 17.6.8 4.0.7 4.0.0.5flir_exx_pn645_pn646_v3.9.5_update_pack.zip 17.6.8 4.0.8 4.0.0.5flir_exx_pn645_pn646_v3.10.5_update_pack.zip 17.6.8 4.0.9 4.0.0.5flir_exx_pn645_pn646_v3.11.6_update_pack.zip 17.6.8 4.0.10 4.0.0.6flir_exx_pn645_pn646_v3.12.7_update_pack.zip 17.6.8 4.0.11 4.0.0.7flir_exx_pn645_pn646_v3.12B.7_update_pack.zip 17.6.12 4.0.11 4.0.0.7flir_exx_pn645_pn646_v3.13.0_update_pack.zip 17.6.10 4.0.12 0 -> no Service Menuflir_exx_pn645_pn646_v3.13.8_update_pack.zip 17.6.10 4.0.12 4.0.0.8flir_exx_pn645_pn646_v3.14.0_update_pack.zip 17.6.10 4.0.13 0 -> no Service Menuflir_exx_pn645_pn646_v3.14.8_update_pack.zip 17.6.10 4.0.13 4.0.0.8flir_exx_pn645_pn646_v3.14.9_update_pack.zip 17.6.10 4.0.13 4.0.0.9flir_exx_pn645_pn646_v3.15.0_update_pack.zip 17.6.10 4.0.14 0 -> no Service Menuflir_exx_pn645_pn646_v3.15.9_update_pack.zip 17.6.10 4.0.14 4.0.0.9flir_exx_pn645_pn646_v3.15.10_update_pack.zip 17.6.10 4.0.14 4.0.0.10flir_exx_pn645_pn646_v3.16.0_update_pack.zip 17.6.12 4.0.15 0 -> no Service Menuflir_exx_pn645_pn646_v3.16.10_update_pack.zip 17.6.12 4.0.15 4.0.0.10flir_exx_pn645_pn646_v3.16.11_update_pack.zip 17.6.12 4.0.15 4.0.0.11flir_exx_pn645_pn646_v3.17.0_update_pack.zip 17.6.12 4.0.16 0 -> no Service Menuflir_exx_pn645_pn646_v3.17.12_update_pack.zip 17.6.12 4.0.16 4.0.0.12flir_exx_pn645_pn646_v3.18.0_update_pack.zip 17.6.12 4.0.17 0 -> no Service Menuflir_exx_pn645_pn646_v3.18.12_update_pack.zip 17.6.12 4.0.17 4.0.0.12flir_exx_pn645_pn646_v4.1.0_update_pack.zip 18.7.0 4.1.0 0 -> no Service Menuflir_exx_pn645_pn646_v4.1.13_update_pack.zip 18.7.0 4.1.0 4.1.0.13flir_exx_pn645_pn646_v4.2.0_update_pack.zip 18.7.2 4.1.1 0 -> no Service Menuflir_exx_pn645_pn646_v4.2.13_update_pack.zip 18.7.2 4.1.1 4.1.0.13flir_exx_pn645_pn646_v4.3.0_update_pack.zip 18.7.2 4.1.2 0 -> no Service Menuflir_exx_pn645_pn646_v4.3.13_update_pack.zip 18.7.2 4.1.2 4.1.0.13flir_exx_pn645_pn646_v4.4.0_update_pack.zip 18.7.4 4.1.2 0 -> no Service Menuflir_exx_pn645_pn646_v4.4.13_update_pack.zip 18.7.4 4.1.2 4.1.0.13flir_exx_pn645_pn646_v4.5.0_update_pack.zip 18.7.6 4.1.3 0 -> no Service Menuflir_exx_pn645_pn646_v4.5.13_update_pack.zip 18.7.6 4.1.3 4.1.0.13flir_exx_pn645_pn646_v4.6.0_update_pack.zip 18.7.6 4.1.4 0 -> no Service Menuflir_exx_pn645_pn646_v4.6.13_update_pack.zip 18.7.6 4.1.4 4.1.0.13flir_exx_pn645_pn646_v4.7.0_update_pack.zip 18.7.6 4.1.5 0 -> no Service Menuflir_exx_pn645_pn646_v4.7.14_update_pack.zip 18.7.6 4.1.5 4.1.0.14flir_exx_pn645_pn646_v4.8.0_update_pack.zip 18.7.6 4.1.6 0 -> no Service Menuflir_exx_pn645_pn646_v4.8.14_update_pack.zip 18.7.6 4.1.6 4.1.0.14flir_exx_pn645_pn646_v4.9.0_update_pack.zip 18.7.8 4.1.7 0 -> no Service Menuflir_exx_pn645_pn646_v4.9.14_update_pack.zip 18.7.8 4.1.7 4.1.0.14flir_exx_pn645_pn646_v4.10.0_update_pack.zip 18.7.8 4.1.8 0 -> no Service Menuflir_exx_pn645_pn646_v4.10.14_update_pack.zip 18.7.8 4.1.8 4.1.0.14flir_exx_pn645_pn646_v4.11.0_update_pack.zip 18.7.8 4.1.9 0 -> no Service Menuflir_exx_pn645_pn646_v4.11.14_update_pack.zip 18.7.8 4.1.9 4.1.0.14flir_exx_pn645_pn646_v4.12.0_update_pack.zip 18.7.8 4.1.10 0 -> no Service Menuflir_exx_pn645_pn646_v4.12.14_update_pack.zip 18.7.8 4.1.10 4.1.0.14flir_exx_pn645_pn646_v4.13.0_update_pack.zip 18.7.10 4.1.11 0 -> no Service Menuflir_exx_pn645_pn646_v4.13.14_update_pack.zip 18.7.10 4.1.11 4.1.0.14

author: eKretz
author_rank: Frequent Contributor
timestamp: February 28, 2019, 05:13:03 pm
content: Any Chanc3 I could get that link too?

author: netpac
author_rank: Contributor
timestamp: February 28, 2019, 06:23:52 pm
content: This is only the filelist. If someone has those files - please share. Thank you.

author: netpac
author_rank: Contributor
timestamp: March 06, 2019, 02:17:39 pm
content: I can confirm that a downgrade for Exx PN645 v4.10 to v3.12.7 is (maybe) possible. My camera is working very well after the downgrade from v4.10.0 to 3.12.7 and I have now access to the whole service menu - with 4.10.0 I had some problems with RNDIS and ftp transfer communication and no service menu. I did the following steps:1. Load the battery from the camera to 100% and connect the external power supply - the upgrade or downgrade tooks around 30 minutes2. Switch camera to rndis3. Backup all files with winscp and ftp4. Copy the new firmware to the sdcard "\StorageCard\FLIRUpdate\"(E2qtcomb_v3.12.7.fif and eFLIRInstall.exe)5. start a Telnet session with <telnet 192.168.0.2>6. from root type <cd \StorageCard\FLIRUpdate>7. and execute <eFLIRInstall.exe \StorageCard\FLIRUpdate\E2qtcomb_v3.12.7.fif>8. confirm all with yes9. when the upgrade is finished restart your camera a second time - there is a second upgrade processnote - it worked for me. But there is no guarantee that it works for you as well.

author: nikoum
author_rank: Contributor
timestamp: May 29, 2019, 03:06:19 pm
content: Does anybody know if an upgraded resolution and menu mk1 E40 with 490 serial and sw:2.23.14 can be updated to a newer software version without losing the upgrade. I have read in old posts, years ago that 2.23.14 is the end of the line, but i am wondering if this is still valid

author: Fraser
author_rank: Super Contributor
timestamp: May 29, 2019, 03:19:09 pm
content: Still valid.The one more recent Mk1 firmware is a total unknown in terms of its reason for existence. There appears no good reason to install it and plenty to not install it. Mk2 firmware does not work on a Mk1 platform.Fraser

author: nikoum
author_rank: Contributor
timestamp: May 29, 2019, 03:31:53 pm
content: Thank you Fraser. Do you or someone else know if the add isotherm / above or below function can be modified to include an alarm with beep function such as in add spot, add box and add circle ?

author: Fraser
author_rank: Super Contributor
timestamp: May 29, 2019, 06:34:06 pm
content: Sorry, cannot help on that request.Fraser

author: Mannyb
author_rank: Newbie
timestamp: June 11, 2019, 06:09:13 pm
content: Dear All i'm a newbie and i just purchased a used Flir E40 and i want to upgrade to e60 softwarei read almost all the tread and spent several hours but still not sure what to dobelow are the informationModel: E40 1.2Serial: 645XXXXXSoftware 5.2.0can i upgrade this this E60 Software?kindly advice please

author: Mannyb
author_rank: Newbie
timestamp: June 12, 2019, 12:14:50 am
content: Just a follow upi managed to run CRC01 and created a file to flashbut there's seems a problem and i can't connect my camera to pc either in USB RNDIS i also tried FileZilla & total commander with no luckdo i have to downgrade the software first?is there another option to flash the e60 fif file?i would really appreciate any feedback

author: cuda12
author_rank: Regular Contributor
timestamp: June 13, 2019, 09:32:06 pm
content: connection errors kind of depend on what OS you are using, windows 7 on up and xp made the connection easy windows 10 at first didn't work but recent version connect now. What are you using?

author: Mannyb
author_rank: Newbie
timestamp: June 14, 2019, 07:17:20 am
content: Posted by: netpac« on: March 07, 2019, 01:17:39 am »Insert QuoteI can confirm that a downgrade for Exx PN645 v4.10 to v3.12.7 is (maybe) possible. My camera is working very well after the downgrade from v4.10.0 to 3.12.7 and I have now access to the whole service menu - with 4.10.0 I had some problems with RNDIS and ftp transfer communication and no service menu. I did the following steps:1. Load the battery from the camera to 100% and connect the external power supply - the upgrade or downgrade tooks around 30 minutes2. Switch camera to rndis3. Backup all files with winscp and ftp4. Copy the new firmware to the sdcard "\StorageCard\FLIRUpdate\"(E2qtcomb_v3.12.7.fif and eFLIRInstall.exe)5. start a Telnet session with <telnet 192.168.0.2>6. from root type <cd \StorageCard\FLIRUpdate>7. and execute <eFLIRInstall.exe \StorageCard\FLIRUpdate\E2qtcomb_v3.12.7.fif>8. confirm all with yes9. when the upgrade is finished restart your camera a second time - there is a second upgrade processnote - it worked for me. But there is no guarantee that it works for you as well.Hi Netpacdo still have the the firmware v3.12.7.fif?would you be able to share as i need itthanks

author: Mannyb
author_rank: Newbie
timestamp: June 15, 2019, 06:10:21 am
content: Thanks all for the supportafter various trial and error with tons of back ups, my Flir E40 1.2 with software 5.2.0 serial 645XXXX, are now 320X240 pixelsLens are also set 4X instead of 2Xstill working to enable some functions especially the insulation warning which is disable on E40again thank you all, this is a great site

author: Mannyb
author_rank: Newbie
timestamp: June 17, 2019, 08:55:36 pm
content: A simple and easy way to replace the flir Logo is just to edit the bootlogo.bmp itself from \FlashBFS\system and paste your own logo on the same picture, just make sure your logo has the same pixels size and format, so every time you boot up or open your unit your information or logo will appear.1. create or edit your own logo save it with 320X240 Pixel using paint editor1. Extract bootlogo.bmp using pft connect, save somewhere2. edit the bootlogo.bmp and paste your own logo with the same pixel 320X2403. put it back using pft connect4. remove the battery and re-start

author: DaJMasta
author_rank: Super Contributor
timestamp: August 31, 2019, 09:00:39 pm
content: Got a used older e40 (gen 1 reports version 0.10) and upgraded to the 2.23.14 firmware available here. Ran ezcrc01 successfully on my modified conf file, but when I go to use the net installer it tells me the .fif I created has a file format error when loaded into the installer, specifically "Missing camera macro file" from the log. The files created were the e8.cfg and the batch file pointing to it, and since those correspond to the other camera series, I tried renaming it to conf.cfg and renaming the batch contents, but it hasn't liked it yet. Is this a candidate for the manual crc01 method instead?Also had some trouble doing a full backup over ftp, since several windows files and a database file were not accessible when the camera was on. Anyone run into that before?Ha! I'm a fool and I'll share it in hopes of solving someone else's upgrade:I zipped the whole folder and not just the contents, making the file structure unexpected and making the error. Zipped the contents properly and it worked first try. Unlocked the resolution, the 4x zoom, and decreased the added noise to 35 (I saw it mentioned as a good baseline for high end models).Also worth mentioning that in my original conf.cfg file, there were two duplicate resIR lines next to each other, I changed both to the new one and it works well.Coming from a 9Hz camera this beauty is night and day! Also for being a bit heaver than my U5855A, the ergonomics actually make it feel a bit better in my hand.

author: DaJMasta
author_rank: Super Contributor
timestamp: October 18, 2019, 05:51:10 am
content: New post since it's been a bit, but the Flir logo over the saved videos is a bit annoying - it's pretty large given such a small overall image size and I'd love to have it removed- does anyone know how to remove it?I tried changing the flir logo jpg to .old over the local FTP connection, and while I would have expected a different format (for an alpha channel, since there is transparency), and I haven't been able to find the image itself in any of the other image formats just sitting around in the file structure.Maybe it requires some sort of firmware hack, and maybe it's not doable, but if it's possible to remove the Flir watermark on the video, it would be great to.

author: Spirit532
author_rank: Frequent Contributor
timestamp: October 18, 2019, 07:50:05 pm
content: Quote from: DaJMasta on October 18, 2019, 05:51:10 amMy addon should be able to do it, and works on all Ex/Exx/T4xx cameras:https://www.eevblog.com/forum/thermal-imaging/flir-t440bx-hacking-firmware-investigation-possible-ultramax-support-for-exx/

author: DaJMasta
author_rank: Super Contributor
timestamp: October 21, 2019, 06:30:20 am
content: Thanks, I gave it a try this evening and while the app is running correctly, I don't actually see the option to remove the logo, and it did not remove it automatically.My camera is the older version e40 modded to an e60, so the MSX option checked by default need not apply (don't have the MSX hardware in the unit) and I have somewhat intermittent menu issues. There are times, before and after that initial app opening, when the menu key doesn't bring up the menu at all, though you can still pull it in from the left side of the screen. Then there are other times when it works exactly as expected, and I haven't been able to find a reason for either one aside from something to do with the new app.Worth mentioning that I'm using the applaunch.dat option to launch it, if it makes a difference.

author: Spirit532
author_rank: Frequent Contributor
timestamp: October 21, 2019, 07:08:08 am
content: Quote from: DaJMasta on October 21, 2019, 06:30:20 amIt's the very first option.

author: DaJMasta
author_rank: Super Contributor
timestamp: October 21, 2019, 07:26:18 am
content: This is what I'm seeing:The first option does actually turn off the NUC like expected. My unit seems to be unhappy with the hack, though. I found booting up for this that the camera would power on, show splash screen, and then power off before booting. Reseating the battery and cold booting fixes it, but it takes several sets of keystrokes to boot the hack menu, and I actually managed to get it into a state where holding the power button did not power down the camera. I think it has something to do with window focus, since pulling in the left side menu re-enabled shutting down with the power button.My software version is 2.23.14

author: Spirit532
author_rank: Frequent Contributor
timestamp: October 21, 2019, 08:39:11 am
content: Ah, it can be buggy sometimes. I'll take a look at it when I get around to poking at it again.

author: DaJMasta
author_rank: Super Contributor
timestamp: October 21, 2019, 04:29:37 pm
content: A little update, maybe the extra info will help figuring out what's wrong.Before disabling, I tried turning on the option in the .ini and just not bothering with the GUI - and the logo was still there. Not only that, I think the app was ignoring the .ini altogether, because I also turned off the MSX option and on cold boot it still showed as enabled (it also wasn't storing settings between reboots, so maybe this is related).I ended up disabling the hack by just commenting out the applaunch.dat line, and I verified that a behavior that started with the hack enabled went away - when I used the hold menu and down keystrokes to open the app GUI, when it was installed, it would hide the temperature range bar on the right, even when it didn't actually bring up the app GUI itself - actually seemed like sort of a handy trick to hide on screen stuff, but on disabling the app, it wasn't a stock behavior :p

author: Dante91
author_rank: Newbie
timestamp: November 25, 2019, 02:00:24 pm
content: Hello every one.I am a new member. I would like to hack my FLIR E40 in 320x240 resolution. Do you have a solution about this ? I have already read the E40 and E30 subject, however I did not find a solution. I have not seen the tutoriel yet.Friendly regards,Dante

author: d.kozminihs
author_rank: Newbie
timestamp: May 13, 2020, 10:28:12 am
content: Did anyone try this new 5.3.0 firmware? Is it safe to upgrade, is it worth upgrading from 4.13.0?P.S.: Thank you all for taking this that far!

author: Fraser
author_rank: Super Contributor
timestamp: May 13, 2020, 11:59:37 am
content: With each new release of firmware comes the risk that the upgrade will be defeated or prevented. FLIR are not particularly happy that people have upgraded their Exx series cameras but they have now released the new models so less time is spent on the old cameras firmware. The Exx series have been around fir a long time now so ask yourself what bugs the firmware would fix that have not already been discovered and sorted in the past. FLIR like to make “housekeeping” changes to firmware...... this normally means they try to make the upgrade harder ! Newest is not always best when it comes to firmware, especially where publicly known hacks are concerned !My advice is to consider what, if any issues you have with the current firmware and whether a firmware upgrade is worth risking. FLIR are normally tight lipped about what improvements the upgrade contains. It may fix an issue you are having, it may not. There is also the very real possibility that a newer firmware contains a bug not previously present in your camera !My advice - stick with the firmware that is known to be safe and stableFraser

author: d.kozminihs
author_rank: Newbie
timestamp: May 13, 2020, 12:29:59 pm
content: I have taken the risk and updated to 5.3.0. Got resolution and noise sorted exactly as before. Will look into other setting later and come back.Unfortunately I had reasons to consider update. My camera was restarting at the end of warm boot every second time (sorted after update).But what concerned me the most - it doesn't allow me to use Wi-Fi and Bluetooth. It has been registered as "FLIR E40 60Hz+radio" if that means anything.Update didn't help with connectivity, but at least solved restart problemI remember someone mentioned they would be able to share files from later E60, but I cant's find any live links. May I ask someone to share those again?

author: Fraser
author_rank: Super Contributor
timestamp: May 13, 2020, 12:39:36 pm
content: I am pleased that the firmware fixed your issue. The Radio function is enabled and disabled in the configuration files. Have you checked that it is actually set to “True” in the configuration ? All E40 cameras should have an active radio module. Did the radio link function work before the upgrade ?The later firmware versions were shared by a member of this forum recently so they should be available from someone here. I am not near my laptop so cannot help at the moment.Fraser

author: d.kozminihs
author_rank: Newbie
timestamp: May 13, 2020, 02:31:59 pm
content: Warm boot restart problem is back. No miracle this time.Both "wlan" and "bluetooth" entries in service/conf.cfg are true. That is how it was when I bought it, never seen radio working.If I change those to false, then whole relevant menu disappears. I have these menus, but nothing can be changed in there.In "Wi-Fi" menu it is permanently set to "Off" and no way to change to "Share" or "Connect to network"There is a message "Wi-Fi is not present" on the bottom.In "Bluetooth..." it is impossible to enable it. No messages.In both menus i am unable to scroll down from the first line.I went through the whole forum yesterday, must have missed the new firmware.

author: d.kozminihs
author_rank: Newbie
timestamp: May 13, 2020, 07:58:07 pm
content: I have searched for that new E60 firmware (for 64... s/n), but all of the links are down. Could you please share it again?I will host it from my own website, so it won't expire any time soon.

author: Fraser
author_rank: Super Contributor
timestamp: May 14, 2020, 01:41:06 pm
content: I take no credit for this firmware collection. It was originally uploaded by a generous fellow forum member.No idea how long the file remains available on filedropper.File Size is 90MBhttp://www.filedropper.com/flir-firmware-masterFraser

author: d.kozminihs
author_rank: Newbie
timestamp: May 15, 2020, 07:15:13 pm
content: Thank you! I will study these files.I will keep it alive at this address:https://drive.google.com/open?id=1zHZE84IzDyBvlQyGhviU6fXpa7Gbx9S8(Hope you don't mind)I have contacted Flir to get more help with inactive radio, will see how it goes.Will come back once some progress will be done

author: Flukav
author_rank: Contributor
timestamp: May 18, 2020, 05:18:59 pm
content: Dear all,After successful update of my E4, I acquired a first gen Flir E40bx, left rotting in a shut-down thermal insulation company basement for 3 years.Battery showed no sign of life (20mV on poles), so I started it up by wiring a 3.7V cell. As soon as voltage reached 2.5V, the E40 unit was able to detect the battery and charge it: pretty resilient.Hardware is 0.9, firmware 2.19.10 .Of course Flir Tools wanted to update to 2.27.16, but most of replies on this feed talk about the 2.23.14 firmware as a safe base for future «improvements».Can anyone share the Flir E40bx -490XXX - 2.23.14 file and some advice on the hack to be performed?Cheers

author: Fraser
author_rank: Super Contributor
timestamp: May 23, 2020, 05:55:37 pm
content: I have uploaded the requested firmware package here:http://www.filedropper.com/flirexxpn490v22314updatepackEnjoyThis reminds me that I have an E40b awaiting release from its shacklesI must dig it out and upgrade it.Fraser

author: Flukav
author_rank: Contributor
timestamp: May 23, 2020, 06:28:20 pm
content: Very, very nice.Can we attach firmwares directly on the post so it can be kept for a longer time than on external data transfer website?On the original post of IgustavoCampos, two programs were given: CRC03.exe and crc01.exeOnly the latter is mentioned in the «upgrade» procedure. Anyone knows what CRC03.exe is doing?Cheers

author: Flukav
author_rank: Contributor
timestamp: May 25, 2020, 04:53:26 pm
content: Hey folks;After 2 attempts, i successfully updated my E40bx to a regular E60bx.First attempt failed, leading to disappearance of wifi/zoom/almost all menus.Second attempt was made with files from «funzt», releasing all E40's power.https://www.eevblog.com/forum/thermal-imaging/flir-e4-thermal-imaging-camera-teardown/msg338671/#msg338671Compared to my previous E4, I am really surprised by image improvement, gotta love this little camera.Fraser, funzt, thank you.

author: Anomalia
author_rank: Newbie
timestamp: June 15, 2020, 06:50:52 am
content: Where do you see firmware version? The settings menu? It reads 2.6.6, E40 0.10.The version that needs to be installed is 2.23.14, but I have 2.6.6? This is confusing. Is it really 2.6.6?

author: Anomalia
author_rank: Newbie
timestamp: June 17, 2020, 09:42:15 am
content: should I proceed with update? The current version number is 2.6.6? Shouldn't it be smaller in number? I checked that I have service menu.Edit: This issue is solved. Thank you Fraser

author: Anomalia
author_rank: Newbie
timestamp: July 02, 2020, 11:55:00 am
content: Is it possible to add medical palette to 640XXX series like 645XXX?

author: unchiu
author_rank: Newbie
timestamp: July 13, 2020, 04:37:27 pm
content: Hello guys!I have an E40bx sn 490 sw 1.24.16. I want to "upgrade" to E60bx with extended temp range.Is it safe to make upgrade directly to 2.23.14?Thanks.

author: kaz911
author_rank: Super Contributor
timestamp: September 18, 2020, 12:45:26 pm
content: Hi all hardworking people,got my hands on a E40 mk2 with MSX - sn 645 HW v. 1.2 FW 4.11.0Managed to get it updated and working in 320 via Parallels Win10 on MBP. Took a while to realise that Flir Tools no longer installs the RNDIS drivers....Questions: I have the 10mm (45deg) lens for my old E50bx. But when I use it on the E40mkII - MSX can not be enabled? (So add lens and REMEMBER to change lens settings to 45DEG)2. Does that require additional calibration to get MSX or will it not work at all? (Got 3 options on MK-II in Lens " None, FOV 45d and FOV15d" - but on the MK I - I have the 45DEG Lens as a 4th option with S/N listed. So "FOV 45d SN 234234234" - I have tried copying the Maps over from the MK I - but no change. So where does FLIR store that info?...In general I find the old MK I - more geeky ... but about the same image quality. I have not found an easy way to add more than 1 measurement box onto the MK II?I do find focus easier with MSX - image kind of "jumps" in place when you have focus.45 Deg lens seems to decrease temperature readings with about 2 deg C. So ALWAYS remember to set the lens settings correct else your measurements are out of whack!3. Does anyone have release notes about what has happened since firmware 4.11.0? And is there a >4.11.0 with service menu available somewhere?The manual now says it has a "Spotting" function which is meant to spot people with high temperatures - but I don't know which release that was in. The Menu for enabling it is not in the 4.11.0 (it disables camera sleep mode as well)/k

author: Fraser
author_rank: Super Contributor
timestamp: September 18, 2020, 02:04:33 pm
content: About supplemental lenses and Exx series......The E40 is designed to take wide or tele supplemental lenses as you know but, as thermal energy supplemental lenses, they have no effect on the built in visible light cameras field of view. MSX uses the visible light camera for scene edge detection so basically as soon as you change the field of view of the thermal lens, the MSX cannot match the FOV and becomes useless. It is therefore disabled.The supplemental lenses are normally included in the cameras factory supplied calibration tables but for the most accurate measurements, FLIR say you need to send the camera and it’s supplemental lenses to them for full calibration with the specific lenses fitted. Whether this is truly justified is open to discussion. What FLIR do is install the supplemental lens and carry out calibration to create a specific calibration table for that specific serial number lens. Hence why your MK1 contains the serial number of the 45 degree lens as an additional 4th lens entry. FLIR state that you should keep the lens with the camera to which it was matched at the time of calibration.The MK1 Exx camera contains the service menu and its calibration routines so a suitably equipped owner can calibrate the camera and any supplemental lenses themselves.You need accurate Blackbody sources for such calibration work. The MK2 Exx series had the service menu removed so sadly you are not normally able to calibrate your own camera or the supplemental lenses. I do not think the calibration tables from your MK1 camera can be used with any success in your MK2 camera.If you really do need accurate temperature measurements whilst using the supplemental lens, you will have little choice but to send the camera and lens to FLIR for a supplemental lens calibration.Fraser

author: wirbelwind
author_rank: Newbie
timestamp: October 08, 2020, 08:14:06 am
content: I found some interesting pictures in the flir_t6xx_pn55903_04_v5.38.8_update_pack.

author: Finderbinder
author_rank: Regular Contributor
timestamp: October 03, 2021, 08:31:41 pm
content: Hello.Just upgraded my E50 1.2, P/N: 64501-0201, SW: 4.11.0 a little bit (resolution and noise).Would want to upgrade it to a full E60 or so. Thought there are many pages written regarding upgrades I didn't find a complete list (or files) corresponding to my camera's version (hw/sw). Am a little scared to brick or mess my cam acting without a propper guide.

author: Finderbinder
author_rank: Regular Contributor
timestamp: October 06, 2021, 03:17:13 pm
content: I think my E50 was altered by previous owner. All *.cfg files I got with my cam are attached.\FlashFS\system\appcore.d\config.d\conf.cfg\FlashFS\system\appcore.d\config.d\ui_conf.cfg\FlashFS\system\ui.d\config.d\conf.cfg\FlashFS\system\services.d\config.d\conf.cfg\FlashFS\system\service\appcore.d\config.d\conf.cfgEspecially service_conf.txt looks strange for me - a common ending for *.cfg files is missing there.And the string in it I doubt corresponds to E50:.caps.config.image.settings.resIR int32 320May someone with more experience check these? Are these files correct or messed up somehow?It would be perfect if someone could share original E50 or E60 or Exx config files of the same HW 1.2, P/N: 64501-0201, SW: 4.11.0 version.Or/and how properly modify these to a full capabilities?

author: Userli
author_rank: Regular Contributor
timestamp: February 07, 2022, 11:01:19 am
content: Hey,I just got hold of a E40 0.10, firmware version 1.24.16 .I applied the config changes and got the higher resolution and all the other goodies working.Now I would like to upgrade to the firmware 2.23.14, which unfortunately I can’t find at any of the places mentioned in this thread.Could somebody please send me or point me to the corresponding file(s)?

author: Fraser
author_rank: Super Contributor
timestamp: February 07, 2022, 11:22:00 am
content: PM with link to the file on my Google drive sent

author: Userli
author_rank: Regular Contributor
timestamp: February 07, 2022, 03:01:53 pm
content: Thank you very much Fraser!!!After a bit of playing around with version 2.23 I noticed that the toolbar is shown vertically on the left, whereas on most pictures here and in the manual I see it horizontal at the bottom of the screen. Looking through the menu and the config files I couldn't see a setting to change this. Is there a possibility to do so?

author: Userli
author_rank: Regular Contributor
timestamp: February 08, 2022, 10:41:44 pm
content: I just compared the content of the firmware updates 2.23.14 and 2.27.16 and that’s what I found:6 new files142 files identical125 files differentFpga*.bin files identicalOS version 15.4.12->15.4.14new strings related to screeningnew camtype Z3 in many .asp filesnew directory system\services.d\factory.d containingdcf.rscfiles_count_limit.rscnew files:system\web\services\Focus\LensDist.aspsystem\sensor.d\ML2.dllsystem\web\images\Fenix.jpgsystem\web\images\Z3_Astra.jpgTo me this looks mainly like an OS update and the introduction of the new camtype. Is there a specific file, which could hint to more security in the new version?

author: Userli
author_rank: Regular Contributor
timestamp: February 09, 2022, 09:57:58 am
content: I checked all the DLLs and didn't find any alarming changes. So I gave it a try and updated to 2.27.16, which worked without any problems. The resolution is still 320x240 and the config files unchanged.

author: Userli
author_rank: Regular Contributor
timestamp: February 09, 2022, 10:11:53 am
content: As a proof an interesting result of emissivity: fabric with black printing.I also copied the medical.pal from the model 2 firmware and added the corresponding translation into the English strings file (strings.en.xml). It now appears as an option. (No real application but I think it was mentioned here somewhere, that it's not possible to add another pallet)There are two hidden items in the service menu, which you can enable in usermenu.inc: WebCamera and Real Time Video

author: jjdemu
author_rank: Newbie
timestamp: February 20, 2022, 08:41:25 am
content: Hi allI recently got a flir e40serial: 490xxxxxpart number: 49001-2001firmware: 2.19.10model: E40without MSXI have tried changing the resolution to 320 and setting noise to 0 in the conf file, but when I reset the camera I lose the cross-hairs. I used crc01 and added that to my conf file. I replace the file back to the original and cross hairs are back. So I am a little lost if someone could chime in on what I must have gone wrong. Still on the fence if I want to upgrade to 2.27.16.Update 1Got the flir 2.23.14 update from Fraser, so updating and will be doing a new backup of files and will report back.update 2still have no cross hairs. Nm think I see what I did wrong and read more.update 3all working greatThank you all for a great forum and the wealth of information I have found here.

author: Userli
author_rank: Regular Contributor
timestamp: February 23, 2022, 08:01:40 pm
content: I developed a web page to be added to the system web pages, to browse and edit the resource tree. The resource tree is a data container/hub centralizing all system parameters. The tree is huge and much of the information is quite cryptic. It still provides a good insight into the camera internals. The edit function will most likely not allow for magic changes but the standard modifications like switching to RNDIS mode or even removing the flir logo on the screen are possible.The installation is quite simple. The attached zip contains the file resources.asp, which needs to be copied to the folder FlashFS\system\web\service\caminfo.Now the the lineCode:menuRow("Resource Tree", "/service/CamInfo/resources.asp", "submenu1", selectedMenu == "mnuCamInfoResources");needs to be added to the file file FlashFS\system\web\service\inc\servicemenu.inc, like in the example file in the attached zip.Finally the functionCode:ResTree.prototype.getResourceType= function( name ){return this.res.GetResourceType(this.expandName(name));}Needs to be added to the file FlashFS\system\web\inc\restree.inc, again like in the example file in the attached zip.I assume by changing the wrong parameters you can brick you camera so use the editing with care and at your own risk.I attach two images showing the browser in action.Happy browsing!

author: Userli
author_rank: Regular Contributor
timestamp: March 03, 2022, 06:42:17 pm
content: I noticed a faint column like structure on the display, which moves with the camera and thus can’t be noise. Looking at some of the pictures posted here, I think to see a similar effect on other cameras.In order to investigate this phenomenon, I took a sequence of 90 images with the dust cap on. I stacked those to remove noise and used autolevel of imagemagick to make it more visible. The resulting structure resembles the effect I noticed before.Quantitatively the effect seems quite small though. I see a change of ~30 which, assuming the full range of two bytes is used, is very few but big enough to be visible.When browsing the resource tree I found background maps referenced (ds120C_we_ap_fi_le_x.bgm) but I don’t find these files on the camera. My guess was that updating those could remove the structure, which most likely developed with age.Did anybody ever look into this?

author: Fraser
author_rank: Super Contributor
timestamp: March 03, 2022, 07:28:31 pm
content: This is column noise and is present on most microbolometer based systems. The columns are read out and small differences in the integrator capacitors produce the differentials that you are seeing.Fraser

author: Bill W
author_rank: Super Contributor
timestamp: March 04, 2022, 01:18:21 pm
content: The term 'noise' may be unhelpful, as 'noise' often gets interpreted as a variable you can average out.It is column fixed pattern, and the source is as you say the readout through the slightly differently performing column amplifiers.The vast majority of the variation is calibrated out, but it is a case of (big number) - (similar calibration big number) and (big number) is highly temperature variable.The remainder is (mostly) sorted at the shutter calibration but between shutters there is no fix, likewise when viewing conditions (ie amplifier signal levels and temperature) are different to the shutter in place condition.One reason most cameras will not let span go under 2°C, unless they are so noisy they can hide the fixed pattern anywayBill

author: Userli
author_rank: Regular Contributor
timestamp: March 23, 2022, 07:48:41 am
content: I started to analyze this problem more in detail. Noise is indeed a random perturbation of the signal and as such can be averaged out. This is not to be confused with systematic effects, which can't.I started again with a sequence of 90 images with dust cap on. You see the grey scaled version of the image with autoleveling to emphasize the effect at the top. Below you find the distribution of the amplitude of the pixel value variation per pixel. This is the noise level which shows a nice peek (the noise generator is switched off). The system noise is roughly 40 pixel units, which is significant as we will see later.The plot below shows the distribution of the averaged pixel values. Here you would expect a sharp line at the dust cup temperature.We can see a random variation around the peek, which makes me wonder if the initial calibration has been done with active noise generator (maybe due to restrictions for civil use?).The tail to the right must be a drift of some kind most likely due to aging or burn in. This becomes handy as we see later.The mean pixel values per image column on the top right show the extend of the column effect and that the drift is regional.In the next post I'll look into the gains.

author: Userli
author_rank: Regular Contributor
timestamp: March 23, 2022, 09:12:53 am
content: I now looked at the content of the file ds120C_we_ap_fi_le_static.gan, which I assume to be the gains of the amplifiers per pixel.The grey scale image on the top is not very revealing, most probably due to outliers for bad pixels. I should exclude those.The distribution of gain values in the middle is difficult to predict. This mostly reflects hardware production variations, which might be random or systematic.The scatter plot on the bottom shows mean pixel values against gains. You would expect a horizontal band with the width of the generated noise (see last post) around a line like the one in green. We can see clearly an additional band in the red square. The latter represents most likely a hardware drift over time. As mentioned already his could be burn in or aging. The interesting part is that, assuming this is a gradual process, this band reflects the function we need to use to compensate for the drift. In visual terms, we need to move those points back to the baseline along the diagonal band.I fitted a line through this band (visually it's most like a higher order function but let's stay simple for the time being) and found a slope of 0.0119 . This is the ratio delta pixel values over delta gains. Using this ration I now (visually speaking) moved all points to the green line and saved the corrected gains to a new gains file. It seems that this file is only being read at camera startup and it's not sufficient to just restart the application with the corresponding batch file. If somebody knows an easier way to do this, I'd be happy to learn about it.I'll show the results in the next post.

author: Userli
author_rank: Regular Contributor
timestamp: March 23, 2022, 09:37:10 am
content: We see that the column structure is still visible but the regional drift is mostly gone. The "U" shape might be due to the linear correction, whilst at least a second order correction would most likely be required.However, the regional effects are now in size close to the column effects. The plot of pixel values against gains shows a single band without the drift.Quantitatively we are in the range of the noise and in principle it doesn't make sense to continue. It would be nice, though, to do a beautification and level out the column noise, to remove the visible effects, which now are already much less visible than before.To be continued...P.S.: I also looked at the coarse map (3rd image), which I assume to be the pedestals. They don't show any remarkable structure, so I assume it's save to ignore them.

author: _Wim_
author_rank: Super Contributor
timestamp: March 23, 2022, 07:20:47 pm
content: Quote from: Userli on March 23, 2022, 09:37:10 amVery interesting. For further testing you should also make one of these:https://www.eevblog.com/forum/thermal-imaging/anyone-have-an-estimated-emissivity-for-the-ivac-9000-radiators/msg3510108/#msg3510108Cheap black body to play with...

author: Userli
author_rank: Regular Contributor
timestamp: March 27, 2022, 08:35:27 am
content: Indeed I thought about buying or building a bb reference. It's very interesting what Fraser and you have done.To me, however, it's important to have a geometrical homogeneous measurement, more than a precise one. I will rather look for temperature differences than for absolute temperatures.Most of the bb sources are too small to cover the whole field of view of the camera and larger ones are quite costly. Having said that, I would definitely be interested to play with such an IVAC unit but whilst they're sold cheap, I'm afraid of the costs of importing an IVAC to Europe.

author: _Wim_
author_rank: Super Contributor
timestamp: March 27, 2022, 09:33:37 am
content: Quote from: Userli on March 27, 2022, 08:35:27 amTotal cost with import and shipping to Europe will probably be around 70€ (an offer of around 30$ for per unit will probably be accepted):https://www.ebay.de/itm/203833704424?epid=6034823438&hash=item2f756f7fe8:g:GuIAAOSwbVViDErSThey do appear to be geometrical quite homogeneous if you look at these test shots I made:https://www.eevblog.com/forum/thermal-imaging/anyone-have-an-estimated-emissivity-for-the-ivac-9000-radiators/msg3504490/#msg3504490Large dedicated BB options are probably slightly better, but price is at least an order of magnitude higher.

author: Userli
author_rank: Regular Contributor
timestamp: March 27, 2022, 06:06:35 pm
content: QuoteThanks for the info! I gave it a try and accepted the counter offer at 40$. The total costs are roughly 80€ delivered. I'll read again your threads in more detail to see what I'll need to do to the device...On another note:I just saw that Flir tools indicate a frame rate of 30fps in the live view, whereas the Exx models should have 60fps. Do I miss a setting somewhere?

author: _Wim_
author_rank: Super Contributor
timestamp: March 27, 2022, 06:35:17 pm
content: Quote from: Userli on March 27, 2022, 06:06:35 pmGreat! If any questions, please feel free to ask (maybe best in the thread about the BB, so the info remains in a single thread).Quote from: Userli on March 27, 2022, 06:06:35 pmGood question, never noticed that before. I presume this is related to the usb speed to transfer the images. Maybe it records only in 60fps on the camera itself. I do not know of any settings to change it in flir tools, but as I did not realize before, have not looked hard also

author: cuda12
author_rank: Regular Contributor
timestamp: April 04, 2022, 02:05:32 pm
content: My e30 /e60 is 30 fps on flir tools and even on a vid recorded just on the camera (no usb cable) and then transferred and watched on a pc it is still always 30 fps. In flir tools you can choose a lower fps but I have never found a higher choice. Just lived with it as it is actually pretty good.

author: cuda12
author_rank: Regular Contributor
timestamp: April 04, 2022, 10:47:58 pm
content: Well I had to play around with it because I can't believe I never have in the past worried about it. I figured (wrong) that it must drop to 30 fps when under great demand like video and thermal at the same time so I tried it just as a regular video camera then as just a fusion camera, then picture in picture with the same result it drops to 7fps in all those modes except actually using thermal then it goes back up to 30 fps.

author: Steve99
author_rank: Newbie
timestamp: May 28, 2022, 01:53:46 pm
content: Hi, I'm about to upgrade my E40 serial 490xxxxx but I can't find a working link to the 2.23.14 Firmware.I currently have an old 1.43.23 version installed. My camera has the separate arrow keys buttons and no MSX, it also has both wifi and bluetooth.Does anybody got a working link to the 2.23.14 Firmware?Thanks

author: Fraser
author_rank: Super Contributor
timestamp: May 28, 2022, 03:42:40 pm
content: I have sent you a link to the firmware on my Google Drive via PMFraser

author: sbvr4
author_rank: Contributor
timestamp: September 09, 2022, 03:25:31 am
content: Hello,I recently purchased a E30bx. It's an old version without MSX. Unfortunately, its running firmware version 2.27.15. I've really only seen hacks which address fw version 2.23.14 or earlier.Does anyone know if the E60 resolution upgrade and possibly added menus can be done on fw 2.27.15? Is it possible to revert to the older fw 2.23.14 if not?Any help is greatly appreciated.Thank you.

author: Fraser
author_rank: Super Contributor
timestamp: September 09, 2022, 09:56:44 am
content: From reports that I have received, FW2.27 does permit the upgrade.You will not break the camera by trying the upgrade. Make sure you take a backup first though !I normally do not recommend moving up to FW 2.27 because FLIR has a habit of removing useful engineering functionality, such as the Service menu. As you are already on 2.27 you are not risking anything. 2.27 May still have all the features and functionality of 2.23.Reversion to an earlier firmware may be possible if you make changes to the update package to fool the camera into thinking it is newer than 2.27….for example 2.28.Fraser

author: sbvr4
author_rank: Contributor
timestamp: September 10, 2022, 03:38:43 pm
content: Thanks Fraser! I can confirm upgrading while on fw 2.27 was no problem thanks you and others on this forum. Upgrade only took a couple mins once I had all the files modified and crc recalculated. The results are definitely worth the time of reading all the related threads. Thank you for all your research and willingness to share what you've learned with the community.Best regards,Sean

author: JazzeyG
author_rank: Contributor
timestamp: December 13, 2022, 03:47:12 pm
content: Hi, I've recently purchased a E40bx and wanted to upgrade. Could anyone send me a link for the upgrade files?Model: E40bx 1.3Software: 4.13.0

author: cuda12
author_rank: Regular Contributor
timestamp: December 14, 2022, 02:50:33 pm
content: Firmware upgrade is 5.30 and available at Flir after you register, but 4.13 was a pretty decent firmware and unless you have a reason to upgrade it is really not worth it. If by upgrade you meant hack files for higher resolution etc. you probably need to read the thread at the beginning and remember there are 2 different models MK1 and MK2 and follow the instructions for the MK2. If you did use another persons files they would not work right as you have to change your own files to have it really work right.

author: JazzeyG
author_rank: Contributor
timestamp: December 15, 2022, 01:12:03 pm
content: Hi, thanks for the response. Apologies should have said looking to hack the files for the extra features.I'll have a look through the thread properly, thanks.

author: kaz911
author_rank: Super Contributor
timestamp: December 21, 2022, 09:21:49 am
content: Hi,my E40 mkII have developed what seems like a "loose" connection - causing the imager to create funny images occasionally. A gentle "tap" can sometimes get it back.Does anyone have a "teardown guide" or can provide some hints on how to best open up the beast? Flir wants £400+VAT for "initial ass-essment"../k

author: JazzeyG
author_rank: Contributor
timestamp: January 08, 2023, 01:22:30 am
content: Hi, have had a read through this thread and think I'm ready to give it a go!Anybody have a link for the latest MK2 hack files? All the old links previously posted seem to be dead

author: cuda12
author_rank: Regular Contributor
timestamp: January 11, 2023, 04:09:53 am
content: Here is a link to a file on the forum.https://www.eevblog.com/forum/thermal-imaging/flir-e4-thermal-imaging-camera-teardown/?action=dlattach;attach=74656You only need the crc01.exe file (I did not see just that file for download so use this one to get it)You will place this in a folder you make and will have a copy of the cfg file from your camera in the same folder, after you change the 2 lines (resolution and noise) you will run the crc01.exe on that saved cfg file and then enter the number it generates to the bottom of that same cfg file then upload it to the camera. So the file you will get from the download and the cfg file you already have is all you need. But please make a backup and place that in a different folder before you begin.

author: JazzeyG
author_rank: Contributor
timestamp: January 11, 2023, 10:17:02 am
content: Thank you very much for your reply, I will give that a try later today and let you know how I get on!

author: defplayr
author_rank: Contributor
timestamp: January 22, 2023, 05:32:14 pm
content: Long time lurker, new poster.This is what the internet is for!Just bought an old E40. My unit has a strange feature, which I've not seen mentioned in any other post. I wonder if anyone has seen this before or has any comments?If I bring up the unit's 'hidden menu' (' settings/i ' selected, then hold right arrow), amongst the pages is a 'Resource browser' entry...Clicking on that brings up a GUI, where you can navigate, and drill down to, various settings/options. If the setting has a numerical value, you are offered a spinning wheel of possible values, and if a text value, you are offered a keyboard. You can edit the value, but the change does not persist when you return out of the wheel/keyboard...UNLESS... If you click on the pink locked box image, a gallery of faces is presented. The changed value will persist* if I choose it while a face is shown. There are a few faces, all of whom have their eyes disguised. Painting with a very broad brush, I would not be the most shocked in the world if, judging by their appearance, these are the faces of software devs.(* It appears that sometimes a value will only save with a particular face, occasionally not at all.)The changed values persist over a cold boot and can easily bugger up the unit (don't ask).I've only had the unit a short time, so to date, I've only upped the I/R resolution and lost the noise, by the usual method of changing conf.cfg, and also put my contact details on the boot up logo. For info, my unit records I/R video, streams whatever is being displayed on the screen to FLIR Tools on WiFi (stream or signal on USB), and has the service menu.

author: cuda12
author_rank: Regular Contributor
timestamp: January 22, 2023, 09:20:33 pm
content: I have had a few MK-1 and MK-II series with all firmware versions and have never seen that. What series camera? And what firmware version?

author: defplayr
author_rank: Contributor
timestamp: January 22, 2023, 09:42:17 pm
content: >cuda12It's second hand, the seller didn't know the history of it, and I'm not an expert. The last photo in my post gives bits and pieces about it... does it answer your q's? I can look at whatever files on the unit you need, if you point me in the right direction. The connector covers are missing (snapped off), but I think they should look like the attached diagram... also it does not have MSX, which makes me believe it's a MK1?This 'Resource browser' does seem very weird... the images are low res and a bit amateurish but it does the job and with humour (typical devs!).

author: cuda12
author_rank: Regular Contributor
timestamp: January 23, 2023, 02:15:19 pm
content: Yes first version MK1 no MMX, looks to be a very early unit maybe that is why the extra entries in the menu. Should have a basic entry for camera information in your menu. The podkit entry in the picture is a very low number so it would be good to confirm in the menu the firmware version.

author: defplayr
author_rank: Contributor
timestamp: January 23, 2023, 03:59:17 pm
content: >cuda12This one?

author: cuda12
author_rank: Regular Contributor
timestamp: January 23, 2023, 07:28:48 pm
content: Yep that confirms 1.24.16! Wow that must be why the extra menu items.

author: JazzeyG
author_rank: Contributor
timestamp: February 06, 2023, 03:06:00 pm
content: Upgraded my unit's resolution, all working good. Thanks again for the help.Just wondering is there a way to get the full temperature range on my E40bx? I'll try again today but not been able to get into the service menu. I am on firmware 5.3.0

author: Fraser
author_rank: Super Contributor
timestamp: February 06, 2023, 05:17:12 pm
content: If you are on firmware 5.x.x you do not have the required files for the service menu in your camera and they cannot easily be added to recreate a working Service Menu. Service Menu access does permit enabling of additional temperature ranges for which a calibration table exists but sadly that is not possible in your case.Fraser

author: JazzeyG
author_rank: Contributor
timestamp: February 07, 2023, 07:14:22 am
content: Hi Fraser, many thanks for your response. Is there anyway of downgrading in order to get the service menu?If it is possible which version would I need to downgrade to?

author: Fraser
author_rank: Super Contributor
timestamp: February 07, 2023, 07:57:30 am
content: The straight answer is that I do not know for sure. From memory it is possible on the older firmware updates to change the version so that the FLIR updater thinks it is installing a newer firmware release when in fact it is installing an old one. The problem in your situation is that you have the very recent firmware release that may contain countermeasures to such an approach. There is also the issue of which hardware you have. From your firmware version I am guessing you have a Mk2 with MSX. If it is a Mk1 you can try to install the Mk1 V1.23 / V1.24 firmware that still contains the Service Menu. If you have a Mk2 camera then that firmware is not designed for the platform and trouble could occur ! If your camera has MSX, it is a MK2. From memory, none of the Mk2 camera firmware releases contain a functional service menu.I regret I cannot remember how to change the firmware update ID to fool the firmware loader but it should be buried somewhere in the FLIR E4 thread as this method was used during E4 modifications.Fraser

author: JazzeyG
author_rank: Contributor
timestamp: February 07, 2023, 08:42:45 am
content: Hi Fraser, yes I have the MK2 MSX model with model number starting 645.I will have a look through the other threads and see if anyone with my model has managed to get the higher temperature range features unlocked. I do have an option for temperature range on the device but it doesn't let me select anything When I go into the option it just has an arrow at the top and bottom but I can't actually select anything, I've attached a photo to this post.Thanks again for your help, I suppose I don't really need the higher temperature range but knowing the hardware is capable of supporting this I have an urge to unlock it lol.

author: cuda12
author_rank: Regular Contributor
timestamp: February 07, 2023, 11:15:11 pm
content: Here is the master firmware file listed on the forum about page 15https://drive.google.com/open?id=1zHZE84IzDyBvlQyGhviU6fXpa7Gbx9S8it has 3.12 firmware so that you can enable the service menu on the newer MKII MSX cameras. It is real easy to go back and forth I do it all the time between 3.12.7 and 5.20All you do is put both of them on your SD card (example) 413autoload.fif and 520autoload.fif then when you want to go to 413 simply rename the file autoload.fif and reboot the camera it will install 413. Then remove the sd card and name it back to 413autoload.fif so that it doesn't try to update everytime you reboot the camera. And so I run on 5.20 and then go backwards to 3.12 when I need the service menu.

author: JazzeyG
author_rank: Contributor
timestamp: February 07, 2023, 11:18:40 pm
content: Hi cuda12, thank you so much for your response. I'll give that a go tomorrow.When you downgrade to 3.12, if I enable the higher range and then upgrade back to say 5.2.0 does it reset the temp range & resolution settings?

author: cuda12
author_rank: Regular Contributor
timestamp: February 07, 2023, 11:33:17 pm
content: nope the changes carry over to the firmware upgrade. Sometimes everything falls back to default settings and you need to put in your wireless password etc. and sometimes it will carry over also. Just make sure the battery is charged and or it is plugged in to the charger. It takes 15 minutes or so.

author: JazzeyG
author_rank: Contributor
timestamp: February 07, 2023, 11:38:43 pm
content: Thanks again, I’ll give it a go tomorrow.Also just wondering any reason you stick to firmware 5.2.0 over 5.3.0?

author: cuda12
author_rank: Regular Contributor
timestamp: February 08, 2023, 01:02:27 am
content: I got used to saying 5.20 but I am actually using 5.30

author: JazzeyG
author_rank: Contributor
timestamp: February 08, 2023, 07:46:34 pm
content: Quote from: cuda12 on February 07, 2023, 11:15:11 pmTried doing this and the camera just boots up as normal, it doesn't update the firmware. I have tried with and without the eFLIRInstall.exe file in the SD card. I am putting all the files in the root folder of the SD card. I am naming the E2qtcomb_v3.12.7.fif file to autoload.fifI have tried changing to MSD mode and various other modes but the firmware doesn't seem to update. When you say reboot the device, I am taking the battery out. Leaving for a few seconds and then starting the device up. Have tried that and have tried holding the power button down for 10 seconds, then pressing the power button again.Just wondering if I'm doing something wrong?

author: cuda12
author_rank: Regular Contributor
timestamp: February 08, 2023, 09:59:32 pm
content: That is how you do it? The usb cable is not connected right? That will disable boot from SD card. The only time I have had it not work is when I accidentally named the file autorun.fif In each firmware file is an instruction file that says the same thing but maybe I have forgoten something so give it a read. In the old days you actually had to run the flirinstall.exe file in windows 7 but modern windows os just load on the SD card. I just read those instructions and that is how I used to do it with flir tools then I read about just using the sd card and that is how I have been doing it but I just checked and I have the eflirinstall.exe on the sd card as well. I am going to remove it and see if my camera still updates just to see.

author: JazzeyG
author_rank: Contributor
timestamp: February 08, 2023, 10:23:15 pm
content: Just tried again, this time I held the power button down when I switched the device on and it seems to have worked! I have no idea if that is how you're suppose to do it or I just got lucky lol.Is installing right now so will let you know how I get on!

author: cuda12
author_rank: Regular Contributor
timestamp: February 08, 2023, 10:32:27 pm
content: I just downgraded to 3.12 just for fun now I am going back to 5.30. I don't hold the power button just let it boot up and go. I hope it works for you but be very careful in the service menu if you unlock the eprom And yes EflirInstall.exe had to be on the sd card also.

author: JazzeyG
author_rank: Contributor
timestamp: February 08, 2023, 11:12:57 pm
content: I've managed to successfully downgrade and have enabled the 0-650 range! Thanks again for all your help.I won't touch anything else in the service menu until I've had a look through past threads on here! Thanks for the heads up.

author: cuda12
author_rank: Regular Contributor
timestamp: February 08, 2023, 11:37:39 pm
content: right on!

author: Fraser
author_rank: Super Contributor
timestamp: February 09, 2023, 07:30:13 am
content: Excellent news. I was not aware that such was possible on a Mk2Fraser

author: JazzeyG
author_rank: Contributor
timestamp: February 09, 2023, 07:39:59 am
content: Had a quick play with it last night, my -20 - -120 range was recently calibrated so it looks like the 0-650 is off by 2-3 degrees. Though my tests are very crude to put it lightly!Also noted one temp range went all the way up to 1200C but says “NO RBF” if I try to enable. From reading up here I guess that means there is no calibration file for this range.Does the sensor support that range and would there be anyone I could send the device to in the UK who could calibrate the two additional ranges and update the relevant calibration files? I’m just wary as I have tampered with files whether these calibration companies would even carry this out!

author: in.Vitro
author_rank: Regular Contributor
timestamp: February 27, 2023, 04:26:46 pm
content: Quote from: tomas123 on July 23, 2015, 02:38:34 pmQuote from: Chanc3 on July 23, 2015, 02:49:19 pmCan some one explain me how to turn of the NUC during Video recorings?

author: defplayr
author_rank: Contributor
timestamp: March 01, 2023, 11:02:47 pm
content: >in.VitroIf you have presets working, you can use this...https://www.eevblog.com/forum/thermal-imaging/a-method-to-change-system-settings-through-presets-**working**/msg4683578/#msg4683578

author: in.Vitro
author_rank: Regular Contributor
timestamp: March 20, 2023, 04:41:21 am
content: I've tried it. Several hours... but somehow, the NUC is still active while recording. :/I posted my issue here a while ago and the glitches still exist:https://www.eevblog.com/forum/thermal-imaging/flir-e40-(e60-upgrade)-several-issues/msg4558438/#msg4558438Allegedly the guy, where I bought the camera (its kinda like craigslist) in the first place, he was so kind to "updated the firmware" (which is not common in germany) ,and he said he had no issues while the video recording but the glitches still apear.Here in Germany, when you buy anything from this plattform you are stuck on your own...because you buy it privatley!After 3-4 Months I cant go back to him to fix the camera because I bought the camera between a regular citizen... since he provided me with a kinda "nice" solution to buy a FLIR 53 for the exchange for the E40/E60...It still sucks because my main thing is to record videos (I dont care about radiometric things and thats) and the main issue is the NUC/FFC while recording video. ugh!

author: jumbo
author_rank: Contributor
timestamp: May 26, 2023, 05:49:45 pm
content: Hello,I bought e50bx and I would like to change temperature range. I made it 6-8years ago in e30bx and resolution and menu hack as you guys mentioned in other post.But now I have strange situation. I made windows 7 on virtual machine (I am using win11 usually) and I connect to service menu but I cant open page "http://192.168.0.2/service/index.asp". So its imposibble to change range.I have a question, do I need to change firmware to older version for changing temperature range? is it save? whith number of software will be the best?I found pack with few firmwares but I think I have different in my camera, so I am not shure that is god idea.

author: jumbo
author_rank: Contributor
timestamp: May 28, 2023, 05:57:45 pm
content: So I downgrade camera by "flir_exx_pn645_pn646_v3.12.7_update_pack".1. I installed 2GB SD CARD with this unpack filr (its important, SD card with 32GB dosnt work)2. Turned on and hold on/off button until boot menu3. Waited 30 minutes to downgardeIs it possible to have 1200.C without RBF? can I use RBF from 0-650?How to upgrade resolutin, eliminate nois etc. in this camera? the production is new, menu is differen (like in e96)

author: robys
author_rank: Newbie
timestamp: November 03, 2023, 10:05:47 am
content: Dear All,thank you to this forum, I succeed to update my E40 1.0 by resolution up and noise down; my firmware is 5.3.0 (latest) and SN is 645xxx (my camera is with MSX).To do so, I was only working on config.cfg file inside folder FlashFS\system\appcore.d\config.d;I did a full backup by Wi-Fi connection, I changed the lines in the file about resolution and noise, according to post information, I recalculated new CRC with posted CRC01.exe and everything is working fine.Considering nice success at first time, I'd like to add some more function which is specifically for E60 (I think) and described in the owner manual; like, for example, condensation or insulation alarm or several other which seems miss in my E40.Is there any possibility to do it just again working on my config file, or I need some additional file change or other things?I saw some post about fully replacing original config file with E60 config file (of course updating SN and CRC), but I'm not sure I can do with my firmware and camera version and cannot understand clearly if additional step are necessary.May please someone help me?thank you again for all effort on pushing our thermocamera to its real technical limit!

author: cuda12
author_rank: Regular Contributor
timestamp: November 05, 2023, 09:38:02 pm
content: When you read this thread and any other on the Exx series always remember that there are MK1 and MKII (msx newer front buttons) Most of the threads are about the MK1 and those extra options are not real easy to make work on the MKII because even though you enable them in the config.ini the gui is not present to be a menu item. But you can go down the same config file you already modified and turn things on and off (usually just a few at a time so you can go back if something really bad happens) Then use the cell phone app flir tools and make a connection to your phone. A lot of the times the app will have things like medical buttons etc. that you can enable on the phone and will happen in real time on your camera. But they do not stay upon reboot. I had a MK1 with almost everything enabled and it was different but not really anything most people need, so just enjoy the MSX feature.

author: robys
author_rank: Newbie
timestamp: November 07, 2023, 09:17:30 am
content: Hello all, just quick upd of work in progress on config.cfg file.I succeed to also implement insulation alert, zoom x8 and some other function, just by working on "false" -> "true" and related parameter line.I think enough satisfied now..so, at least if not discovering some other interesting (to me) "hidden" feature, I will stop here my update.thank you again for forum support on suggesting way to improve E40.regards

author: maksym
author_rank: Newbie
timestamp: December 13, 2023, 07:03:36 pm
content: A happy new Exx MKII owner here. I wonder if anyone owns an optional 15 degree lens - does it make any sense for PCB work? The specs say it is 1.7x magnification, but the minimum focus distance is listed as 1.2 meters, which probably makes it pointless for close-up inspections.

author: azur
author_rank: Newbie
timestamp: January 03, 2025, 12:50:24 pm
content: Quote from: kaz911 on September 18, 2020, 12:45:26 pmGood day!Do you still have your own E50bx + 10mm (45deg) ?

author: EE-digger
author_rank: Frequent Contributor
timestamp: March 08, 2025, 05:22:11 pm
content: The part number for the manual for the E40, 50, 60 manual isT559845. TheT559845manual also has a very detailed table of features and specs across these models. It is not an Exx manual. The "Exx" manual, commonly available, includes functions not in these models, like auto focus.

author: matthieu.e
author_rank: Regular Contributor
timestamp: September 29, 2025, 03:07:45 pm
content: Hi,Do you know, what line I need to modify to replace the « E40 » camera name in the info menu to « E60 » ?Same question in the windows flir app. Can my E40 camera be detected as a E60 camera ?

author: Fraser
author_rank: Super Contributor
timestamp: September 29, 2025, 03:12:37 pm
content: Model number is stored in the eeprom that is accessed via the service menu.It is purely cosmetic and has no effect on camera behaviour.

author: matthieu.e
author_rank: Regular Contributor
timestamp: September 29, 2025, 04:04:07 pm
content: Hi Fraser,Thank you ! So I can’t update the number in the conf file and I need to modify the EEPROM directly on the circuit ?

author: Fraser
author_rank: Super Contributor
timestamp: September 29, 2025, 04:18:53 pm
content: CorrectThe eeprom contents are editable in the cameras service menu after entering the required password.

author: matthieu.e
author_rank: Regular Contributor
timestamp: September 29, 2025, 04:43:27 pm
content: I have a E40 mk2 can explain you me how to access to the service menu and share the password ?Is the service menu the same as the one we have to go to change the usb mode ? Or is it only for accessible on the mk1 version ?

author: Fraser
author_rank: Super Contributor
timestamp: September 29, 2025, 07:59:30 pm
content: EEPROM access password: 1235The rest is detailed in posts on this forum. Use search for Ex, E4 and E40 to find out about eeprom access.

author: matthieu.e
author_rank: Regular Contributor
timestamp: October 02, 2025, 12:44:49 pm
content: Thank you, I will do the research.

author: matthieu.e
author_rank: Regular Contributor
timestamp: October 02, 2025, 01:03:40 pm
content: Hi Fraser,Do you refer to this menu to update the camera number ?(attached picture, not my camera).If yes I think it is only editable on the mk1 version. My E40 mk2 do not have this menu. Or perhaps I need to downgrade the firmware ?

author: Fraser
author_rank: Super Contributor
timestamp: October 02, 2025, 04:46:55 pm
content: Yes that is the correct menu and it is present on my E40 Mk1.Some Mk2 owners have reported that they have the Service Menu in their camera. It would appear that some do and some do notI do not know whether a firmware downgrade would provide the service menu for your camera.Fraser

author: RRtheone
author_rank: Contributor
timestamp: October 08, 2025, 07:41:40 am
content: Quote from: matthieu.e on October 02, 2025, 01:03:40 pmYou need 3.18 firmware (can be found in this forum). I have a E40 mk2 and get this menu after downgrading.