Author Topic: Flir E4 Thermal imaging camera teardown (Read 3803720 times)

flir-ID10T · « **Reply #4500 on:** March 23, 2014, 06:19:32 am »

Hi, I received the flir E4 this past Friday. I have read and watched the resolution upgrade video, and tried to install the resolution upgrade. when I install the tools1 conf.cnc, I get the high resolution, but I lose the center spot, the MSX, and the picture (photo) is black. I have looked and found that It may be due to not unplugging and pulling the battery. I re installed the original resolution, and tried again this time unplugging and pulling the battery. I keep getting the same issue with the center spot, no msx and no digital camera. Their is no zoom. the resolution is excellent on the upgrade, but for my work, I need the other features.

I have the menu upgrade via the ADDMENU Beta3, and all but a few of the additional features work fine with the original resolution; I have msx, digital photo, and center spot. I think a few functions do not work, but I am not too concerned with them; some measurement tools, the delta T...)

I have a flir e4 1.21.0 e4 1.1L.
here is the conf.cnc template:

# Generated at 2013-10-25 09:37:31
#
.caps entry
.caps.config entry
.caps.config.name text "app E8"
.caps.config.revision text "1.1"
.caps.config.image entry
.caps.config.image.framegrab entry
.caps.config.image.framegrab.fusion entry
.caps.config.image.framegrab.fusion.enabled bool true
.caps.config.image.framegrab.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.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.IRwidth int32 320
.caps.config.image.settings.IRheight int32 240
.caps.config.image.sysimg entry
.caps.config.image.sysimg.alarms entry
.caps.config.image.sysimg.alarms.enabled bool true
.caps.config.image.sysimg.alarms.measfunc entry
.caps.config.image.sysimg.alarms.measfunc.enabled bool true
.caps.config.image.sysimg.alarms.measfunc.maxCount int32 3
.caps.config.image.sysimg.alarms.humidity entry
.caps.config.image.sysimg.alarms.humidity.enabled bool true
.caps.config.image.sysimg.alarms.humidity.maxCount int32 1
.caps.config.image.sysimg.alarms.insulation entry
.caps.config.image.sysimg.alarms.insulation.enabled bool true
.caps.config.image.sysimg.alarms.insulation.maxCount int32 1
.caps.config.image.sysimg.irMarkers entry
.caps.config.image.sysimg.irMarkers.enabled bool true
.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 4
.caps.config.image.sysimg.irMarkers.box entry
.caps.config.image.sysimg.irMarkers.box.enabled bool false
.caps.config.image.sysimg.irMarkers.box.maxCount int32 0
.caps.config.image.sysimg.measureFuncs entry
.caps.config.image.sysimg.measureFuncs.enabled bool true
.caps.config.image.sysimg.measureFuncs.diff entry
.caps.config.image.sysimg.measureFuncs.diff.enabled bool true
.caps.config.image.sysimg.measureFuncs.diff.maxCount int32 1
.caps.config.image.sysimg.measureFuncs.diff.calcMask int32 65526
.caps.config.image.sysimg.measureFuncs.isotherm entry
.caps.config.image.sysimg.measureFuncs.isotherm.enabled bool true
.caps.config.image.sysimg.measureFuncs.isotherm.calcMask int32 20
.caps.config.image.sysimg.measureFuncs.isotherm.dual bool false
.caps.config.image.sysimg.measureFuncs.isotherm.fixScale bool false
.caps.config.image.sysimg.measureFuncs.isotherm.interval bool true
.caps.config.image.sysimg.measureFuncs.isotherm.invInterval bool false
.caps.config.image.sysimg.measureFuncs.isotherm.maxCount int32 1
.caps.config.image.sysimg.measureFuncs.mbox entry
.caps.config.image.sysimg.measureFuncs.mbox.enabled bool true
.caps.config.image.sysimg.measureFuncs.mbox.calcMask int32 1924
.caps.config.image.sysimg.measureFuncs.mbox.maxCount int32 5
.caps.config.image.sysimg.measureFuncs.mcircle entry
.caps.config.image.sysimg.measureFuncs.mcircle.enabled bool false
.caps.config.image.sysimg.measureFuncs.mcircle.calcMask int32 1924
.caps.config.image.sysimg.measureFuncs.mcircle.maxCount int32 0
.caps.config.image.sysimg.measureFuncs.mline entry
.caps.config.image.sysimg.measureFuncs.mline.enabled bool false
.caps.config.image.sysimg.measureFuncs.mline.calcMask int32 1924
.caps.config.image.sysimg.measureFuncs.mline.maxCount int32 0
.caps.config.image.sysimg.measureFuncs.reftemp entry
.caps.config.image.sysimg.measureFuncs.reftemp.enabled bool true
.caps.config.image.sysimg.measureFuncs.reftemp.calcMask int32 1924
.caps.config.image.sysimg.measureFuncs.reftemp.maxCount int32 1
.caps.config.image.sysimg.measureFuncs.script entry
.caps.config.image.sysimg.measureFuncs.script.enabled false
.caps.config.image.sysimg.measureFuncs.script.maxCount int32 0
.caps.config.image.sysimg.measureFuncs.spot entry
.caps.config.image.sysimg.measureFuncs.spot.enabled bool true
.caps.config.image.sysimg.measureFuncs.spot.calcMask int32 514
.caps.config.image.sysimg.measureFuncs.spot.maxCount int32 5
.caps.config.image.sysimg.visualMarkers entry
.caps.config.image.sysimg.visualMarkers.enabled bool true
.caps.config.image.sysimg.visualMarkers.spot entry
.caps.config.image.sysimg.visualMarkers.spot.enabled bool false
.caps.config.image.sysimg.visualMarkers.spot.maxCount int32 0
.caps.config.image.sysimg.visualMarkers.arrow entry
.caps.config.image.sysimg.visualMarkers.arrow.enabled bool true
.caps.config.image.sysimg.visualMarkers.arrow.maxCount int32 4
.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.contadj entry
.caps.config.image.contadj.minSpanFactor entry
.caps.config.image.contadj.minSpanFactor.enabled bool true
.caps.config.image.contadj.minSpanFactor.factorAuto double 2.0
.caps.config.image.contadj.minSpanFactor.factorManual double 2.0
.caps.config.image.targetNoise entry
.caps.config.image.targetNoise.enabled bool true
.caps.config.image.targetNoise.targetNoiseMk int32 5
.caps.config.image.zoom entry
.caps.config.image.zoom.enabled bool true
.caps.config.image.zoom.maxFactor double 8
.caps.config.system entry
.caps.config.system.focus entry
.caps.config.system.focus.laser entry
.caps.config.system.focus.laser.updateFocus entry
.caps.config.system.focus.laser.updateFocus.enabled bool true
.caps.config.ui entry
.caps.config.ui.fusion entry
.caps.config.ui.fusion.PIP entry
.caps.config.ui.fusion.PIP.enabled bool true
.caps.hw entry
.caps.hw.sdcard entry
.caps.hw.sdcard.enabled bool false
# ID 6391xxxx
# CRC03 8071xxxx

