Author Topic: FLIR E4 Teardown Q/A and newbie questions  (Read 45176 times)

0 Members and 1 Guest are viewing this topic.

Offline Gallymimus

  • Regular Contributor
  • *
  • Posts: 174
  • Country: us
FLIR E4 Teardown Q/A and newbie questions
« on: March 27, 2014, 03:32:53 PM »
This topic is for questions and answers that are not related to technical development or NEW understanding of the FLIR Ex and Exx thermal camera systems.

This isn't a promise that I will answer your questions but hopefully myself and many others will be will to answer here instead of in the main thread.

I've gotten a lot of private messages asking for help so it's probably better that we get them in the public so everyone can benefit from input and advice.

Please start by reading this post: http://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg309194/#msg309194

It is a great culmination of instructions and procedures.  If you ask a question that is answered easily by reading the above post or a few of the links provided in that post you will probably get a cold response here. 

That said this should be a thread for helping people who might not have enough technical knowledge to execute the instructions on the main thread.
 

Offline Gallymimus

  • Regular Contributor
  • *
  • Posts: 174
  • Country: us
Re: FLIR E4 Teardown Q/A and newbie questions
« Reply #1 on: March 27, 2014, 03:33:20 PM »
Blank Page for future use if needed.
 

Online Fraser

  • Super Contributor
  • ***
  • Posts: 6741
  • Country: gb
Re: FLIR E4 Teardown Q/A and newbie questions
« Reply #2 on: March 31, 2014, 03:14:07 AM »
@Gallymimus,

Thanks for starting this thread  :-+

I hope it gets used.
 

Offline Gallymimus

  • Regular Contributor
  • *
  • Posts: 174
  • Country: us
Re: FLIR E4 Teardown Q/A and newbie questions
« Reply #3 on: March 31, 2014, 03:15:32 AM »
@Gallymimus,

Thanks for starting this thread  :-+

I hope it gets used.

We'll see!  We should be diligent in pushing questions over here, and then being kind in answering them.  To bad we don't have mods who can help push stuff into different topics.
 

Offline mago

  • Contributor
  • Posts: 12
Re: FLIR E4 Teardown Q/A and newbie questions
« Reply #4 on: April 02, 2014, 08:33:32 PM »
hi guys,

a newbie question abour IRCameraTools:
i'm trying to install the free IRCameraPlayer 2.3.3 (last version on flir website).
When launched, it tries to install some runtime envroiment, which are already on my pc, until it tries to install "Bonjour for windows" which ends to a "there already a more recent version of Bonjour installed" THEN it comes to the main install window where there's the list of runtimes to install: bonjour is still there, and checked (i cannot uncheck). Clicking "next" button make it try to install it again, error and back again to the starting window.
So i cannot install this tool due to this stupid bug...? Any help?

Thanks!
 

Offline Gallymimus

  • Regular Contributor
  • *
  • Posts: 174
  • Country: us
Re: FLIR E4 Teardown Q/A and newbie questions
« Reply #5 on: April 02, 2014, 08:46:14 PM »
Did you try uninstalling bonjour first.  You should also try FLIR tech support
 

Offline pts

  • Newbie
  • Posts: 3
  • Country: se
Re: FLIR E4 Teardown Q/A and newbie questions
« Reply #6 on: April 02, 2014, 08:52:36 PM »
hi guys,

a newbie question abour IRCameraTools:
...? Any help?

This may not be the right place ask about flir software.

You have a better chance to get a better  answer if you give some more information about the camera and what  OS and version etc... your are using.
 

Offline mago

  • Contributor
  • Posts: 12
Re: FLIR E4 Teardown Q/A and newbie questions
« Reply #7 on: April 03, 2014, 12:59:45 AM »
So i cannot install this tool due to this stupid bug...? Any help?

Just to tell i done it by unistalling bonjour and letting its own to be installed.

PS to make it work, i set USB mode to "RNDIS and UVC", because on the MSD mode it won't be recognized
 

Offline Gallymimus

  • Regular Contributor
  • *
  • Posts: 174
  • Country: us
Re: FLIR E4 Teardown Q/A and newbie questions
« Reply #8 on: April 03, 2014, 02:11:13 AM »
So i cannot install this tool due to this stupid bug...? Any help?

Just to tell i done it by unistalling bonjour and letting its own to be installed.

PS to make it work, i set USB mode to "RNDIS and UVC", because on the MSD mode it won't be recognized

Glad it worked!  UVC being turned on makes sense.
 

Offline humdinger13

  • Contributor
  • Posts: 28
Can't get hack to work. Please help!
« Reply #9 on: April 08, 2014, 01:23:15 AM »
I finally got the connection issue taken care of by switching to another computer.  Apparently the 80070005 error relates to permissions problems in case anyone is wondering, but I don't have time to sort through all that.

