There is Flir E4 owners who are testing my new "2.3.0 Menu 2014 Advanced update".
Some things with this may be hard to understand. I can give a little guide from things
I figured out so far. Sometimes camera needs restart too... there is windows : )
While reading this I was wondering where to fetch that file until realizing that you probably didn't
post a preliminary "2.3.0 Menu 2014 Advanced update" but must have sent it around
in private - this way you have the overhead of distributing the files and it's limiting the people
who might take a look at it (can be helpful or not).
While I'm already writing... here some old info that might help: with advanced measurements
I had the strong impression that we can't fix stuff anything inside the bytecode where the
camera will lock up etc.. It probably never had to do those functions and the only reason why
those functions exists is likely just due to the fact that developers used a common source.
In my experience any function depending on the preset.d folder or -more generally said-
writing some files seemed to be _at least_ a bit sluggish (most likely due to the extra I/O).
IMHO there's a good chance that the Ex series runs a hardware that is simply not as capable
in regard to I/O performance as the higher models - thereby causing all sorts of "wonderful"
effects by running into deadlocks or waiting for the (slow) file-I/O-reply.
From my own experience the following did help a lot:
- clear versioning, describing version changes and keeping a backlog of what has changed
- openness (post everything, sometimes somebody else will be able to assist - helped me several times)
- some ignorance (you will get private requests like "I can't open cmd or copy a file but want to ..."
Last but not least:
Keep on going