if anyone is still afraid to permanently hack his\her i3\i5 here is simple step by step guide
read post #524 https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg321956/#msg321956
1. power on camera
2. press menu button once
3. press play (gallery) button for 5 seconds
4. switch to RNDIS usb mode
5. install flir drivers on your pc
6. connect camera to pc, give it a minute to install and start
7. connect to camera's ftp server at 192.168.0.2 user:flir password:3vlig with ftp client capable of passive mode i.e. total commander
8. make full backup of filesystem to a secure location
9. download mike's crc01 tool from this https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg321956/#msg321956 post
10. install some proper text editor i.e. notepad++ (and enable showing all characters in view \ show symbols)
11. open backup\FlashFS\system\appcore.d\config.d\conf.cfg
12. remove last line that saysCode: [Select]# CRC01 ????????
13. replace number at the end of ||.caps.config.image.settings.resIR int32 X|| with value from ||.caps.config.image.settings.fpgaResolution.resIR int32 X||*
14. save changes as new file
15. use crc01 to calculate checksum of this file
16. open backup\FlashFS\system\appcore.d\config.d\conf.cfg file again, do the same resolution modification and replace checksum with calculated one
17. save changes as new file that you will upload to camera (in extra step i have changed attributes and date & time of new file to be the same as old one, but this is most likely unnecesary)
18. connect to ftp again, and upload created file overwriting one that sits in \FlashFS\system\appcore.d\config.d\conf.cfg (or check mike's post just under this one and let us know)
19. unmount & disconnect camera, use reset button in battery compartment to reboot it
it worked for me, i don't take any responsibility for anything but merely sharing what i did described as good as i could, do it at your own risk
*Code: [Select]* Z-cam has a detector with 80x80, 120x120 or 144x144 pixels.
.calib.lens.leExFOL7: (23)
C1 0.00982
C2 0.0424
clearanceDistance 0.04
descr "FOL7"
fNumber 1.5
focLen 6.57
isMeasured false
refTTransmission 0.94
theta 0.33983691
If someone figures out a 30hz mod this would be perfect.
Actually that one would be a real nasty problem as it would turn the camera to a "dual use" item that can be treated just like "arms/weapons" - so it would fall under trade restrictions and mean that any applicable government would have to take special care about the camera... guess how good that would be...
Matter of fact: If you buy one of the higher spec'ed 30/60Hz cameras, then you'll be politely asked to explain(fill out a form) the security measurements against theft etc. - thus preventing some foreign intelligence person from easily stealing the camera, shipping/smuggling it to some "axis of evil" and turning the sensor into a missile guidence system, unwanted airborne defense or hell knows what else (yeah, what horrible threat such a thermal camera must be ).
Well, this of cause assumes that a whole "enemy" country (usually that's one that didn't attack somebody else yet) will stay offline, dumb and will fail to produce any high-tech on it's own... but I guess the intention is to make it for them as difficult as possible (for a while)...
For best accuracy you do have to wait for the moment where it finishes its internal calibration.
I found that you can initiate the calibration by pressing the play button for 5 seconds
If someone figures out a 30hz mod this would be perfect.
Actually that one would be a real nasty problem as it would turn the camera to a "dual use" item that can be treated just like "arms/weapons" - so it would fall under trade restrictions and mean that any applicable government would have to take special care about the camera... guess how good that would be...
Matter of fact: If you buy one of the higher spec'ed 30/60Hz cameras, then you'll be politely asked to explain(fill out a form) the security measurements against theft etc. - thus preventing some foreign intelligence person from easily stealing the camera, shipping/smuggling it to some "axis of evil" and turning the sensor into a missile guidence system, unwanted airborne defense or hell knows what else (yeah, what horrible threat such a thermal camera must be ).
Well, this of cause assumes that a whole "enemy" country (usually that's one that didn't attack somebody else yet) will stay offline, dumb and will fail to produce any high-tech on it's own... but I guess the intention is to make it for them as difficult as possible (for a while)...If I remember correctly a few (or many) pages back in this thread it was determined that those restrictions apply to sensors over a certain number of pixels and framerate. Wise to check this again.
I think the map compensates for the lens vignetting, not for the supposed non-uniform black body...
I have used a model of modern military cryo' cooled thermal camera that had a manual dead pixel detection and correction mode. I was surprised when I used that mode as I could see all the dead pixels in the 320x240 detector array. The image looked just like that of the E4.
Only path loss changes. No reason for any calibration issues with re-focussing lens
1. Lens is same
2. Detector is same
3. Illumination of detector by lens is same
4. Path loss changes but not mentioned by FLIR as a calibration issue for this camera
Adding an auxiliary lens does introduce more path loss as the ZnSe does not have 100% transmission and over illuminates the primary lens area (not matched to primary lens). Effect is minor in the real world and easily measured for compensation factor table.
The non hacked E4 did not offer a manual span mode. The auto mode did have a span of approx. 8°C as minimum.
If someone figures out a 30hz mod this would be perfect.
Actually that one would be a real nasty problem as it would turn the camera to a "dual use" item that can be treated just like "arms/weapons" - so it would fall under trade restrictions and mean that any applicable government would have to take special care about the camera... guess how good that would be...
Matter of fact: If you buy one of the higher spec'ed 30/60Hz cameras, then you'll be politely asked to explain(fill out a form) the security measurements against theft etc. - thus preventing some foreign intelligence person from easily stealing the camera, shipping/smuggling it to some "axis of evil" and turning the sensor into a missile guidence system, unwanted airborne defense or hell knows what else (yeah, what horrible threat such a thermal camera must be ).
Well, this of cause assumes that a whole "enemy" country (usually that's one that didn't attack somebody else yet) will stay offline, dumb and will fail to produce any high-tech on it's own... but I guess the intention is to make it for them as difficult as possible (for a while)...If I remember correctly a few (or many) pages back in this thread it was determined that those restrictions apply to sensors over a certain number of pixels and framerate. Wise to check this again.I don't think this is the case - ISTR that the lower resolution for >9fps is something silly like 32 pixels. There was a recent (2009) change to regs for cams with <111,000 pixels but I didn't read far enough to figure out exactly what changed - I don't recall seeing any framerate references. There is a link to some relevant docs either somewhere in this thread or the "buying E4 in Australia" thread
I bought a refurbished E30 from flir about a year ago. My decision was based on the ability to focus the lens which was not available on the lower priced units.
Anybody looking into an E30 upgrade ? I am sure that the higher end models, like the E60 are just firmware settings as well.
Anybody looking ??
Paul
The non hacked E4 did not offer a manual span mode. The auto mode did have a span of approx. 8°C as minimum.
That's the answer then! 8°C vs 4°C as a minimum temperature span equates to doubled the temperature difference required on the display to discern the difference... that means hacking the E4 allows a thermal sensitivity of 1/2 the original E4.
2 Degrees span is very useful. If it can be enabled then I recommend it.
.caps.config.image.contadj.minSpanFactor.factorAuto double 2.0
.caps.config.image.contadj.minSpanFactor.factorManual double 2.0
Just noticed in the standard e8 hack .cfg file
Quote
.caps.config.image.contadj.minSpanFactor.factorAuto double 2.0
.caps.config.image.contadj.minSpanFactor.factorManual double 2.0
Yet it's limiting to 4 Maybe it's +/-2?