Author Topic: Flir E40 Upgrade & Configuration (Read 186434 times)

ElectroTuna · « **on:** November 20, 2014, 04:39:47 am »

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!

Pinkus · « **Reply #1 on:** November 20, 2014, 08:08:26 am »

Edit: Section removed as pointed to the wrong thread

You 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.

tomas123 · « **Reply #2 on:** November 20, 2014, 11:13:47 am »

there is no point-to-click hack for the Exx

the first post from mike
https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/

referenced
https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg342072/#msg342072

and go to 19 "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 it

a 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.

ElectroTuna · « **Reply #3 on:** November 20, 2014, 03:53:35 pm »

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.

ElectroTuna · « **Reply #4 on:** November 30, 2014, 03:42:31 am »

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!

ElectroTuna · « **Reply #5 on:** December 01, 2014, 05:01:44 am »

Is there anyone out there who can help?

tomas123 · « **Reply #6 on:** December 01, 2014, 10:25:17 am »

Quote from: tomas123 on November 20, 2014, 11:13:47 am

I will give no further reply in this thread.

do 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

mikeselectricstuff · « **Reply #7 on:** December 01, 2014, 10:32:02 am »

The changes are just a few parameters - look at the E4 stuff, most of it will be the same.

ElectroTuna · « **Reply #8 on:** December 02, 2014, 02:13:44 am »

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 edit NAME userconf VERSION E40 1.0 DATE 16-Oct-2013 # format: FILE <filename> <size> <CRC32> # or: FILE <filename> undefined FILE flashfs\system\appcore.d\config.d\conf.cfg undefined FILE flashfs\system\appcore.d\factory.d\adjust.rsc 113 568770501 FILE flashfs\system\appcore.d\factory.d\intensity.rsc 145 2456191835 FILE flashfs\system\appcore.d\factory.d\laser.rsc 143 2190380121 FILE flashfs\system\appcore.d\factory.d\palette.rsc 268 767855916 FILE flashfs\system\appcore.d\factory.d\pathimages.rsc 139 4242760020 FILE flashfs\system\appcore.d\factory.d\power.rsc 333 1829598383 FILE flashfs\system\appcore.d\factory.d\time.rsc 128 3305292736 FILE flashfs\system\appcore.d\factory.d\usb.rsc 114 2394224369 FILE flashfs\system\kits.d\confkit.rev undefined FILE flashfs\system\service\appcore.d\config.d\conf.cfg undefined FILE flashfs\system\service\appcore.d\factory.d\bw.rsc 258 4267495318 FILE flashfs\system\service\appcore.d\factory.d\rndis.rsc 84 1796347983 FILE flashfs\system\services.d\config.d\conf.cfg undefined FILE flashfs\system\services.d\factory.d\dcim.rsc 119 4038415784 FILE flashfs\system\services.d\factory.d\no_wzctool.rsc 60 2262041015 FILE flashfs\system\ui.d\config.d\conf.cfg undefined

But 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 edit NAME userconf VERSION E60 0.10 DATE 28-Apr-2011 # format: FILE <filename> <size> <CRC32> # or: FILE <filename> undefined FILE \flashfs\system\appcore.d\config.d\conf.cfg undefined FILE \flashfs\system\appcore.d\factory.d\adjust.rsc 113 568770501 FILE \flashfs\system\appcore.d\factory.d\intensity.rsc 145 2456191835 FILE \flashfs\system\appcore.d\factory.d\laser.rsc 143 2190380121 FILE \flashfs\system\appcore.d\factory.d\palette.rsc 267 3727757887 FILE \flashfs\system\appcore.d\factory.d\power.rsc 333 1829598383 FILE \flashfs\system\appcore.d\factory.d\time.rsc 128 3305292736 FILE \flashfs\system\appcore.d\factory.d\usb.rsc 114 195315524 FILE \flashfs\system\arctic.pal 2037 747452631 FILE \flashfs\system\bw.pal 3192 1681767566 FILE \flashfs\system\iron.pal 3112 2395977639 FILE \flashfs\system\kits.d\confkit.rev undefined FILE \flashfs\system\lava.pal 3645 3268586420 FILE \flashfs\system\rainbow.pal 3095 986361025 FILE \flashfs\system\rainhc.pal 3081 336971817 FILE \flashfs\system\service\appcore.d\config.d\conf.cfg undefined FILE \flashfs\system\service\appcore.d\factory.d\bw.rsc 258 4267495318 FILE \flashfs\system\service\appcore.d\factory.d\rndis.rsc 84 1796347983 FILE \flashfs\system\services.d\config.d\conf.cfg undefined FILE \flashfs\system\services.d\factory.d\dcim.rsc 119 4038415784 FILE \flashfs\system\services.d\factory.d\no_wzctool.rsc 60 2262041015 FILE \flashfs\system\ui.d\config.d\conf.cfg undefined FILE \flashfs\system\ui.d\factory.d\320_240.rsc 119 3416508497 FILE \flashfs\system\ui.d\factory.d\autofusion.rsc 260 727783077 FILE \flashfs\system\ui.d\factory.d\pipfusion.rsc 267 532069858 FILE \flashfs\system\ui.d\factory.d\regional.rsc 182 2653315878 FILE \flashfs\system\ui.d\factory.d\save_direct.rsc 139 3237695249 FILE \flashfs\system\ui.d\factory.d\sim_save.rsc 131 1198853717 FILE \flashfs\system\ui.d\factory.d\tfsdir.rsc 312 3781116346

The 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.

ixfd64 · « **Reply #9 on:** December 02, 2014, 02:53:33 am »

This post may be of interest: https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg561266/#msg561266

ElectroTuna · « **Reply #10 on:** December 02, 2014, 03:00:14 am »

Quote from: ixfd64 on December 02, 2014, 02:53:33 am

This post may be of interest: https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg561266/#msg561266

Thanks. 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.

Pinkus · « **Reply #11 on:** December 02, 2014, 08:09:34 am »

Quote from: ElectroTuna on December 02, 2014, 03:00:14 am

Quote from: ixfd64 on December 02, 2014, 02:53:33 am
This post may be of interest: https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg561266/#msg561266

Thanks. 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.

Older 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

ElectroTuna · « **Reply #12 on:** December 02, 2014, 02:21:59 pm »

Quote from: Pinkus on December 02, 2014, 08:09:34 am

Quote from: ElectroTuna on December 02, 2014, 03:00:14 am
Quote from: ixfd64 on December 02, 2014, 02:53:33 am
This post may be of interest: https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg561266/#msg561266

Thanks. 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.
Older 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

Thank 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!

tomas123 · « **Reply #13 on:** December 02, 2014, 03:31:07 pm »

I asked for your 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

Resolution upgrade Flir E30/E40/E50 to E60 and i3/i5 to i7
https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg407320/#msg407320
https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg371680/#msg371680
https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg379141/#msg379141
you must edit your crc01 inside E60 goodies.zip:
https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg338671/#msg338671
a nice history from E30 (without WLAN) to E60 (with WLAN)
https://www.eevblog.com/forum/profile/?area=showposts;u=89829
and https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg561266/#msg561266

tomas123 · « **Reply #14 on:** December 02, 2014, 04:02:24 pm »

as sample the path and critical content for the old E40 (without MSX)

Code: [Select]

>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 pm

Although you can edit the file, a "safer" way is to create a second file - settings files which are alphabetically later will override any earlier ones.
Obviously it's a good idea to make backups of everything first.

Take the config file, edit the settings. Delete the CRC line and run the CRC util to create a new CRC and add it to the file.
Save that file in the same dir as the original, with a higher alphabetic name (case sensitive), e.g. e60.cfg
Then do a hard reboot

firmware 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 Pack
http://support.flir.com/SwDownload/app/RssSWDownload.aspx?ID=127

Code: [Select]

> dir fpg*
06.12.2011  17:23           592.029 fpga.bin
02.02.2012  17:57           797.881 fpga_c4_55.bin
06.12.2011  17:00           798.274 fpga_c55.bin

my 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 Pack
http://support.flir.com/SwDownload/app/RssSWDownload.aspx?ID=194

Code: [Select]

> dir fpg*
28.04.2014  16:26           807.922 fpga_B2CO3.bin
17.12.2013  08:18           805.703 fpga_C4_55.bin

unzip the E2qtcomb_v4.9.0.fif
Flir changed the file structure from \Flashfs\system\*.exe to \FlashBFS\system\*.exe (like the Ex)
but the path for the config file is the same

we 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 fimware

off topic: fgpa of Ex

Quote from: tomas123 on November 21, 2014, 10:41:16 am

current E4 FW from June 12, 2014
http://support.flir.com/SwDownload/app/RssSWDownload.aspx?ID=196
contain two fpga FW
Code: [Select]
07.04.2014 09:26 632.594 fpga.bin 17.12.2013 08:18 606.097 fpga_lepton.bin

ElectroTuna · « **Reply #15 on:** December 03, 2014, 03:41:24 am »

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: [Select]

#
# 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 645XXXXX

FlashFS/system/appcore.d/config.d/conf.cfg

Code: [Select]

#
# 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 645XXXXX

FlashFS/system/ui.d/config.d/conf.cfg

Code: [Select]

#
# 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 645XXXXX

Cheers,

tomas123 · « **Reply #16 on:** December 03, 2014, 08:33:58 am »

Do you have deleted the last line?
I need information about the CRC.

if the last line in
FlashFS/system/appcore.d/config.d/conf.cfg
begins with

Code: [Select]

CRC01 then you must only edit this two lines

Code: [Select]

.caps.config.image.settings.resIR int32 160
..
.caps.config.image.targetNoise.targetNoiseMk int32 55

to

Code: [Select]

.caps.config.image.settings.resIR int32 320
..
.caps.config.image.targetNoise.targetNoiseMk int32 0

and generate a new CRC01

use tutorial and CRC01.exe from Mike

https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg321956/#msg321956

same 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 E40

I 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 telnet

old Exx

Code: [Select]

> rls .registry.caps.config.image.settings
r------------- 0 root   root   <b> downsample                 false
r------------- 0 root   root   <b> enabled                     true
r------------- 0 root   root   <i> resIR                        320 

>rls .caps.config.image.targetNoise
enabled                     true
targetNoiseMk                  0

it's possible, that you have the new pathes like Ex
then you can search in your whole config with

Code: [Select]

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 editor

PS: some users prefer to switch off the noise generator

Code: [Select]

.caps.config.image.targetNoise.enabled bool false

ElectroTuna · « **Reply #17 on:** December 03, 2014, 06:41:01 pm »

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 2

and

.caps.config.ui.fusion.PIP.locked bool true

I 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.

ElectroTuna · « **Reply #18 on:** December 04, 2014, 04:42:27 am »

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,

tomas123 · « **Reply #19 on:** December 04, 2014, 08:56:00 am »

bad pixel:

Quote from: mrflibble on November 10, 2013, 07:46:59 pm

If you want to have a quick look at the dead pixels on yooooouuuur E4, do the following:

Code: [Select]
# check for yourself that I'm not making stuff up. :P rls .image.flow.maps.combGainDeadMap.pixReplace # show dead pixels rset .image.flow.maps.combGainDeadMap.pixReplace false # hide dead pixels again (default) rset .image.flow.maps.combGainDeadMap.pixReplace true

you can see severals clusters

you can simple readout your calibration mapping images
look for *.fff files in thread https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown
like ds250C_we_ap_fi_le_static.fff and ds250C_we_ap_fi_le_static.gan

https://www.google.de/#q=site:eevblog.com%2Fforum%2Ftestgear%2Fflir-e4-thermal-imaging-camera-teardown+ds250C_we_ap_fi_le_static

you can convert this *.fff files with exiftool to png and count your bad pixels

rls helps
see https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/?action=dlattach;attach=84060

Code: [Select]

.calib.detector.deadPixMap: (2)
rw-dr---r---np 0 root   root   <x> ds250C_we_ap_fi_le               
rw-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

ElectroTuna · « **Reply #20 on:** December 04, 2014, 09:15:16 am »

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?

tomas123 · « **Reply #21 on:** December 04, 2014, 09:18:18 am »

do you mean MSX?

the current E40 hardware (late 2013) has MSX on board
http://www.flir.com/uploadedFiles/Thermography_USA/Products/Product_Literature/flir-e-series-datasheet.pdf

you wrote

Quote from: ElectroTuna on November 20, 2014, 04:39:47 am

E40 camera is rather old. I have one unit which I recently got with firmware Version 3.18.0 (E40 1.0).

your E40 ref 1.0 fw 3.18.0 (Late 2013) with MSX
my E40 ref 0.10 fw 2.23.14 (Late 2012) without MSX

I thought, that the last firmware for old E40 hardware (without MSX) is 2.23.14

Quote from: tomas123 on December 02, 2014, 04:02:24 pm

firmware 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 Pack
http://support.flir.com/SwDownload/app/RssSWDownload.aspx?ID=127
my 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 Pack
http://support.flir.com/SwDownload/app/RssSWDownload.aspx?ID=194

for old E40 I activated fusion and pdf in

Code: [Select]

\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 files
best entry is

Code: [Select]

rls -r -l and grep fusion

with rls you can find hidden unknown switches but not all works

here is the corresponding part for the file above (old E40)
\flashfs\system\ui.d\config.d\conf.cfg

Code: [Select]

.ui.caps.config.fusion: (3)
rw--r--------- 0 root   root   <e> PIP                             
r---r--------- 0 root   root   <b> enabled                     true
rw--r--------- 0 root   root   <e> thermal                         

.ui.caps.config.fusion.PIP: (2)
r---r--------- 0 root   root   <b> enabled                     true
r---r--------- 0 root   root   <b> locked                      true

.ui.caps.config.fusion.thermal: (5)
r---r--------- 0 root   root   <b> above                      false
r---r--------- 0 root   root   <b> auto                       false
r---r--------- 0 root   root   <b> below                      false
r---r--------- 0 root   root   <b> enabled                    false
r---r--------- 0 root   root   <b> interval                   false