I have a 1.22 unit, and I've tried the hack as shown in the video (short of the menu hack) countless times.  My first attempt resulted in better resolution, but loss of msx and ability to import images into flir tools.  Every other attempt resulted in no change in res or menu.  Then I decided to try the guitool.  I'm not sure I'm doing it right, but here is a sample from the most recent attempt:

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

yes, there is a line feed

uploaded resulting conf.crc to  flashfs/system/appcore.d/config.d


I don't know what I'm missing here, and hope someone can spot a problem.

I should note that at one point I noticed one of my antimalware programs was notifying me of some process that was trying to configure the "thermacam".  It was right around that time I happened to note the ip address had changed to 169..244 or something, and was no longer able to access the cam via ftp.  When I killed the process that was doing the configuring, I was able to access the cam again.

Could it be the camera phoning home and being secretly updated?

I have spent countless hours on this, and beg for mercy.  Thanks
 

Offline Gallymimus

  • Regular Contributor
  • *
  • Posts: 174
  • Country: us
Re: FLIR E4 Teardown Q/A and newbie questions
« Reply #10 on: April 08, 2014, 01:35:08 AM »
This is a bummer, but happens to most people who are doing the upgrade.  You have to have everything EXACTLY right and there isn't any feedback that it is wrong until you see the MSX missing.

did you unpack your original CFC file and get the proper UID strings and then use them again when packing your cfg to cfc?

When you created the CRC03 did the CFG file have a line feed AND carriage return at the end.

your final file should also have LF AND CR

I assume it is a type but you called it conf.crc instead of conf.cfc in your post.
 

Offline stefbeer

  • Regular Contributor
  • *
  • Posts: 57
  • Country: de
Re: FLIR E4 Teardown Q/A and newbie questions
« Reply #11 on: April 08, 2014, 01:44:34 AM »
uploaded resulting conf.crc to  flashfs/system/appcore.d/config.d
The file must be named "conf.cfc" but this just might be a typo, as Gallymimus said.

I don't know what I'm missing here, and hope someone can spot a problem.
As long as your serial number is correct, the file looks fine at first glance.

Could it be the camera phoning home and being secretly updated?
I also was a bit paranoid a while back  ;) but somebody (I think Mike) stated, that if they would secretly update the firmware of the camera and you would interrupt the process by removing the battery or something like that, then they would be in trouble. So I really doubt that.

As Gallymimus said, it's most certainly an issue with the CRC03 checksum, the linefeed or the SUID (there's not much left ;D ). If you can't get it to work by yourself and / or with the guitool, you could try this:
http://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg411505/#msg411505
Just make sure you use your own, original conf.cfc as input file. Any othe file might contain a wrong SUID.
« Last Edit: April 08, 2014, 01:48:56 AM by stefbeer »
 

Offline humdinger13

  • Contributor
  • Posts: 28
Re: FLIR E4 Teardown Q/A and newbie questions
« Reply #12 on: April 08, 2014, 02:41:58 AM »
This is a bummer, but happens to most people who are doing the upgrade.  You have to have everything EXACTLY right and there isn't any feedback that it is wrong until you see the MSX missing.

did you unpack your original CFC file and get the proper UID strings and then use them again when packing your cfg to cfc?

When you created the CRC03 did the CFG file have a line feed AND carriage return at the end.

your final file should also have LF AND CR

I assume it is a type but you called it conf.crc instead of conf.cfc in your post.

Yeah, that was a typo.  It is cfc not crc.  As for the line feed AND carriage return - I guess I'm not aware of the distinction between the two, but after entering the CRC number I would press enter and usually made sure there were no more characters.

What I found interesting is the different SUID's I got between the gui tool and the ftool method - but maybe it's just a data format issue, but they didn't resemble each other at all.  Thanks!
 

Offline humdinger13

  • Contributor
  • Posts: 28
Re: FLIR E4 Teardown Q/A and newbie questions
« Reply #13 on: April 08, 2014, 02:44:59 AM »
uploaded resulting conf.crc to  flashfs/system/appcore.d/config.d
The file must be named "conf.cfc" but this just might be a typo, as Gallymimus said.

I don't know what I'm missing here, and hope someone can spot a problem.
As long as your serial number is correct, the file looks fine at first glance.

Could it be the camera phoning home and being secretly updated?
I also was a bit paranoid a while back  ;) but somebody (I think Mike) stated, that if they would secretly update the firmware of the camera and you would interrupt the process by removing the battery or something like that, then they would be in trouble. So I really doubt that.

