-
-
Just received my new flir E4 with software 2.11. Without downgrading I followed the fubar procedure here http://fubar.gr/hacking-the-flir-e4/ substituting the script pack files FLIR_E4_2.11.0_hack from 2lps here https://www.eevblog.com/forum/thermal-imaging/flir-e4-thermal-imaging-camera-teardown/msg921880/#msg921880
It worked great and I have full resolution and thermal noise removed and lots more menu options and features. I have not detected any issues. All menu features seem to be there and working. I especially like the 3 spots measurement feature.
Thank you very much to fubar and 2lps and to everyone else involved in setting up the scripts and files needed and working out the various improvements.
Changes were done on windows 7 64bit virtual machine on Virtualbox running on macosx hardware. Drivers were fine on windows 7 64bit. Only trick was trying to get Virtualbox to own the flir USB devices as macosx kept trying to mount the USB volume.
Notes for people running a similar virtualbox set up:
– connect the flir to the computer so Virtualbox can see that it exists, then go into the virtual machine settings to tell the virtual machine to own the device. This does not work instantly – you are just configuring it. Then try and unmount the drive in macosx and unplug the flir.
– I think I shut down windows at this point and quit Virtualbox. Might not be needed.
– Start Virtualbox and boot the windows virtual machine
– plug in the flir and windows should see it and install drivers
– once you go through the procedure to change to RNDIS mode, it is a different USB device so you will have to go through a similar procedure (adding the new device to the virtual machine config) to get Virtualbox and the windows virtual machine to own it. Less difficult this time because macosx is not trying to mount a USB drive.
Cheers,
Anthony
I received an E4 (obviously non wifi) with firmware 2.11 over the weekend and had a similar experience as Anthony here. Only difference is I used an old computer running Windows XP (non virtualized) to do the install. The only minor issue I had was after first switching the E4 to RNDIS mode, when I first turned it on it got hung trying to pick up an IP address. The XP command line interface completely locked up to where I couldn't even force quit out of it (this has happened on other occasions, don't think it was specifically because of the Flir). After around 10 minutes I finally decided to turn the E4 off and unplug the USB cable from it, and as soon as I did networking and the CLI became responsive again. After plugging the E4 back in I was able to continue on with the guide. All in all it only took about 30 minutes (even with the wasted 10 minutes of being hung up) and I have not had any issues with the Flir since (I did get 1 error on the Flir around an hour after completing the upgrade, but have seen others mention receiving the same error, and have not had it since).
Thanks to all who figured all this out.
Edit: Wanted to add that the message from this thread where the FLIR_E4_2.11.0_hack file is supposed to be located (
https://www.eevblog.com/forum/thermal-imaging/flir-e4-thermal-imaging-camera-teardown/msg921880/#msg921880) seems to have been deleted. Sorry, I don't remember where exactly I got the FLIR_E4_2.11.0_hack file from, but its definitely out there somewhere.
-
-
I have an E4 Wifi on order, it is expected to ship 3/30. Does anyone have more information on the 2.5 firmware previously mentioned? When I receive the camera would anyone be interested in taking a look at the files though a program like teamviewer? Or I could upload them if you let me know which files to upload.
I think a new thread would be appropriate for a significant new model variant.
If Flir were more like Keysight, they'd be sending me a freebie, but all I ever got from them was a soft case!
-
#8177 Reply
Posted by
Theamber
on 16 Mar, 2017 04:45
-
I hacked my Flir E4 long time ago the resolution was upgraded so were the new menus the only thing is that the camera firmware stills said it is an E4 and not E8. Can that be fixed?
-
#8178 Reply
Posted by
Fraser
on 16 Mar, 2017 10:57
-
It is possible to change the ID from E4 to E8 but most owners do not bother. The camera still has E4 on its faceplate anyway.
The camera model ID is held is an eeprom chip that would need to be edited. IIRC the details are buried somewhere early in this thread when we were looking for possible ways to release the cameras full potential. It was a thought that the ID in the eeprom might set the capabilities but this is not the case as we now know.
Fraser
-
#8179 Reply
Posted by
pimpinge46
on 20 Mar, 2017 02:31
-
I I have been trying to upgrade first gen i3 to an i7 per the pdf but it wont take . I am missing in the original config file some lines that it seems like other have. Example ".caps.config.image.settings.fpgaResolution.resIR int32 "
I have attached below the original file. any help would be great..
#
# ZCam Radiometric - Measurement active + 1 spot + no isotherm + no mbox
# + radiometric store, compatible radiometric format
#
.caps entry
.caps.config entry
.caps.config.name text "i3"
.caps.config.revision text "3.4"
.caps.config.image entry
.caps.config.image.sysimg entry
.caps.config.image.sysimg.measureFuncs entry
.caps.config.image.sysimg.measureFuncs.enabled bool true
.caps.config.image.sysimg.measureFuncs.mbox entry
.caps.config.image.sysimg.measureFuncs.mbox.enabled bool false
.caps.config.image.sysimg.measureFuncs.mbox.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.maxCount int32 1
.caps.config.image.sysimg.measureFuncs.isotherm entry
.caps.config.image.sysimg.measureFuncs.isotherm.enabled bool false
.caps.config.image.sysimg.measureFuncs.isotherm.maxCount int32 0
.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.resIR int32 60
.caps.config.hw entry
.caps.config.hw.sdcard entry
.caps.config.hw.sdcard.enabled bool true
# ID xxxxxxxxxx
# CRC01 xxxxxxxxx
-
#8180 Reply
Posted by
KrzysztofB
on 01 Apr, 2017 06:22
-
Hello guys.
I'm thinking about getting E4, and trying to figure out, how to determine which units are hackable and which not. One seller told me, that new cameras comes with 2.11. But are all of them hackable? Or maybe not hackable?
-
#8181 Reply
Posted by
Fraser
on 01 Apr, 2017 10:17
-
E4 up to 2016 model (no Wi-Fi). .......... yes
E4 2017 model with Wi-Fi ........ not known
-
#8182 Reply
Posted by
DaveWB
on 04 Apr, 2017 06:30
-
-
#8183 Reply
Posted by
Chanc3
on 08 Apr, 2017 21:25
-
I'm pretty sure you don't actually need to decrypt the conf file on 1.22 - maybe that's why?
Sent from my ONE A2003 using Tapatalk
-
#8184 Reply
Posted by
ollihd
on 11 Apr, 2017 13:21
-
I'm in the process of hacking my E4 from 2.8 to 2.3 and then hacking. I'm guessing from all the reading that this is the right route? Does anyone have a link to the 2.3 downgrade package? The link in the first page is not working anymore. After this I'm going to do the step-by-step 2.3 hack. This is also current stuff I believe?
Thanks in advance.
-
#8185 Reply
Posted by
ollihd
on 11 Apr, 2017 14:03
-
-
#8186 Reply
Posted by
ollihd
on 11 Apr, 2017 18:39
-
Would there be any point in updating the 2.8 to 2.11 via. Flir Tools and then applying the 2.11 hack? Or should I just wait for someone to send the 2.8 to 2.3 downgrade file?
-
#8187 Reply
Posted by
Xavier64
on 12 Apr, 2017 17:28
-
-
#8188 Reply
Posted by
ollihd
on 12 Apr, 2017 17:29
-
Thanks a lot Xavier!
Is the 2.11 upgrade the same that Flir Tools offers as an update? If you want to manually update the firmware, how can it be done? I see no place to manually insert a firmware file?
Thanks again!
-
#8189 Reply
Posted by
Xavier64
on 12 Apr, 2017 17:33
-
yes, original Flir files.
You can also do it with Flir tools or manual with FLIRInstallNet.exe which is part of your Flir tools installation. Just search in the programm folder.
Switch to RNDIS mode before manually updating, otherwise it will take hours to complete!
Flir tools upgrade will switch automatically to temporary RNDIS mode.
Enjoy!
-
#8190 Reply
Posted by
ollihd
on 12 Apr, 2017 17:38
-
Thanks alot Xavier! You saved my day!
The only thing wrong with my E4 is that it seems to have some calibration problem? Sometimes vertical lines appear on the screen and when the unit self calibrates, the lines disappear. I have no idea why this is. Also before the capture-function (trigger) works I have to wait for like 5 mins (otherwise it says it can't find the memory card).
Some pictures of the issue:
https://goo.gl/photos/TL43oRGJaUtYBjx98
-
#8191 Reply
Posted by
Chanc3
on 12 Apr, 2017 17:39
-
Did you do a hard reset after upgrading?
Sent from my ONE A2003 using Tapatalk
-
#8192 Reply
Posted by
ollihd
on 12 Apr, 2017 17:40
-
Did a software factory reset, and removed battery waited for 2 min and put it back in (if this is hard reset?). Same problem was with 2.8 and now also with the 2.11
-
#8193 Reply
Posted by
Xavier64
on 12 Apr, 2017 17:42
-
The camera reboots automatically after upgrade. KEEP it connected - FlirNetinstall.exe will finish the upgrade after reboot !
For the calibration issue, search in the forum. I might think I have read it before but never saw it on my camera.
regards
-
#8194 Reply
Posted by
ollihd
on 12 Apr, 2017 17:43
-
Ok, I will, thanks!
-
#8195 Reply
Posted by
Xavier64
on 12 Apr, 2017 17:45
-
-
#8196 Reply
Posted by
ollihd
on 12 Apr, 2017 17:58
-
-
#8197 Reply
Posted by
ollihd
on 12 Apr, 2017 18:00
-
I bought the camera used without hacks. I think the best thing to do now is take it to Flir repair (before applying any hacks). I think it should have some warranty still left. At least it was not registered and after registering it said that the warranty was extended for 1year.
-
#8198 Reply
Posted by
Xavier64
on 12 Apr, 2017 18:14
-
Very good idea. hopefully you will get hardware 1.2L back not 2.0.
-
#8199 Reply
Posted by
ollihd
on 12 Apr, 2017 18:20
-
Hope so! I take it that the hacks won't work with 2.0?