.ui.caps.config.mode: (5)
r---r--------- 0 root   root   <b> enabled                     true
r---r--------- 0 root   root   <b> panorama                   false
r---r--------- 2 root   root   <b> program                    false
r---r--------- 0 root   root   <b> radiometricVideo           false
r---r--------- 2 root   root   <b> video                       true

.ui.caps.config.report: (2)
r---r--------- 0 root   root   <b> createPdf                  false
r---r--------- 0 root   root   <b> enabled                     true

watch for the syntax of the config files
you must go every step with "entry"!!

tomas123 · « **Reply #22 on:** December 04, 2014, 11:30:19 am »

Quote from: ElectroTuna on December 04, 2014, 04:42:27 am

I got the resolution to work!

Please take the time and write a good tutorial for upgrading the E40 Late 2013 and link it in the first post of this thread

thank you

ElectroTuna · « **Reply #23 on:** December 04, 2014, 06:10:11 pm »

Quote from: tomas123 on December 04, 2014, 11:30:19 am

Quote from: ElectroTuna on December 04, 2014, 04:42:27 am
I got the resolution to work!

Please take the time and write a good tutorial for upgrading the E40 Late 2013 and link it in the first post of this thread

thank you

I will.

By the way, by thermal fusion, I mean like this:

https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg426832/#msg426832

I'll try the changes you suggested above to see if I can get this feature.

tomas123 · « **Reply #24 on:** December 04, 2014, 10:36:45 pm »

in your config files I see

Code: [Select]

.caps.config.image.framegrab.fusion.pip entry
.caps.config.image.framegrab.fusion.pip.enabled bool true

and

Code: [Select]

.caps.config.ui.fusion.PIP entry
.caps.config.ui.fusion.PIP.enabled bool true
.caps.config.ui.fusion.PIP.locked bool true

as entry point for fusion

watch my post above for syntax details

PS: do you really want to use fusion instead of MSX ?

ElectroTuna · « **Reply #25 on:** December 04, 2014, 11:31:52 pm »

Quote from: tomas123 on December 04, 2014, 10:36:45 pm

in your config files I see
...

Thomas, 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).

ElectroTuna · « **Reply #26 on:** December 05, 2014, 07:07:41 am »

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.

tomas123 · « **Reply #27 on:** December 05, 2014, 08:22:46 am »

Quote from: ElectroTuna on December 04, 2014, 11:31:52 pm

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?

Yes you can have both, but do you need thermal fusion (feature junkie)?
simple edit the lines, as described above

Quote from: ElectroTuna on December 05, 2014, 07:07:41 am

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.

please describe exactly, what do you have modified and the result of lost calibration

the is calibration of temperature parameters
for details see my excel sheet here
http://u88.n24.queensu.ca/exiftool/forum/index.php/topic,4898.msg27546.html#msg27546

Quote from: tomas123 on December 04, 2013, 02:23:30 pm

12 edit temperature calibration values of E4 in /FlashFS/system/calib.rsc for improvement of measurement accuracy
https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg348622/#msg348622
https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg348703/#msg348703
the Excel sheet
https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg358979/#msg358979
https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg350457/#msg350457

...and a bad pixel mapping

Fraser · « **Reply #28 on:** December 05, 2014, 12:17:12 pm »

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

tomas123 · « **Reply #29 on:** December 05, 2014, 01:49:07 pm »

Quote from: ElectroTuna on December 05, 2014, 07:07:41 am

Do the calibration image files have some kind of checksum?

alle config-txt-files have checksums

config files uses CRC32

sample in bash

Code: [Select]

a crc32 sample on command line
// count lines
$ wc -l FlashFS/system/calib.rsc
     801 FlashFS/system/calib.rsc

//print last line
$ tail -n1  FlashFS/system/calib.rsc
# CRC32 ef8f7e0e

//calc a new crc32 for 801-1=800 lines
$ crc32 <(head -n 800 FlashFS/system/calib.rsc)
ef8f7e0e

or search crc32 in https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown

tomas123 · « **Reply #30 on:** December 05, 2014, 02:03:35 pm »

Quote from: Aurora on December 05, 2014, 12:17:12 pm

the comments on modifying the bad pixel map is of great interest in case it is needed in the future

Firmware_FlirE4
\FlashFS\system\calib.rsc

Code: [Select]

.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.gan
use exiftool and imagemagick

Code: [Select]

>exiftool ds250C_we_ap_fi_le_static.gan
ExifTool Version Number         : 9.75
File Name                       : ds250C_we_ap_fi_le_static.gan
Directory                       : .
File Size                       : 151 kB
File Type                       : FLIR
MIME Type                       : application/unknown
Creator Software                :
Gain Dead Map Image Width       : 320
Gain Dead Map Image Height      : 240
Gain Dead Map Image Type        : TIFF
Gain 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.tif
1.tif TIFF 320x240 320x240+0+0 16-bit Grayscale Gray 154KB 0.000u 0:00.000

> convert 1.tif -depth 8 1.png

the next step is tricky
see the exiftool documenation
http://cpansearch.perl.org/src/EXIFTOOL/Image-ExifTool-9.76/lib/Image/ExifTool/FLIR.pm

the embedded image is a 16 bit raw binary
exiftool 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

Fraser · « **Reply #31 on:** December 05, 2014, 02:10:43 pm »

@tomas123,

Thank you

Aurora

ElectroTuna · « **Reply #32 on:** December 05, 2014, 06:29:43 pm »

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: [Select]

    # 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[4] file format ID = "FFF\0"
    # 0x04 - string[16] 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[7] spares
    # 0x34 - int32u[2] reserved
    # 0x3c - int32u checksum

The 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.

tomas123 · « **Reply #33 on:** December 06, 2014, 02:19:27 am »

sorry, I forgot it because the checksum is ignored by flir tools and exiftools

as attachment the document for calculating the checksum

Code: [Select]

   unsigned long  dwChecksum;   /* Data checksum   4  32 bytes */

       dwChecksum is checksum of tag data block. It may be set to
       0 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 the
          tag data block given by dwDataPtr and dwDataSize modulo 0x20000000
          or'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 the
          tag data block given by dwDataPtr and dwDataSize modulo 0x20000000
          or'ed with 0x4000 0000 (MSB always set, MSB-1 always 0).
   */

but first try

Code: [Select]

"Checksum may be set to 0 when not used."
the different map file names comes from range:
E4 250 °C temp. range
E40 120 and 650°C temp. range

PS: on shell there is a interesting command

Quote

>ftest
usage: ftest [-q] [-n nr] [-e] [-x] [-i imageid] [-g groupid] [-s siteid]
[-l 0|1] [-t <tag>:<subtag>:<rev>:<file>] [-j <file>] [-d <tag>]
[-m] [-f] [-c <file>] [-r <x>:<y>:[e:]<file>] [-a <file>]
[-v <file>] [-b <file>] <image1> [image2] ...
-q quiet mode, only print error messages (on stderr)
-n read file <nr> in seq file, or "iter" to iterate whole file
-e extract parts to file
-x extract each image in a sequence
-i replace EXIF image ID with <imageid>, "rand" creates new
-g replace EXIF group ID with <groupid>, "rand" creates new
-s replace EXIF site ID with <siteid>, "rand" creates new
-l replace stitchLast with 0 or 1
-t replace/add <tag> with data from <file> at revision <rev>
-j replace JPEG pixels with data from <file>
-d delete <tag> from file
-m force map stats calc on image
-f force loading by ignoring broken CRCs
-c create color JPEG <file> from FFF data
-r rescale to size <x>x<y> in <file> (add :e: for exact rescale)
-a resave using original format to <file>
-v save IR pixels as temp values as csv data in <file>
-b save image1, image2,... to seq <file> (.csq = compressed)

tomas123 · « **Reply #34 on:** December 06, 2014, 02:33:12 am »

Do have tried the service menu of E40?

http://192.168.64.1/service/index.asp
login: flir
pw: 3vlig

then activate Service Mode

there you can also map the dead pixel

PS: I never used the EEPROM unlock password: 1235

fast way to count the mapped bad pixel:

first convert ds120C_we_ap_fi_le_static.gan with exiftool and IM
then

Code: [Select]

$ identify -verbose ds120C.gif
  Histogram:        
     17: (  0,  0,  0) #000000 black
     76783: (255,255,255) #FFFFFF white
  Colormap: 256

tomas123 · « **Reply #35 on:** December 06, 2014, 03:20:31 am »

ah I see, that the current fw of E40 Late 2013 v4.9.0 has no service menu

the important files for mapping bad pixels from old E40 FW 2.23.14

Code: [Select]

$ ls flir_exx_pn490_v2.23.14_update_pack/E2comb_v2.23.14.fif/FlashFS/system/web/service/ImgCorr 
ActivateDigFilters.asp	GainMapResult.asp	Operability.asp		StaticMap.asp		StaticMapResult.asp
GainMap.asp		GainMapSelCase.asp	OperabilityLog.asp	StaticMapCalc.asp	StaticMapWarm.asp
GainMapCalc.asp		GainMapWarm.asp		PixKill.asp		StaticMapCold.asp	gainmapcalcGF.asp
GainMapCold.asp		ImgCorrSelCase.asp	ShutterMap.asp		StaticMapPrepare.asp	index.asp

see here for links to this files
https://www.eevblog.com/forum/testgear/flir-e40-upgrade-configuration/msg561542/#msg561542

you 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 name HighRes.asp = full resolution

):

Code: [Select]

$ 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 get

Code: [Select]

restree.setResourceValue( "prod.preparation.command", "restartHighRes" );and this is the same command on the shell

Code: [Select]

#start HighRes Modus
>rset prod.preparation.command restartHighRes

on the old E40 the command restartHighRes perform following 2 steps:
(1) copy service config files and folders from
/FlashFS/system/service/appcore.d
to
/Temp/appcore.d
and calculate a new CRC01 checksum for the copied config files (it's a integrated crc01 keygen

)
(2) boot Exx to full resolution over restartapp.bat

Code: [Select]

$ cat flir_exx_pn490_v2.23.14_update_pack/E2comb_v2.23.14.fif/FlashFS/system/restartapp.bat 
set PATH=\windows;\FlashFS\system\;
rset .watchdog.enable false
rset .services.log.active false
ps -k Prod
ps -k prod
ps -k uicore
ps -k Gui
ps -k MediaServer
ps -k appcore
ps -k AppServices
ps -k Resmon
ps -k Bit
ps -k syslog
ps -k Cam
ps -k cam
ps -k geni
ps -k dig
ps -k Dig
ps -k watch
ps -k Watch
ps -k RTP
ps -k fwa
ps -k progress
ps -k Med
delay 1
start appcore
delay 10
start prodapp

Not all listed processes are running!

for better understanding of the restartapp.bat I will illuminate the 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 list

Code: [Select]

\>ps
Process NK.EXE          (87 threads), id 0x00400002, loaded at 0x88190000
Process udevice.exe     ( 1 threads), id 0x01550002, loaded at 0x00010000
Process udevice.exe     ( 2 threads), id 0x01630002, loaded at 0x00010000
Process udevice.exe     ( 1 threads), id 0x01F20002, loaded at 0x00010000
Process udevice.exe     ( 1 threads), id 0x03BF0002, loaded at 0x00010000
Process servicesd.exe   (18 threads), id 0x04030002, loaded at 0x00010000
Process cmd.exe         ( 1 threads), id 0x05000006, loaded at 0x00010000
Process appcore.exe     (35 threads), id 0x05530006, loaded at 0x00010000
Process AppServices.exe (17 threads), id 0x070D0006, loaded at 0x00010000
Process Resmon.exe      (12 threads), id 0x07260006, loaded at 0x00010000
Process MediaServer.exe (15 threads), id 0x07380006, loaded at 0x00010000
Process uicore.exe      ( 9 threads), id 0x07850006, loaded at 0x00010000
Process CMD.EXE         ( 1 threads), id 0x090C0046, loaded at 0x00010000
Process ps.EXE          ( 1 threads), id 0x04C1001E, loaded at 0x00010000

i.e. the command "ps -k uicore" from restartapp.bat kills the process uicore.exe

applaunch.dat old E40 FW v2.23.14

Code: [Select]

$ cat flir_exx_pn490_v2.23.14_update_pack/E2comb_v2.23.14.fif/FlashFS/system/applaunch.dat 
# Show intro bootlogo and start progress
progressapp -f \flashfs\system\bootlogo.bmp
# Start command shell on the RS-232 port
cmd /R
# Register a default user
defaultusr
# Start appcore. Appcore starts other necessary processes
appcore

and now with some new CRC checks in FW v4.9.0 against hacking in E40 Late 2013

Code: [Select]

$ cat flir_exx_pn645_pn646_v4.9.0_update_pack/E2qtcomb_v4.9.0.fif/FlashBFS/system/applaunch.dat 
# Show intro bootlogo and start progress
progressapp -f \flashbfs\system\bootlogo.bmp -d1
# Start command shell on the RS-232 port
cmd /R
# Register a default user
defaultusr
# Start appcore. Appcore starts other necessary processes
appcore

# 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

@ ElectroTuna
Contains your FW 3.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 unnecessary

Quote from: Taucher on February 05, 2014, 06:18:35 pm

+++ticker+++ticker+++ticker+++

ATTENTION ALL USERS
the new firmware (1.21.0) is likely designed to hinder/stop the hack!

look for yourself - introduction of a new CRC algo ....

Code: [Select]
Applaunch.dat: # doCRC FlashBFS\system\appcore.exe 1760768 3442989494 # doCRC FlashBFS\system\common_dll.dll 1193984 3567384037 # doCRC FlashBFS\system\progressapp.exe 27648 3868968713 # doCRC FlashBFS\system\defaultusr.exe 5120 784976136 # ID all # CRC03 aad87665
... do I need to say more?

