I think we were all a bit surprised that the noise generator was active on the most expensive models, hence the concern about turning it off completely.
targetNoiseMk is a noise generator in mK (conforming with NETD/ thermal sensity in Flir Datasheets of the selected cam)
Formerly I stacked some noisy images with Registax or AviStax to subtract out the randomly noise and it works great!!
after setting targetNoiseMk to zero, stacking of images don't improve results
here a sample from a Flir E40 (old cam hacked formerly from 160x120 to 320x240)
in service menu I can measuring the noiseCode: [Select]rset .caps.config.image.targetNoise.targetNoiseMk 60 (MilliKelvin)
Temporal noise MilliKelvin Digital Units
Pixel Noise 61.28 12.13
Row Noise 14.84 2.94
Column Noise 13.67 2.71
Spatial noise MilliKelvin Digital Units
Pixel Noise 25.69 5.09
Row Noise 7.08 1.40
Column Noise 7.82 1.55
Uniformity 198.23 39.25
Total noise MilliKelvin Digital Units
Pixel Noise 67.01 13.27
Row Noise 9.71 1.92
Column Noise 10.10 2.00
and now without noise (cam temperature is 25 Grad):Code: [Select]rset .caps.config.image.targetNoise.targetNoiseMk 0 (MilliKelvin)
Temporal noise MilliKelvin Digital Units
Pixel Noise 19.85 3.93
Row Noise 6.39 1.26
Column Noise 8.64 1.71
Spatial noise MilliKelvin Digital Units
Pixel Noise 18.98 3.76
Row Noise 4.70 0.93
Column Noise 5.54 1.10
Uniformity 210.23 41.63
Total noise MilliKelvin Digital Units
Pixel Noise 28.96 5.73
Row Noise 5.76 1.14
Column Noise 7.66 1.52
see the differences (NETD is 0,03 °C @ 25°C)Quotehttp://gs.flir.com/surveillance-products/surveillance-technology/imaging-technotes/IR_Technology_Parameters
Uncooled infrared cameras systems are typically a little noisier, in the range of 30 - 120mK. Noise in an image can be spatial or temporal.
Spatial noise is noise across the image at any given point in time. It is perceived as an unchanging fixed pattern on top of the image.
Temporal noise is noise at any point in the image over time. It is perceived as the static that moves in an image.
NETD is typically the measure of both these noise types.
remarkably Flir dont't disable the noise generator at the top cams of a serie (Flir E4 -> E8 , Flir E30 -> E60)
#
# Generated at 2011-04-28 17:34:36
#
.caps entry
.caps.config entry
.caps.config.name text "app E60"
...
.caps.config.image.targetNoise entry
.caps.config.image.targetNoise.enabled bool true
.caps.config.image.targetNoise.targetNoiseMk int32 40
...
# ID 490xxxxx
\>rls .registry.caps.config.image.targetNoise
enabled true
targetNoiseMk 0
\>rls .system.tempsens
TSBoard 317.285
TSFpa 316.633
TShutterDigFilt1 322.03729
TShutterDigFilt2 0
// Service Menu
Temporal noise MilliKelvin Digital Units
Pixel Noise 17.50 1.63
Row Noise 11.02 1.02
Column Noise 9.59 0.89
Spatial noise MilliKelvin Digital Units
Pixel Noise 12.51 1.16
Row Noise 2.71 0.25
Column Noise 4.32 0.40
Uniformity 178.43 16.59
Total noise MilliKelvin Digital Units
Pixel Noise 17.86 1.66
Row Noise 4.81 0.45
Column Noise 5.89 0.55
site:eevblog.com/forum/thermal-imaging/flir-e4-thermal-imaging-camera-teardown MilliKelvin Spatial noise
only this postOn my 1.19.8 F/W model, I've got a temporal noise of 14.899144 mK in the calibration file. Added 05/27/2015: F/W 1.19.8, H/W 1.1. May add row / Column noise later... Added 05/29/2015: Well, here it is, right from the internal test and calibration menu:Code: [Select]Temporal noise MilliKelvin Digital Units
Pixel Noise 15.19 1.29
Row Noise 9.81 0.83
Column Noise 9.11 0.77
Spatial noise MilliKelvin Digital Units
Pixel Noise 9.55 0.81
Row Noise 2.58 0.22
Column Noise 4.49 0.38
Uniformity 207.72 17.66
Total noise MilliKelvin Digital Units
Pixel Noise 13.36 1.14
Row Noise 5.26 0.45
Column Noise 5.26 0.45
Hi, I have a FLiR E30 which I imported from a U.S. Supplier and its the full 30 fps version.
I would like to know if anyone else has done the E30 to E60 "conversion" on a 30 fps unit without it being then restricted to 9 fps. I can't find an explicit reference to fps in the config files ( I could have missed it ).
I don't know if the frame rate is hardware or software limited, but I would assume (don't like doing that) if it is a security requirement that it would be set by the hardware. Does anyone know this for sure?
Thanks
I just sold my e4 that I had upgraded to an e8 to buy a e30bx that the person sold as hacked to an e60, and it is but the bluetooth when turned on shuts itself off in about 1 second so no bluetooth is possible, and the wlan can not connect to even open networks. I already backed up everything and my thoughts where to start from scratch but the info is not nearly as complete as doing an e4 so I was wondering if maybe there was something else to try before starting at the beginning. Thanks!
Hey guys,
Got my E4 today, its the following:
model: E4 1.2L
part number: 63901-0101
Software 2.3.0
Is this good for doing the hack?
Well I connected to the service menu 192.168.02 and it just shows the * sign at the spot where the bluetooth/wifi module is, so I guess I might not have the actual hardware in mine like some people have had. Mine is one of the last built of the e30bx units sept. 2013 in case someone is looking at buying one. I didn't really need the bluetooth just wanted it if you know what I mean.
Well I connected to the service menu 192.168.02 and it just shows the * sign at the spot where the bluetooth/wifi module is, so I guess I might not have the actual hardware in mine like some people have had. Mine is one of the last built of the e30bx units sept. 2013 in case someone is looking at buying one. I didn't really need the bluetooth just wanted it if you know what I mean.yes, this will be the case. Somewhere (can't find it now) a serial # range was posted so you can check upfront if a E30 will come with or without the hardware for bluetooth and wifi.
Forget the e4... Get the new FLIR X6900sc with 1000 fps
Is it possible to modify the E40bx to a E60 and get the +650*C range or will it me limited to +120*C as the E60bx?
Is it possible to modify the E40bx to a E60 and get the +650*C range or will it me limited to +120*C as the E60bx?
You can enable new ranges in the service section of the camera (plug it in to PC via USB and go to 192.168.0.2 in Internet explorer).
Any new ranges that are added are not calibrated, thus the readings can be inaccurate.