Author Topic: FLIR E4 Wifi Resolution and Menu Hack Thread  (Read 132141 times)

0 Members and 3 Guests are viewing this topic.

Offline frogg

  • Regular Contributor
  • *
  • Posts: 57
  • Country: us
Re: FLIR E4 Wifi Resolution and Menu Hack Thread
« Reply #850 on: August 23, 2019, 04:02:02 pm »
Did you restore UVC mode prior to the upgrade, or did you upgrade with the camera still in RNDIS mode?

One thing to try is to restore UVC mode. Check to make sure that your camera can still connect as a USB storage drive through UVC.

If that's still ok, THEN try switching to RNDIS mode again.
 

Offline likuidphreon

  • Contributor
  • Posts: 8
  • Country: us
Re: FLIR E4 Wifi Resolution and Menu Hack Thread
« Reply #851 on: August 24, 2019, 01:30:38 am »
The firmware upgrade was done while still in RNDIS mode (unfortunately).
I am unable to set the camera back to UVC mode either by way of the built-in camera menu or using FlirInstallNet with the fif file.
Running ipconfig I see the IP address I statically set for the RNDIS adapter (192.168.0.1) but there is NO gateway or device IP, so I cannot ping 192.168.0.2 as I first thought.
I have tried a factory reset on the device through its menu, still no change.
 

Offline frogg

  • Regular Contributor
  • *
  • Posts: 57
  • Country: us
Re: FLIR E4 Wifi Resolution and Menu Hack Thread
« Reply #852 on: August 24, 2019, 06:52:21 pm »
fyi the built in camera menu won't ever do anything :)

make sure you disable all your actual NICs so that RNDIS is the only active adapter.