PS: I like the "all" keyword there

PS: I hope you have now enough informations for understanding and hacking a E40

ElectroTuna · « **Reply #36 on:** December 06, 2014, 05:06:10 am »

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'.

ElectroTuna · « **Reply #37 on:** December 06, 2014, 05:14:33 am »

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

ElectroTuna · « **Reply #38 on:** December 06, 2014, 05:28:45 am »

This is my header for my calibration file: (In hex)

Code: [Select]

46 46 46 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 64 00 00 00 40 00 00 00 0e
00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 02 5a 20 00 00 00 00 e0 b5 cc a1
00 05 00 02 00 00 00 64 00 00 00 01 00 00 02 00
00 02 58 20 00 00 00 00 00 00 00 00 ba de ee fe
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
02 00 40 01 f0 00 00 00 00 00 00 00 3f 01 00 00
ef 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Which hex segments are the CRC?! Man, I am going crazy!

tomas123 · « **Reply #39 on:** December 06, 2014, 11:19:21 am »

Quote from: ElectroTuna on December 06, 2014, 05:14:33 am

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

I 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 above

hint from old E40:
The fastet way to load configurations is using temp path for config files and the script restartapp.bat
After full reboot the camera is restored to standard configuration

You don't give me the asked informations about your firmware!
clone your filesystem with ftp and post the directory listing
or post appkit.rev and prodkit.rev

tomas123 · « **Reply #40 on:** December 06, 2014, 11:22:09 am »

Quote from: ElectroTuna on December 06, 2014, 05:28:45 am

This is my header for my calibration file: (In hex)

Code: [Select]
46 46 46 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 64 00 00 00 40 00 00 00 0e 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 5a 20 00 00 00 00 e0 b5 cc a1 00 05 00 02 00 00 00 64 00 00 00 01 00 00 02 00 00 02 58 20 00 00 00 00 00 00 00 00 ba de ee fe
Which hex segments are the CRC?! Man, I am going crazy!

I'm disappointed

64 Byte Header

Quote from: ElectroTuna on December 05, 2014, 06:29:43 pm

In the EXIF documentation, I see the following:

Code: [Select]
# 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[4] file format ID = "FFF\0" ... # 0x3c - int32u checksum

0x00: 46 46 46= FFF
0x3c: e0 b5 cc a1

and the next checksum is in the 32 Byte index
see pdf above

Code: [Select]

typedef struct tagFLIRFILEINDEX-> ba de ee fe

edit:
first try zeroing the checksum

ElectroTuna · « **Reply #41 on:** December 07, 2014, 04:32:45 am »

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.

ElectroTuna · « **Reply #42 on:** December 07, 2014, 06:18:03 am »

I am working on re-calculating the CRC based on this:

Code: [Select]

Type 1 for longword aligned data:
dwChecksum & 0xC0000000 == 0x80000000.
Checksum is calculated as the sum of all 32-bit longwords in the
tag 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...

tomas123 · « **Reply #43 on:** December 07, 2014, 10:52:26 am »

Quote from: ElectroTuna on December 07, 2014, 06:18:03 am

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.

not to the end - look for dwDataSize
add longword (4 Byte) as you wrote

Code: [Select]

00 05                                            Type   FFF_TAGID_GainDeadMap = 5,
      00 02                                      wSubType
            00 00 00 64                          dwVersion
                        00 00 00 01              dwIndexID
                                    00 00 02 00  dwDataPtr  0x00000200
00 02 58 20                                      dwDataSize 0x00025820
            00 00 00 00                          dwParent
                        00 00 00 00              dwObjectNr
                                    ba de ee fe  dwChecksum 0xBADEEEFE

ElectroTuna · « **Reply #44 on:** December 07, 2014, 08:02:10 pm »

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:

Quote

%% Generate CRC for Flir Ex & Exx thermal camera calibration files.
clear alll; clc;
FileID = fopen('ds_we_ap_fi_le.dpx');
CalFileChar = fscanf(FileID, '%c',inf);
CalFileDec = uint8(CalFileChar);
CalFileHex = dec2hex(CalFileDec,2);
fclose(FileID);

ModID = '20000000';
RevArray = [0 1 2 3];

DataFileChar = CalFileChar(hex2dec('201'):end);
DataFileDec = uint8(DataFileChar);
DataFileHex = dec2hex(DataFileDec,2);

SumData = 0;
for ChunkIndex = 1:4:length(DataFileHex)
TempData = '';
for DataIndex = 1:4
RevIndex = ChunkIndex + RevArray(DataIndex);
TempData = [TempData DataFileHex(RevIndex,:)];
end
SumData = SumData + hex2dec(TempData);
end
CalCRC = mod(SumData, hex2dec(ModID));
CalCRCBin = dec2bin(CalCRC, 32);
CalCRCBin(1) = '1'; % MSB always set to 1;
CalCRCHex = dec2hex(bin2dec(CalCRCBin),8);

Remember that Matlab array indexes start from 1.

tomas123 · « **Reply #45 on:** December 07, 2014, 09:44:22 pm »

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 byte

Code: [Select]

46 46 46 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 64 00 00 00 40 00 00 00 0e
00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 02 5a 20 00 00 00 00 00 00 00 00
00 05 00 02 00 00 00 64 00 00 00 01 00 00 02 00
00 02 58 20 00 00 00 00 00 00 00 00 00 00 00 00

flir sometimes use a reversed byte order in the data stream (usSwapPattern)

see here
https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg348398/#msg348398

tomas123 · « **Reply #46 on:** December 08, 2014, 09:42:38 am »

I also can't calculate the checksum of the header

see attachment

you have not posted your file list appkit.rev and prodkit.rev

next try https://www.eevblog.com/forum/testgear/flir-e40-upgrade-configuration/msg563460/#msg563460

Code: [Select]

>rset prod.preparation.command xyz

tomas123 · « **Reply #47 on:** December 08, 2014, 10:04:10 am »

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.zip
and there are all files for WebGUI inside

Code: [Select]

> dir flir_exx_pn645_pn646_v3.12.7_update_pack\E2qtcomb_v3.12.7\FlashBFS\system\web\service\Calib
21.08.2013  20:23             2.331 AccMeas.asp
21.08.2013  20:23             9.743 AccMeasMeasure.asp
21.08.2013  20:23               515 AccMeasProtocol.asp
21.08.2013  20:23             4.725 AccMeasRemove.asp
21.08.2013  20:23            10.017 AccMeasSelect.asp
21.08.2013  20:23             8.231 AccMeasSetObjpar.asp
12.09.2013  12:01             4.203 CalibAcc.asp
21.08.2013  20:23             1.067 index.asp
21.08.2013  20:23             3.427 SysCalib.asp
21.08.2013  20:23             7.762 SysCalibActivate.asp
21.08.2013  20:23             6.841 SysCalibAddLensCase.asp
21.08.2013  20:23            12.181 SysCalibCalculate.asp
21.08.2013  20:23            13.272 SysCalibEditLimits.asp
21.08.2013  20:23             9.292 SysCalibEditMeas.asp
21.08.2013  20:23             6.244 SysCalibEnaDisa.asp
21.08.2013  20:23             3.954 SysCalibFarFocus.asp
21.08.2013  20:23             8.372 SysCalibMeasure.asp
21.08.2013  20:23               513 SysCalibProtocol.asp
21.08.2013  20:23             6.154 syscalibRangeEnaDisa.asp
21.08.2013  20:23             9.998 SysCalibSelect.asp
21.08.2013  20:23             5.895 SysCalibSwitch.asp
21.08.2013  20:23            12.171 transmission.asp
              22 Datei(en),        146.908 Bytes

Code: [Select]

> dir flir_exx_pn645_pn646_v3.12.7_update_pack\E2qtcomb_v3.12.7\FlashBFS\system\web\service\ImgCorr
21.08.2013  20:23             7.123 ActivateDigFilters.asp
21.08.2013  20:23             2.882 GainMap.asp
21.08.2013  20:23             9.935 GainMapCalc.asp
21.08.2013  20:23             5.588 gainmapcalcGF.asp
21.08.2013  20:23             5.819 GainMapCold.asp
21.08.2013  20:23             9.655 GainMapResult.asp
21.08.2013  20:23             2.385 GainMapSelCase.asp
21.08.2013  20:23             2.689 GainMapWarm.asp
21.08.2013  20:23             6.803 ImgCorrSelCase.asp
21.08.2013  20:23             1.566 index.asp
21.08.2013  20:23             5.246 Operability.asp
21.08.2013  20:23             1.684 OperabilityLog.asp
04.09.2013  12:22            47.416 PixKill.asp
21.08.2013  20:23             5.660 ShutterMap.asp
21.08.2013  20:23             1.558 StaticMap.asp
21.08.2013  20:23             5.138 StaticMapCalc.asp
21.08.2013  20:23             7.070 StaticMapCold.asp
21.08.2013  20:23             3.144 StaticMapPrepare.asp
21.08.2013  20:23             8.810 StaticMapResult.asp
21.08.2013  20:23             3.864 StaticMapWarm.asp
              20 Datei(en),        144.035 Bytes

as attachment the relevant part (file size limit here is 1mb)
rename to zip

watch for the full file list of the firmware v3.12.7 in folder kits.d (appkit.rev and prodkit.rev)

some screenshots from the bad pixel mapping procedure

Quote

Instruction

These pages are used to create gain maps. Gain maps even out variations in sensitivity througout the detector, and variations in the transmission of the optical elements of the camera.

The camera can have many gain maps, so different calibration cases can use different maps.

On the Select Case page you shall select a case on which the new map shall be based.

You will then take images of two mapping blackbodies , preferably one in the upper and one in the lower part of the temperature range, using the Warm Image and Cold Image pages.

Popular mapping temperatures are 30°C, 100°C and 300°C.

When both images are taken, you will on the Calc Map page be asked how the new map shall be applied.

The map can become more or less specific, ranging from a default map meant for all cases to a map only used for the selected case.

The dead pixel replacement codes in the gain map are normally lost during the gain map calculations, so the camera Operability can change for the worse. You had better use the Pixel Replacement web page to clean the image afterwards.

tomas123 · « **Reply #48 on:** December 08, 2014, 11:32:49 am »

wow,
I found a menu, where you can replace single dead pixels!
the page only work with internet explorer ( no firefox or chrome)

Select a method $:-\$

show all bad pixels (currently mapped)

kill a single bad pixel

Fraser · « **Reply #49 on:** December 08, 2014, 12:07:14 pm »

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 images

I suggest serches on "IR calibration source" is a safer option

Aurora

Chanc3 · « **Reply #50 on:** December 09, 2014, 01:05:51 pm »

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.

tomas123 · « **Reply #51 on:** December 09, 2014, 03:55:01 pm »

great

Please 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 pm

so here the E60 files I used for my E30, pw funzt666
...
but good news: it works as good as the orig E60 I have rent

he killed the serial in the files

Code: [Select]

# ID 490xxxxx
# CRC01 xxxxxxxx

Chanc3 · « **Reply #52 on:** December 09, 2014, 04:09:32 pm »

Quote from: tomas123 on December 09, 2014, 03:55:01 pm

great
Please 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 pm
so here the E60 files I used for my E30, pw funzt666
...
but good news: it works as good as the orig E60 I have rent
I'll check it all out tomorrow and report back!

What is the best way to remove all of the serial numbers from the files?
Quote
he killed the serial in the files
Code: [Select]
# ID 490xxxxx # CRC01 xxxxxxxx

ElectroTuna · « **Reply #53 on:** December 09, 2014, 05:46:01 pm »

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.

Chanc3 · « **Reply #54 on:** December 09, 2014, 08:39:48 pm »

Quote from: ElectroTuna on December 09, 2014, 05:46:01 pm

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.

When you say you cannot get it to work, what have you tried?

Camera in Network mode (RSNVC or something like that)
Plug into PC
Then 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.

tomas123 · « **Reply #55 on:** December 09, 2014, 10:21:41 pm »

my experience:
connect Exx over a router with wlan, it's a bulletproof method (instead USB RNDIS and driver)

Chanc3 · « **Reply #56 on:** December 11, 2014, 09:15:58 am »

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...

ElectroTuna · « **Reply #57 on:** December 12, 2014, 05:52:35 am »

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!

tomas123 · « **Reply #58 on:** December 12, 2014, 03:38:21 pm »

Do you activated the service mode in the menu?

Read the html code and try some commands on telnet

As I wrote above, I think that not all rset commands are implemented in your firmware
https://www.eevblog.com/forum/testgear/flir-e40-upgrade-configuration/msg563460/#msg563460

ElectroTuna · « **Reply #59 on:** December 13, 2014, 09:26:42 pm »

Quote from: tomas123 on December 12, 2014, 03:38:21 pm

Do you activated the service mode in the menu?

Read the html code and try some commands on telnet

As I wrote above, I think that not all rset commands are implemented in your firmware
https://www.eevblog.com/forum/testgear/flir-e40-upgrade-configuration/msg563460/#msg563460

I 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,

tomas123 · « **Reply #60 on:** December 14, 2014, 12:20:12 pm »

Quote from: ElectroTuna on December 13, 2014, 09:26:42 pm

Did you have a chance to look at the files I posted?

yes
As presumed, your FW v3.18.0 is crippled for security reasons.

the old firmware v3.12.7 contains all necessary parts

Quote from: tomas123 on December 08, 2014, 10:04:10 am

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.zip
and there are all files for WebGUI inside

some compares of appkit.rev between FW v3.12.7 and v3.18.0

Code: [Select]

