Flir E40 Upgrade & Configuration

[Zucca]

I think your E30 will only have the lower temperature range enabled.

No I have two ranges out of the box  , which means they are also calibrated.... YES! this is really the ultimate E8+ upgrade, finger crossed for WIFI.
That's also why I was suspecting I had an already hacked unit.
I contacted the previous owner and he doesn't know what I am talking about.
It's funny how many people sell those wonderful toys without knowing the  Exx cameras true secret power.
Good for us!

[Fraser]

My mistake, it does have two ranges but, according to FLIR, Range 2 is limited to 350C rather than 650C. It would be worth your time to look into enabling the full range capability via the Service menu.

http://www.flir.co.uk/cs/display/?id=41959

https://www.ivytools.com/v/vspfiles/assets/images/flir-e30-data-49001-1801.pdf

Fraser

[Zucca]

Ah ah, it's not your mistake.
PN 49001-1601 E30 has one range:  -20°C  to +250°C  (see data sheet attached)
PN 49001-1801 E30 has two ranges:  –20°C to +120°C and 0°C to +350°C

[Fraser]

Take a look at this thread for all the info on the range changes via the Service Menu

https://www.eevblog.com/forum/thermal-imaging/just-got-an-e30bx-have-the-usual-questions/

I was wrong about the E30 noise injection..... it is set to 90mK in the E30 !

Fraser

[Zucca]

it is set to 90mK in the E30 !

Printig money SW machine...
The PN 49001-1801 E30bx has just the first range enabled.
Those FLIR marketing guys deserved this Hack! 

On the side I found the technical drawings, useful if we have to make some 3D print things...
https://www.tme.eu/pl/Document/4c91ec07e961c92226a3919fcc80768a/1196960_en_51.pdf

[Fraser]

I wish I could get my hands on technical drawings of the lens bayonet part that mates with the camera. I will be using my trusty digital calliper to design an adapter to fit that type of bayonet mount. I have a project on hold at the moment to adapt a Fluke Tele2 lens to the Exx camera mount. I will either 3D print the adapter, or cut it out of Aluminium on my lathe. Maybe both

Fraser

[Vipitis]

I have printed and designed then printed, lens adapters. They work, but need a little bit of help with sanding some parts.

But I wouldn't use them as a solution, unless you glue them in, I am too worried to just have my lens drop out.

It's great for prototyping.

[Zucca]

Going into the jungle of hacking... already made a backup of everything I could read out.

This is my hack reference:
https://www.eevblog.com/forum/thermal-imaging/flir-e4-thermal-imaging-camera-teardown/msg561266/#msg561266

Now... I would like to use those Fraser config:
https://www.eevblog.com/forum/thermal-imaging/flir-e40-upgrade-configuration/msg1299159/#msg1299159
because he is the best on the market 

Here where I'm not sure:

1) Difference between my APPconf.txt and Fraser's one, see attachments.
I don't care if the values are different, but a few parameters/lines are missing.

2) Here my \FlashFS\system\kits.d\confkit.rev

# confkit.rev
# This file contains revision information for all loaded
# files in a kit
# Do not edit

NAME userconf
VERSION E30_B 1.1
DATE 16-Sep-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

should I modify the line VERSION like this

VERSION E60_B 1.1

?
Same story with GUIconf.txt see attachment.

I have a bad feeling about it.

Thanks gentleman.

[Zucca]

https://www.eevblog.com/forum/testgear/flir-e30-config-and-specs/msg946297/#msg946297

EDIT: It looks like I have WIFI... see below...



finger double crossed.

[Fraser]

Hiya,

Do not modify anything in that 'kit' file. There is no need. Note that the files that are altered in the update are stated as being "undefined" which is good

There is no requirement to change the references to E30, they have no effect on on the configuration or operation of the camera. They are just detailing the file identity. The file identity in the updated files is changed and this is seen when looking at the camera information. It becomes an E60 in the camera type details.

The ".cfg" configuration files are all that need to be changed for the upgrades and there are many options that are available. I enabled those that worked fir me. Note that the graphing mode in my configuration did not work correctly. It turns out that the associated configuration line needs to be set to a value of 5.

IIRC you will be adding a configuration file that provides the Wi-Fi configuration and enablement. I forget whether that folder even existed on the E30. I think I had to add it from the E60 image that I was using. It should all be detailed in the E30 upgrade instructions.

IIRC, the camera will be identified by FLIR Tools as its original model, in your case, an E30. This effects nothing as it is just read out of the eeprom and is not used by FLIR Tools to set any paremeters. IIRC, the camera ID can be changed in the Service Menu. I personally did not bother as I am not trying to pass the camera off as an E60 in my usage. Some users may want the camera ID to read "E60" in the file metadata.