As Gallymimus said, it's most certainly an issue with the CRC03 checksum, the linefeed or the SUID (there's not much left ;D ). If you can't get it to work by yourself and / or with the guitool, you could try this:
http://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg411505/#msg411505
Just make sure you use your own, original conf.cfc as input file. Any othe file might contain a wrong SUID.

Thanks Stefbeer, not sure how I missed this and will give it a try! 
 

Offline humdinger13

  • Contributor
  • Posts: 28
Re: FLIR E4 Teardown Q/A and newbie questions
« Reply #14 on: April 08, 2014, 03:16:51 AM »
This is a bummer, but happens to most people who are doing the upgrade.  You have to have everything EXACTLY right and there isn't any feedback that it is wrong until you see the MSX missing.

did you unpack your original CFC file and get the proper UID strings and then use them again when packing your cfg to cfc?

When you created the CRC03 did the CFG file have a line feed AND carriage return at the end.

your final file should also have LF AND CR

I assume it is a type but you called it conf.crc instead of conf.cfc in your post.

Yeah, that was a typo.  It is cfc not crc.  As for the line feed AND carriage return - I guess I'm not aware of the distinction between the two, but after entering the CRC number I would press enter and usually made sure there were no more characters.

What I found interesting is the different SUID's I got between the gui tool and the ftool method - but maybe it's just a data format issue, but they didn't resemble each other at all.  Thanks!

Well, all I can say is your tool really simplifies things.  Still waiting to see if the file works.  Now I'm having trouble connecting again for some reason.  Thanks.  Will let you know how it goes when I get it uploaded..
 

Offline Gallymimus

  • Regular Contributor
  • *
  • Posts: 174
  • Country: us
Re: FLIR E4 Teardown Q/A and newbie questions
« Reply #15 on: April 08, 2014, 03:19:43 AM »


Yeah, that was a typo.  It is cfc not crc.  As for the line feed AND carriage return - I guess I'm not aware of the distinction between the two, but after entering the CRC number I would press enter and usually made sure there were no more characters.


CR and LF are very different things.  Different operating systems will treat them differently as well.  It comes from the old typewriter days.  CR returns the carriage to the beginning of the line, in a terminal program this would send you to the beginning of your current line and you could overwrite what you had typed on that line.

LF advances the next line but does not return you to the beginning of the line.  so your text would look like this if you only used LF

Code: [Select]
this is what I type
                   and after a LF
                                 I just keep moving down but after a CRLF
I end up back here

most modern text editors add a CRLF after each line.  a text editor like notepad++ can enable visibility of these special characters to see if it is all good.
 

Offline humdinger13

  • Contributor
  • Posts: 28
Re: FLIR E4 Teardown Q/A and newbie questions
« Reply #16 on: April 08, 2014, 03:48:13 AM »


Yeah, that was a typo.  It is cfc not crc.  As for the line feed AND carriage return - I guess I'm not aware of the distinction between the two, but after entering the CRC number I would press enter and usually made sure there were no more characters.


CR and LF are very different things.  Different operating systems will treat them differently as well.  It comes from the old typewriter days.  CR returns the carriage to the beginning of the line, in a terminal program this would send you to the beginning of your current line and you could overwrite what you had typed on that line.

LF advances the next line but does not return you to the beginning of the line.  so your text would look like this if you only used LF

Code: [Select]
this is what I type
                   and after a LF
                                 I just keep moving down but after a CRLF
I end up back here

most modern text editors add a CRLF after each line.  a text editor like notepad++ can enable visibility of these special characters to see if it is all good.

That makes sense.  I guess that hitting the enter key is actually both then, right. 

Still having trouble with uploading.  When I ping it returns "transmit failed.  General failure"  but then somehow it was assigned a new ip - 169.254.149.84 which a whois shows it's an iana  number..  My networking skills are a little rusty, this may take a while.

I appreciate your help!
 

Offline Gallymimus

  • Regular Contributor
  • *
  • Posts: 174
  • Country: us
Re: FLIR E4 Teardown Q/A and newbie questions
« Reply #17 on: April 08, 2014, 03:57:08 AM »
169.254 are reserved autoconfigure addresses, many computers/devices will fall back to that subnet if they can't get a DHCP address or don't have a static IP.

you can assign static address to your virtual network adapter on your computer in the same subnet as the camera (i.e. 192.168.1.10 or 192.168.0.10) I can't remember which subnet the camera is on by default.
 

Offline humdinger13

  • Contributor
  • Posts: 28
Re: FLIR E4 Teardown Q/A and newbie questions
« Reply #18 on: April 08, 2014, 05:30:10 AM »
Well, sad to say that this didn't work either I'm afraid.  That is a great tool for sure though!!  Anyone have any ideas? 

I will also mention that when I downloaded the camera files for a backup, ws-ftp failed on some empty directories, and in the process I may have missed some files, but I am fairly certain I am working off an original copy.  I did do a backup again with filezilla, but by then the files on the camera had changed.