There should be no gateway or statically set device IP (I've never seen either when doing my hack).

Manually set your machine IP to 192.168.250.1

Try to connect to 192.168.250.2 (the camera)

any luck that way?
« Last Edit: August 24, 2019, 06:56:44 pm by frogg »
 

Online Bud

  • Super Contributor
  • ***
  • Posts: 3530
  • Country: ca
Re: FLIR E4 Wifi Resolution and Menu Hack Thread
« Reply #853 on: August 26, 2019, 12:04:31 am »
to rule out some network variables, i'd suggest using a WinXP computer. Those always worked, not like Win 7 and can't even speak for Win 10
Facebook-free life and Rigol-free shack.
 

Offline FlirAl

  • Contributor
  • Posts: 14
  • Country: be
Re: FLIR E4 Wifi Resolution and Menu Hack Thread
« Reply #854 on: September 05, 2019, 07:36:02 am »
Hi everyone,
New member here.
I have a E6 WiFi on my way, supposed to arrive next week.
I know the serial 639022*** ,mfg date  January 31 2018  and product numbers 63907-0***.
Is there any way to kinnda foresee the FW type so I can start preparing the necessary files? It's a brand new unit, open case.

Al
 

Offline DaveWB

  • Regular Contributor
  • *
  • Posts: 141
Re: FLIR E4 Wifi Resolution and Menu Hack Thread
« Reply #855 on: September 09, 2019, 01:18:02 am »
Hmm, got a hold of an E5-xt, however when looking at the conf.cfc file, it doesn't seem like there is anything different than before. Maybe it's part of another file? Maybe it's a gimmick?
Code: [Select]
#
 # Generated at 2018-12-04 13:15:14
 #
.caps entry
.caps.config entry
.caps.config.name text "app E5xt"
.caps.config.revision text "2.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 160
.caps.config.image.settings.IRheight int32 120
.caps.config.image.sysimg entry
.caps.config.image.sysimg.alarms entry
.caps.config.image.sysimg.alarms.enabled bool false
.caps.config.image.sysimg.alarms.measfunc entry
.caps.config.image.sysimg.alarms.measfunc.enabled bool false
.caps.config.image.sysimg.alarms.measfunc.maxCount int32 3
.caps.config.image.sysimg.alarms.humidity entry
.caps.config.image.sysimg.alarms.humidity.enabled bool false
.caps.config.image.sysimg.alarms.humidity.maxCount int32 1
.caps.config.image.sysimg.alarms.insulation entry
.caps.config.image.sysimg.alarms.insulation.enabled bool false
.caps.config.image.sysimg.alarms.insulation.maxCount int32 1
.caps.config.image.sysimg.irMarkers entry
.caps.config.image.sysimg.irMarkers.enabled bool false
.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 false
.caps.config.image.sysimg.irMarkers.arrow.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 entry
.caps.config.image.sysimg.measureFuncs.enabled bool true
.caps.config.image.sysimg.measureFuncs.diff entry
.caps.config.image.sysimg.measureFuncs.diff.enabled bool false
.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 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.reftemp entry
.caps.config.image.sysimg.measureFuncs.reftemp.enabled bool false
.caps.config.image.sysimg.measureFuncs.reftemp.calcMask int32 1924
.caps.config.image.sysimg.measureFuncs.reftemp.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.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 1
.caps.config.image.sysimg.visualMarkers entry
.caps.config.image.sysimg.visualMarkers.enabled bool false
.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 false
.caps.config.image.sysimg.visualMarkers.arrow.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
.caps.config.image.targetNoise entry
.caps.config.image.targetNoise.enabled bool false
.caps.config.image.targetNoise.targetNoiseMk int32 0
.caps.config.image.zoom entry
.caps.config.image.zoom.enabled bool false
.caps.config.image.zoom.maxFactor double 1
.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 false
.caps.config.ui entry
.caps.config.ui.image entry
.caps.config.ui.image.adjust entry
.caps.config.ui.image.adjust.enabled bool false
.caps.config.ui.image.adjust.manual bool false
.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 639060xxx
 # CRC03 xxxxxxx
 

Offline FlirAl

  • Contributor
  • Posts: 14
  • Country: be
Re: FLIR E4 Wifi Resolution and Menu Hack Thread
« Reply #856 on: September 27, 2019, 06:32:42 pm »
Hi all,

first of all I need to thank to this beautiful community for making all this possible.

Got a E6 3.12 and successfully upgraded to the E8+ via wifi telnet  :-+ BUD.  The whole operation took like 3.5h, most of it looking around the forums for small bits of info. All hacking done via WIN 10 x64, no hiccups at all. I ll try to write a one big post with all the info and files that I used.

 small bits that bother me after :

---MXM alignment is off.  Looking over the forum I found solutions but the info is so scarce and scattered that it kinda freaks me out to try.

 Is the CRC32 of calib.rsc declared on an XML somewhere or is it only in the file? like if i want to correct it, do I only need to get the new CRC32 and write it on the file?

--- small bright spot appeared lower left, seems like dust or something INSIDE the sensor. Camera was factory calibrated 18/01/2018 so it's still on the warranty period :-X (of course with the E6 software)
see attach

Q. Is the charging via USB port reserved only to charge with the genuine charger? heard stories about people frying the charging IC with a regular 5V 1A microUSB charger


 
   
« Last Edit: September 27, 2019, 06:51:39 pm by FlirAl »
 
The following users thanked this post: 4cx10000

Offline negative_feedback

  • Contributor
  • Posts: 10
  • Country: cs
Re: FLIR E4 Wifi Resolution and Menu Hack Thread
« Reply #857 on: September 29, 2019, 06:41:22 pm »
Hello. Got E4 3.16 calibrated on 28/08/2019, used 3.12 Basic package + 3.16 dll and will do Advanced just for lols. I used RNDIS method via USB cable (menu for enabling RNDIS is not working properly for some time) and cfccfg_V2 (for encoding and decoding original configs).

Some notes:

* I forgot to insert serial number (used SUID instead) in conf.cfc and E4 ignored config file resulting in "broken MSX". It totally ignored .cfc so many things where off, not just MSX. Re-encoding of the file with python script fixed the issue.
* I have used VMWare Win7 32bit and RNDIS procedure from here https://fubar.gr/hacking-the-flir-e4/ but everything else from this thread. I suggest WiFi method to novice users.


small bits that bother me after :

---MXM alignment is off.  Looking over the forum I found solutions but the info is so scarce and scattered that it kinda freaks me out to try.

 Is the CRC32 of calib.rsc declared on an XML somewhere or is it only in the file? like if i want to correct it, do I only need to get the new CRC32 and write it on the file?

--- small bright spot appeared lower left, seems like dust or something INSIDE the sensor. Camera was factory calibrated 18/01/2018 so it's still on the warranty period :-X (of course with the E6 software)
see attach

Q. Is the charging via USB port reserved only to charge with the genuine charger? heard stories about people frying the charging IC with a regular 5V 1A microUSB charger   

Did you try to set distance in "Image menu" and shooting distance in Settings? Those 2 are independant and both accept "meters" as input.

How can someone fry it when it can get 900mA from USB3 or something... I dont like it charging off usb data cable but they got spare batteries for sale anyway :)