Any help would be most appreciated.

Thanks.

Rainer · « **Reply #4501 on:** March 23, 2014, 08:26:30 am »

If msx and digital-cam didn´t work, there is a problem with your patched/generated config-file. The TIC has a "fail-safe"-mode, if the configFile is corrupt(checksum, last CR-LF-Charakter, ID etc.)

Tauchers BETA do not touch the config. So his special menue-option will work partly(some options working "stand-alone" and some options are in the FLIR-System and need the patched e8-config)

Rainer · « **Reply #4502 on:** March 23, 2014, 08:57:41 am »

Quote from: tomas123 on March 22, 2014, 09:22:33 am

user uski own an e30bx
https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg397343/#msg397343

Do you compared your settings with my config file?
https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg371680/#msg371680

I compared my config with your file. Your config has some differences.

special parameters of your E40-TIC:

.caps.config.image.sensor entry
.caps.config.image.sensor.enabled bool true

.caps.config.image.settings.downsample bool false
.caps.config.image.settings.resIR int32 320

special parameters, which are only in E8 and not in your E40-TIC:

.caps.config.image.settings.IRwidth int32 320
.caps.config.image.settings.IRheight int32 240

.caps.config.image.contadj entry
.caps.config.image.contadj.minSpanFactor entry
.caps.config.image.contadj.minSpanFactor.enabled bool true
.caps.config.image.contadj.minSpanFactor.factorAuto double 2.0
.caps.config.image.contadj.minSpanFactor.factorManual double 2.0