Anyhow, I copied my original results from the cmd line processing, from the beginning, and the SUID's match so I think that is not the problem.

Thanks again.
 

Offline ixfd64

  • Frequent Contributor
  • **
  • Posts: 301
  • Country: us
    • Facebook
Re: FLIR E4 Teardown Q/A and newbie questions
« Reply #19 on: April 08, 2014, 05:35:01 AM »
I currently don't own a thermal imager, but I have a few questions:

1. The official bag for the FLIR E4 is quite expensive. Are there any third-party bags or pouches (not necessarily one designed for thermal imagers) that fits the E4 well?

2. What happens if the user tries to measure a temperature that is outside the E4's range? Is there an error message? Does the E4 try to give an approximation? Or does it indicate that the temperature is above 482°F or below -4°F?

Offline DaveWB

  • Regular Contributor
  • *
  • Posts: 118
Re: FLIR E4 Teardown Q/A and newbie questions
« Reply #20 on: April 08, 2014, 05:40:36 AM »
I currently don't own a thermal imager, but I have a few questions:

1. The official bag for the FLIR E4 is quite expensive. Are there any third-party bags or pouches (not necessarily one designed for thermal imagers) that fits the E4 well?

2. What happens if the user tries to measure a temperature that is outside the E4's range? Is there an error message? Does the E4 try to give an approximation? Or does it indicate that the temperature is above 482°F or below -4°F?
The hard case the camera comes with is pretty nice, it can hold an extra battery and external charger. I believe if you get too hot you start to ruin something within the camera, I believe that's what I read over on the teardown thread but I could be totally off.
 

Offline stefbeer

  • Regular Contributor
  • *
  • Posts: 57
  • Country: de
Re: FLIR E4 Teardown Q/A and newbie questions
« Reply #21 on: April 08, 2014, 05:41:06 AM »
@ humdinger13:
You could try to unprotect another *.cfc file from your backup with ftool, just to see if the SUID matches. Maybe you have overwritten the file before you made the backup? Or you have overwritten the file from your backup?
 

Offline humdinger13

  • Contributor
  • Posts: 28
Re: FLIR E4 Teardown Q/A and newbie questions
« Reply #22 on: April 08, 2014, 06:01:47 AM »
@ humdinger13:
You could try to unprotect another *.cfc file from your backup with ftool, just to see if the SUID matches. Maybe you have overwritten the file before you made the backup? Or you have overwritten the file from your backup?

Good idea - I thought about that too.  I did just confirm that my cfc with the timestamp of when I first backed up did make it, and does match  suid's.  I will see if I can verify using your recommendation.  Hopefully this can tell us something..
 

Online Fraser

  • Super Contributor
  • ***
  • Posts: 6741
  • Country: gb
Re: FLIR E4 Teardown Q/A and newbie questions
« Reply #23 on: April 08, 2014, 06:12:50 AM »
@ixfd64

When outside its measurement capability, the E4 places a ' * ' in front of the indicated temperature.

The microbolometer in the E4 is 'sun safe' and you would have to try pretty hard to burn out the VOX elements. it is possible to do if you are so inclined, but not in everyday use ! Don't worry about that as a likely risk of ownership. The microbolometer also carries a 10 year (tbc) guarantee.

The soft case for the E4 cost me GBP18 (~$30). Considering the highe quality of build and the protection it affords the camera, that isn't bad value for money. A standard large camcorder case would lilely hold the camera in the horizontal plane, but anything with decent padding will likely cost the same as the OEM ergonomic Ex case. It should also be remembered that even though the poch is classified as a soft case, it is in fact thick semi-rigid nylon coated laterial and this acts like an armour layer around a camera that is already pretty rugged.

I also own the soft case for the Exx series (E60 etc) and I must admit that it is my preferred case for the E4. The camera is much easier to insert and remove. The Ex case is a little too snug for my liking. If money is tight you could likely sell the decent quality hard case that comes with the E4 for the price of the Ex soft case so the soft case would not cost extra.
« Last Edit: April 08, 2014, 06:21:51 AM by Aurora »
 

Offline ixfd64

  • Frequent Contributor
  • **
  • Posts: 301
  • Country: us
    • Facebook
Re: FLIR E4 Teardown Q/A and newbie questions
« Reply #24 on: April 08, 2014, 06:16:26 AM »
@ixfd64

When outside its measurement capabiluity the E4 places a '*' in front of the indicated temperature.

So I guess it can approximate temperatures higher than 482°F or lower than -4°F. In that case, do you know what's the highest or lowest temperature the Ex series will display?
« Last Edit: April 08, 2014, 06:27:10 AM by ixfd64 »
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf