FLIR E4 Wifi Resolution and Menu Hack Thread

[Squawk]

Here is a .FIF I made for the normal E4 that turns off NUC'ing until the camera is restarted. (rset .tcomp.services.autoNuc.active false)
When I am going to record video I power on the camera - run the FIF, leave it connected to the charger for 15-20 min to warm up/equalize, then run a manual NUC by holding the "play" button to level it out.
Then your good to record without calibration popups.

(remember to rename it from .zip to .fif)

Thanks! I'll save this fif to try it out.

But I think I will follow Bud's suggestion initially, so that I don't have to connect it to the PC to turn off auto calibration.

[Squawk]

Man.. hahaha.. if you keep going, you end up digging stuff up even FLIR doesn't know is there.. 

B.t.w. has there been any setting you came across (that could be unlocked) that enables you to turn off the "auto calibration"?
Or set it to "manual" or a user settable "time interval"?

You may be able to turn off autoNUC in the resource tree using rset command, and then use long press of Archive button to trigger manual NUC when you want. If you do not know how to dump and manipulate the resource tree, search E4 Teardown thread for rls,rset,resource keywords.

Thanks! Will look into this! 

[TheSteve]

Wow, the hack is already being used for profit on ebay - so sad.

[Squawk]

Ok, this is a bit far from my skill set and searching an hour on the teardown thread did not bring me much further..

I'm not sure I understand the resource tree thing.
Are Bud and OrBy saying the same thing? Meaning you can only temporarily activate "no auto calibration" just like how you turn the E4 to USB mode using the "FLIRInstallNet" and "Set_RNDIS_temporary.fif"?

Meaning, to activate it you need a PC and after a full restart (>6 sec. ON/OFF button & temporary battery removal) all is back to "normal" mode?

Or is there a permanent way to turn off the auto calibration and 'long-press' Archive/Play to manually calibrate, untill one uses another fif file to undo that?

[Bud]

If it is difficult for you then just use the solution OrBy provided. Yes you need a PC but once you upload the fif it takes effect rght away. Some parameters in the resource database have permanent properties, some not. You have to look at the attributes for the parameter, there is no one answers all thing. Flir cameras software is  MUCH more sofisticated than one may think.

[Squawk]

Thanks, I'll try to figure out a 'permanent' solution by strolling the threads later on..

[Squawk]

Can anybody tell me how to get into the service menu after executing the "Set_RNDIS_temporary.fif" command in the "FLIRInstallNet.exe" and accessing the web browser interface to the E4 by typing 192.168.0.2?

I can't seem to pass by the login screen with "flir" and "3vlig"..

[Bud]

I do not think the new stock cameras have service menu in the web interface.

[Squawk]

It does show the service menu item, but when clicking on it, it requests login data.
None of the login combinations mentioned in this thread worked..

But then how did you access the part where you could access the EEPROM?

[Fraser]

Have you tried password 1235 ? That WAS the EEPROM password. 2017 cameras may have a new password though.

Tread carefully inside the EEPROM !

Fraser

[Zs8192]

I got my E4 2.0L with stock 3.9 FW.

1, After run FlirInstallNet and upload the temporary RNDIS fif file. (Set_RNDIS_temporary.fif from e4hack3c.zip)
2, Wait for the camera to get IP address assigned as usual, ping 192.168.0.2 and make sure the camera responds to ping.

I tried Win7 64bit and Win10 64bit but the RNDIS mode not working. Network starting but no usable IP. (169.254.96.140 or similar). No responds to ping. 

Would I be rude to ask if you could post these files?

I'm a newby at this and can find files about hack 2.3.0 (http://fubar.gr/hacking-the-flir-e4/) but not the 2.11.0 and I'm not sure they're the same.. 

pull the RNDIS fif files from this zip archive

https://www.eevblog.com/forum/thermal-imaging/flir-e4-thermal-imaging-camera-teardown/msg531346/#msg531346

I recommend only using the Temporary one. You will be in better control over the camera USB interface. The Temporary fif only enables RNDIS until reboot, after which the camera returns to UVC mode. You will perhaps need to run it 2-3 times during the procedure as you reboot but it makes sure the camera will not get stuck in RNDIS using some weirdo IP settings which may give you headache and inability to connect to it. Ask me how I know this.

[capt bullshot]

I tried Win7 64bit and Win10 64bit but the RNDIS mode not working. Network starting but no usable IP. (169.254.96.140 or similar). No responds to ping. 

