Hi. I got to repair a thermal imaging camera Flir E4. No image. No thermal image also from the camera no image. I can enter the menu. The computer sees the old photos. Firmware 2.11.0 . In memory contains the file - Z3comb_v2.11.0.fif, Z3comb_v2.3.0.fif and eFLIRInstall.exe and flir.db. I don't know the history of the imager. Maybe he changed the firmware. I think the problem is in the firmware. How to restore it? I don't know where to start?
Uho,
I am no expert on the software side but I would not normally expect to find .fif files in the camera. I thought .fif files were what sat on a PC during an upgrade and were then installed by the FLIR install program.
I could well be wrong about that though. Others will advise.
The fact that two versions of firmware .fif files are present also seems wrong to me.
If they do not belong on the camera, they need to be removed. They would also be evidence that someone tried to upgrade the camera and did not really know what they were doing.
Fraser
Yes. I think that someone incorrectly stitched the camera. This camera was bought by a friend on ebay. The files were in the folder FLIRUPdate.
Yep, no such update folder belongs on the camera. Maybe someone tried to run the FLIR update program on the Camera !
It would Be useful if you can list the various folders and files on the camera as we can then look for modification dates and missing files.
If you look through the cameras file system you will see which files have changed as their file date will be more recent than the majority on the camera.
Look in Appcore and Ui folders first.
Fraser
I checked the files. They were changed. And one more nuisance. I could not turn on the camera. She did not turn on. Loading started only after the memory chip was warmed up.
I have not checked but on first glance there appear to be be a lot of files in that root list that do not belong on an Excseries camera.... rdump, rclone etc. To me this looks like someone trying to investigate the OS from within the cameras OS. It is possible that it has a hardware fault and someone was trying to investigate it with Win CE tools and even tried a firmware update to solve the problem.
I am not near my E4 at the moment so cannot confirm my suspicions yet. I will check later.
Fraser
Yep, no such update folder belongs on the camera. Maybe someone tried to run the FLIR update program on the Camera !
Looking in the command file from v3.9.0 firmware update package there is a line:
Command:\FlashIFS\FLIRUpdate\eFLIRInstall -c \FlashIFS\FLIRUpdate\Excomb_v3.9.0\eFLIRInstall_MSD.dat
Which is an indication that FLIRUpdate folder and eFLIRInstall.exe both exist on the camera at some point as part of firmware update process. They may get deleted after successful update. The files still sitting there may be an indication of a failed update, e.g. because of power or communication interruption, etc
I found a picture in the camera's memory. Perhaps this was the reason for the flashing. I looked at the dates of the changes. .How to re-flash 2.11.0?
(As a side note, 2.3 already use public key cryptography to sign the configuration files, and had a chain-of-trust by verifying the hashes of everything that they boot. They just messed it up when they didn't implement MD160 correctly because they assumed "char" is an unsigned type - which it is on some compilers - but in fact it was signed. That allowed to patch files without changing their hash, and in turn allowed to remove the signature requirement for cfc files)
Many thanks tmbinc, i capitalized on your work to liberate the latest camera model
I found a picture in the camera's memory. Perhaps this was the reason for the flashing. I looked at the dates of the changes. .How to re-flash 2.11.0?
Why do you want 2.11, did you try updating to the latest applicable one? Did you try this procedure?
Thanks for the instruction. But I've already tried to use Flir Tools. Writes: this is the newest firmware for the camera. It does not allow to flash again. Perhaps need a different version of the program?
Try searching this thread for 2.3.0 update package or ask if anyone can provide one.
Hello Uho
I had the same problem as you
the thermal sensor has been cleaned
I thought there was a dust after dismantling the camera I clean the thermal sensor I found myself with the same problem as you
Not a software problem but rather because you disassembled the camera
The camera did not work in the assembled state. I think that there is a problem with the memory chip. Once the camera stopped turning on. I heated the microcircuit. The camera turned on. Someone tried to change the firmware, but it was not properly installed due to the aparat problem. I want to reinstall the firmware.
I found a picture in the camera's memory. Perhaps this was the reason for the flashing. I looked at the dates of the changes. .How to re-flash 2.11.0?
Hi,
I think that might the VOx uncooled thermal sensor has a problem of connection,
please check the connector or the golden wire is broken which connect sensor signal to pcb.
BTW, if it's a firmware problem usually has two conditions,
1.signature check failed: your camera will never login again.(stuck in FLIR logo)
2.an older mixed new firmware: the screen will be like water stains on it. (It ain't completely no picture)
Thank you. I'll check tomorrow contacts. But I think this is the problem of firmware. Not only thermal but also a visual camera does not work. As soon as I got it, he was hanging on the Flir screensaver.
What the FLIR screensaver is ? The boot screen with FLIR logo ?
Yes. Only the Flir logo was on display. The first time I waited 30 minutes. Download has not started. Only after several attempts the thermal imager was turned on. Some of the functions did not work. Did not show the serial number. I saw the serial number only after warming up the memory chip.
Can you switch the camera to RNDIS and ftp to it?
Please help: Is LCD in E4 custom or somehow standard, cause I need a replacement - some salty water got inside and corroded couple contacts in flex cable. Camera works via usb just OK, but not viewfinder.
(I'm not that sure in my ability to restore copper tracks, but had ordered microscope just in case)
Congratulations!
Let's say you won a lottery!
I would be just happy to have the same sensor noise value as you have!
Absolute record was something like 12.84 or so...
The absolute looser I am with 26.56
You are much closer to the first than to the second
I think you are happy now!
Digging this one up from the grave, but I think I set a new low noise record with my E4
measureInfo.temporalMk double 12.779606