.caps.hw entry
.caps.hw.sdcard entry
.caps.hw.sdcard.enabled bool false
@mike: is there any HW-Option for a micro-SD in the TIC?

The set-to-false-parameters, in both config-files are:

.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.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.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.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.script entry
.caps.config.image.sysimg.measureFuncs.script.enabled false
.caps.config.image.sysimg.measureFuncs.script.maxCount int32 0

.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.box entry
.caps.config.image.sysimg.visualMarkers.box.enabled bool false
.caps.config.image.sysimg.visualMarkers.box.maxCount int32 0

My question is, what options are "behind" this parameters? are there some extras in the TIC? In the datasheet of the e60bx are "insulation performance alarm", "scaleable or moveable PIP-IR-selection" an rotation of the picture (if you use the TIC lateral or upside-down). And the rotation-option i had in my TIC too, but in a "SW-bug"-condition

tomas123 · « **Reply #4503 on:** March 23, 2014, 12:04:31 pm »

Exx

I'm not a feature junkie. So I tested only functions, which I'm interested in.

I only found the rotation option in the hidden menu. It's not public.

Here are the data sheets for the E60bx

old version 2012: http://www.mrtestequipment.com/getfile.php?s=FLIR+E60bx+Thermal+Camera+Data+Sheet.pdf
new version 2013: http://www.flir.com/uploadedFiles/Thermography_USA/Products/Product_Literature/flir-e-series-bx-datasheet.pdf

this is interesting

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.

with my config files I can change the PiP size smooth over the touch screen
if required: as workaround for MSX I zoom the PiP to fullscreen, then takes the PiP images and convert the image with flir tools to a MSX image

stefbeer · « **Reply #4504 on:** March 23, 2014, 01:46:32 pm »

Since so many people seem to struggle with generating their own conf.cfc , I took the time and wrote a quick'n'dirty (well, not really quick but still a bit dirty) GUI for the tools in AutoIt. See the attached .zip .
I did some testing and everything should work. Also most errors should be handled. But ("sadly"

) I only have an E4 with firmware 1.19.8 , but maybe someone could do some testing by herself / himself and give me some feedback.

@ flir-ID10T : Maybe this will help you.

DaveWB · « **Reply #4505 on:** March 23, 2014, 06:01:09 pm »

Quote from: stefbeer on March 23, 2014, 01:46:32 pm

Since so many people seem to struggle with generating their own conf.cfc , I took the time and wrote a quick'n'dirty (well, not really quick but still a bit dirty) GUI for the tools in AutoIt. See the attached .zip .
I did some testing and everything should work. Also most errors should be handled. But ("sadly" ) I only have an E4 with firmware 1.19.8 , but maybe someone could do some testing by herself / himself and give me some feedback.

@ flir-ID10T : Maybe this will help you.

Nice work!

pomonabill221 · « **Reply #4506 on:** March 23, 2014, 06:04:57 pm »

Thanks for your detailed work and screenshots!
I know not ALL the people that are trying to "improve" their Ex's find the procedure 'easy" or "familiar", so when someone explains the procedure or creates a video or a script to help out, it is very much appreciated!

Thanks again to all that have helped out.

heavybarrel · « **Reply #4507 on:** March 23, 2014, 06:11:28 pm »

@pomonabill221
Just curious how you made out with the resizing of the measurements box waayyyy back on page 163!
I would like to do the same thing and was curious what your results were. And yes, i agree, great work on the GUI
version!!

flir-ID10T · « **Reply #4508 on:** March 23, 2014, 07:21:28 pm »

Quote from: stefbeer on March 23, 2014, 01:46:32 pm

Since so many people seem to struggle with generating their own conf.cfc , I took the time and wrote a quick'n'dirty (well, not really quick but still a bit dirty) GUI for the tools in AutoIt. See the attached .zip .
I did some testing and everything should work. Also most errors should be handled. But ("sadly" ) I only have an E4 with firmware 1.19.8 , but maybe someone could do some testing by herself / himself and give me some feedback.

