EEVblog Electronics Community Forum
Products => Thermal Imaging => Topic started by: ksilabs on September 09, 2018, 05:55:38 am
-
It is at https://tinyurl.com/yc6wes78
Fully working Service Menu, all E60 and E60bx features. It is one zip archive with README.txt file inside. Please read the ENTIRE file before applying that set.
It will be kept there for 3 days from now. Please feel free to put it on file sharing sites for longer availability.
Please note -- it only applies to newer (64xxxxx) Exx cameras with 3.18.0 firmware.
-
Thanks ksilabs, will try it later on today and report back. :)
-
Thanks Ksilabs - although just upgraded to 4.13.0 |O so will wait for your 4.13.X version as you said in your README it might take long....
Btw noticed that you left targetNoise on and at 35. Any particular reason? Mine is set at false (and at 0 didn't test if it matters when set to false)...
-
That's almost verbatim original E60 config file except insulation and moisture palettes enabled. They do have targetNoise set to 35 in original, not hacked E60 so I left it where it was. IR image quality seems to be better with targetNoise at 35 vs 0. I did a quick blind test :) with my wife and she also chose images with targetNoise set to 35 over those with 0 all the time without knowing which is which.
-
BTW, if somebody has original 3.18.0 firmware update pack please share -- I would make a full 3.18.7 update pack.
-
BTW, before I started digging would you mind checking if prodapp.exe starts and runs on 4.13.0? I have 3.18.7 on my camera now and don't want to risk whatever I have by upgrading to 4.13.0 without being sure I can easily port everything to it.
It would be a great help if you could copy FlashBFS/system/prodapp.exe and restartapp.bat from that update pack into your camera's FlashBFS/system and make some checks. It would save me a lot of time making 4.13.7 version...
If you don't mind here are the steps:
1.) Connect to your camera with telnet and do the following:
rset appl.supv.exec prodapp
2.) If that didn't output any error message check if prodapp is running with
ps
3.) If it is running check if it initialized properly:
rls prod.log.status -- you should get "ready"
If that all worked and you want to take another step try to do:
rset prod.preparation.command restartHighRes
that might fail with "out of range" message if you have your camera hacked for 320x240 resolution but still have "E40" in EEPROM. If it happened you can change your config back to original 160x120 resolution and try the entire thing again after hard powercycle.
wait for a minute then do:
rls prod.preparation.status -- you should get "ready"
rls prod.preparation.ecode -- you should get 0
rls prod.log.serviceMode -- you can get either "true" or "false", let me know what you had
then check if you have \Temp\__highres.cnf file with single "HandsOff" string in it (use "type" to output file content to console)
If that all worked path to interim 4.13.7 update would be way shorter -- I could make a quick'n'dirty update for time being while I'm breaking that entire thing to pieces and creating my own WinCE Exx BSP.
NB: Once you are done with the above make hard powercycle to get rid of all prodapp artifacts and get you camera back to normal.
-
Can do - only on Saturday though. Works for you?
-
That's almost verbatim original E60 config file except insulation and moisture palettes enabled. They do have targetNoise set to 35 in original, not hacked E60 so I left it where it was. IR image quality seems to be better with targetNoise at 35 vs 0. I did a quick blind test :) with my wife and she also chose images with targetNoise set to 35 over those with 0 all the time without knowing which is which.
Interesting - will check over the weekend...
-
Sure, there is no rush...
-
BTW, before I started digging would you mind checking if prodapp.exe starts and runs on 4.13.0? I have 3.18.7 on my camera now and don't want to risk whatever I have by upgrading to 4.13.0 without being sure I can easily port everything to it.
It would be a great help if you could copy FlashBFS/system/prodapp.exe and restartapp.bat from that update pack into your camera's FlashBFS/system and make some checks. It would save me a lot of time making 4.13.7 version...
If you don't mind here are the steps:
1.) Connect to your camera with telnet and do the following:
rset appl.supv.exec prodapp
2.) If that didn't output any error message check if prodapp is running with
ps
3.) If it is running check if it initialized properly:
rls prod.log.status -- you should get "ready"
Step 1: no error message
Step 2: no sign of prodapp running
Step 3: rls: .prod.log.status: bad data
-
Oh, it’s sad, I just got an E30bx and missed the link, can you post it again?
-
https://tinyurl.com/yc6wes78
Will be there for 2 days until the end of Sunday.
-
This is great! Well done! Would you mind sharing again and then I can host it.
-
OK, that means the path to 4.13.X is not going to be quick and easy :(
Thanks for testing, now I know 4.0.0.7 prodkit won't work in 4.x.x versions that all included 4.1.x.x prodkits in their non-release versions.
So whoever have cameras with 3.18.0 firmware do NOT upgrade to any 4.x.x version if you still want to have that full service menu. It is EXTREMELY valuable feature that allows one to re-calibrate his camera without paying arm and leg to Flir, enable and calibrate ranges disabled by some configurations (bx and High Temp in all of them), calibrate for different lenses, replace dead pixels if needed, re-align MSX fusion and much more...
4.13.14 will have to take a difficult route -- an easy one is blocked.
-
Done.
Please let me know when you're done so I could remove it.
-
:palm: although I don't really need most of the features in the service menu... but still |O
-
Less everything else there is calibration there so one won't have to send his camera to Flir to get it calibrated for mere $600+ per lens...
-
Is the service menu the only way to increase the temperature range?
-
Might be not but you still need to calibrate your camera for that extended range.
-
How can I enable "Panorama" ? It is possible?