Edit#2
Reverified the image resolution using http://exif.regex.info/exif.cgi. The extracted image says 80x60. Rechecked my setup and I overlooked the fact that I am running a Win7 64bit laptop, not a 32bit one.
I assume this resolution failure is due to using the 64bit machine to run the python script, correct? Does anyone have information on running a VM for this liberation? Again I apologize for the misinformation.
Known rabbithole is that one of the old conf. or common is still there in camera.
One way is to delete first then copy if you are to lazy to use stopapp.
check file date to be shure copy is done in camera.
There is a good easy phython explanation in this thread with picture.
Can 2.0 owners dream about getting higher temerature messurement ?
...
4. Obtain cfccfg.zip archive:
https://www.eevblog.com/forum/thermal-imaging/flir-e4-thermal-imaging-camera-teardown/msg596959/#msg596959
and extract cfccfg_V2.py from it.
5. Install Python 2.7 . The script may not work with later Python versions.
6. Open the supplied conf.cfg , scroll down to the very bottom to the line that starts with "# ID " and replace the 9-digit number with your camera serial number.
Save the file.
7. Encrypt the updated conf.cfg from step 6 with your suid by running this command from command line on your PC with Python:
python cfccfg_v2.py XXXXXXXXXXXXXXXX conf.cfg conf.cfc
(where XXXXXXXXXXXXXXXX is the suid string from step 3)
This step will produce a new encrypted conf.cfc .Save it to your working folder for transferring to the camera.
...
Just a small update on cfccfg.py for 2.3. It now drops the signature/tail from the .cfg file. You can also make changes to the .cfg in plain text before converting back to .cfc, the file tail is created with the proper file size info (the signature is set to all 0). Note that you need the "HIRES" patch first in order to skip the CRC/signature check for this to work.
I tested adding a few lines to the .cfg file (comments, putting back 80x60 resolution...), convert to .cfc and use that on camera. Seems to work fine.
original post:
https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg594600/#msg594600
python cfccfg_V2.py XXXXXXXXXXXXXXXX C:/conf.cfg conf.cfc
The Ex series do not contain the required additional pixel bias voltage tables or associated calibration files for the other temperature ranges.
The temperature imaging capabilities of the Ex series may be extended using various attenuators placed in front of the lens. A non multi coated UV (Haze) glass photographic filter enables imaging of a gas flame etc. Sadly calibration is not simple though. Other materials can act as attenuators as well. It is a case of experimenting. Try plastics first.
Fraser
I think it would help to provide a bit more detailed insight on how to perform the step for those who aren't familiar with this.
Also worth pointing that you can record video and remote control the Flir camera using the free PC-based Flir IR Camera Player (http://www.flir.com/instruments/display/?id=50428) from Flir, as I haven't seen any mention of this yet in the "can I record video" discussions here.
Also worth pointing that you can record video and remote control the Flir camera using the free PC-based Flir IR Camera Player (http://www.flir.com/instruments/display/?id=50428) from Flir, as I haven't seen any mention of this yet in the "can I record video" discussions here.
For some reason that player never worked for me thru Ethernet. Also, as far as I remember it does not display radiometric video (i.e. with temperature measuring cursor so you can measure different parts of the image), it is just a color overlay. For true radiometric video streaming we made an effort here but it was a quite convoluted solution and only available on Linux.
I followed the steps correctly. Perhaps my SUID is wrong? In step 3 you ask to get the SUID by two different means. Why is that? We expect them to be the same right? I copied the SUID to the cfg file and encrypted it with the "python cfccfg_v2.py XXXXXXXXXXXXXXXX conf.cfg conf.cfc"
script.