You can up the resolution on your e40 just like the e4.
Found this ... Bascally speaking, I should:
- Connect E40 to computer to get access to the filesystem (didn't get that part completely - is there any special driver required for this operation (access to filesystem) )
- Locate files that are in the corresponding folders as the ones in the attached E60 map
- Check for # ID 490xxxxx in one of the files on the camera and apply this ID to all files
- Calculate CRC of each (new) file with V1 tool (https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg321956/#msg321956) and add this information as a last line (+ one CRLF)
- Make backup of all original files (probably renaming them is just fine and they can stay, where they are?)
- Move "new" files to the location of the old files
Is that so?
Regards,
Gregor
p.s. Things will get more complicated, if new Flir's E40 firmware also has "new" protection methods ... However, then this can be done the same way as described here (https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown/msg403480/#msg403480)?
Another question about E40 (hmm, shall I say E60?! ):
- How to make FLIR logo on image transparent as it is done in menu hack for E4 (is it possible to simply browse for it and replace it with transparent PNG? Guess not )
rset .ui.userSettings.overlayLogo false
It was happen in this thread at about page 270
Camera (E40bx, ver. 490xxxxx) still works and works with 320x240 resolution! Should work with all Exx cameras I guess.
However, I have 2 questions:
- I can't get thermal fusion to work - any idea here?
Remember that (AIUI) all config files in a folder are scanned, in alphabetical order so if you find somewhere that a setting appears to be set, you should be able to override it by adding another rsc file with a later alphabetical name.
> type \FlashFS\system\service\appcore.d\config.d\conf.cfg
....
caps.config.image.framegrab.fusion.hcf.enabled bool true
If you have a Exx without MSX (year 2012) you can activate the MSX menu but you only see a live real image on the LCD.
If you take a picture, then you save a normal MSX jpg on your SD card.
I think, the MSX code is embedded in the windows CE binaries but not in the fpga code.
You can take PiP images and convert then with Flir Tools to MSX images.with my config files I can change the PiP size smooth over the touch screen
if required: as workaround for MSX I zoom the PiP to fullscreen, then takes the PiP images and convert the image with flir tools to a MSX image
It was happen in this thread at about page 270Page numbers are not meaningful, as users can configure the number of posts per page - for me this thread isn't up to 100 pages yet.
Hi guys,
bad news, I now have a very expensive paperweight: downgrading went fine (well, except for a couple of complains here and there but not of them looked that bad. didn't think to copy/paste the log before hitting "reboot"....) and then, upon reboot of the unit, I got a FAT partition mounted on my laptop with 2 files, ERROR.TXT which says "no error" (how ironic) and TYPEINFO.TXT which has
FLIR cam boot
MSDcmd 1.3
ASCO
and then 2 serial (including the one from the unit) and the ethernet MAC of the unit. The unit itself just displays the FLIR logo.
I suppose my best bet is to return it, unless somebody has any brilliant ideas ? (don't feel sorry. Gambling implies losses...)
So there *is* something lurking at the firmware level, I would say...
Someone reported that TEquipment is selling 1.22.2 so maybe they patched the new hack.