Playing with the .cfg fires is both easy and relatively safe to do. Just make sure to double check the CRC01 calculation each time and keep the. Andra in RNDIS mode until,all playing is completed. That way you can always load the previous working .cfg file if required. It is possible to play with the various  .rsc files as well but I have not needed to do that to date. You need CRC32 for their checksum calculation.

This is all from memory so take it as my best recollection rather than hard facts.

Fraser

[Fraser]

Just thinking about the "E30" ID. I seem to recall the entry in the kit list DOES set what is seen in the cameras information page. As stated, this is just cosmetic and makes no difference to the cameras operation.

You can set your various configuration files to read E60 if you like, just be sure to recalculate the CRC01 if you change a file that has such listed at the bottom.

The additional Wi-Fi support configuration is held in the Services.d folder as detailed in the E30 upgrade instructions you referenced. Just use the E60 file and all should be fine.

There is much that can be experimented with in this easily edited firmware
I enabled everything that worked in my configuration files and there is plenty of added functionality to enjoy.

As a word of warning, including the later Exx (MK2) series MSX entries in the configuration file caused my camera to misbehave. It saved only blank images. Removal of the MSX related lines returned the camera to normal operation.

Fraser

[Fraser]

Zucca,

I am happy to send you my cameras complete back-up file set if it is of any interest/help.

Let me know if you need it. It is, of course, basically just an E60 build plus a few additional configuration options enabled.

Fraser

[Zucca]

Hack time 

Regarding this file:

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

I was missing these lines:

.caps.config.image.framegrab entry
.caps.config.image.framegrab.visual entry
.caps.config.image.framegrab.visual.enabled bool true
.caps.config.image.settings.resVIS int32 1600

from Fraser conf.cfg

I modified only the last one, bringing the numer to 3200

.caps.config.image.settings.resVIS int32 3200

because my default conf.cfg was

.caps.config.image.settings.resIR int32 160
.caps.config.image.settings.resVIS int32 1600

so with the caps.config.image.settings.resIR upgrade to 320, I did the same proportional thing to .caps.config.image.settings.resVIS .

I also left this to default:

.caps.config.revision text "1.1"

and did not change to Fraser one:

.caps.config.revision text "0.10"

because maybe those missing lines are somehow interpreted in the v1.1 config, it should be just a text so just cosmetic I hope.

for this puppy:

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

I used the Fraser one as reference but I didn't touched the caps.config.revision text and left the value "1.1" there

same story with

\FlashFS\system\services.d\config.d\conf.cfg

Finally I did change the

\FlashFS\system\kits.d\confkit.rev

with the following:

VERSION E60 0.1

because I paid for a E60 not a smelly E30B.

Just thinking about the "E30" ID. I seem to recall the entry in the kit list DOES set what is seen in the cameras information page. As stated, this is just cosmetic and makes no difference to the cameras operation.

Yes, I can confirm this.

Here the result... 

before:



after with range 0 to 350 C



after with range -20 to 120 C


Much less noise in this range, expected? I think yes.

Please also notice I upgraded the digital camera...

before



after



now it's bed time... will continue to play tomorrow.

No I can't go sleep I need to check the radio board...

WIFI is there! So in 2 units E30 PN 49001-1801 with serial number 4902XXXX, we have the radio board there. I can also confirm the slbwver info in the service menu theory about WIFI.

ah... I will never sleep tonight... regarding the second T range, it's interesting... here what i got:

before


after



funny I can select now the range 200 to 1200 C   

I am pretty sure it is not calibrated but 
We just need to service it and calibrate it... 

Here the calibration protocol on the service menu:

Camera type :   FLIR E30   Product code :   49001-1801
Serial :   4902XXXX   Manuf. date :   2012-XX-XX
Det. serial :   S054XXXX   SW version :   3.0.18
Calib version :   org      

Lense(s):   Serial:
  FOL18     -
  FOL10     -
  FOL30     -

FOL18, -20C - 120C
Constants:
  R: 15457.7
  B: 1407.40
  F: 1.00
  J0: 5862.0
  J1: 89.93
  AdErr: 0.00946
  Locks: F
  Rem: RBF OK
Adaptation result:
Calibrated 2012-01-11 in Stockholm by KaKa2.


FOL18, 0C - 350C
Constants:
  R: 16315.1
  B: 1415.70
  F: 1.25
  J0: 7786.0
  J1: 10.58
  AdErr: 0.06750
  Locks: F
  Rem: RBF OK