And about your broken sensor. I also had E4 with broken sensor, returned it and got brand new one. However I get some backlight bleed above FLIR logo so I sport Display in Low brightness now. Fraser suspects refurbrished unit(s) because everyone is hacking them now so it makes sense. He suggested FLIR Exx because of more robust touch screens. Does that "spot" show on PC when you transfer images or not?

PS About USB port: there is underrated post on this forum about using magnetic usb charing cables to physically protect charging port on FLIR cameras because it fits under rubber cover I guess so its perfect.
« Last Edit: September 29, 2019, 06:46:52 pm by negative_feedback »
 

Offline FlirAl

  • Contributor
  • Posts: 14
  • Country: be
Re: FLIR E4 Wifi Resolution and Menu Hack Thread
« Reply #858 on: September 30, 2019, 10:16:43 am »
Quote

PS About USB port: there is underrated post on this forum about using magnetic usb charing cables to physically
protect charging port on FLIR cameras because it fits under rubber cover I guess so its perfect.


Yeah, I did it via an QI charging pad so I can wireless charge it.
The spot looks like some runaway thermal pixels, the spot is not visible when cold booting but appears aftef 1-2 mins.
Someone on a different forum promsed to send me a link with the Flir service firmware so at least I could get the servicing WI up and running. For now the E6 is dismantled and hooked up to the special brain (I do ATM servicing for a living).


 

Online Fraser

  • Super Contributor
  • ***
  • Posts: 8633
  • Country: gb
Re: FLIR E4 Wifi Resolution and Menu Hack Thread
« Reply #859 on: September 30, 2019, 11:23:55 am »
FlirAI,

That spot and the symptoms you describe normally indicates a foreign body on the window of the Microbolometer. I presume you have removed the lens to look closely at that window to eliminate that from your investigation ? The reason the foreign body behaves like this is that it warms up due to the Microbolometers self heating radiation through the window and the foreign body reflects heat back to the die.

The FFC event would normally correct any drift in pixels as the Ex series are non uniformity corrected at the factory across their full 320 x 240 pixel FPA. It is true that the NUC table can become out of date if the Microbolometer suffers abuse that changes the temperature response of pixels, but that is unusual.

The dead pixel correction utility that is built into the early Ex cameras firmware has, to date, been a challenge to add to later models with the edited firmware content. From memory, people managed to insert the missing Service Menu utility files but when the dead pixel map utility was run, it reported missing code that was needed for it to run. Also from memory, the missing code resides in Areas of the firmware that are not easily edited.

Also, please be aware that the E4 went through both firmware and hardware changes that make using the original firmware (with service menu), such as V1.19 incompatible with later hardware cameras. You end up with a bricked camera. The E4 Teardown thread is massive but it tracks the various changes that were made over the life of the Ex series to date. In Précis, FLIR we’re trying to prevent users unlocking the full potential of an E4 and tried various approaches. All were flawed due to the Ex series using the less than secure Windows CE6 OS.