$ 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.rsc	FILE \flashbfs\system\appcore.d\factory.d\default_params.rsc
FILE \flashbfs\system\appcore.d\factory.d\fusion_params.rsc	FILE \flashbfs\system\appcore.d\factory.d\fusion_params.rsc
FILE \flashbfs\system\appcore.d\factory.d\ui_archive.rsc	FILE \flashbfs\system\appcore.d\factory.d\ui_archive.rsc
FILE \flashbfs\system\appcore.d\factory.d\ui_control.rsc	FILE \flashbfs\system\appcore.d\factory.d\ui_control.rsc
FILE \flashbfs\system\appcore.d\factory.d\ui_display.rsc	FILE \flashbfs\system\appcore.d\factory.d\ui_display.rsc
FILE \flashbfs\system\appcore.d\factory.d\ui_fusion_always.rs	FILE \flashbfs\system\appcore.d\factory.d\ui_fusion_always.rs
FILE \flashbfs\system\appcore.d\factory.d\ui_noantialias.rsc	FILE \flashbfs\system\appcore.d\factory.d\ui_noantialias.rsc
FILE \flashbfs\system\appcore.d\factory.d\ui_pipfusion.rsc	FILE \flashbfs\system\appcore.d\factory.d\ui_pipfusion.rsc
FILE \flashbfs\system\appcore.d\factory.d\ui_remove_uicore_gu	FILE \flashbfs\system\appcore.d\factory.d\ui_remove_uicore_gu
FILE \flashbfs\system\appcore.d\factory.d\ui_start_facet.rsc	FILE \flashbfs\system\appcore.d\factory.d\ui_start_facet.rsc
FILE \flashbfs\system\appcore.exe				FILE \flashbfs\system\appcore.exe
FILE \flashbfs\system\appcore_dll.dll				FILE \flashbfs\system\appcore_dll.dll
FILE \flashbfs\system\applaunch.dat				FILE \flashbfs\system\applaunch.dat
FILE \flashbfs\system\appservices.exe				FILE \flashbfs\system\appservices.exe
FILE \flashbfs\system\arctic.pal				FILE \flashbfs\system\arctic.pal
FILE \flashbfs\system\battest.exe				FILE \flashbfs\system\battest.exe
FILE \flashbfs\system\bootlogo.bmp				FILE \flashbfs\system\bootlogo.bmp
FILE \flashbfs\system\bt.exe					FILE \flashbfs\system\bt.exe
FILE \flashbfs\system\bw.pal					FILE \flashbfs\system\bw.pal
FILE \flashbfs\system\cecompat6.dll				FILE \flashbfs\system\cecompat6.dll
FILE \flashbfs\system\cemgrc.exe			      <
FILE \flashbfs\system\cerdisp.exe			      <
FILE \flashbfs\system\cetlstub.dll			      <
FILE \flashbfs\system\chargeapp.exe				FILE \flashbfs\system\chargeapp.exe
FILE \flashbfs\system\clientshutdown.exe		      <
FILE \flashbfs\system\cmaccept.exe			      <
FILE \flashbfs\system\colorize.exe				FILE \flashbfs\system\colorize.exe
FILE \flashbfs\system\combtabs.d\combtab.appkit			FILE \flashbfs\system\combtabs.d\combtab.appkit
FILE \flashbfs\system\common_dll.dll				FILE \flashbfs\system\common_dll.dll
FILE \flashbfs\system\common_unittest.exe		      <
FILE \flashbfs\system\conmanclient2.exe			      <
FILE \flashbfs\system\conmanclient3.exe			      <
FILE \flashbfs\system\dbtest.exe				FILE \flashbfs\system\dbtest.exe
FILE \flashbfs\system\defaultusr.exe				FILE \flashbfs\system\defaultusr.exe
FILE \flashbfs\system\devicedma.dll			      <
FILE \flashbfs\system\dumpcoff.exe			      <
FILE \flashbfs\system\edbgtl.dll			      <
FILE \flashbfs\system\facet_core.dll				FILE \flashbfs\system\facet_core.dll
FILE \flashbfs\system\facet_exe.exe				FILE \flashbfs\system\facet_exe.exe
FILE \flashbfs\system\facet_ui_qml.dll				FILE \flashbfs\system\facet_ui_qml.dll
FILE \flashbfs\system\fmqping.exe			      <
FILE \flashbfs\system\fpga_b2co3.bin				FILE \flashbfs\system\fpga_b2co3.bin
FILE \flashbfs\system\fpga_c4_55.bin				FILE \flashbfs\system\fpga_c4_55.bin
FILE \flashbfs\system\freeze.exe				FILE \flashbfs\system\freeze.exe
FILE \flashbfs\system\ftest.exe					FILE \flashbfs\system\ftest.exe
FILE \flashbfs\system\fvd.dll					FILE \flashbfs\system\fvd.dll
FILE \flashbfs\system\fvd.exe				      <
FILE \flashbfs\system\gethwtype.exe				FILE \flashbfs\system\gethwtype.exe
FILE \flashbfs\system\i2c.exe				      <
FILE \flashbfs\system\imageformats\qgif4.dll			FILE \flashbfs\system\imageformats\qgif4.dll
FILE \flashbfs\system\iron.pal					FILE \flashbfs\system\iron.pal
FILE \flashbfs\system\kitcrc.exe				FILE \flashbfs\system\kitcrc.exe
FILE \flashbfs\system\kits.d\appkit.rev				FILE \flashbfs\system\kits.d\appkit.rev
FILE \flashbfs\system\kits.exe					FILE \flashbfs\system\kits.exe
FILE \flashbfs\system\lava.pal					FILE \flashbfs\system\lava.pal
FILE \flashbfs\system\level.exe					FILE \flashbfs\system\level.exe
FILE \flashbfs\system\mediaserver.exe				FILE \flashbfs\system\mediaserver.exe
FILE \flashbfs\system\mp4.dll					FILE \flashbfs\system\mp4.dll
FILE \flashbfs\system\nuc.exe					FILE \flashbfs\system\nuc.exe
FILE \flashbfs\system\palette.exe				FILE \flashbfs\system\palette.exe
FILE \flashbfs\system\pmic.exe				      <
FILE \flashbfs\system\progressapp.exe				FILE \flashbfs\system\progressapp.exe
FILE \flashbfs\system\qtcore4.dll				FILE \flashbfs\system\qtcore4.dll
FILE \flashbfs\system\qtdeclarative4.dll			FILE \flashbfs\system\qtdeclarative4.dll
FILE \flashbfs\system\qtgui4.dll				FILE \flashbfs\system\qtgui4.dll
FILE \flashbfs\system\qtnetwork4.dll				FILE \flashbfs\system\qtnetwork4.dll
FILE \flashbfs\system\qtscript4.dll				FILE \flashbfs\system\qtscript4.dll
FILE \flashbfs\system\rainbow.pal				FILE \flashbfs\system\rainbow.pal
FILE \flashbfs\system\rainhc.pal				FILE \flashbfs\system\rainhc.pal
FILE \flashbfs\system\rclone.exe				FILE \flashbfs\system\rclone.exe
FILE \flashbfs\system\rcreate.exe				FILE \flashbfs\system\rcreate.exe
FILE \flashbfs\system\rdelete.exe				FILE \flashbfs\system\rdelete.exe
FILE \flashbfs\system\rdump.exe					FILE \flashbfs\system\rdump.exe
FILE \flashbfs\system\recall.exe				FILE \flashbfs\system\recall.exe
FILE \flashbfs\system\regsvrce.exe			      <
FILE \flashbfs\system\resmon.exe				FILE \flashbfs\system\resmon.exe
FILE \flashbfs\system\restool.exe				FILE \flashbfs\system\restool.exe
FILE \flashbfs\system\restree.dll				FILE \flashbfs\system\restree.dll
FILE \flashbfs\system\rfind.exe					FILE \flashbfs\system\rfind.exe
FILE \flashbfs\system\rls.exe					FILE \flashbfs\system\rls.exe
FILE \flashbfs\system\rpatch.exe				FILE \flashbfs\system\rpatch.exe
FILE \flashbfs\system\rreload.exe				FILE \flashbfs\system\rreload.exe
FILE \flashbfs\system\rsctest.exe				FILE \flashbfs\system\rsctest.exe
FILE \flashbfs\system\rset.exe					FILE \flashbfs\system\rset.exe
FILE \flashbfs\system\rsubscr.exe				FILE \flashbfs\system\rsubscr.exe
FILE \flashbfs\system\rverify.exe				FILE \flashbfs\system\rverify.exe
FILE \flashbfs\system\sensor.d\ex845.dll			FILE \flashbfs\system\sensor.d\ex845.dll
FILE \flashbfs\system\sensor.d\ml2.dll				FILE \flashbfs\system\sensor.d\ml2.dll
FILE \flashbfs\system\sensor.d\mo297.dll			FILE \flashbfs\system\sensor.d\mo297.dll
FILE \flashbfs\system\services.d\factory.d\dcf.rsc		FILE \flashbfs\system\services.d\factory.d\dcf.rsc
FILE \flashbfs\system\services.d\factory.d\dcim.rsc		FILE \flashbfs\system\services.d\factory.d\dcim.rsc
FILE \flashbfs\system\services.d\factory.d\no_wzctool.rsc	FILE \flashbfs\system\services.d\factory.d\no_wzctool.rsc
FILE \flashbfs\system\services.d\factory.d\wlan_nosort.rsc	FILE \flashbfs\system\services.d\factory.d\wlan_nosort.rsc
FILE \flashbfs\system\services.d\sql.d\default.sql		FILE \flashbfs\system\services.d\sql.d\default.sql
FILE \flashbfs\system\services.d\sql.d\defaulttextfield.sql	FILE \flashbfs\system\services.d\sql.d\defaulttextfield.sql
FILE \flashbfs\system\span.exe					FILE \flashbfs\system\span.exe
FILE \flashbfs\system\sqlite.dll				FILE \flashbfs\system\sqlite.dll
FILE \flashbfs\system\stopapp.bat				FILE \flashbfs\system\stopapp.bat
FILE \flashbfs\system\store.exe					FILE \flashbfs\system\store.exe
							      >	FILE \flashbfs\system\suid.exe
FILE \flashbfs\system\supv.exe					FILE \flashbfs\system\supv.exe
FILE \flashbfs\system\syslog.exe				FILE \flashbfs\system\syslog.exe
FILE \flashbfs\system\taskmgr.exe				FILE \flashbfs\system\taskmgr.exe
FILE \flashbfs\system\tcpconnectiona.dll		      <
FILE \flashbfs\system\tcpipc.dll			      <
FILE \flashbfs\system\tprls.exe					FILE \flashbfs\system\tprls.exe
FILE \flashbfs\system\treeproxy.dll				FILE \flashbfs\system\treeproxy.dll
FILE \flashbfs\system\ui.d\design_ui_e2.xml			FILE \flashbfs\system\ui.d\design_ui_e2.xml
FILE \flashbfs\system\ui.d\facet_e2.rcc				FILE \flashbfs\system\ui.d\facet_e2.rcc
FILE \flashbfs\system\ui.d\fonts\gulim.ttf			FILE \flashbfs\system\ui.d\fonts\gulim.ttf
FILE \flashbfs\system\ui.d\fonts\mingliu.ttf			FILE \flashbfs\system\ui.d\fonts\mingliu.ttf
FILE \flashbfs\system\ui.d\fonts\msgothic.ttf			FILE \flashbfs\system\ui.d\fonts\msgothic.ttf
FILE \flashbfs\system\ui.d\fonts\simsun.ttf			FILE \flashbfs\system\ui.d\fonts\simsun.ttf
FILE \flashbfs\system\ui.d\languages\strings_cs.qm		FILE \flashbfs\system\ui.d\languages\strings_cs.qm
FILE \flashbfs\system\ui.d\languages\strings_da.qm		FILE \flashbfs\system\ui.d\languages\strings_da.qm
FILE \flashbfs\system\ui.d\languages\strings_de.qm		FILE \flashbfs\system\ui.d\languages\strings_de.qm
FILE \flashbfs\system\ui.d\languages\strings_el.qm		FILE \flashbfs\system\ui.d\languages\strings_el.qm
FILE \flashbfs\system\ui.d\languages\strings_en.qm		FILE \flashbfs\system\ui.d\languages\strings_en.qm
FILE \flashbfs\system\ui.d\languages\strings_es.qm		FILE \flashbfs\system\ui.d\languages\strings_es.qm
FILE \flashbfs\system\ui.d\languages\strings_fi.qm		FILE \flashbfs\system\ui.d\languages\strings_fi.qm
FILE \flashbfs\system\ui.d\languages\strings_fr.qm		FILE \flashbfs\system\ui.d\languages\strings_fr.qm
FILE \flashbfs\system\ui.d\languages\strings_hu.qm		FILE \flashbfs\system\ui.d\languages\strings_hu.qm
FILE \flashbfs\system\ui.d\languages\strings_it.qm		FILE \flashbfs\system\ui.d\languages\strings_it.qm
FILE \flashbfs\system\ui.d\languages\strings_ja.qm		FILE \flashbfs\system\ui.d\languages\strings_ja.qm
FILE \flashbfs\system\ui.d\languages\strings_ko.qm		FILE \flashbfs\system\ui.d\languages\strings_ko.qm
FILE \flashbfs\system\ui.d\languages\strings_nb-no.qm		FILE \flashbfs\system\ui.d\languages\strings_nb-no.qm
FILE \flashbfs\system\ui.d\languages\strings_nl.qm		FILE \flashbfs\system\ui.d\languages\strings_nl.qm
FILE \flashbfs\system\ui.d\languages\strings_pl.qm		FILE \flashbfs\system\ui.d\languages\strings_pl.qm
FILE \flashbfs\system\ui.d\languages\strings_pt.qm		FILE \flashbfs\system\ui.d\languages\strings_pt.qm
FILE \flashbfs\system\ui.d\languages\strings_ru.qm		FILE \flashbfs\system\ui.d\languages\strings_ru.qm
FILE \flashbfs\system\ui.d\languages\strings_sv.qm		FILE \flashbfs\system\ui.d\languages\strings_sv.qm
FILE \flashbfs\system\ui.d\languages\strings_tr.qm		FILE \flashbfs\system\ui.d\languages\strings_tr.qm
FILE \flashbfs\system\ui.d\languages\strings_zh-chs.qm		FILE \flashbfs\system\ui.d\languages\strings_zh-chs.qm
FILE \flashbfs\system\ui.d\languages\strings_zh-cht.qm		FILE \flashbfs\system\ui.d\languages\strings_zh-cht.qm
FILE \flashbfs\system\ui.d\presets.d\preset_centerhotcoldspot	FILE \flashbfs\system\ui.d\presets.d\preset_centerhotcoldspot
FILE \flashbfs\system\ui.d\presets.d\preset_centerspot.rsc	FILE \flashbfs\system\ui.d\presets.d\preset_centerspot.rsc
FILE \flashbfs\system\ui.d\presets.d\preset_coldspot.rsc	FILE \flashbfs\system\ui.d\presets.d\preset_coldspot.rsc
FILE \flashbfs\system\ui.d\presets.d\preset_deltaspot.rsc	FILE \flashbfs\system\ui.d\presets.d\preset_deltaspot.rsc
FILE \flashbfs\system\ui.d\presets.d\preset_deltatemp.rsc	FILE \flashbfs\system\ui.d\presets.d\preset_deltatemp.rsc
FILE \flashbfs\system\ui.d\presets.d\preset_fivespots.rsc	FILE \flashbfs\system\ui.d\presets.d\preset_fivespots.rsc
FILE \flashbfs\system\ui.d\presets.d\preset_hotcoldspot.rsc	FILE \flashbfs\system\ui.d\presets.d\preset_hotcoldspot.rsc
FILE \flashbfs\system\ui.d\presets.d\preset_hotspot.rsc		FILE \flashbfs\system\ui.d\presets.d\preset_hotspot.rsc
FILE \flashbfs\system\ui.d\presets.d\preset_threespots.rsc	FILE \flashbfs\system\ui.d\presets.d\preset_threespots.rsc
FILE \flashbfs\system\ui.d\presets.d\preset_twohotspots.rsc	FILE \flashbfs\system\ui.d\presets.d\preset_twohotspots.rsc
FILE \flashbfs\system\ui.d\toolbar-config_e2.xml		FILE \flashbfs\system\ui.d\toolbar-config_e2.xml
FILE \flashbfs\system\version.exe				FILE \flashbfs\system\version.exe

