FLIR E4 Wifi Resolution and Menu Hack Thread

[Fraser]

If you have Firmware 2.11, I recommend you hack that firmware and do not upgrade the firmware first.

2.11 is far easier to upgrade and manipulate. Later firmware does not offer any bug fixes, just different countermeasure types.

Fraser

[peppy88]

You can still add whatever palette you want. It is just not possible to add it to the toolbar if it is not included in facet_ui_qml.dll.

Just look at flashbfs/system/appcore.d/factory.d/default_params.rsc where it loads iron.pal (or palette.rsc in flashfs/system/appcore.d/factory.d for older firmware.)

It might be also possible to add a different palette to a preset in a newer firmware (look at flashbfs/system/ui.d/presets/*.rsc.) I didn't try it -- lots of other things of higher priority -- but it might work. And if everything else fails it might be possible to just set .image.sysimage.palette.* resource branch with whatever you want using rset.

BTW, flashbfs/system/appcore.d/factory.d/ui_control.rsc reads MULTIPLE Qt external resource files by using "facet_*.rcc" and the same is true for menu design (" design_ui*.xml") that would probably allow adding additional properly named resource/menu design files with user elements.

I might be wrong but I have a strong gut feeling that those settings can be simply added to regular user config files...

Hmm does anyone know what the available options are in the facet_ui_qml.dll. Even better yet. How do you decompile the facet_ui_qml.dll, what software do you use?

[peppy88]

I was able to make some sense of the dll. I used "Hex Fiend" and found this: (I don't think bw.pal/ color_gray is being used)

bwcold.pal
bwhot.pal
lava.pal
arctic.pal
medical.pal
bw.pal
rainhc.pal
rainbow.pal
iron.pal

ID_HUMIDITYIc_Colorize_IsothermHumidity
ID_HUMIDITY_HEADERID_HUMIDITY_ATMOSPHERIC_TEMP
ID_HUMIDITY_RELATIVE_HUMID_HUMIDITY_RELATIVE_HUM_LIMIT
ID_INTERVALIc_Colorize_IsothermIntervalcolor_iso_interval
ID_BELOW
Ic_Colorize_IsothermBelowcolor_iso_below
ID_ABOVE
Ic_Colorize_IsothermAbove
.image.sysimg.measureFuncs.isotherm.1color_iso_above
ID_COLOR_BLUE_BELOW
Ic_Colorize_PaletteGrayColdBlue
*color_blue_below
ID_COLOR_RED_ABOVE
Ic_Colorize_PaletteGrayHotRed
*color_red_above
ID_LAVA
Ic_Colorize_PaletteLava
*color_lava
ID_ARCTIC
Ic_Colorize_PaletteArtic
*color_arctic
ID_BLACK_HOT
Ic_Colorize_PaletteGrayHotBlack
*color_gray_hot_black
ID_GRAY
color_gray
ID_WHITE_HOT
Ic_Colorize_PaletteGrayHotWhite
*color_gray_hot_white
ID_MEDICAL
Ic_Colorize_PalettePredator
*color_medical
ID_RAINBOW_HC
Ic_Colorize_PaletteRainbowHighColor
*color_rainbow_hicolor
ID_RAINBOW
Ic_Colorize_PaletteRainbow
*color_rainbow
ID_IRON
Ic_Colorize_PaletteIron
*color_iron
ID_RECORDING_MODE_SPORT
Ic_Options_RecordingModeTimeLapse

[giovannirat]

One more question from my side.

I've upgraded the software to Release 2.11.0.

But I noticed that the temperature display in the upper left corner was different from what I've seen on different web sites.
Is this normal or is there some problem (the camera works flawlessly) on my Flir E4?

Since SW Release 2.1. there is a separation between the temp itself and the temp unit (see pictures).


I want to apply the resolution and menue hack, but I'm not sure, if it's safe.....

Should I reinstall the 2.11.0 SW Release?

Any help appreciated.

[cq-317]

This is no problem with the sw 2.11 of your e4.you don't need  reinstall sw 2.11.

It's very easy to liberate your E4. This is very mature in version 2.11. If you follow the documentation carefully, there is no risk. The thread you are entering now is the e4 wifi version, which is different from your E4 hardware. Please refer to the following link to liberate your E4.

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

[forrestc]

I looked through the thread and couldn't find what I think is the definitive answer to this...

Are the currently shipping Flir E4 Wifi's (aka from Amazon) upgradeable?   (Realizing that things could have changed since the last data point).

[cq-317]

The latest version is known to be 3.13 and it can liberated.

[Bud]

You can create an account on Flir support portal and check the latest published firmware update version.

[rocky79]

Hello,

I found an E4 wifi version with firmware version 3.9.0. Is it possible to downgrade it to version 2.11 for the hack?

[Simkins]

Sorry if I’m missing something however I cannot find the instructions for liberating my Flir E4 that’s on its way from Amazon. I recently read through the 30 pages and see that it can be done and also see people referring to a step by step guide however I cannot find the post. Can someone help?

[Bud]

The link is in the very first post of this topic.

[Simkins]

Thank you - links don’t open on my mobile devices. I will complete the procedure when I return from vacation / have access to a computer. Donation to follow.

[Simkins]

Hi everyone - moving along with the liberation of my E4 - I'm having an issue with Step 6/7.

I downloaded / extracted the "cfccfg_v2.py" file however when opening in "IDLE" (Python) I cannot see the "# ID" section to add my SUID.

Hoping someone can point me in the right direction - thanks very much.

[Bud]

I have forgotten some things but isn't SUID entered as a command line argument when you run the script? Not sure what you mean by saying "cannot see #ID.

[Simkins]

It’s the step right before the command line. Believe I am to open the Phython file and insert my SUID at the bottom where it says “# ID” per the notes file in the download. Sorry if I’m misinterpreting.

[Bud]

You do not touch the .py script file. It is some other file you need to edit, read the instructions carefully again. I am not in front of my computer at the moment but i think it is the template configuration file provided in the down.oad that you need to update  with your camera serial number. Also do not confuse SUID with the Serial Number, they are different values. The instructions should say where to get SUID and where to get S/N.

[PRBG]

Thank you Bud for the files in #478.
Basic Package works for Flir E4, WiFi 2.0L, firmware v3.13.0.
I have a question - What includes the Advanced Package (from the same Reply) and it is compatible with v3.13.0 as well?

Thank you!

[Bud]

Advanced you need to load and try, i cannot remember, it was a year ago, sorry.
I do not have a 3.13.0 device, so i do not know.

[PRBG]

Thank you, Bud! I have tried the Advanced package and it works on 3.13.0!
It added the new Medical Palette, Edit Image options and new Measurement settings.

[victorhooi]

I recently purchased a Flir E4 WiFi. Model is E4 2.0L and firmware version out of the box was 3.12.0

However - I didn't realise this till later but it came set to 320x240 already. How is that possible?

I performed the steps in the Basic guide, then realised that the resolution actually looked worse. I connected the camera via USB, and looked at the images, and noticed that the resolution was now 80x60 but the old images were 320x240.

So I reverted back the conf.cfc and common_dll.dll file, and rebooted the camera. I left the other files (e.g. palette etc) in place. The camera is now back to 320x240.

However,  I don't have the mode that shows hot/cold/centre spots at the same time - which is something I wanted.

My questions are:

• Has anybody heard of this, where a new E4 is already set to 320x240? Any explanations?
• Is it safe to not apply the conf.cfc and common_dll.dll changes, but apply the other changes?
• What is the purpose of the updated common_dll.dll file?
• Is there some way to get simultaneous hot/cold/centre spot mode measurements? Is this part of the advanced package or something?
• Is there a safe way to apply the advanced changes? The Advanced instructions talk about running the Python config script again - I assume this will break my unit back to 80x40?

[Bud]

Chances are you did not perform the Basic procedure properly. There were several people in this thread who experienced low res during or after update and it was because of errors or misinterpretation of the instructions. They all got it right in the end as far as we know. Low res and broken menu are the symptoms of such errors because the camera could not load the config file.

[victorhooi]

Right - but why would the resolution out of the box, before any changes be 320x240?

[eKretz]

It's not. The photo that it puts out is 320x240 pixels, but the camera is only utilizing an 80x60 portion of the thermal sensor and upscaling that to 320x240.

[Bud]

You have to check the Thermal resolution using Flir tools, archive button on the camera or programs like Exiftool. Looking at the files in standard File Explorer gives you upscaled image resolution, not Thermal one.

[Vipitis]

Flir Tools also displays incorrect resolution on Lepton images from like FLIR ONE or CAT S60.