Fraser
« Last Edit: September 30, 2019, 02:26:27 pm by Fraser »
 

Offline negative_feedback

  • Contributor
  • Posts: 10
  • Country: cs
Re: FLIR E4 Wifi Resolution and Menu Hack Thread
« Reply #860 on: September 30, 2019, 02:11:17 pm »
The spot looks like some runaway thermal pixels, the spot is not visible when cold booting but appears aftef 1-2 mins.

Happend to me after 10min, whole array went crazy. Camera had old pictures still inside indicating same anomaly so it was easy decision to return it. Demo unit probably.  :scared:


What about MSX issue?
 

Offline FlirAl

  • Contributor
  • Posts: 14
  • Country: be
Re: FLIR E4 Wifi Resolution and Menu Hack Thread
« Reply #861 on: September 30, 2019, 07:28:16 pm »
Hi,
MSX was user imput stupidity, adjusting distance makes it perfect... Don't want to rush to conclusions, but the WinCe implementation is kinda stupid and half baked, I need to rent an XT model and an e60 to get really see where the flags are. My associate is busy hacking the sensor driver and maybe we can even sign it. For sure this E6 will not survive but maybe I'll get a super liberation FW. I can see discarded frames, if I can see the eprom via WI I'll be able to understand more.
What really bothers is that with dual use legality and whatnot, Flir engineers took a really childish path. There's a guy in Netherlands that succeeded in getting raw frames.
 
Fraser, you are really kind and helpful. If u look at timestamps it's all 2012 and older. I'll blow the sensor as soon as I can, and post the results. Why there should be anything under the lens on a brand new unit????
I'll try my way a bit, my associate knows wince better than breathing....
.
PS.  Sensor looks clean, brush and air. Tomorrow I'll see mayhe on the upper side of the isri
« Last Edit: September 30, 2019, 08:02:59 pm by FlirAl »
 

Online Fraser

  • Super Contributor
  • ***
  • Posts: 8633
  • Country: gb
Re: FLIR E4 Wifi Resolution and Menu Hack Thread
« Reply #862 on: September 30, 2019, 07:49:35 pm »
FlirAI,

The dirt on the Microbolometer window appears to stem from less than perfect production cleanliness !
Tiny bits of plastic or dirt find their way into the area around the Microbolometer where the FFC shutter resides. Plastic can even come out of the plastic lens barrel threads as it is screwed into the somewhat rough metal lens mount ! In transit the loose material can find its way onto the Microbolometer window. This situation is rare but has occurred a few times in the past. The worst case is when the contamination occurs in the factory before the NUC tables are created. This is because the NUC tables capture the dirt blemish and it becomes part of the cameras correction process. If the contamination falls off in transit or is cleaned away by the user, the NUC table becomes inaccurate for that area of the Microbolometer. This causes a blemish on the display that can only be corrected with a repeat NUC calibration. FFC will try to correct the issue but it is not always possible.

The work you are doing on the firmware sounds fascinating  :-+ WinCE was always a bit flakey in my experience and I tend to avoid anything that runs it ! I found Linux based equipment far more stable.

Fraser
« Last Edit: September 30, 2019, 07:58:39 pm by Fraser »
 

Offline FlirAl

  • Contributor
  • Posts: 14
  • Country: be
Re: FLIR E4 Wifi Resolution and Menu Hack Thread
« Reply #863 on: September 30, 2019, 09:04:33 pm »
Fraser,
Thanks for the quick reply. I suspect a small flake either veery close to microbolometer or a big one 2 mm far. The spot is roughly 30 pixels in diameter. 30 pix diagonally is under 1mm so maybe the small flake is an impurity in a close screen to the sensor. Maybe there are indeed technical issues with lower resolution imagers. Like on cpu industry, maybe the sensors are so expensive that they get reused in lower specs animals. They all tend to I7 but i5 is median and x9 is a rare find. They reroute the die and use it as i3 or atom if fault is grouped. Could be the case here. Maybe our sensors cannot possibly output 45 Hz reliable so they get assigned to 9 hz automatically. Maybe my sensor is like that when read at E8 resolution. Anyway it's not bothering, it is quite possible in this case.
One should not forget that they are made in Europe where clean room operators, in this kind of cost range, are more sloppy than operators on a 70k sensor made by a robot that runs in  millions of euros. Robots that run wince BTW.