or only the differences

Code: [Select]

$ 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.exe
FILE \flashbfs\system\tcpconnectiona.dll		      <
FILE \flashbfs\system\tcpipc.dll			      <

your FW missed some binaries

tomas123 · « **Reply #61 on:** December 14, 2014, 12:20:26 pm »

and some compares of prodkit.rev between FW v3.12.7 and v3.18.0

Code: [Select]

$ 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.prodkit
FILE \flashbfs\system\camtorrent.exe			      |	FILE flashbfs\system\kits.d\prodkit.rev
FILE \flashbfs\system\combtabs.d\combtab.prodkit	      |	FILE flashbfs\system\web\ctrlcam.asp
FILE \flashbfs\system\kits.d\prodkit.rev		      |	FILE flashbfs\system\web\images\flirtrans.gif
FILE \flashbfs\system\prodapp.exe			      |	FILE flashbfs\system\web\inc\camtype.inc
FILE \flashbfs\system\prodisapi.dll			      |	FILE flashbfs\system\web\inc\restree.inc
FILE \flashbfs\system\restartapp.bat			      |	FILE flashbfs\system\web\inc\sitewidgets.inc
FILE \flashbfs\system\torrenterrorcodes.xml		      |	FILE flashbfs\system\web\inc\usermenu.inc
FILE \flashbfs\system\torrenterrorcodes.xsd		      |	FILE flashbfs\system\web\inc\versions.inc
FILE \flashbfs\system\torrenterrorcodes.xsl		      |	FILE flashbfs\system\web\index.asp
FILE \flashbfs\system\web\black-240x320.mov		      |	FILE flashbfs\system\web\rtp.asp
FILE \flashbfs\system\web\ctrlcam.asp			      |	FILE flashbfs\system\web\smallcam.asp
FILE \flashbfs\system\web\images\a2.jpg			      |	FILE flashbfs\system\web\styles\flirweb.css
FILE \flashbfs\system\web\images\a320.gif		      |	FILE flashbfs\system\web\sysinfo.asp
FILE \flashbfs\system\web\images\cross.gif		      |	FILE flashbfs\system\web\webcam.asp
FILE \flashbfs\system\web\images\cross_1.gif		      |	FILE flashbfs\system\web\webpopup.asp
FILE \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 files

Code: [Select]

\flashbfs\system\prodapp.exe
\flashbfs\system\restartapp.bat

and therefore you can' start the service mode
see
https://www.google.de/?gws_rd=ssl#q=site:eevblog.com+prodapp

I post the missed files for the web GUI here:

Quote from: tomas123 on December 08, 2014, 10:04:10 am

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.zip
and there are all files for WebGUI inside

tomas123 · « **Reply #62 on:** December 14, 2014, 12:33:30 pm »

A firmware downgrade is possible, but you risk a bricked stone.
see E4 thread for experience reports

ElectroTuna · « **Reply #63 on:** December 15, 2014, 03:38:25 pm »

Quote from: tomas123 on December 14, 2014, 12:33:30 pm

A firmware downgrade is possible, but you risk a bricked stone.
see E4 thread for experience reports

Tomas,

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.bat

Like 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!

tomas123 · « **Reply #64 on:** December 16, 2014, 11:29:21 am »

I uploaded the original package flir_exx_pn645_pn646_v3.12.7_update_pack.zip here

durability 30 days
http://www.filedropper.com/flirexxpn645pn646v3127updatepack
and here
http://www.file-upload.net/download-10007428/flir_exx_pn645_pn646_v3.12.7_update_pack.zip.html

You can harmless copy the prodapp.exe and restartapp.bat to your E40 (service mode app, also for Web GUI)

see
https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg415480/#msg415480
and here for using rls
https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg400024/#msg400024

But a full firmware downgrade is risky.
Good luck!

tomas123 · « **Reply #65 on:** December 16, 2014, 11:58:00 am »

@ElectroTuna
read the post here
https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg563620/#msg563620

I 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, see https://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 libitum

I also think, you can run the prodapp.exe but I'm not suggest to downgrade the firmware.

google:

Code: [Select]

site:eevblog.com downgrade firmware e4 
site:eevblog.com downgrade firmware e4 1.19

tomas123 · « **Reply #66 on:** December 18, 2014, 12:10:58 pm »

Quote from: ElectroTuna on December 07, 2014, 08:02:10 pm

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:
...

I looked in a gain map file and found it's a common CRC32 checksum

Quote from: ElectroTuna on December 07, 2014, 06:18:03 am

I am working on re-calculating the CRC based on this:

Code: [Select]
Type 1 for longword aligned data: dwChecksum & 0xC0000000 == 0x80000000. Checksum is calculated as the sum of all 32-bit longwords in the tag 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...

I calculated the CRC32 of the block (size 0x25820) with the HxD Hexeditor http://mh-nexus.de/de/hxd/

it's the same

Code: [Select]

// truncate 0x25820 bytes
$ dd skip=$((0x200)) count=$((0x25820)) bs=1  if=ds250C_we_ap_fi_le_static.gan > truncate.bin
153632+0 records in
153632+0 records out
153632 bytes transferred in 0.233211 secs (658768 bytes/sec)

// calc crc32
$ crc32 truncate.bin
4a2ad6ac

// compare with dwChecksum 
$ dd skip=$((0x5c)) count=4 bs=1  if=ds250C_we_ap_fi_le_static.gan 2>/dev/zero| hexdump 
0000000 4a 2a d6 ac

And now the bad news

see attachment

Code: [Select]

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: [Select]

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 checksums

Quote from: ElectroTuna on December 06, 2014, 05:28:45 am

This is my header for my calibration file: (In hex)

46 46 46 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 64 00 00 00 40 00 00 00 0e
00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 02 5a 20 00 00 00 00 e0 b5 cc a1
00 05 00 02 00 00 00 64 00 00 00 01 00 00 02 00
00 02 58 20 00 00 00 00 00 00 00 00 ba de ee fe
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
02 00 40 01 f0 00 00 00 00 00 00 00 3f 01 00 00
ef 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Which hex segments are the CRC?! Man, I am going crazy!

a hint:
head size: 64 Byte
index size: 32 Byte
dwNumUsedIndex = 0xE (marked blue above) = 14
-> Head & index: 64 + 14x32=512 Byte

but 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

tomas123 · « **Reply #67 on:** December 20, 2014, 11:26:56 am »

@ ElectroTuna
you search a way to map a bad pixel

why do you don't try out my suggest

Quote from: tomas123 on December 06, 2014, 02:19:27 am

PS: on shell there is a interesting command
Quote

>ftest
usage: ftest [-q] [-n nr] [-e] [-x] [-i imageid] [-g groupid] [-s siteid]
[-l 0|1] [-t <tag>:<subtag>:<rev>:<file>] [-j <file>] [-d <tag>]
[-m] [-f] [-c <file>] [-r <x>:<y>:[e:]<file>] [-a <file>]
[-v <file>] [-b <file>] <image1> [image2] ...
-q quiet mode, only print error messages (on stderr)
-n read file <nr> in seq file, or "iter" to iterate whole file
-e extract parts to file
-x extract each image in a sequence
-i replace EXIF image ID with <imageid>, "rand" creates new
-g replace EXIF group ID with <groupid>, "rand" creates new
-s replace EXIF site ID with <siteid>, "rand" creates new
-l replace stitchLast with 0 or 1
-t replace/add <tag> with data from <file> at revision <rev>
-j replace JPEG pixels with data from <file>
-d delete <tag> from file
-m force map stats calc on image
-f force loading by ignoring broken CRCs
-c create color JPEG <file> from FFF data
-r rescale to size <x>x<y> in <file> (add :e: for exact rescale)
-a resave using original format to <file>
-v save IR pixels as temp values as csv data in <file>
-b save image1, image2,... to seq <file> (.csq = compressed)

in ftest.exe are parts for broken CRCs and handling of tags like

Code: [Select]

$ strings \ e40/flir_exx_pn490_v2.23.14_update_pack/E2comb_v2.23.14.fif/FlashFS/system/ftest.exe | grep -i dead
FFF_TAGID_DeadMap
FFF_TAGID_GainDeadMap

tomas123 · « **Reply #68 on:** December 23, 2014, 01:48:07 pm »

Quote from: ElectroTuna on December 07, 2014, 04:32:45 am

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.

@ ElectroTuna
you are a little bit lazily $:-\$

Quote from: tomas123 on December 06, 2014, 02:19:27 am

PS: on shell there is a interesting command
Quote

>ftest
usage: ftest [-q] [-n nr] [-e] [-x] [-i imageid] [-g groupid] [-s siteid]
[-l 0|1] [-t <tag>:<subtag>:<rev>:<file>] [-j <file>] [-d <tag>]
[-m] [-f] [-c <file>] [-r <x>:<y>:[e:]<file>] [-a <file>]
[-v <file>] [-b <file>] <image1> [image2] ...
...
-f force loading by ignoring broken CRCs
-a resave using original format to <file>
...

I'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 above

as attachment the original gain map file (ds250C_we_ap_fi_le_static.gan) and a crc patched map file (badCRC.gan)

from my PC:

Quote

$ hexdump -C -n 96 /e40/ds250C_we_ap_fi_le_static.gan
00000000 46 46 46 00 00 00 00 00 00 00 00 00 00 00 00 00 |FFF.............|
00000010 00 00 00 00 00 00 00 64 00 00 00 40 00 00 00 0e |.......d...@....|
00000020 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00000030 00 00 00 00 00 02 5a 20 00 00 00 00 c2 b6 bd 68 |......Z .......h|
00000040 00 05 00 02 00 00 00 64 00 00 00 01 00 00 02 00 |.......d........|
00000050 00 02 58 20 00 00 00 00 00 00 00 00 4a 2a d6 ac |..X ........J*..|

$ hexdump -C -n 96 /e40/badCRC.gan
00000000 46 46 46 00 00 00 00 00 00 00 00 00 00 00 00 00 |FFF.............|
00000010 00 00 00 00 00 00 00 64 00 00 00 40 00 00 00 0e |.......d...@....|
00000020 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00000030 00 00 00 00 00 02 5a 20 00 00 00 00 01 02 03 04 |......Z ........|
00000040 00 05 00 02 00 00 00 64 00 00 00 01 00 00 02 00 |.......d........|
00000050 00 02 58 20 00 00 00 00 00 00 00 00 05 06 07 08 |..X ............|

now let the camera calculate the CRC

from telnet to E40:

Quote

>\FlashFS\system\ftest \StorageCard\test\badCRC.gan
Cannot read file \StorageCard\test\badCRC.gan: bad checksum

>\FlashFS\system\ftest -f \StorageCard\test\badCRC.gan
Read file \StorageCard\test\badCRC.gan in 39 ms
File format is FFF
Number of images = 1
- FFF_TAGID_GainDeadMap present, sz = 153632, rev = 100 (320x240)
map avg = 35212, median = 34812, stddev = 2125.103331, max = 42276, min = 4321

>\FlashFS\system\ftest -a \StorageCard\test\new_crc.fff -f \StorageCard\test\badCRC.gan
Read file \StorageCard\test\badCRC.gan in 7 ms
File format is FFF
Number of images = 1
- FFF_TAGID_GainDeadMap present, sz = 153632, rev = 100 (320x240)
map avg = 35212, median = 34812, stddev = 2125.103331, max = 42276, min = 4321
resaving to \StorageCard\test\new_crc.fff = 0

and now the checksum on my PC

Quote

