Just added the new menu hack and when selecting 3 spots nothing really happens. The circle target is a little to the left on the screen as if it's stuck. Is that normal?
Just added the new menu hack and when selecting 3 spots nothing really happens. The circle target is a little to the left on the screen as if it's stuck. Is that normal?
Just added the new menu hack and when selecting 3 spots nothing really happens. The circle target is a little to the left on the screen as if it's stuck. Is that normal?This is normal when you do not apply correctly conf.cfc patch.
Just added the new menu hack and when selecting 3 spots nothing really happens. The circle target is a little to the left on the screen as if it's stuck. Is that normal?
Just added the new menu hack and when selecting 3 spots nothing really happens. The circle target is a little to the left on the screen as if it's stuck. Is that normal?
I had the same experience when I used conf.cfc from hi-res hack backup (from Python backupxxxx folder) instead of conf.cfc from camera. So I reapplied hi-res hack and then got right conf.cfc from camera for janekivi Python script.
Another step accomplished - .rcc is extracted
deRcc attachment is the code used to unpack - repacking should work somehow like that
Thanks. Also, typo in instructions. That should be qmake -project && qmake && make (not -profile).
Can someone help compile this and post back a ready to use executable?
I need help. I don't know yet anything about files I am using. These are from first 2.3.0Menu_Upgrade.zip
They are smaller than inside ADDMENU-BETA3. Who made them or who can make them? I can't use
ADDMENU-BETA3, in 2.3.0 camera picture is black. But something I can't do here. That manual temp
scale is fighting back. And there is black holes in conf.cfc files. What might be after
.caps.config.image.zoom.maxFactor double 8 to the # IDXXXXXX? Somehow PIP too is not cooperative
with me... Or something is blocked in UI/conf.cfc whose contents I have no clue... yet
All other stuff might be done in near future.
I believe Taucher was the guy who did the magic on the first menu patch. Haven't seen too many posts from him
as of late, hope he is still out there!! Nice work BTW Janekivi!!
Actually there is 1372 different combinations of use now.
4 - Image mode
7 - Measurement
12 - Colors (Gray and White hot is the same but you want always "more" : ) )
4 - Zoom
Does anybody know the difference between this and the good old Taucher menu mod done on the FW 1.19.x?
https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg326024/#msg326024
Hi there. I am a newbie and didn't mean to double post, but it seems the Newbie Q&A thread is not as active as this one.
I am about to purchase an E4B and I would like to know if it can be hacked the same way as the E4. Thank you!
I think I use other menu files for this year release
Small peek in 2015 menu for 2.3.0 E4
If you don't have 1.x firmware running then just don't bother with the older files unless you're trying to understand about some historic inner workings of the camera - but be aware of internal structural changes between the FW releases.
[...]
In native 2.3.0 you can get to the menu but cannot change selection. If we could find a way to unlock that menu that would be great.
Just a thought for a workaround:
You were able to set the image quality to 100 with those measuring spot preset files. Maybe it's possible to use this for RNDIS as well? Might not be the best solution but I think that would be still better than using FIF files all the time.
Something like: No spot = RNDIS+UVC, Center spot = UVC+MSD
In Set_RNDIS_Permanent.fif a new file with following commands is generated:Code: [Select].system entry
So you should only have to add those lines to the preset files as you desire.
.system.usbmode text "RNDIS"
And in the ressource tree the following possible values are listed:Code: [Select].system: (17)
[...]
rw--r---r---1p*2 root root <a> usbmode "RNDIS_UVC"
["RNDIS" "MSD" "UVC" "RNDIS_UVC" "RNDIS_MSD" "UVC_MSD" "RNDIS_UVC_MSD"]
[...]
I think there's a good chance this will work
Hi guys,
My first post here and I think it might save you all some time.
instead of loading/unloading any temp or permanent RNDIS FIF file, try holding the right button while powering up your camera from a cold state, this will take you straight into RNDIS mode
Good luck
instead of loading/unloading any temp or permanent RNDIS FIF file, try holding the right button while powering up your camera from a cold state, this will take you straight into RNDIS mode
Good luck