What we tend to forget is that the E series is for Flir like iPhone cases for Apple. I bet Flir could sell e8 at 900 in profit.

They are mainly a super duper govt and ultra specialized equipment with a price rage to millions easy. That's where our luck resides. My bet is that they RD a unique HW platform for the entire E series and implemented different types of content. Easy and) fast. Of course, every mainboard has to be built according to connections and inputs, hence touchscreen and SD card support developing different software interfaces on wince is not economical and it's time consuming (think only about supoort fees :-X). Nixdorf found out the hard way about support. WinCE is a worn-out embedd that can be explored like a skin mole, with proven exploits and man in the middle attacks. Wince is running on missiles also. It's easy to deploy. Easy to install but also easy to hack. U can't hack a missile
 

Online Fraser

  • Super Contributor
  • ***
  • Posts: 8633
  • Country: gb
Re: FLIR E4 Wifi Resolution and Menu Hack Thread
« Reply #864 on: September 30, 2019, 09:44:30 pm »
FlirAI,

I can provide some comments on the Microbolometers as there are data-sheets already in the public domain.

It is no secret that modern microbolometers can output much higher frame rates than normally seen on cameras. 120 frames per second has already been seen from a ULIS Microbolometer running in a fire fighting camera.

When considering a microbolometer we need to remember its architecture when considering its capabilities.
In précis, it has a matrix of pixels that are read out in rows and columns in a serial or parallel reading mode.
The pixels are only biased for the read cycle to avoid self heating issues. The Read-Out IC carries out the reading of the rows and columns plus, in some Microbolometers, it handles timing functions and analogue to Digital conversion of the signal coming from the read-out matrix. The ROIC may be quite specialist in its content, but it is not the limiting factor in maximum frame rate, nor is it something that would lead to performance binning of finished modules. Self heating can be an issue with the ROIC but is not a great issue at 30fps or 60fps.

Where binning is concerned, I can advise that such is not applied to the FLIR cameras. All of their Microbolometers have to achieve a minimum standard of functionality to be used in a camera. This usually relates to the number of functional pixels and not read out IC performance. FLIR offer a 10 year warranty on their Microbolometers and have no interest in sub spec units ending up in their cameras. One of the challenges in Microbolometer production is achieving an industry standard acceptable percentage of functioning pixels and, where dead pixels are concerned, a maximum number of pixels in failure in a particular defined area. It is the creation of the Microbolometer pixels that is challenging and not really the ROIC that resides behind the die.

The read out limitation of a Microbolometer is, in reality, set by the physics of the pixels and associated read-out capacitors. It is well known that many thermal cameras that are limited to less than 9fps actually output 30fps or 60fps to the video processing stages. The exact nature of how the <9fps limit is imposed is what I cannot comment on. There are several ways to achieve it in an effective manner. Some are better for the cameras end user experience than others.

So now you know, the Ex series and Exx series both output high frame rate data from the Microbolometer. If you look at Mike’s Teardown and investigation videos you will see him discovering this with an oscilloscope. That does not help you with circumventing the frame rate limitation though. You could build a new video processing stage to create a high frame rate camera but you would basically be rebuilding the camera to do so.

This is where my commentary must stop though  ;)

All the best

Fraser
« Last Edit: September 30, 2019, 10:23:14 pm by Fraser »
 
The following users thanked this post: FlirAl

Online Bud

  • Super Contributor
  • ***
  • Posts: 3530
  • Country: ca