$ hexdump -C -n 96 /e40/new_crc.fff
00000000 46 46 46 00 00 00 00 00 00 00 00 00 00 00 00 00 |FFF.............|
00000010 00 00 00 00 00 00 00 64 00 00 00 40 00 00 00 0e |.......d...@....|
00000020 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00000030 00 00 00 00 00 02 5a 20 00 00 00 00 c2 b6 bd 68 |......Z .......h|
00000040 00 05 00 02 00 00 00 64 00 00 00 01 00 00 02 00 |.......d........|
00000050 00 02 58 20 00 00 00 00 00 00 00 00 4a 2a d6 ac |..X ........J*..|

$ md5 badCRC.gan new_crc.fff ds250C_we_ap_fi_le_static.gan
MD5 (badCRC.gan) = 4e67bc3c063b0d85a99cced25a722537
MD5 (new_crc.fff) = 68231d1d262f77134f4311e0621bfed7
MD5 (ds250C_we_ap_fi_le_static.gan) = 68231d1d262f77134f4311e0621bfed7

same MD5 like original

bretzeljoe · « **Reply #69 on:** March 02, 2015, 09:41:15 pm »

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/#msg338671

User "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/#msg561266

Important 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)!

WEL0058 · « **Reply #70 on:** March 14, 2015, 08:52:16 pm »

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 temperature

Thanks for all help.

bretzeljoe · « **Reply #71 on:** March 16, 2015, 10:11:09 pm »

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.

Chanc3 · « **Reply #72 on:** March 17, 2015, 01:00:19 pm »

Does anyone still require the files from the E60 2014 model? I have both sitting on my desktop at the moment (2012 and 2014).

WEL0058 · « **Reply #73 on:** March 19, 2015, 04:02:04 am »

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

Chanc3 · « **Reply #74 on:** March 19, 2015, 12:04:36 pm »

Quote from: WEL0058 on March 19, 2015, 04:02:04 am

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

I 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.

rterens · « **Reply #75 on:** March 26, 2015, 05:25:01 pm »

I am interested in the e60 files. I have an older e40bx with 2.23.14 firmware I would like to try and update

Gasburner · « **Reply #76 on:** July 07, 2015, 03:28:12 pm »

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.0
Serial: 645xxxxx
Software: 3.18.0

So let me know if you need a unedited software version, before i start trying to hack mine

And we can make all together a nice guide for 645xxxxx version users.

Chanc3 · « **Reply #77 on:** July 07, 2015, 04:17:58 pm »

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

Gasburner · « **Reply #78 on:** July 07, 2015, 06:48:20 pm »

Thanks Chanc3, dont worry we all got our daily work lol..

My first intention is to only upgrade the resolution to a E60
And as it develops to do the rest and do some trial and error on the rest.

Gasburner · « **Reply #79 on:** July 07, 2015, 10:22:17 pm »

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 code

Quote from: tomas123 on December 03, 2014, 08:33:58 am

Do you have deleted the last line?
I need information about the CRC.

if the last line in
FlashFS/system/appcore.d/config.d/conf.cfg
begins with
Code: [Select]
CRC01 then you must only edit this two lines
Code: [Select]
.caps.config.image.settings.resIR int32 160 .. .caps.config.image.targetNoise.targetNoiseMk int32 55
to
Code: [Select]
.caps.config.image.settings.resIR int32 320 .. .caps.config.image.targetNoise.targetNoiseMk int32 0
and generate a new CRC01

use tutorial and CRC01.exe from Mike
https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg321956/#msg321956

same 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 E40

I 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 telnet

old Exx
Code: [Select]
> rls .registry.caps.config.image.settings r------------- 0 root root downsample false r------------- 0 root root enabled true r------------- 0 root root resIR 320 >rls .caps.config.image.targetNoise enabled true targetNoiseMk 0
it's possible, that you have the new pathes like Ex
then you can search in your whole config with
Code: [Select]
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 editor

PS: some users prefer to switch off the noise generator
Code: [Select]
.caps.config.image.targetNoise.enabled bool false

- Save file (Overwrite)

From there page 8 How to upgrade your flir I3 or I5, to I7 small.pdf

Thanks in advance for the help

Chanc3 · « **Reply #80 on:** July 07, 2015, 10:24:15 pm »

Quote from: Gasburner on July 07, 2015, 10:22:17 pm

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:

- 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 code

Quote from: tomas123 on December 03, 2014, 08:33:58 am
Do you have deleted the last line?
I need information about the CRC.

if the last line in
FlashFS/system/appcore.d/config.d/conf.cfg
begins with
Code: [Select]
CRC01 then you must only edit this two lines
Code: [Select]
.caps.config.image.settings.resIR int32 160 .. .caps.config.image.targetNoise.targetNoiseMk int32 55
to
Code: [Select]
.caps.config.image.settings.resIR int32 320 .. .caps.config.image.targetNoise.targetNoiseMk int32 0
and generate a new CRC01

use tutorial and CRC01.exe from Mike
https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg321956/#msg321956

same 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 E40

I 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 telnet

old Exx
Code: [Select]
> rls .registry.caps.config.image.settings r------------- 0 root root downsample false r------------- 0 root root enabled true r------------- 0 root root resIR 320 >rls .caps.config.image.targetNoise enabled true targetNoiseMk 0
it's possible, that you have the new pathes like Ex
then you can search in your whole config with
Code: [Select]
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 editor

PS: some users prefer to switch off the noise generator
Code: [Select]
.caps.config.image.targetNoise.enabled bool false

- Save file (Overwrite)

From there page 8 How to upgrade your flir I3 or I5, to I7 small.pdf

Thanks in advance

Go to camera information and hold the right arrow key for 10-12 seconds

Sent from my HTC One_M8 using Tapatalk

Gasburner · « **Reply #81 on:** July 07, 2015, 11:22:34 pm »

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 possible

My E40 battery died on my for today, to be continued after recharge

Guide File updated: on 8 july 2015

Gasburner · « **Reply #82 on:** July 22, 2015, 04:55:04 am »

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.2
Username= flir
Password= 3vlig

Any ideas, wrong password for this E40 maybe ?

Thanks in advanced

Chanc3 · « **Reply #83 on:** July 22, 2015, 06:00:21 am »

Try using filezilla, had no issues with that.

Sent from my HTC One_M8 using Tapatalk

reallybigone916 · « **Reply #84 on:** July 22, 2015, 11:16:06 am »

I'm planning to get a used E40, 2011 model. Is there a different in performance between the newer model?

Thanks

tomas123 · « **Reply #85 on:** July 22, 2015, 01:25:48 pm »

missing live MSX, but you can overlay the thermal and real image with the postprocessing Flir Tools

Pinkus · « **Reply #86 on:** July 22, 2015, 01:31:28 pm »

Quote from: reallybigone916 on July 22, 2015, 11:16:06 am

I'm planning to get a used E40, 2011 model. Is there a different in performance between the newer model?

Thanks

The 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).

bookaboo · « **Reply #87 on:** July 22, 2015, 01:43:16 pm »

Agree, at 320x240 there's no need for MSX especially with the manual focus of the Exx.

Gasburner · « **Reply #88 on:** July 22, 2015, 03:33:51 pm »

Thanks Chanc3 that did the trick using FileZilla

Gasburner · « **Reply #89 on:** July 22, 2015, 03:38:56 pm »

This should be the only things needed for the resolution the upgrade, and generate a new CRC01. Please correct me if wrong
i add my conf.cfg as a reference.

FlashFS/system/appcore.d/config.d/conf.cfg
begins with
Code: [Select]
CRC01
then you must only edit this two lines
Code: [Select]
.caps.config.image.settings.resIR int32 160
..
.caps.config.image.targetNoise.targetNoiseMk int32 55

to
Code: [Select]
.caps.config.image.settings.resIR int32 320
..
.caps.config.image.targetNoise.targetNoiseMk int32 0

Code: [Select]

#
# 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

Chanc3 · « **Reply #90 on:** July 22, 2015, 03:50:44 pm »

I believe it has a few more measurement options:

Code: [Select]

#
# 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 xxxxxxxx

This was taken from the E4 thread. I'll try and pull the E60 2012 files when it is back from cal.

Chanc3 · « **Reply #91 on:** July 22, 2015, 03:56:58 pm »

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!

Gasburner · « **Reply #92 on:** July 22, 2015, 04:12:52 pm »

All in the conf.cfg, or in some other directory ?

Quote from: Chanc3 on July 22, 2015, 03:56:58 pm

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!

Chanc3 · « **Reply #93 on:** July 22, 2015, 04:15:16 pm »

In the ui.d directory

Gasburner · « **Reply #94 on:** July 22, 2015, 06:15:39 pm »

Any info which ones someone ?, or you upload them if your E60 comes back Chance3 ?

Thanks a lot for all help so far

Quote from: Chanc3 on July 22, 2015, 04:15:16 pm

In the ui.d directory

Chanc3 · « **Reply #95 on:** July 22, 2015, 08:59:32 pm »

Quote from: Gasburner on July 22, 2015, 06:15:39 pm

Any info which ones someone ?, or you upload them if your E60 comes back Chance3 ?

Thanks a lot for all help so far

Quote from: Chanc3 on July 22, 2015, 04:15:16 pm
In the ui.d directory

In 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

Gasburner · « **Reply #96 on:** July 22, 2015, 09:46:46 pm »

Where to find the lastest CRC01.exe ?, most links end dead on here.

Chanc3 · « **Reply #97 on:** July 22, 2015, 09:49:06 pm »

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 Tapatalk

EDIT: I can email over tomorrow if I can find it!

encryptededdy · « **Reply #98 on:** July 22, 2015, 11:04:30 pm »

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

tomas123 · « **Reply #99 on:** July 23, 2015, 02:38:34 pm »

there are very few applications, where you need high frame rates with a wide-angle lens

I 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

Chanc3 · « **Reply #100 on:** July 23, 2015, 02:49:19 pm »

Quote from: tomas123 on July 23, 2015, 02:38:34 pm

there are very few applications, where you need high frame rates with a wide-angle lens

I 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
https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg621514/#msg621514

You can turn off the logo via telnet I believe!

Sent from my HTC One_M8 using Tapatalk

tomas123 · « **Reply #101 on:** July 23, 2015, 02:50:20 pm »

yes, I know

// old firmware

Code: [Select]

rset .ui.userSettings.overlayLogo false

tomas123 · « **Reply #102 on:** July 23, 2015, 02:54:16 pm »

Quote from: Chanc3 on July 22, 2015, 03:50:44 pm

I'll try and pull the E60 2012 files when it is back from cal.

see here for E60 files version 2012 (pw funzt666)
https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg338671/#msg338671

Gasburner · « **Reply #103 on:** July 24, 2015, 12:14:42 am »

Do i need the CRC01 or CRC03 ? for my E40

E40 1.0
Serial: 645xxxxx
Software: 3.18.0

Chanc3 · « **Reply #104 on:** July 24, 2015, 06:44:51 am »

Quote from: Gasburner on July 24, 2015, 12:14:42 am

Do i need the CRC01 or CRC03 ? for my E40

E40 1.0
Serial: 645xxxxx
Software: 3.18.0

Does it say CRC01 after your serial number?

I highly doubt it is CRC03

Sent from my HTC One_M8 using Tapatalk

tomas123 · « **Reply #105 on:** July 24, 2015, 07:55:19 am »

you need CRC01 if your configuration files are not encrypted (plain text)

but you need CRC03:

old E40
http://80.77.70.144/SwDownload/app/RssSWDownload.aspx?ID=127
FLIR Exx P/N:490xx (Firmware 2.23.14)
Last Updated: April 23, 2013
this works with CRC01 (self tested

)

new E40 with MSX
http://80.77.70.144/SwDownload/app/RssSWDownload.aspx?ID=194
FLIR Exx P/N:645xx / 646xx (Firmware 4.10.0)

Gasburner · « **Reply #106 on:** July 24, 2015, 01:15:58 pm »

Thanks Chance3 and tomas123

Its 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 decryption

So 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.0
Anyone 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

Chanc3 · « **Reply #107 on:** July 24, 2015, 08:36:04 pm »

https://www.eevblog.com/forum/index.php?topic=21772.msg321956.msg#321956 in the zip file

Sent from my HTC One_M8 using Tapatalk

Gasburner · « **Reply #108 on:** July 24, 2015, 10:52:01 pm »

Thanks a lot Chance3

Quote from: Chanc3 on July 24, 2015, 08:36:04 pm

https://www.eevblog.com/forum/index.php?topic=21772.msg321956.msg#321956 in the zip file

Sent from my HTC One_M8 using Tapatalk

Gasburner · « **Reply #109 on:** July 25, 2015, 01:07:38 am »

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 320 and .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 CRC01

Do 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 result

I am not very familiar with computers these days, and CD / \ stuff was a long.... time ago. so bare with me guys.

Chanc3 · « **Reply #110 on:** July 25, 2015, 05:37:57 am »

Quote from: Gasburner on July 25, 2015, 01:07:38 am

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 320 and .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 in to the E8.cfg ?)
- Remove the old CRC number in your file, and replace this with the new generated CRC01

Do 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 result

I am not very familiar with computers these days, and CD / \ stuff was a long.... time ago. so bare with me guys.[emoji14]hew:

Just 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

Gasburner · « **Reply #111 on:** July 25, 2015, 08:36:23 pm »

Sorry for my ignorance
But 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.cfg

Create a zip file containing the flashfs folder tree and camera.cmd
Rename the file from .zip to .fif

Install FLIR tools
Go to the install folder\bin
Turn camera on and plug USB in
Run FLIRInstallNet
Browse to your .fif file

Click Run FIF

Unplug USB, remove battery and replace

Enjoy!

tomas123 · « **Reply #112 on:** July 26, 2015, 09:30:12 pm »

do you read this post ?
https://www.eevblog.com/forum/testgear/flir-e40-upgrade-configuration/msg561922/#msg561922

Don't copy files from forum. Edit your cfg file!