I've experienced this behaviour quite a few times.  Windows or the Flir drivers or both really suck at RNDIS.
Anyway, when such an IP was reported, the camera was still accessible at "add one to the visible IP", say 169.254.96.141 for your 169.254.96.140 example.
I found the other method "connect camera to computer while completely turned off, see the battery charging screen, don't turn it on but apply the .fif" more reliable. The FTP server is then accessible with "anonymous" / no password, way less files locked, no need to telnet and "stopapp".

[CABNY]

That's awesome!   

[Bud]

I tried Win7 64bit and Win10 64bit but the RNDIS mode not working. Network starting but no usable IP. (169.254.96.140 or similar). No responds to ping. 

Try unplugging your computer from the network before running the .fif

[Zs8192]

I tried Win7 64bit and Win10 64bit but the RNDIS mode not working. Network starting but no usable IP. (169.254.96.140 or similar). No responds to ping. 

Try unplugging your computer from the network before running the .fif

Problem solved:
Without network connection it not works. (Active network device, not need internet connection). I switched on the wifi connenction and everything is ok. 

Thanks! Good work Bud! 

[mario.ti]

hi,
i stuck at the beginning. When i switch to RNDIS mode, the connection is look ok, camera has IP 192.168.1.2 but then i receive  message in new little window: \\IRCAM8823\images, Information=53, can't find network path (or something like this, message is in my language, so i doesn't know, is translating is right)

[Bud]

It is irrelevant, as long as you can connect using ftp you can go ahead.

[mario.ti]

i took back everyting, it's working just great. I have liberated e4 

p.s. i have 8-digit serial, but it doesn't matter,

[p5ycho]

Well, jumped in on an E4 after following this thread, and what do I receive? An 1.2L/2.11 E4. Not what I expected. Apparently the 2016 E4's are still around...

Now I have some questions:
- Is there any reason to prefer the 2017 non-wifi E4 with 2.0 hardware over the 1.2L hardware?
- Will the hack for 3.9.0 also work on the 1.2L hardware?

I'd hate to miss out on all the extra goodies of the 3.9.0 hack... will this be 'backported' in the future?

I'm not sure if it's reasonable to demand a swap for a 2017 version. The one I received came with a completely flat battery, it needed an hour on the charger before any signs of life of the unit.

[CABNY]

Hi Bud,
Where do we get the extras (Advanced Pack) from?  Is it still in development?
Thanks!

[DaveWB]

Well, jumped in on an E4 after following this thread, and what do I receive? An 1.2L/2.11 E4. Not what I expected. Apparently the 2016 E4's are still around...

Now I have some questions:
- Is there any reason to prefer the 2017 non-wifi E4 with 2.0 hardware over the 1.2L hardware?
- Will the hack for 3.9.0 also work on the 1.2L hardware?

I'd hate to miss out on all the extra goodies of the 3.9.0 hack... will this be 'backported' in the future?

I'm not sure if it's reasonable to demand a swap for a 2017 version. The one I received came with a completely flat battery, it needed an hour on the charger before any signs of life of the unit.

I believe they ship the batteries completely dead now due to new regulation with shipping lithium-ion batteries.

[Bud]

Hi Bud,
Where do we get the extras (Advanced Pack) from?  Is it still in development?
Thanks!

You get it here when it is released. Not yet.

[Bud]

... will this be 'backported' in the future?

Sorry we are not running a full time business operation here.

[MicroBliss]

hi
I cant connect my flir
I have already done backup, but on the other day I cant connect by filezilla or ever PC cant see it like usb flashcard.
when I plug in flir in PC: ''configuring terma cam...   camera ip adress 192.168.1.2... connecting to 192.168.1.2 Please wait...''
Flir E5 fw 3.9.0

[capt bullshot]

hi
I cant connect my flir
I have already done backup, but on the other day I cant connect by filezilla or ever PC cant see it like usb flashcard.
when I plug in flir in PC: ''configuring terma cam...   camera ip adress 192.168.1.2... connecting to 192.168.1.2 Please wait...''
Flir E5 fw 3.9.0

Try "recovery procedure" https://www.eevblog.com/forum/thermal-imaging/flir-e4-wifi-resolution-and-menu-hack-thread/msg1336326/#msg1336326 to connect the camera and access files etc.
Or try remove your wired network from the computer before connecting the camera, sometimes rebooting windows before connecting the camera helps.

BEWARE: Bud's package is for the E4 model. Anything else is at your own risk and not supported here, as applying the package to the E4 is at your own risk anyway.