Adaptation result:
Calibrated 2012-01-11 in Stockholm by KaKa2.


FOL18, 200C - 1200C
Disabled

I went back to 2 ranges and disabled the 200 to 1200 C, because the camera in this range was not working properly. it was just showing >80C all the time but the infrared image was there 

[Fraser]

My comments......

Great work !

1. Yes the changes you made in the Vis settings removes the resolution restriction from the visible light camera. Its is now the full 3.2MP

2. The higher the temperature range, the lower the thermal sensitivity. This is normal and shown in the E60 specifications when it switches between Range 1 and Range 2. Perfectly normal and not a problem. The reason is that the bias voltages on the microbolometer are changed to allow the sensor array to cope with higher temperatures. The most highest sensitive of the sensor array is at lower temperatures where the bias voltages are carefully set to provide best performance. As the temperature capability rises, the bias voltages are moved away from that optimum performance setting. Just a fact of life with Microbolometers.

3. I was not aware that your camera range options were limited to a maximum capability of 350C. I thought there would be a 650C available but having never looked in that menu for an E30 I was not sure.

4. Range 3 is the optional (chargeable) high temperature range. In your camera is was not calibrated, hence its failure to provide sensible temperature measurements. I suspect this range is only calibrated if you buy the high temperature option you have the physical high temperature filter and the camera is calibrated to take account of its characteristics. There is certainly. High temperature filter listed on the accessories list.

5. Very pleased to see your camera contains the wireless module. The E30bx I upgraded had no module details listed in the hardware list. When I enabled the Wi-Fi, the menu for it appeared and I could activate it, but there was no SSID emitted and it could not see my router SSID. No module present on that unit. Bluetooth could not be activated, it just flipped back to 'off' whenever I switched it on. The BT module is an integral part of the Wi-Fi module.

Fraser

[Fraser]

With regard to adding any extra lines to the configuration files. Only the MSX lines are likely to cause issues as the camera tries to obey them without having the required hardware performance to cope with such.

Adding missing lines from an E60 is otherwise very safe to do. I tried enabling all of the lines in the configuration file that would provide additional functionality. Some worked, some added nothing as there are other changes are needed to enable a function. The camera at no time crashed as a result of my changes. You are just activating functions already in the firmware.... if they have the required support files, they work. If the support files or other settings are missing, they do not work, simple if you stick with the contents of a Mk1 E60 configuration file contents, you are very safe

Note that some options in the configuration file actually restrict the cameras functionality so do not activate PiP lock or anything that appears to be restriction. Some of the config lines that are either already a active (True) or that you make active have a line below them with the ending 'Int' these set the valuecassociated with the function above. In the case of measurement functions, this setting can set the number of spot temperatures or measurement boxes you can have on the screen. Take a look at my configuration file and compare your "Int" values.  I have multiple spot and box measurements. I also enabled circle measurement areas and special functions like the Sketch capability that lets you use the touch screen to draw on a saved image to highlight a point of interest when doing a survey. I enabled image editing and any other useful features I found. Take a close look at my configuration file. You can actually use my complete configuration file in your camera provided you edit the serial number and calculate the CRC01 for your serial number and configuration file.

Once you get used to editing the configuration files, you can have great fun  with them at low risk to to the camera. Just keep the camera set to RNDIS mode whilst playing as any issues are easily corrected in that mode using FileZilla and your file back-ups.

Have fun.

Fraser

[Zucca]

2. The higher the temperature range, the lower the thermal sensitivity. This is normal and shown in the E60 specifications when it switches between Range 1 and Range 2. Perfectly normal and not a problem. The reason is that the bias voltages on the microbolometer are changed to allow the sensor array to cope with higher temperatures. The most highest sensitive of the sensor array is at lower temperatures where the bias voltages are carefully set to provide best performance. As the temperature capability rises, the bias voltages are moved away from that optimum performance setting. Just a fact of life with Microbolometers.

Many many thanks! This is a game changer information for me. I always understood the bigger the range the better it is but I was not considering the noise factor.
If I understood it correctly the 0-350 have less noise than the 0-650. If this is the case then I prefer the 0-350 as I don't need every day the >350 range, but I need less noise as possible! It's a trade off.

Regarding the calibration parameters I found this:
http://u88.n24.queensu.ca/exiftool/forum/index.php?topic=4898.60

which is cool!
Don't want to go up to 1200 C, I am scared to melt the camera...  the 1200 range is for the Flir TXX Cameras.