reallybigone916 · « **Reply #113 on:** July 31, 2015, 01:01:11 pm »

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!

snakemars · « **Reply #114 on:** August 19, 2015, 07:48:26 pm »

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!

reallybigone916 · « **Reply #115 on:** August 20, 2015, 02:04:04 am »

are you able to access your unit via FTP?
limited menu options? what can you do or see?

jumbo · « **Reply #116 on:** August 30, 2015, 07:08:00 am »

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:492xxxxx
catalogue:49001-1901
firmware:2.23.14
model:E30bx_B1.1
without MSX
I 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;)

jumbo · « **Reply #117 on:** August 30, 2015, 08:40:17 pm »

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?

tomas123 · « **Reply #118 on:** August 31, 2015, 03:23:08 pm »

Quote from: jumbo on August 30, 2015, 07:08:00 am

I bought old Flir E30_bx yesterday

my camera have parameters:
serial:492xxxxx

interesting, I only know

Quote from: tomas123 on July 24, 2015, 07:55:19 am

old E40
http://80.77.70.144/SwDownload/app/RssSWDownload.aspx?ID=127
FLIR Exx P/N:490xx (Firmware 2.23.14)
Last Updated: April 23, 2013
this works with CRC01 (self tested )

new E40 with MSX
http://80.77.70.144/SwDownload/app/RssSWDownload.aspx?ID=194
FLIR Exx P/N:645xx / 646xx (Firmware 4.10.0)

but your firmware is 2.23.14 -> use hack for P/N:490xx

jumbo · « **Reply #119 on:** August 31, 2015, 08:46:30 pm »

Quote from: tomas123 on August 31, 2015, 03:23:08 pm

Quote from: jumbo on August 30, 2015, 07:08:00 am
I bought old Flir E30_bx yesterday

my camera have parameters:
serial:492xxxxx

interesting, I only know
Quote from: tomas123 on July 24, 2015, 07:55:19 am

old E40
http://80.77.70.144/SwDownload/app/RssSWDownload.aspx?ID=127
FLIR Exx P/N:490xx (Firmware 2.23.14)
Last Updated: April 23, 2013
this works with CRC01 (self tested )

new E40 with MSX
http://80.77.70.144/SwDownload/app/RssSWDownload.aspx?ID=194
FLIR Exx P/N:645xx / 646xx (Firmware 4.10.0)

I made mistake, I forgot/didnt know to delete # CRC01 line before run CMD command - CRC01.exe "conf.cfg".

I hack camera, how much for noise mK i should have? I had originality 90 now I have 5.
How I can set up WiFi? I should install some programs on my PC or what? to connect with camera?

Thanks EEVBLOG users again for useful information on forum;)
but your firmware is 2.23.14 -> use hack for P/N:490xx

simclardy1 · « **Reply #120 on:** November 02, 2015, 01:59:02 pm »

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 cfa0408e

I 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.

Chanc3 · « **Reply #121 on:** November 02, 2015, 02:07:10 pm »

You must change the CRC number!

If you send me your conf.cfg file I will adjust it for you

tomas123 · « **Reply #122 on:** November 02, 2015, 11:52:28 pm »

Nice service

simclardy1 · « **Reply #123 on:** November 03, 2015, 03:39:50 am »

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.

tomas123 · « **Reply #124 on:** November 03, 2015, 11:46:43 am »

You're welcome!

Please tell us, which Exx hardware version (generation) do you updated.

simclardy1 · « **Reply #125 on:** November 04, 2015, 01:19:56 am »

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 link https://youtu.be/oXJYv_MxIHw

tomas123 · « **Reply #126 on:** November 04, 2015, 03:41:56 pm »

ok, it's an old Exx P/N:490xx without the MSX feature

this is your firmware
http://80.77.70.144/SwDownload/app/RssSWDownload.aspx?ID=127

simclardy1 · « **Reply #127 on:** November 04, 2015, 09:10:08 pm »

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?

tomas123 · « **Reply #128 on:** November 04, 2015, 11:52:10 pm »

This is no language, only a config file

There are different hardware versions of E30

But user funzt send a feedback of success (bluetooth and wifi)
https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg336470/#msg336470

https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg336470/#msg336470

simclardy1 · « **Reply #129 on:** November 05, 2015, 11:13:37 am »

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

cuda12 · « **Reply #130 on:** March 12, 2016, 06:40:07 pm »

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.

targit · « **Reply #131 on:** March 18, 2016, 02:57:11 am »

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/tn8aF you 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 here http://imgur.com/a/tn8aF/zip

tomas123 · « **Reply #132 on:** March 19, 2016, 02:23:20 pm »

it's impressive how many parts used Flir for the Exx series compared to the new generation Flir One with Lepton chip

Pinkus · « **Reply #133 on:** March 20, 2016, 03:01:32 pm »

Quote from: targit on March 18, 2016, 02:57:11 am

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/tn8aF you 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 here http://imgur.com/a/tn8aF/zip

Great photos. Thank you for sharing.

Bill W · « **Reply #134 on:** March 20, 2016, 03:38:56 pm »

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 unit

The double skin on the camera allows the antenna to sit outside the EMC box and inside the environmental box.

Bill

hikanio · « **Reply #135 on:** May 21, 2016, 04:00:16 pm »

Flir E30 49001-1801 Serial # 492xx Success Report

Successfully 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.

Cheers
hikanio

cuda12 · « **Reply #136 on:** May 21, 2016, 09:13:43 pm »

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.

hikanio · « **Reply #137 on:** May 22, 2016, 09:22:26 am »

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?

Cheers
Hikanio

tomas123 · « **Reply #138 on:** May 22, 2016, 03:46:12 pm »

from my E40:

Code: [Select]

http://192.168.64.1/SysInfo.asp

Camera
Name	Part #	Serial #	Date
FLIR E40 	49001-2001 	490xxxx	2012-12-22 

Hardware
Name	Part #	Revision # 	Serial #
...
mainboard	T198133	01	19xxxxx
slbwver	T197877	04	19xxxxx
sliover	T197713	13	19xxxxxx
...

and the registry entry

Code: [Select]

\>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 E4

Quote from: mrflibble on November 30, 2013, 02:48:53 pm

The unlock password is 1235.

tomas123 · « **Reply #139 on:** May 22, 2016, 08:33:29 pm »

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 490xxxxx

Quote from: lgustavocampos on December 01, 2014, 11:58:58 pm

Upgrading E30 to E8 including resolution upgrade.

...

I had with an E30, I successfully upgraded it to an E60, using all the available hardwares, including “Camera”, Flash Light for illumination, 320x240 resolution with full frame buffer, WiFi, Bluetooth, Video Recording, and even the name of it is E60 instead.

....
To use the full potential of the unit, take the cove of the laser off and make wholes where the Flash light and Camera are located, it is hidden beneath it.

and this user used an external bluetooth stick

Quote from: uski on March 11, 2014, 02:55:38 pm

Hi,

For those of you with an E30(bx) (not E4) PN 40xxx-xxxx with firmware 2.23.14, you can add Bluetooth by :
- Adding a cheap USB bluetooth dongle (there's the bluetooth USB driver in the OS), see the attached picture
- Modify the \FlashFS\system\services.d\config.d\conf.cfg to enable Bluetooth :

--------------------
#
# Appservices wlan configuration
#
.caps entry
.caps.config entry
.caps.config.name text "srvs E60"
.caps.config.revision text "0.10"
.caps.config.wlan entry
.caps.config.wlan.enabled bool true
.caps.config.bluetooth entry
.caps.config.bluetooth.enabled bool true
# ID 49xxxxxx
# CRC01 xxxxxxxx
--------------------

And voila it should work. I say it should because I don't have any MeterLink compatible device to test. But it shows the Bluetooth icon, allows me to turn it off/on and the LED pattern on the Bluetooth dongle changes accordingly, and I can start a scan.
The Bluetooth feature allows you to link some MeterLink compatible meters to add data directly into the IR images OSD (current, humidity, ...). http://www.extech.com/meterlink/

About Wifi ? Well I found out that the chipset used must be 88W8688 (it's a combination bluetooth/wifi chip).
The bad news is that it's SDIO only, which means a module most be soldered onto the PCB. I didn't open the camera yet but I suspect the module is not there (or if it's there it's disabled either by hardware of software).

tomas123 · « **Reply #140 on:** May 22, 2016, 08:54:29 pm »

Quote from: hikanio on May 22, 2016, 09:22:26 am

How to find out, if my E30 49001-1801 is physically missing it's wlan/bluetooth modul?

here you find a full teardown of an E30

Quote from: targit on March 18, 2016, 02:57:11 am

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/tn8aF you 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 here http://imgur.com/a/tn8aF/zip

Looks a nice F antenna design used for the wifi unit

hikanio · « **Reply #141 on:** May 23, 2016, 05:45:08 am »

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 options

1. 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 :-)

Cheers
Hikanio

hikanio · « **Reply #142 on:** May 25, 2016, 09:48:38 am »

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.

Cheers
Hikanio

hikanio · « **Reply #143 on:** June 13, 2016, 01:09:50 pm »

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 true

shows 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.

Cheers
Hikanio

Chanc3 · « **Reply #144 on:** June 13, 2016, 08:31:19 pm »

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

tomas123 · « **Reply #145 on:** June 13, 2016, 09:17:17 pm »

I can confirm this "crippled MSX" feature with old Exx hardware.

I found my old post

Quote from: tomas123 on March 16, 2014, 10:59:50 am

If you have a Exx without MSX (year 2012) you can activate the MSX menu but you only see a live real image on the LCD.
If you take a picture, then you save a normal MSX jpg on your SD card.

I think, the MSX code is embedded in the windows CE binaries but not in the fpga code.

You can take PiP images and convert then with Flir Tools to MSX images.

Or see my footnote for other program code for converting RAW images.

reallybigone916 · « **Reply #146 on:** July 22, 2016, 04:04:05 am »

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

Flir E30 49001-1801 Serial # 492xx Success Report

Successfully 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.

Cheers
hikanio

tomas123 · « **Reply #147 on:** September 06, 2016, 02:17:49 pm »

for information and archiving:

FLIR E40 S/N:645XXXXXX F/W: 4.11.0

Quote from: xbnipx on September 05, 2016, 01:55:44 pm

CONFIRMED: E40 4.11.0 is CRC01 based and is 320x240 RESOLUTION HACKABLE

Basically I did not do the CRC01 right. YOU HAVE TO BE VERY CAREFUL WITH THE KEYSTROKES

Steps:
1) Downloaded CRC01.exe from lgustavocampos's E30_Hack folder :
https://www.eevblog.com/forum/thermal-imaging/flir-e4-thermal-imaging-camera-teardown/msg561266/#msg561266
2) Backup (Using RNDIS/FileZilla) FlashFS\system\appcore.d\config.d\conf.cfg from E40 to a safe location
3) Replace only the numbers 160->320 and 55->0 in Notepad++ :
.caps.config.image.settings.resIR int32 320
.caps.config.image.targetNoise.targetNoiseMk int32 0
4) Delete CRC Line making sure there is only one return space after your serial number
- You can check that you have only one return character by going to the find function and
type in [\r\n]+ and select search mode Regular Expression.
4) Place a conf.cfg in the same folder as CRC01.exe
4) Open up Command Prompt and cd to that directory
5) Type/Execute: crc01.exe conf.cfg
6) Go to conf.cfg enter after your serial number and type in new CRC (do not paste)
9) Save and upload via RNDIS to FlashFS\system\appcore.d\config.d\conf.cfg
10) Reset camera by removing battery.

nongken · « **Reply #148 on:** December 04, 2016, 04:49:11 pm »

Quote from: tomas123 on September 06, 2016, 02:17:49 pm

for information and archiving:

FLIR E40 S/N:645XXXXXX F/W: 4.11.0

Quote from: xbnipx on September 05, 2016, 01:55:44 pm
CONFIRMED: E40 4.11.0 is CRC01 based and is 320x240 RESOLUTION HACKABLE

Basically I did not do the CRC01 right. YOU HAVE TO BE VERY CAREFUL WITH THE KEYSTROKES

Steps:
1) Downloaded CRC01.exe from lgustavocampos's E30_Hack folder :
https://www.eevblog.com/forum/thermal-imaging/flir-e4-thermal-imaging-camera-teardown/msg561266/#msg561266
2) Backup (Using RNDIS/FileZilla) FlashFS\system\appcore.d\config.d\conf.cfg from E40 to a safe location
3) Replace only the numbers 160->320 and 55->0 in Notepad++ :
.caps.config.image.settings.resIR int32 320
.caps.config.image.targetNoise.targetNoiseMk int32 0
4) Delete CRC Line making sure there is only one return space after your serial number
- You can check that you have only one return character by going to the find function and
type in [\r\n]+ and select search mode Regular Expression.
4) Place a conf.cfg in the same folder as CRC01.exe
4) Open up Command Prompt and cd to that directory
5) Type/Execute: crc01.exe conf.cfg
6) Go to conf.cfg enter after your serial number and type in new CRC (do not paste)
9) Save and upload via RNDIS to FlashFS\system\appcore.d\config.d\conf.cfg
10) Reset camera by removing battery.

Thank You "tomas123"

tomas123 · « **Reply #149 on:** December 04, 2016, 05:39:50 pm »

You are welcome!

layws · « **Reply #150 on:** January 04, 2017, 07:45:14 am »

Thanks this form and everbody. I upgrade E40 with 320x240
SN: 645xxxxxx
firmware: 3.12B.7 -> 4.10

Q1:
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.

Chanc3 · « **Reply #151 on:** January 04, 2017, 09:14:02 am »

Quote from: layws on January 04, 2017, 07:45:14 am

Thanks this form and everbody. I upgrade E40 with 320x240
SN: 645xxxxxx
firmware: 3.12B.7 -> 4.10

Q1:
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.

RE: 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.