@ flir-ID10T : Maybe this will help you.

stefbeer,

Thank you So much. I ran your zip tool under post (« Reply #4548 on: Today at 12:46:32 AM »).

I ran your zip tool, installed the easily generated conf.cfc, ran it into the flir, unplugged, pulled battery, and restarted. Everything works. All options appear to be working; center spot, camera, MSX, as well as pip, zoom, humidity setting.....

Thank you so much, and it definitely worked on my flir e4 1.21.0 e4 1.1L. # ID 639168xx.

I can't begin to thank you enough. I spent two days reading post, watching videos, and could not get it to work.

you are Awesome!

preacher · « **Reply #4509 on:** March 24, 2014, 06:31:32 am »

I made the upgrade and camera seems to work fine. However, I don't seem to be able to connect again in filezilla with the given ftp info(i.e. IP, name, and password). Any ideas for me? I get a timeout.

DaveWB · « **Reply #4510 on:** March 24, 2014, 08:48:36 am »

Quote from: preacher on March 24, 2014, 06:31:32 am

I made the upgrade and camera seems to work fine. However, I don't seem to be able to connect again in filezilla with the given ftp info(i.e. IP, name, and password). Any ideas for me? I get a timeout.

Did you try a coldboot on the camera?

Fraser · « **Reply #4511 on:** March 24, 2014, 11:33:39 am »

Information direct from FLIR on the E4 microbolometer

As I previously posted, I wrote to FLIR regaring temperature stability. Today I received a very helpful response to my questions. I asked them if the microbolometer in the E4 is temperature stabilised with a TEC and whether the camera will cope with an ambient temperature of 50 Degrees Celcius. I further asked what type of microbolometer was installed.

The response surprised me. As ever FLIR were very helpful on the tech side, but I was not expecting what was stated in the comments. I reproduce the response here:

There is nothing particular about 30?C besides the fact that most cameras happen to be running at 30-35?C during the production process. It is very probable that they will produce good accurate readings under such conditions. The assumption that they must deteriorate under other conditions is perhaps likely, but definitely not always true. It all depends on how fast and well the temperature drift stabilization math copes with the changed conditions. In Ex, a standard compensation is being used, and it will work better in some cameras and worse in others.

Since the Ex cameras do not contain any germanium optics (which starts to get dim at about 50?C), nothing drastic is expected to happen with the accuracy above 50?C. But, you are then using the camera outside of the specification limits.

To answer your questions: The Ex detector is not stabilized in any way. Neither heated nor cooled. The Ex detector is made of Vanadium Oxide.

So there you have it, from the people who know, the E4 is running bareback without ANY temperature stabilisation of the microbolometer. From a TIC design point of view this is interesting as I was aware that maths could be used to remove the need for the TEC but I was not expecting it in the E4. The comment on the issues of Germanium optics was very interesting. I was already aware that Germanium lenses start to lose transmission efficiency at 100 Degrees Celcius and above. As we know the Ex series uses the Chalcogenide-Glass lens material that obviously does not suffer such effects, or less so anyway. Without testing, I cannot say how well the maths algorithms map the microbolometer drift but FLIR are experts in the field so it may do a half decent job on SOME cameras.

My thanks to FLIR for responding on these questions so fully, so that I have a better understanding of my E4 cameras limitations. If I am working in high temperature environments, I will use the PM695's.

Aurora

tjb1 · « **Reply #4512 on:** March 24, 2014, 12:40:38 pm »

I'm finally about to get my E4 and was reading about the hack and was wondering if Tauchers Menu Hack is still used/needed? I see it added PIP, color tables, and some other stuff and most that do the hack on the newer units mention these features being useable already. Is this menu hack now included in the template files?

DaveWB · « **Reply #4513 on:** March 24, 2014, 12:56:18 pm »

Quote from: tjb1 on March 24, 2014, 12:40:38 pm

I'm finally about to get my E4 and was reading about the hack and was wondering if Tauchers Menu Hack is still used/needed? I see it added PIP, color tables, and some other stuff and most that do the hack on the newer units mention these features being useable already. Is this menu hack now included in the template files?

Taucher's menu hack still works on the 1.21 and 1.22, I believe you also have to do the resolution hack for all the menu hack features to work. If you're looking to order one I got mine from calright instruments (calright.com) and he gave me a discount. The menu hack is not in the template files, you just transfer the system folder in FlashBFS in filezilla to the FlashBFS folder on the cam to overwrite the existing system folder.

inline · « **Reply #4514 on:** March 24, 2014, 02:26:37 pm »

So I've sent like 6 emails at least to LuneValley3D trying various methods, the contact form and the direct email address with never a reply back. I also tried sending from different email addresses in case on was getting flagged as spam. Quite frustrating. Shapeways wants like $30 to print the lens holder. I did try to PM a forum member who said he'd print them for $5+ship, but still no word back from him after many days.

Does anyone know of a place that can print the lens holder for me at a reasonable cost? Thanks!

muvideo · « **Reply #4515 on:** March 24, 2014, 02:29:36 pm »

lunevalley3d answered pretty fast to me on the second try, the first attempt
was ignored. Maybe they have some strong antispam or other email problems.ù
I'm waiting their prints to arrive.

tjb1 · « **Reply #4516 on:** March 24, 2014, 02:59:04 pm »

Quote from: inline on March 24, 2014, 02:26:37 pm

So I've sent like 6 emails at least to LuneValley3D trying various methods, the contact form and the direct email address with never a reply back. I also tried sending from different email addresses in case on was getting flagged as spam. Quite frustrating. Shapeways wants like $30 to print the lens holder. I did try to PM a forum member who said he'd print them for $5+ship, but still no word back from him after many days.

Does anyone know of a place that can print the lens holder for me at a reasonable cost? Thanks!

Scratch that, printer is currently on its mood swing.

Brickmaster · « **Reply #4517 on:** March 24, 2014, 04:18:23 pm »

Quote from: DaveWB on March 24, 2014, 08:48:36 am

Quote from: preacher on March 24, 2014, 06:31:32 am
I made the upgrade and camera seems to work fine. However, I don't seem to be able to connect again in filezilla with the given ftp info(i.e. IP, name, and password). Any ideas for me? I get a timeout.
Did you try a coldboot on the camera?

I am struggling with the same problem. I was able to log in to the first screen just twice in 50+ attempts, always hanging up and timing out. Is there another way to go about this without using filezilla? While this is quickly humbling me, I had hoped the process would be simpler as greater minds than mine have seemed to grasp.

Gallymimus · « **Reply #4518 on:** March 24, 2014, 05:10:26 pm »

some basic networking knowledge might be helpful/needed.

Make sure the network adapter that is created when you have RNDIS mode turned on is present under network settings in control panel. Make sure that the IP address is set properly (probably 192.168.0.1). I think that the IP address auto sets after some time, but explicit setting might be more effective and reliable.

also before connecting with filezilla see if you can ping the camera (from a command prompt: ping 192.168.0.2). If you can't ping it, you won't be able to connect to it with FTP.

I had a few problems getting it working and it was always related to basic networking problems, but the hiccups were pretty minor.

BTW, I didn't verify that my memory of the right IP addresses above are in fact the correct ones. I'll update this if I got them wrong.

bookaboo · « **Reply #4519 on:** March 24, 2014, 05:16:14 pm »

I helped a friend modify at the weekend, we had connection issues until we figured 192.168.1.2 was the IP in use by the E4.
Was a laptop running some version of Windows 7, E4 was v1.22.0.

pomonabill221 · « **Reply #4520 on:** March 24, 2014, 06:05:04 pm »

Quote from: heavybarrel on March 23, 2014, 06:11:28 pm

@pomonabill221
Just curious how you made out with the resizing of the measurements box waayyyy back on page 163!
I would like to do the same thing and was curious what your results were. And yes, i agree, great work on the GUI
version!!

Hi HB!
Yes, it did work out pretty well, but there is a "bug" so to speak.... when going from delta T or delta S to center/hot/cold setting, the window defined by the bounding box is only half as tall as it should be, but re-selecting the same setting loads the correct window height. Strange!

Changing from any other setting to C/H/C doesn't show this problem, so for me it is not an issue and is an easy fix.

This only seemed to happen when the box was over a certain size as the original size worked fine.

The first pic (pic1) shows the delta T box, the second pic shows the C/H/C selected and the problem (note the lower two bounding corners are half height), and the third pic shows AFTER re-selecting C/H/C and pressing the center button (if you just "esc" out of the menu, the problem isn't fixed). The upper left bounding box does overlay the temp display, but I wanted the larger box size

Also, I find that after a cold boot, the default menu selection is the temperature scale, but after a warm boot, the last menu selection is still selected. I would imagine that there is a setting for default menu?

Brickmaster · « **Reply #4521 on:** March 24, 2014, 07:42:57 pm »

Okay, with a few deep breaths, re-reading through everything, and another cold boot - IT WORKS! Thank you so much to everyone. Now I need to learn to interpret the output, and use it to it's best abilities.

By the way, Firmware is 1.22.0, Serial #: 639171xx.

Special thanks to DaveWB for the video and StefBeer for the GUI.

heavybarrel · « **Reply #4522 on:** March 24, 2014, 08:17:36 pm »

Quote from: pomonabill221 on March 24, 2014, 06:05:04 pm

Quote from: heavybarrel on March 23, 2014, 06:11:28 pm
@pomonabill221
Just curious how you made out with the resizing of the measurements box waayyyy back on page 163!
I would like to do the same thing and was curious what your results were. And yes, i agree, great work on the GUI
version!!
Hi HB!
Yes, it did work out pretty well, but there is a "bug" so to speak.... when going from delta T or delta S to center/hot/cold setting, the window defined by the bounding box is only half as tall as it should be, but re-selecting the same setting loads the correct window height. Strange!

Changing from any other setting to C/H/C doesn't show this problem, so for me it is not an issue and is an easy fix.

This only seemed to happen when the box was over a certain size as the original size worked fine.

The first pic (pic1) shows the delta T box, the second pic shows the C/H/C selected and the problem (note the lower two bounding corners are half height), and the third pic shows AFTER re-selecting C/H/C and pressing the center button (if you just "esc" out of the menu, the problem isn't fixed). The upper left bounding box does overlay the temp display, but I wanted the larger box size

Also, I find that after a cold boot, the default menu selection is the temperature scale, but after a warm boot, the last menu selection is still selected. I would imagine that there is a setting for default menu?

Pomonabill221!
Thanks for the reply! I am assuming you had to change the box dimensions in the .rsc file for each of the menu items? By that i mean, hot spot, cold spot, center/hot/cold, etc, .rsc files. If you didn't maybe that is where the glitch is coming from?? I also am guessing you went the telnet route to get it done. How great would it be to just be able to use the keypad up, down, left, and right to re-size the box in real time!!! Wish i had the coding skills for that!!!
In tauchers post about where in the file to find the box dims it looked like there was an option to place its x and y origin as well. Assuming that is the center of the box you might be able to bump yours over a bit to the right to get it away from the measurement display on the left! (If it bugs you that is)
Another huge thanks to Taucher for helping with this one!! Is there anything that guy doesn't know how to do with this camera? I am a tad jealous of his ninja like skills! Glad that worked out for you! Maybe a little fine tuning and those dreaded bugs will go away! Please keep me posted if you decide to go further with it, i would appreciate it very much.

MrRedHat · « **Reply #4523 on:** March 24, 2014, 08:51:31 pm »

I got a 1.21.0 firmware version one today. Calibration date is 3-11-2014. I tried the hack and I think it is working. When I went to Camera information it still says it’s an E4, not sure if it’s supposed to change.

I will have to play around with it some more.

heavybarrel · « **Reply #4524 on:** March 24, 2014, 09:03:56 pm »

It will always say E4 in the cameras info screen. If you look back in the thread quite a way it shows how change the model.
Keep in mind it will only show the change in flir tools, not on the cam itself.


EEVblog Main Site	EEVblog on Youtube	EEVblog on Twitter	EEVblog on Facebook	EEVblog on Odysee

Poll

Has the hackabiliy of the E4 made you buy one :

Author Topic: Flir E4 Thermal imaging camera teardown (Read 3803720 times)

Share me