Matmoe: thank you for the 2.3.0 package it worked perfectly for me...
At the moment it is not confirmed
If I see pictures which are in line numbers, it will be a confirmation.
It has to be visible number !!!
And it has to be seen yet this number to version 2.8.0
This picture proves nothing, sorry
Pah! I certainly will not post my serial number. And its ok when you decide for yourself, that its not true. It worked for me and that is nice O0
So do not confirmed.
Sorry
guys guys don't argue so violently!
you are both right... I think we will go a long way with slow accumulating statistics
Not to mention that guys from FL** will certainly monitor this blog and can anonymously even post confusing messages
Now... we need desperate volunteers! Who wants to bet 1,000 or above one guy against another?
It has to be visible number !!!
And it has to be seen yet this number to version 2.8.0
This picture proves nothing, sorry
Pah! I certainly will not post my serial number. And its ok when you decide for yourself, that its not true. It worked for me and that is nice O0
Are you able to provide a serial range? Like maybe the 63000 range or so? I have helped people modify cameras that were up to the 62,000 range which would be serial number 63962000. (All serials start with 639 and then the unit number)
I've been following this thread for quite a while now, and the standard response to new claims has always been "cool! show us how to do it", or possibly "it's not working for me, help me figure out what I'm doing wrong", not "YOU'RE LYING". I have to say that I don't think much of the new approach.
I agree wholeheartedly I really only threw out what worked for me to try to help others out that might have also ordered a gift for Christmas. The 2.3.0 zip file that matmoe got while his version of flir tools was offering "upgrade" to 2.3.0 from 2.8.0 was likely an error on fl**'s part that they offered the upgrade to any firmware version other than 2.3.0 and released cameras with newer 2.8.0 firmware before they update the servers that flir tools checks for upgrade availability.
If that is the case then matmoe deserves even more credit from everyone who enhances their 2.8.0 camera.
I am fairly sure that someone will figure out a way to break the 2.8.0 firmware but the fact that it was this easy to downgrade and it happened so fast is a "Christmas" miracle!
I received my Flir E4 today and I immediately checked the firmware version which was 2.8.0.
I downgraded to 2.3.0 on a Windows 7 32 bit computer and it worked like a charm
.
After testing and verifying that it worked correctly I used the resolution and menu hack.
All well! Now I have a fully functional E4 with zoom etc..
Many thanks to you all for the hard work.
I finished making the macro lens holder. Why make it so hard you ask.
1. Reliability of fastening of the lenses.
2. Versatility.
3. The ability to get low distortion image.
For some works you can use a simple plastic holder. But if you want a large zoom the idea of one lens does not work well. The photo shows some image distortion if you use the lens ZNSE F25mm. Two lenses F38.1mm did work better. Distortion less.
Can set different lenses in different sequences to obtain
the required degree of zoom when in macro mode from 1X to 8X. More expensive germanium lenses maximum diameter of 28 mm will provide low distortion (spherical and chromatic aberrations and distortions type "pillow"/"sheet"), the best ratio signal/noise. More
cheap lenses from zinc selenide small diameter will allow you to obtain a budget option with low cost optics, but still applicable for simple works. Thus, the adapter provides maximum
flexibility in the use of available lenses, cheaper or more expensive.
For example, in the medical - photo palm. The use of macro lenses for diagnostics of electronics - photo phone.
Do you have the STL file for the lens holder available?
I did the 3D model. The forum participants tsmith35, Solare, mardaso helped in the measurements and tests. The holder contains a lot of detail. Not only plastic. Tubes for the lenses are made of aluminium alloy. Anodized necessary. For of pushers I did the brass screws. Pushers contain rubber anti-slip elements. For manufacturing these parts need a lot of equipment.
Thank you matmoe, Navynuke and neggles. Because of you
I bit the bullet and downgraded my new Flir 2.8.0 to 2.3.0, successfully!!!
Flir E4 1.2L
Serial 63968xxx
Windows XP, 32 bit
FLIR Tools v4.1.14066.1001 - run as admin
flir_ex_pn639_v2.3.0_update_pack.zip from
http://s000.tinyupload.com/?file_id=00983732806372988148Comodo Internet Security - disable
Before the update, I deleted all saved images and did reset device settings to factory default.
Happy Holidays to everyone!
it proves nothing - I saw a camera with 2.3.0 starting with 639670xx
I saw 63968XXX with 2.3.0
before or after you downgraded the E4?
New one. Begining of 63968XXX serie.
I thought I would also chime in my series is 63967 and the software as I already earlier said is the 2.8.0.
Could someone help me decide if I should be worried about those pixels I see when in the 'Device Settings' I don't exactly remember the menu name.
I haven't tried to downgrade my firmware just yet, would be nice to hear from that one person on how he got his cameras bricked.
Also how inadvisable is it to use Windows 7 instead of Windows XP. The only laptop I have with Windows XP has problems and the only way for me would be to install it on another laptop. I mean I have no problem with installing XP on a laptop if there is a risk with Win 7.
Also one thing I wanted to add. LCD's or at least in my knowledge have a native resolution, has anyone tried to set their laptop resolution on a setting other then the native? So then the higher resolution is basically the native resolution for these cameras.
2 Anonyman,
screw it... these pi?els, unless they are on radiometric image permanently, is not a trouble at all... they appear there because of a simple masking bug of E4 interface. One may be able to correct this, but I won't do this in my view unnecessary work associated with increased risks to ruin something important in the camera. My advise - live with that as I do
2 Anonyman,
screw it... these pi?els, unless they are on radiometric image permanently, is not a trouble at all... they appear there because of a simple masking bug of E4 interface. One may be able to correct this, but I won't do this in my view unnecessary work associated with increased risks to ruin something important in the camera. My advise - live with that as I do
Advice Taken,
Thanks All for your advice.
CONFIRMED!!
I'm down to 2.3.0. I also took picks from the previous version. I won't post them publicly.
Matmoe is the MAN.
Repeat. Matmoe is the man.
I would follow Matmoe's directions. Read them carefully.
I used Window XP 32bit SP3 and Fl tools 4xxxxxxx.
It took me about 2 hours to get the nerves to do it and then it took around 15 mins for the work.
Now I will be working on step two tonight.
UPDATE: DONE.
Tried in a VM, but no go, so now doing Windows update on a copy on bare metal that has not been booted since 2009, so I can get SP3 for it. Apparently the tools need SP3 to install, otherwise they fail in an endless restart required loop.