layws · « **Reply #152 on:** January 04, 2017, 03:02:07 pm »

Quote from: Chanc3 on January 04, 2017, 09:14:02 am

Quote from: layws on January 04, 2017, 07:45:14 am
Thanks this form and everbody. I upgrade E40 with 320x240
SN: 645xxxxxx
firmware: 3.12B.7 -> 4.10

Q1:
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.

RE: 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.

Maybe 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.

Chanc3 · « **Reply #153 on:** January 04, 2017, 03:07:30 pm »

Can you try and copy it over?

layws · « **Reply #154 on:** January 04, 2017, 03:09:39 pm »

Quote from: Chanc3 on January 04, 2017, 03:07:30 pm

Can you try and copy it over?

Service menu function, only folder not have any files.

Chanc3 · « **Reply #155 on:** January 04, 2017, 03:35:39 pm »

I'll see if I can find the files on the older 2012 model of the E60.

tomas123 · « **Reply #156 on:** January 04, 2017, 08:50:11 pm »

here I posted the web files
https://www.eevblog.com/forum/thermal-imaging/flir-e40-upgrade-configuration/msg564687/#msg564687

and the config files of my E40 2012
https://www.eevblog.com/forum/thermal-imaging/flir-e40-upgrade-configuration/msg565342/#msg565342

but read the post from Electrotuna - it doesn't work

Quote from: ElectroTuna on December 12, 2014, 05:52:35 am

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.

Chanc3 · « **Reply #157 on:** January 05, 2017, 10:43:45 am »

Do you not think those files could be transferred over also?

tomas123 · « **Reply #158 on:** January 05, 2017, 12:49:32 pm »

I think, the binary is crippled in newer firmwares

old path

Code: [Select]

\Flashfs\system\prodapp.exe
new path

Code: [Select]

\flashbfs\system\prodapp.exe

layws · « **Reply #159 on:** January 05, 2017, 01:26:05 pm »

Dear tomas123
Thanks 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.zip
And copy E2comb_v2.23.14.zip\FlashFS\system\web\ all folder *.asp and *.inc to E40

It can work some function. Pixel Replacement can not work. Electrotuna - it doesn't work, the same result

You can use WIFI, direct connect to E40. No need hack and use USB cable.

I am try reset "Usage statistics" function as well.

tomas123 · « **Reply #160 on:** January 05, 2017, 02:46:23 pm »

great

can you make some noise tests?

Quote from: tomas123 on December 04, 2013, 11:25:32 pm

Quote from: mikeselectricstuff on October 25, 2013, 01:26:45 pm
Quote
.caps.config.image.targetNoise.enabled bool true
.caps.config.image.targetNoise.targetNoiseMk int32 135
It could actually be noise reduction or shaping - maybe this is a threshold to decide when to apply noise reduction, i.e. adjust filter until noise is below the target value. "Mk" - mask? Perhaps something like a hysteresis function?

targetNoiseMk is a noise generator in mK (conforming with NETD/ thermal sensity in Flir Datasheets of the selected cam)
Formerly I stacked some noisy images with Registax or AviStax to subtract out the randomly noise and it works great!!

after setting targetNoiseMk to zero, stacking of images don't improve results

here a sample from a Flir E40 (old cam hacked formerly from 160x120 to 320x240)
in service menu I can measuring the noise

Code: [Select]
rset .caps.config.image.targetNoise.targetNoiseMk 60 (MilliKelvin) Temporal noise MilliKelvin Digital Units Pixel Noise 61.28 12.13 Row Noise 14.84 2.94 Column Noise 13.67 2.71 Spatial noise MilliKelvin Digital Units Pixel Noise 25.69 5.09 Row Noise 7.08 1.40 Column Noise 7.82 1.55 Uniformity 198.23 39.25 Total noise MilliKelvin Digital Units Pixel Noise 67.01 13.27 Row Noise 9.71 1.92 Column Noise 10.10 2.00

and now without noise (cam temperature is 25 Grad):
Code: [Select]
rset .caps.config.image.targetNoise.targetNoiseMk 0 (MilliKelvin) Temporal noise MilliKelvin Digital Units Pixel Noise 19.85 3.93 Row Noise 6.39 1.26 Column Noise 8.64 1.71 Spatial noise MilliKelvin Digital Units Pixel Noise 18.98 3.76 Row Noise 4.70 0.93 Column Noise 5.54 1.10 Uniformity 210.23 41.63 Total noise MilliKelvin Digital Units Pixel Noise 28.96 5.73 Row Noise 5.76 1.14 Column Noise 7.66 1.52

see the differences (NETD is 0,03 °C @ 25°C)

Quote
http://gs.flir.com/surveillance-products/surveillance-technology/imaging-technotes/IR_Technology_Parameters
Uncooled infrared cameras systems are typically a little noisier, in the range of 30 - 120mK. Noise in an image can be spatial or temporal.
Spatial noise is noise across the image at any given point in time. It is perceived as an unchanging fixed pattern on top of the image.
Temporal noise is noise at any point in the image over time. It is perceived as the static that moves in an image.
NETD is typically the measure of both these noise types.

remarkably Flir dont't disable the noise generator at the top cams of a serie (Flir E4 -> E8 , Flir E30 -> E60)

layws · « **Reply #161 on:** January 06, 2017, 12:10:49 am »

Dear tomas123
Q1: How to check Temporal noise data? I can try to do a test. Thanks
Q2: Would you have 3.12.7 flir firmware? I want to test \web\ *.asp to try

My 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

tomas123 · « **Reply #162 on:** January 06, 2017, 06:08:51 pm »

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 2013
http://support.flir.com/SwDownload/app/RssSWDownload.aspx?ID=127
Flir never updated the firmware of this "old" camera

my data, but for what?

Code: [Select]

.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                     true
rw--r--------- 0 root   root   <e> incompatible                    
rw--r--------- 0 root   root   <e> radiometric                     

.caps.config.image.services.store.incompatible: (2)
r---r--------- 0 root   root   <b> enabled                    false
r---r--------- 0 root   root   <i> level                          0

.caps.config.image.services.store.radiometric: (1)
r---r--------- 0 root   root   <b> enabled                     true

this means, that you add 5mK fake noise to your images

.caps.config.image.targetNoise.targetNoiseMk int32 5

look at my full dump above

Code: [Select]

rset .caps.config.image.targetNoise.targetNoiseMk  60 (MilliKelvin)

results in:

Code: [Select]

Temporal noise        MilliKelvin      
Pixel Noise           61.28

layws · « **Reply #163 on:** January 07, 2017, 01:45:07 am »

Sorry no response, maybe 2.23.14 can not copy for 4.10.0

Chanc3 · « **Reply #164 on:** January 08, 2017, 09:26:19 am »

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

layws · « **Reply #165 on:** January 08, 2017, 01:58:19 pm »

Quote from: Chanc3 on January 08, 2017, 09:26:19 am

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

I try those again, T4***, T6*** series firmware still can not use.

layws · « **Reply #166 on:** May 10, 2017, 05:20:02 am »

FLIR Exx P/N:645xx / 646xx (4.13.0) Update Pack

Would you have good idea?

http://support.flir.com/SwDownload/app/RssSWDownload.aspx?ID=194

Chanc3 · « **Reply #167 on:** May 10, 2017, 06:18:00 am »

I'd try and not update firmware. The older the better, really.

Sent from my ONE A2003 using Tapatalk

Fraser · « **Reply #168 on:** September 04, 2017, 01:52:07 pm »

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 screen

My E40(E60) is performing flawlessly and is now even more impressive with its increased resolution

Now to help a non IT confident E30 owner update his camera via a conference call. Wish me luck !

Fraser

HighVoltage · « **Reply #169 on:** September 05, 2017, 09:58:14 am »

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

Fraser · « **Reply #170 on:** September 05, 2017, 10:56:09 am »

@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 helps

Fraser

tomas123 · « **Reply #171 on:** September 05, 2017, 11:01:07 am »

Quote from: Fraser on September 04, 2017, 01:52:07 pm

All went well but after the upgrade the measurement crosshairs were located in the top left quadrant of the screen.

I 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 position

After a reset of a configuration (FW update) the cross hair also moves to the center...

Fraser · « **Reply #172 on:** September 05, 2017, 11:05:21 am »

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

Fraser · « **Reply #173 on:** September 05, 2017, 11:06:51 am »

@tomas123,

Thanks for the information on the cross hairs position issue

Fraser

Fraser · « **Reply #174 on:** September 05, 2017, 11:29:03 am »

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 far

Last 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 files

Fraser

Fraser · « **Reply #175 on:** September 06, 2017, 11:28:55 am »

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 idea

Wow 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

Fraser · « **Reply #176 on:** September 06, 2017, 11:35:57 am »

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

Pinkus · « **Reply #177 on:** September 07, 2017, 09:13:38 pm »

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!

Fraser · « **Reply #178 on:** September 07, 2017, 09:56:54 pm »

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

tomas123 · « **Reply #179 on:** September 08, 2017, 08:08:43 am »

Quote from: Fraser on September 06, 2017, 11:35:57 am

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.

Yes, two years ago we had a hard discussion in this forum about this topic.

with bash/cmd set noise to zero

Code: [Select]

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 test

Code: [Select]

 Temporal noise        MilliKelvin      Digital Units
Pixel Noise      19.85      3.93
Row Noise         6.39      1.26
Column Noise      8.64      1.71


Spatial noise        MilliKelvin      Digital Units
Pixel Noise      18.98      3.76
Row Noise         4.70      0.93
Column Noise      5.54      1.10
Uniformity      210.23      41.63


Total noise        MilliKelvin      Digital Units
Pixel Noise      28.96      5.73
Row Noise         5.76      1.14
Column Noise      7.66      1.52

compare with 60mk noise

Quote

rset .caps.config.image.targetNoise.targetNoiseMk 60 (MilliKelvin)

Temporal noise MilliKelvin Digital Units
Pixel Noise 61.28 12.13
Row Noise 14.84 2.94
Column Noise 13.67 2.71

Spatial noise MilliKelvin Digital Units
Pixel Noise 25.69 5.09
Row Noise 7.08 1.40
Column Noise 7.82 1.55
Uniformity 198.23 39.25

Total noise MilliKelvin Digital Units
Pixel Noise 67.01 13.27
Row Noise 9.71 1.92
Column Noise 10.10 2.00

tomas123 · « **Reply #180 on:** September 08, 2017, 08:17:53 am »

Quote from: Fraser on September 06, 2017, 11:28:55 am

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 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.

Fraser · « **Reply #181 on:** September 09, 2017, 10:26:58 pm »

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 E60

The 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 file

1. 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

Fraser · « **Reply #182 on:** September 10, 2017, 09:15:27 pm »

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 performance

The 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

HighVoltage · « **Reply #183 on:** September 11, 2017, 12:03:34 pm »

Thank you Fraser for the feedback and buyers guide to the E40.

How about the E40bx
Can 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.

Zucca · « **Reply #184 on:** September 11, 2017, 12:33:54 pm »

HighVoltage

according 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!

Fraser · « **Reply #185 on:** September 11, 2017, 01:01:43 pm »

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

Fraser · « **Reply #186 on:** September 11, 2017, 01:09:55 pm »

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

Pinkus · « **Reply #187 on:** September 11, 2017, 01:53:49 pm »

Quote from: Fraser on September 11, 2017, 01:09:55 pm

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.

Mmmmh - 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°C

Look 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).

Zucca · « **Reply #188 on:** September 11, 2017, 02:37:41 pm »

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.

Fraser · « **Reply #189 on:** September 11, 2017, 02:51:31 pm »

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 you

But that's another story

Fraser

Fraser · « **Reply #190 on:** September 11, 2017, 02:58:37 pm »

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

Pinkus · « **Reply #191 on:** September 11, 2017, 03:01:50 pm »

For me, usually the temperature difference is 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.

Pinkus · « **Reply #192 on:** September 11, 2017, 03:07:54 pm »

I think that the E30 with Wifi module 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.

HighVoltage · « **Reply #193 on:** September 11, 2017, 03:45:20 pm »

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 4903xxxx
and is allegedly from 2013 with FW 2.19 installed

On 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-xxxx

Since the one offered to me falls right in to the second category, is that good, bad or may be does not matter?

Zucca · « **Reply #194 on:** September 11, 2017, 03:54:33 pm »

According to here:

https://www.eevblog.com/forum/thermal-imaging/flir-e40-upgrade-configuration/msg561542/#msg561542

it'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, Pinkus is right.

Fraser · « **Reply #195 on:** September 11, 2017, 03:55:25 pm »

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

Fraser · « **Reply #196 on:** September 11, 2017, 03:59:42 pm »

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 out

Fraser

Fraser · « **Reply #197 on:** September 11, 2017, 05:55:51 pm »

Test of some close-up lenses mounted on the E40(E60+) completed

Not 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 - Germanium
3. Inframetrics 60mm diameter 150MM (6") FL Close-up lens - Germanium
4. Agema/FLIR 55mm diameter 150mm (6") FL Close-up lens - Germanium
5. EEV ARGUS 2 rear Germanium lens element - Spec unknown. Aperture 25mm
6. EEV ARGUS 2 front Germanium lens element - Spec unknown. Aperture 20mm

Test PCB Dimensions: 98mm x 63mm

5 pin SMD (PCB ID: U7) component dimensions :
Plastic case : 2.94mm x 1.7mm
Across full width of pins: 3.16mm

Resistor (PCB ID: R8) Dimensions
Case including solder areas 3.24mm x 1.55mm

Pictures to follow .... time for my tea now

Fraser

Fraser · « **Reply #198 on:** September 11, 2017, 05:58:20 pm »

Lens 1 - 20mm diameter 100mm FL Znse

Fraser · « **Reply #199 on:** September 11, 2017, 06:01:31 pm »

Lens 2 - Inframetrics 60mm diameter 300mm FL Germanium