Anyway the service menu is bombastic! You can add lens, modify calibrations add ranges.... do want you want! Now I understood why the FW is the key!

I will play with video and with all your settings Fraser stay tuned!

[Fraser]

Hi Zucca,

There are normally three microbolometer bias voltage sets used to cover low, medium and high temperature ranges on thermal cameras capable of such.

I forget the switch points but Range 1 usually tops out at around 120C and Range 2 usually covers up to around 650C, as found on the E60. Range 3 usually extends coverage up to around 1000C. Range 3 has pretty low sensitivity figures due to the less than optimal bias voltages on the pixels.

In your case I do not know whether FLIR set the range 2 bias voltages for a 650C maximum temperature, and calibrated to 350C, or whether they tuned the Range 2 Bias voltages to be optimum for a 350C maximum. A check of the difference between Range 1 and Range 2 sensitivity on the E60 and E30 may suggest what FLIR has done. The increased noise injection on the E30 spec hopefully does not muddy the waters too much. We are looking at Delta Sensitivity here. I will take a look.

Fraser

[Fraser]

Hmmmm FLIR choose to not detail the difference in sensitivity on the different ranges. That is unhelpful. Agilent provide that data on their camera specs.

Fraser

[Zucca]

There are normally three microbolometer bias voltage sets used to cover low, medium and high temperature ranges on thermal cameras capable of such.

So if the bias voltage is the same, also the noise is the same? In this case if the same bias is used in the 0-350 and 0-650 then the noise is the same in the two ranges... oh well... I really don't need the 650 range...

[Fraser]

Yes

Fraser

[joe-c]

Hey Guys,

i am not finish with my observations about the Config stuff, but i have some info's...
i never used the Webpanel to activate Calibration cases, i use the calib.rsc directly.

Therefore my E40bx has all 3 Cases, one of them need a Filter, see here:
https://www.infraredcamerawarehouse.com/flir-high-temperature-option-1200-c-2192-f-t197000/

Additional you can adjust the Digital Filter settings, for the old Exx you need to adjust the Noise generator setting there... i also make some changes about the Spartial Filter and the Temporal filter... the Temporal filter will incase the Quality but make the framerate a bit lower.
Maybe you just have to look what you prefer (try with EX-Tools on the "Setup" Tabs).

See here a Comparison between Ex, Exx and Bxx, all enhanced to 320x240, the Exx has default filter setting, the Bxx has adjusted Setting, see results 
best wishes

Additional: you can just add some *.pal files in default folder. They are added to menu after restart and you have to add the name you want in:
FlashFS\system\ui.d\tml\languages\strings.en.xml

[Fraser]

Joe-C,

Thanks, as always, for the helpful input

Do you have the values you settled upon for the filters ? I may have a play with those as your 'tweaked' pictures are very nice It would be useful to know what you settled on in terms of filtering as a comparison with any experimentation I do with such.

I saw the high temperature upgrade advertised but could not see a physical filter shown. I also note in your referenced page that the shipping weight is zero. It is possible to bias a microbolometer to work up to 1200C so I have to wonder whether this is actually a payment for FLIR to enable and calibrate that range.

On the PAL file front ..... thanks for the tip. I intend to add some PAL files at some point and wondered about how I get them recognised by the system. Now I know

Fraser

[Zucca]

Thanks joe-c for the input,

Using the web service menu I was able to get this too:


The problem is the calibration. If that range was not calibrated at factory I see no use in activating the uncalibrated range.
I don't have the 650 range, but just the 350 calibrated. FYI Some user reported the 650 range calibrated in the E3x device but not activated, it´s another story.
A DIY calibration is out of dicussion for me. Trusted Fraser reported here in this therad some pics from FLIR calibrations labs...






so, I am not going in that direction.

when you select the 1200 range do you get readings which make sense? in other words, is the 200-1200 range on your device calibrated?

Anyway I don´t need the 0-650, my E8+ had 250 max, now I have 350 totally happy with that.

My todo list:

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

and this Spirit532 Menu hack (.jpg quality 100%, remove
flir logo):

https://www.eevblog.com/forum/thermal-imaging/flir-t440bx-hacking-firmware-investigation-possible-ultramax-support-for-exx/msg1421638/#msg1421638

