Received an E4 from Amazon today with version 1.22. The hack worked nicely. I did not make a copy of the original menu files (wasn't included in the YouTube video). Is there any way to get those in case I need to restore the camera to the factory configuration?
Received an E4 from Amazon today with version 1.22. The hack worked nicely. I did not make a copy of the original menu files (wasn't included in the YouTube video). Is there any way to get those in case I need to restore the camera to the factory configuration?
Have anyone bought new E4 lately?
Are they still shipping units with 1.2L and 2.1.0?
Any news?
Bought two from Grainger a week ago. 1.1L and 1.22 on both
Bought two from Grainger a week ago. 1.1L and 1.22 on both
What day are the calibration dates?
The newest one has a cal date of May 5
Thanks to the people who created the hack. Will stand by for the video to restore factory defaults.I attached fif files for use with FlirInstallNet.exe. addmenu_v1.22.0.fif to add tauchers addmenu-beta3, restoremenu_v1.22.0.fif to remove the changes and restore original menu files from fw 1.22.0.
I have tested both files and they work really well.
Do I need to use USB RNDIS MODE in order to use flir instalment.exe to use the .fif for the menu hack? Or no need to change the mode
ThanksYou can use Flirs standard settings (MSD and UVC). RNDIS mode also possible but not needed. Your camera device must shown in FlirInstall Camera Selection.
you mean livestream?
it is greyed out, i cant seem to connect for live picture feed
but i can import the pictures from the camera
i am missing some drivers?I think so.
well i tried to reinstall flir tools
also tried to install flir drivers
still the same, i can download the pictures from camera no problem
but i still cant not connect for live streaming from flir tools
i dont know what else i can do.
btw i am using windows 7 64bit
flir tools the newest version i think
E4 1.22
I have to enable both MSD+UVC. MSD is needed to see the flir as a drive and UVC is needed to stream, from what I've found.
If cloning a camera, the SN must also cloned.
In theory it should be possible to dump the (Toshiba NAND E2PROM??) memory from a working unit, and flash it to a bricked unit of the same HW rev. A lot of trial/error and solder work though!
@joe-c
So to be clear, you received your camera back from FLIR repaired and the attempt to flash it with FW 1.22 killed it ?
Not easily as unless you're very lucky, the bad-block map won't be right. You'd need to get access at the filesystem level, either in situ, or mounted on another compatible system - this may be possible via the serial console boot menu which AFIAK nobody has exploted yet.
joe-c's conf.cfc has a new size (112 byte bigger) and ftool outputs an error.