Re: FLIR E4 Wifi Resolution and Menu Hack Thread
« Reply #865 on: September 30, 2019, 10:53:33 pm »
My associate is busy hacking the sensor driver and maybe we can even sign it.
Makes me think what type of job you do on the ATMs for living   >:D
Facebook-free life and Rigol-free shack.
 

Offline FlirAl

  • Contributor
  • Posts: 14
  • Country: be
Re: FLIR E4 Wifi Resolution and Menu Hack Thread
« Reply #866 on: October 01, 2019, 11:16:17 am »
Took a look under a microscope and indeed the sensor was dirty and already scratched. The spot comes from something that is embedded in the material  :palm: looks shiny and there's no way to remove it without scratching. I tried special sensor glue sticks, special brushes .... I'll upload later some more images with the stain . the metal iris in not in focus bcs FF is like 0.5 mm @ 25X

@ BUD
Did u try running the MVT (+MCT) on any Ex/Exx machines?

<Makes me think what type of job you do on the ATMs for living> I'm more on the penetrations/sniffing part, most fascinating job.
« Last Edit: October 01, 2019, 11:18:29 am by FlirAl »
 

Online Fraser

  • Super Contributor
  • ***
  • Posts: 8633
  • Country: gb
Re: FLIR E4 Wifi Resolution and Menu Hack Thread
« Reply #867 on: October 01, 2019, 12:02:25 pm »
Wow! That is one seriously dirty Microbolometer window !

I have not seen one that badly contaminated in an E4 before. Most unusual and unexpected.

The window is made from silicon on that unit. I have read a FLIR service bulletin regarding minor scratches on the window and advice to be provided to customers who query such. Basically FLIR consider minor scratching on these units Microbolometers “normal” and state that because they are not in focus, they are not seen and any anomalies caused by them are captured and countered during factory calibration.

I have seen small chips/defects in Microbolometer Windows, minor scratching and dirt stuck to the surface but not something actually embedded in the surface. That would be like arc welding splash !

In a case such as this we can consider all cleaning options. You have tried specialist optical cleaning approaches common in modern DSLR sensor cleaning. Many such cleaning solutions are too ‘gentle’ !
The Microbolometer window is not as fragile as I once thought and, with due care, can tolerate more ‘aggressive’ cleaning approaches on the less expensive cameras. I would be hesitant to use them on a very expensive thermal camera as there is more at stake and the high quality sensor windows are normally pretty much perfect when they come out of the factory. Your window already has minor scratching but nothing serious. Whilst I note your comment regarding the particle being embedded in the window, I recommend you ret to dissolve it or release its bond to the window. There is low risk in my approach but I am also minded that removing the particle could create an anomaly if the camera was calibrated with that particle present. Decisions, Decisions, Decisions !

If I wanted to ‘deep clean’ that window I would normally remove the Microbolometer from the camera to have easy access to the whole Microbolometer module. I would then soak a piece of cotton wool in IPA and gently drag it across the window to thoroughly wet the surface. I would repeat this operation several times and inspect the result under magnification. Likely most dirt will be removed by this simple action and the window may be VERY gently ‘polished’ using a soft microfibre cloth intended for optics. If no great pressure is applied, scratching is unlikely. If there was a stubborn dirt particle remaining on the window I would not go to the ‘polishing’ stage ! If it broke away under the cloth it could cause a nasty scratch ! I would ‘attach’ that particle with a cotton bud (used for ear cleaning) that is soaked in distilled water to gently rub the particle to see if it will release. If no change, I would advance to IPA on the cotton bud, followed by pure Acetone (not nail polish remover as it can contain other ‘stuff’). With some very gentle wetting and rubbing, most particles will lift off of the surface. That is, unless they have become a part of the surface through some unusual event.

It us your decision but remember, the Ex series have a 10 year warranty on the Microbolometer so you could consider making a claim under that warranty as this is a production defect. If the area is visible with the camera in its native resolution, you should have no problem making a claim.