also your SW and the tomas123`s one

tripod mount...

https://www.eevblog.com/forum/thermal-imaging/fraser-has-bought-his-new-favourite-daily-use-camera-the-flir-exx-love-it/msg1450338/#msg1450338

lens ... and so on...

[joe-c]

Do you have the values you settled upon for the filters ? I may have a play with those as your 'tweaked' pictures are very nice It would be useful to know what you settled on in terms of filtering as a comparison with any experimentation I do with such.

Shure, here my last settings:
.calib.nrdp.ds120C_we_ap_fi_le.alt.0.noiseGen.level int32 0
.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial.bilateral.sigma double 30
.calib.nrdp.ds120C_we_ap_fi_le.alt.0.temporal.level int32 16
.calib.nrdp.ds120C_we_ap_fi_le.alt.0.temporal.threshold int32 16

my regardings... rise the Sigma value will reduce the noise on uniform surfaces, but loose details.
rise the Temporal level will lower the noise, but add some "ghost Effect".
all other was just shortly tried and leaved as is.

for the other ranges use:
.calib.nrdp.ds650C_we_ap_fi_le.alt.0.noiseGen.level int32 0
the full set is:

Code: [Select]

.calib.nrdp.ds120C_we_ap_fi_le.alt.0.noiseGen.enabled bool true
.calib.nrdp.ds120C_we_ap_fi_le.alt.0.noiseGen.level int32 0
.calib.nrdp.ds120C_we_ap_fi_le.alt.0.qualityRanking int32 1
.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial entry
.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial.bilateral entry
.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial.bilateral.enabled bool true
.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial.bilateral.sigma double 30
.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial.column entry
.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial.column.enabled bool true
.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial.column.threshold int32 50
.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial.column.thresholdPix int32 80
.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial.edge entry
.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial.edge.enabled bool false
.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial.edge.gain double 0
.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial.offsetPixel entry
.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial.offsetPixel.altThreshold int32 0
.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial.offsetPixel.altThresholdArea int32 0
.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial.offsetPixel.altThresholdDiff int32 0
.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial.offsetPixel.apr bool false
.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial.offsetPixel.enabled bool false
.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial.offsetPixel.threshold int32 0
.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial.offsetPixel.thresholdArea int32 0
.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial.offsetPixel.thresholdDiff int32 0
.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial.offsetPixel.thresholdPix int32 0
.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial.row entry
.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial.row.enabled bool false
.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial.row.threshold int32 0
.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spatial.row.thresholdPix int32 0
.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spr entry
.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spr.enabled bool false
.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spr.threshold int32 0
.calib.nrdp.ds120C_we_ap_fi_le.alt.0.spr.thresholdTemp int32 0
.calib.nrdp.ds120C_we_ap_fi_le.alt.0.temporal entry
.calib.nrdp.ds120C_we_ap_fi_le.alt.0.temporal.enabled bool true
.calib.nrdp.ds120C_we_ap_fi_le.alt.0.temporal.level int32 16
.calib.nrdp.ds120C_we_ap_fi_le.alt.0.temporal.threshold int32 16
.calib.nrdp.ds120C_we_ap_fi_le.alt.0.temporalRow entry
.calib.nrdp.ds120C_we_ap_fi_le.alt.0.temporalRow.enabled bool false
.calib.nrdp.ds120C_we_ap_fi_le.alt.0.temporalRow.level int32 14
.calib.nrdp.ds120C_we_ap_fi_le.alt.0.temporalRow.limit int32 10250
.calib.nrdp.ds120C_we_ap_fi_le.alt.0.temporalRow.threshold int32 20
.calib.nrdp.ds120C_we_ap_fi_le.alt.0.type int32 100
.calib.nrdp.ds120C_we_ap_fi_le.calcNoise entry
.calib.nrdp.ds120C_we_ap_fi_le.calcNoise.factor double 286
.calib.nrdp.ds120C_we_ap_fi_le.calcNoise.temporalMkDefault double 20
.calib.nrdp.ds120C_we_ap_fi_le.measureInfo entry
.calib.nrdp.ds120C_we_ap_fi_le.measureInfo.spatialDu double 4.2782106
.calib.nrdp.ds120C_we_ap_fi_le.measureInfo.spatialMk double 20.633417
.calib.nrdp.ds120C_we_ap_fi_le.measureInfo.temporalDu double 4.6188022
.calib.nrdp.ds120C_we_ap_fi_le.measureInfo.temporalMk double 22.276059

[tomas123]

I'm looking for the old firmware 2.23.14 (Exx without MSX) .
The old link goes to current FW 2.27.16.
http://support.flir.com/SwDownload/app/RssSWDownload.aspx?ID=127

Can anybody upload the file flir_exx_pn490_v2.23.14_update_pack.zip from FLIR Exx P/N:490xx (2.23.14) Update Pack ?

Thanks for help.