Flir E4 Thermal imaging camera teardown

[Bud]

Just added the new menu hack and when selecting 3 spots nothing really happens.  The circle target is a little to the left on the screen as if it's stuck.  Is that normal?

See my post #6302 what it should be

[lofitohifi]

Got my E4 yesterday with the zoro 30% discount
1.2L V 2.30
After 1hr the resolution hack was perfectly working. 
Thanks for all your work and information!!
(Didn't dare to work on menus yet)

edit:
Menu now installed - perfect  -  thanks janekivi!!

[janekivi]

Just added the new menu hack and when selecting 3 spots nothing really happens.  The circle target is a little to the left on the screen as if it's stuck.  Is that normal?

This is normal when you do not apply correctly conf.cfc patch.

[blaster]

Just added the new menu hack and when selecting 3 spots nothing really happens.  The circle target is a little to the left on the screen as if it's stuck.  Is that normal?

This is normal when you do not apply correctly conf.cfc patch.

No errors were shown and it did appear successfully updated.
Do I have to get my backup "conf.cfc" and try again?  Will this cause any errors since it has already been applied.

Is there anything else I need to do before I reply the menu?

[sky@eevblog]

Just added the new menu hack and when selecting 3 spots nothing really happens.  The circle target is a little to the left on the screen as if it's stuck.  Is that normal?

I had the same experience when I used conf.cfc from hi-res hack backup (from Python backupxxxx folder) instead of conf.cfc from camera. So I reapplied hi-res hack and then got right conf.cfc from camera for janekivi Python script.

[janekivi]

Simple situation when conf allowing only one spot

rls .caps.config.image.sysimg.measureFuncs.spot.maxCount

You must miss something more in menu too.

[blaster]

Just added the new menu hack and when selecting 3 spots nothing really happens.  The circle target is a little to the left on the screen as if it's stuck.  Is that normal?

I had the same experience when I used conf.cfc from hi-res hack backup (from Python backupxxxx folder) instead of conf.cfc from camera. So I reapplied hi-res hack and then got right conf.cfc from camera for janekivi Python script.

I used the "conf.cfc" from the camera with the hack res applied not the one which Python created in backup folder.  I believe the one that's in the backup folder is the original one from Flir.

In my case it must be something else I did wrong along the way.

Damn so close.

[blaster]

This is interesting I retraced my steps and I found out that I used my "conf.cfc" which didn't have the res hack.
After trying one more time I finally got it to work.
Below is the installation being completed successfully.

Connected
Installation started...
Adding /FlashBFS/system/arctic.pal
Adding /FlashBFS/system/lava.pal
Adding /FlashBFS/system/rainhc.pal
Adding /FlashBFS/system/bootlogo_legal.bmp
Adding /FlashBFS/system/appcore.d/factory.d/ui_control.rsc
Adding /FlashBFS/system/ui.d/presets.d/preset_centerHotColdSpot.rsc
Adding /FlashBFS/system/ui.d/presets.d/preset_centerspot.rsc
Adding /FlashBFS/system/ui.d/presets.d/preset_coldspot.rsc
Adding /FlashBFS/system/ui.d/presets.d/preset_deltaSpot.rsc
Adding /FlashBFS/system/ui.d/presets.d/preset_deltaTemp.rsc
Adding /FlashBFS/system/ui.d/presets.d/preset_fiveSpots.rsc
Adding /FlashBFS/system/ui.d/presets.d/preset_hotColdSpot.rsc
Adding /FlashBFS/system/ui.d/presets.d/preset_hotspot.rsc
Adding /FlashBFS/system/ui.d/presets.d/preset_nomeasure.rsc
Adding /FlashBFS/system/ui.d/presets.d/preset_threeSpots.rsc
Adding /FlashBFS/system/ui.d/presets.d/preset_twoHotSpots.rsc
Adding /FlashBFS/system/ui.d/toolbar-config.xml
Adding /FlashBFS/system/ui.d/design_ui.xml
Adding /FlashBFS/system/ui.d/facet.rcc
Process local command: SHOW "Camera will now restart",7
User selected YES
Camera command restart
Close TELNET link
Process local command: DISCONNECT
Disconnecting...
Camera update completed

Now it works and thanks to janekivi for helping me out and all his hard work and other that pinched in.

[Taucher]

Another step accomplished - .rcc is extracted 

deRcc attachment is the code used to unpack - repacking should work somehow like that

Thanks. Also, typo in instructions. That should be qmake -project && qmake && make (not -profile).

Can someone help compile this and post back a ready to use executable?

I did use debian/ubuntu and did use apt-get to install the QT-development environment - It didn't make sense to setup the whole stuff on windows too (just to make a binary for unpacking a file that needs unpacking just once).

Qmake is from the QT-development env - so as soon as you have a working QT development environment set up, then you can make use of the code. Hope that helps a bit.

(yes, I read backlog and know this is "ancient")

[Taucher]

I need help. I don't know yet anything about files I am using. These are from first 2.3.0Menu_Upgrade.zip
They are smaller than inside ADDMENU-BETA3. Who made them or who can make them? I can't use
ADDMENU-BETA3, in 2.3.0 camera picture is black. But something I can't do here. That manual temp
scale is fighting back. And there is black holes in conf.cfc files. What might be after
.caps.config.image.zoom.maxFactor double 8 to the # IDXXXXXX? Somehow PIP too is not cooperative
with me... Or something is blocked in UI/conf.cfc whose contents I have no clue... yet
All other stuff might be done in near future.

I believe Taucher was the guy who did the magic on the first menu patch. Haven't seen too many posts from him
as of late, hope he is still out there!! Nice work BTW Janekivi!!

Yep and thanks - menu goes on me, but the real work was done by FLIR - they just disabled stuff in order to make the Ex product less attractive (what a design goal ... market segmentation bulls***) ... I've just suspected that if they crippled the resolution, then they probably had crippled other functions as well... and guess what - so it was.
The most troubling parts were the missing preset files because it seems the multi-spot-programs were constructed in a somehow exotic fashion - caused lots of lockups until that cause was identified.
There's also the "advanced measurement" mode where one can define boxes and stuff.. but that's even worse (crashy) and more intended for cameras in static setups and industrial applications (measure average of surface and similar tasks)...

Regarding manual scale: I've read in the update notes that Flir factory-enabled this in the E8 branch ... so it could be tied to the device-string or product-string in newer firmwares... there is direct binary access to the res-tree from within the running binaries - wouln't be hard for Flir to implement a mechanism to override any config files on boot this way.

[Taucher]

Actually there is 1372 different combinations of use now.
4 - Image mode
7 - Measurement
12 - Colors (Gray and White hot is the same but you want always "more" : ) )
4 - Zoom