Regards

Fraser
 

Offline FlirAl

  • Contributor
  • Posts: 14
  • Country: be
Re: FLIR E4 Wifi Resolution and Menu Hack Thread
« Reply #868 on: October 01, 2019, 12:30:53 pm »
That would be like arc welding splash !
not only a helpful member of this forum but also a clairvoyant... see the pic with the splash. 3 zones 7,6 and 2 o'clock
7,6 zones looks like splashed glue 2 looks like a weld drop. Idk if I should send this pic to Flir/.... 
 

Online Bud

  • Super Contributor
  • ***
  • Posts: 3530
  • Country: ca
Re: FLIR E4 Wifi Resolution and Menu Hack Thread
« Reply #869 on: October 01, 2019, 01:37:03 pm »
@ BUD
Did u try running the MVT (+MCT) on any Ex/Exx machines?
Have no clue what that is. Answer is no.
Facebook-free life and Rigol-free shack.
 

Offline FlirAl

  • Contributor
  • Posts: 14
  • Country: be
Re: FLIR E4 Wifi Resolution and Menu Hack Thread
« Reply #870 on: October 01, 2019, 01:59:23 pm »
more pics
 

Offline FlirAl

  • Contributor
  • Posts: 14
  • Country: be
Re: FLIR E4 Wifi Resolution and Menu Hack Thread
« Reply #871 on: October 01, 2019, 02:00:23 pm »
sensor pic
 

Online Fraser

  • Super Contributor
  • ***
  • Posts: 8633
  • Country: gb
Re: FLIR E4 Wifi Resolution and Menu Hack Thread
« Reply #872 on: October 01, 2019, 02:28:52 pm »
If returning the camera is an option, I personally would return it. If not, I would look to FLIR customer services for assistance. Make sure they realise that you know your way around thermal cameras and such a contaminated Microbolometer window is unacceptable, no matter which model of camera it is. Do not worry too much if there is some evidence of access inside the camera. The returns centre appear non too interested unless there is obvious abuse when they open the parcel. Options open to you may be a replacement camera or a repair. If a repair is accepted, FLIR will either replace the whole system board, including Microbolometer, fit a new Microbolometer, or clean the original part (if possible) and carry out the calibration routine again to update the NUC table.

I forget whether your camera is new or bought second hand. FLIR normally want sight of the original sales receipt but, as you know, the camera is less than 10 years old so they should be reasonable about an issue with a Microbolometers window defect

Hope this works out OK for you

Fraser
« Last Edit: October 01, 2019, 02:30:54 pm by Fraser »
 
The following users thanked this post: FlirAl

Offline FlirAl

  • Contributor
  • Posts: 14
  • Country: be
Re: FLIR E4 Wifi Resolution and Menu Hack Thread
« Reply #873 on: October 01, 2019, 06:36:54 pm »
Fraser, camera was a gift from a partener in order to see if there are some weak points visible from outside on some specific machines that got hacked via RF abuse. I can put the camera back, there's absolutely no abuse visible at all (I have used pDCPD tools) so no scratches on screws. I only need to Un-liberate it. I could ask for the original invoice, but it would make me look like a choosing beggar :clap:. I looked with higher magnification and the silicon is not smooth at all, it has a rough surface. No antistatic coating also. I'll try calling them tomorrow, never had to deal with Flir customer service.
On the other side I caught an very interesting call on wince(via MCT) about a certain serial from rom, I'd bet that's what neuteres the ex vs exx. I'll spend the night digging further. Microsoft has some very nice tools to a trace anything on Wince.

Al








 

Offline negative_feedback

  • Contributor
  • Posts: 10
  • Country: cs
Re: FLIR E4 Wifi Resolution and Menu Hack Thread
« Reply #874 on: October 01, 2019, 06:46:02 pm »
I'll spend the night digging further. Microsoft has some very nice tools to a trace anything on Wince.

First try to patch NAG screen. kthxbye  :-DD
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf