A bit more info about the defective camera.. I let it sit overnight and this morning noticed that when it first starts up, there isn't as much of a temperature gradient problem. I took a snap when it started up and once a minute for the first 5 minutes. You can see that the gradient forms when its internal electronics begin heating up. This time, the inner aperture moved a bit and the gradient is now top to bottom.
These are all with the cover closed and the unit sitting still.
I'm curious to see what someone else's model does in the first 5 minutes of startup after sitting several hours to cool off.
A bit more info about the defective camera.. I let it sit overnight and this morning noticed that when it first starts up, there isn't as much of a temperature gradient problem. I took a snap when it started up and once a minute for the first 5 minutes. You can see that the gradient forms when its internal electronics begin heating up. This time, the inner aperture moved a bit and the gradient is now top to bottom.
These are all with the cover closed and the unit sitting still.
I'm curious to see what someone else's model does in the first 5 minutes of startup after sitting several hours to cool off.
If as Aurora says, your camera is defective, maybe you should try the FLIR-Tools update.
Nothing to lose if you are going to get exchanged/repaired under warranty. AND it may tell the rest of us whether the update is safe for the hack or not.
Hoping that they don't ding me too bad on the repair for mine... Dunno if the dog yanking the cord was the issue or not, but can't just straight up claim warranty...
Lesson learned.. No picture transfers near the pooch... (he is a tad rambunctious and got tangled in the usb when he jumped up on the couch )
QuoteI got a message today: New FLIR Tools Version
Should we be worried?
This is one of those times where you should actually read (I know) the EULA. If the new version is going to automatically update firmware files on your camera, you'll have to agree to it somewhere for legal purposes
Just to make sure I'm not missing anything, has someone unlocked wifi on the E4?
I got a message today: New FLIR Tools Version
Should we be worried?Well, try out and tell us
... just kidding ... why risk something? Old Flir tools are working fine.True It would be way out of my league to mess with software on this level. I didn't save the complete ZIP of the last version but the new one's got a "terminatetrueupdate.exe" and it scares the crap out of an amateur like me.
InstallNet from 11/26
md5 B1E0E444F97ED212357A35AA71E29457
sha2 256 578A716CC9B790266EF92A14EAB09557D5BEC02152F3DF69FF49776B27C4DCD9
FLIR Tools / FLIR Tools+ 4.0 (4.0.13330.1003)
FLIR Reporter 9.2 PRO, 30-Day Evaluation (9.2.13330.1001)
FLIR Sensor Manager 3.10 (v3.10.0.0)
FLIR Sensor Manager 3.10 (v3.10.0.0)
FLIR ix v6.5.3 Update Pack (P/N: 6010X-XXXX)
FLIR Exx P/N:645xx / 646xx (3.12.7) Update Pack
FLIR Kxx (1.19.9) Update Pack
FLIR Ex (1.18.7) Update Pack
FLIR ResearchIR MAX 3.5 with SCxxxx and Xsc series drivers, 30-Day Evaluation (3.5.13277.1001)
FLIR ResearchIR 3.5, 30-Day Evaluation (3.5.13277.1001)
Hoping that they don't ding me too bad on the repair for mine... Dunno if the dog yanking the cord was the issue or not, but can't just straight up claim warranty...
Lesson learned.. No picture transfers near the pooch... (he is a tad rambunctious and got tangled in the usb when he jumped up on the couch )Did you remove the battery/hard reset the cam - and did you try the reset to factory settings funktion?
At this point its now stuck on the Flir start up screen... Removed the battery but no go. Is there another way to reset?
... got changed due to version information strings:
_TUProj.dat-> old: "http://cdn.cloud.flir.se/update/flir tools/4.0.13284.1003"
_TUProj.dat-> new: "http://cdn.cloud.flir.se/update/flir tools/4.0.13330.1003"
that .dat file beeing some .lua script made by/for TrueUpdate 3.0 - whoever likes to take a look - now you know where...
The URLs above seem to be some webservices or to require getting/posting some additional value
Also possibly helpful: /CHECK_UPDATE_AVAILABLE_ONLY
At this point its now stuck on the Flir start up screen... Removed the battery but no go. Is there another way to reset?
That doesn't sound too good. What did you do to that poor camera? With a bit of luck it "only" hangs on trying to startup appcore. As in, if you had RNDIS enabled before mucking about you might still have ftp + telnet because these services are seperate from appcore + the gui with which you interact. If that is the case I suggest you do a full download of all files now. Yes, again even if you did that already in the past. And obviously to a seperate location so that you have both old and new situation.
It may just fail on some messed up resource / config file combination, but no way to be sure.
At any rate, if you are still having this problem after battery removal etc ... try ftp-ing all files.
Nothing as exciting as that. "http://cdn.cloud.flir.se/update/flir tools/4.0.13284.1003" is just the url prefix for where to grab the iso/exe/zip file. That XML you see is just because the other end is just some REST api serving binary blobs. And when you configure that mickeysoft style, you get that XML on a 404.
Nothing as exciting as that. "http://cdn.cloud.flir.se/update/flir tools/4.0.13284.1003" is just the url prefix for where to grab the iso/exe/zip file. That XML you see is just because the other end is just some REST api serving binary blobs. And when you configure that mickeysoft style, you get that XML on a 404.As you see I had added the direct DL link in my post ... so yes, I know that DL url ... but I'd suppose there's some mechanism to detect when a new version is available - and that version number can't be known by the old updater... well, time for a wireshark
Nothing as exciting as that. "http://cdn.cloud.flir.se/update/flir tools/4.0.13284.1003" is just the url prefix for where to grab the iso/exe/zip file. That XML you see is just because the other end is just some REST api serving binary blobs. And when you configure that mickeysoft style, you get that XML on a 404.As you see I had added the direct DL link in my post ... so yes, I know that DL url ... but I'd suppose there's some mechanism to detect when a new version is available - and that version number can't be known by the old updater... well, time for a wireshark
You also said "The URLs above seem to be some webservices or to require getting/posting some additional value ", which is the bit I was responding to. No webservice there. Definitely not at an url that already contains the version string in it.
But running the update + wireshark should show you fast enough where it gets it's "new update available" information from.
But running the update + wireshark should show you fast enough where it gets it's "new update available" information from....it does
Flir Tools on start:
http://internalstore.flir.com -> StatusCode: 302, Moved temporarily -> Location: http://www.flir.com/internalstore/
http://www.flir.com/internalstore/ -> Http: Request, GET /,
Query:/?productname=FLIR%20Tools&licensefileid=50040&licenseserialnumber=&computername=EXISTS&username=EXISTS/EXISTSALSO
= Reply: HtmlPayload: <!DOCTYPE html ... <title>FLIR Tools</title> ... <meta http-equiv="Content-Type" ....
Flir Tools Updater:
Ipv4: Dest = cdn.cloud.flir.se ... aka ....msecn.net (microsoft windows azure cloud I assume)
UserAgent: TrueUpdate 3.5
Http: Request, GET /update/flir%20tools/4.0.13284.1003/flir_tools.ts1
Http: Request, GET /update/flir%20tools/4.0.13284.1003/flir_tools.ts2
Http: Request, GET /update/flir%20tools/4.0.13284.1003/flir_tools.ts3
Reply contains an executeable file
I've detected no further traffic from Flir Tools - but note that I have an extensive hosts-file and might be blocking google analytics attempts this way - a second packet sniff would be helpful here
I installed the Flir Windows driver, enabled the RNDIS + UVC on the cam, and tried to connect to the cam via 192.168.0.2. Upon connection the page showed but no files were listed.
I installed the Flir Windows driver, enabled the RNDIS + UVC on the cam, and tried to connect to the cam via 192.168.0.2. Upon connection the page showed but no files were listed.
use whatever ftp client you like. ftp connect to 192.168.0.2, user=flir, pass=3vlig, grab all files.
I installed the Flir Windows driver, enabled the RNDIS + UVC on the cam, and tried to connect to the cam via 192.168.0.2. Upon connection the page showed but no files were listed.
use whatever ftp client you like. ftp connect to 192.168.0.2, user=flir, pass=3vlig, grab all files.I have found that not all FTP clients work - filezilla is fine