Does anybody know the difference between this and the good old Taucher menu mod done on the FW 1.19.x?
https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg326024/#msg326024

Flir did change the firmware to increase protection/checksumming/encryption of the config files, they have removed some entry-vectors - and as far as I can tell there were also some changes made to internal data-structures (res-tree incl. names).

If you don't have 1.x firmware running then just don't bother with the older files unless you're trying to understand about some historic inner workings of the camera - but be aware of internal structural changes between the FW releases.

[arekm]

Hi there. I am a newbie and didn't mean to double post, but it seems the Newbie Q&A thread is not as active as this one.
I am about to purchase an E4B and I would like to know if it can be hacked the same way as the E4. Thank you!

Here E4B is almost 1/5 cheaper than regular E4... Unfortunately I didn't find any information about hacking state of E4B, too.

[janekivi]

I think I use other menu files for this year release.
Must learn unpacking and packing.
Small peek in 2015 menu for 2.3.0 E4
How to edit saved images.

[Sofia]

janekivi TUNING
:-)
Super

[janekivi]

I have here Ic_Colorize_PalettePredator_Def.png
You remember this film... Schwarzenegger... Minigun = no forest
Where I can get this palette? Or can someone make this?

[Bud]

I think I use other menu files for this year release

We want, as Billy Gibbons of ZZ Top said, "the old stuff, the new stuff, and everything in between"
 

Small peek in 2015 menu for 2.3.0 E4

Please tell us this all works
 

[janekivi]

Sometimes I can move added box and sometimes no.
Arrows are reserved to scale which is manual by default or something...
Centering working always, and other buttons too - cancel, save, delete, select...
If I holding down archive button it forces camera to Calibrate.
I think there is possible to use some button for my "zoom popup" idea...

In Exx you must hold finger on touch.
That table adding to image is working too but... touch screen keyboard...

[Zucca]

If you don't have 1.x firmware running then just don't bother with the older files unless you're trying to understand about some historic inner workings of the camera - but be aware of internal structural changes between the FW releases.

Taucher! Good to see you again! Let me put it in a easy way. Did you upgraded your HW1.0 E4 to the 2.3.x FW? If not do you believe it is possible without getting stuck with the low resolution for the rest of my days?

The new janekivi menu looks attractive... and my mouth is watering...

[Prodigy]

[...]
In native 2.3.0 you can get to the menu but cannot change selection. If we could find a way to unlock that menu that would be great.

Just a thought for a workaround:
You were able to set the image quality to 100 with those measuring spot preset files. Maybe it's possible to use this for RNDIS as well? Might not be the best solution but I think that would be still better than using FIF files all the time.
Something like: No spot = RNDIS+UVC, Center spot = UVC+MSD

In Set_RNDIS_Permanent.fif a new file with following commands is generated:

Code: [Select]

.system entry
.system.usbmode text "RNDIS"So you should only have to add those lines to the preset files as you desire.

And in the ressource tree the following possible values are listed:

Code: [Select]

.system: (17)
[...]
rw--r---r---1p*2 root   root   <a> usbmode              "RNDIS_UVC"
                 ["RNDIS" "MSD" "UVC" "RNDIS_UVC" "RNDIS_MSD" "UVC_MSD" "RNDIS_UVC_MSD"]
[...]
I think there's a good chance this will work

Hi guys,
My first post here and I think it might save you all some time.
instead of loading/unloading any temp or permanent RNDIS FIF file, try holding the right button while powering up your camera from a cold state, this will take you straight into RNDIS mode 
Good luck

[janekivi]

I can't set usb mode in hidden menu.
But I captured this video from usb after some hacking.
With phone cam it was bit fuzzy
E4 2015 beta menu

[joe-c]

Hi guys,
My first post here and I think it might save you all some time.
instead of loading/unloading any temp or permanent RNDIS FIF file, try holding the right button while powering up your camera from a cold state, this will take you straight into RNDIS mode 
Good luck

you welcome,

nice... I never noted this before. I tried it with my 1.19.8 Camera and it brings the camera in the Black-Screen-Mode (RNDIS is active, no Password, Files in FlashBFS are not in use...).
Good to know 

[FredB]

Wow Janekivi,
if you make something, you make it perfect. 
It looks like you did something wonderful again.
The E4 is turned into an E.....9.....10...11?
 

[Emoticon]

This is for anyone else out there who may not have played with one of those focus tools people were making early in this thread... I had one made and shipped to me today... WOW my focus was significantly off from the factor! My outdoor images are razor sharp now compared to what they used to be. For anyone else out there I can say you might end up like me and have a camera with significantly messed up focus and not even really know it. It was totally worth the $12 it cost me to have one of these printed it's almost like it's own resolution hack by itself!

[Fraser]

@Emoticon,

Have you read my E4 Useful information thread ?It includes some comment on the E4 focus point. Fixed focus simple lenses as used in the E4 are a compromise between sharp focus in the near and far field. You may well have had a poorly set lens but have you checked the focus at the specified minimum focus distance ? It is possible to set a sharp focus at infinity and totally mess up the lens focus at closer distances.

I hope you have achieved an improvement in your cameras focus but it is worth checking for negative effects of such a 'tweek'.

Aurora

[Bud]

instead of loading/unloading any temp or permanent RNDIS FIF file, try holding the right button while powering up your camera from a cold state, this will take you straight into RNDIS mode 
Good luck

Thanks for the information. I could not get it to work though on my 2.3.0, but may be I am doing it wrong. I can see the black screen and the camera seems to go to RNDIS but does not activate a proper IP. Can you give a bit more details as to what the cold state is and if a USB cable should be connected or not when doing this. Thank you.