Hello
Yesterday i will test for upgrade my flir E4 2.3 to E8 but when i used set_permantly-RNDIS.fif (find in e4hack3c in this tread) i can't connect me to my E4 with 192.168.0.2 and i can't remove RNDIS because he is not connect ....
I think i forget to make something but i don't know what.
I need your help
Thanks
Did you install drivers from support.flir.com? In your device manager Flir should be listed as a network adapter while it is in RNDIS mode.
Hello
Yesterday i will test for upgrade my flir E4 2.3 to E8 but when i used set_permantly-RNDIS.fif (find in e4hack3c in this tread) i can't connect me to my E4 with 192.168.0.2 and i can't remove RNDIS because he is not connect ....
I think i forget to make something but i don't know what.
I need your help
Thanks
Did you already try to change the menu with '<ToolBar name="scale_scale_manual"/>' in the file 'toolbar-config.xml' to make a change button on the camera scaleMenu in stead of toggling from unlock tot lock in scaleMenu for manual setting of temperature? Or can't the menu not be changed so easily as I say or think?
In the flir updatepack 2.3.0 are more ToolBar names for the file toolbar-config.xml. Can they easily put into the camera or is this dangerous for bricking the camera? I think you did maybe already try this?
Fre
I use W8
All you need is to disable and then enable the "flir usb video" in device manager , then timeout notice will be fixed
Did you already try to change the menu with '<ToolBar name="scale_scale_manual"/>' in the file 'toolbar-config.xml' to make a change button on the camera scaleMenu in stead of toggling from unlock tot lock in scaleMenu for manual setting of temperature? Or can't the menu not be changed so easily as I say or think?
In the flir updatepack 2.3.0 are more ToolBar names for the file toolbar-config.xml. Can they easily put into the camera or is this dangerous for bricking the camera? I think you did maybe already try this?
FreI have bit different files in my camera, there are more menu stuff and more commands.
Then I can see what becomes visible when I change or hack something. I release only stuff what working
correctly and there no others test lines in files. That _manual" have no affect so far but I add first zoom
what is actually digital zoom and in 8x mode show you 40x30 image. Before I played with reso I saw
this is its minimum thermal resolution.
I need help. I don't know yet anything about files I am using. These are from first 2.3.0Menu_Upgrade.zip
They are smaller than inside ADDMENU-BETA3. Who made them or who can make them? I can't use
ADDMENU-BETA3, in 2.3.0 camera picture is black. But something I can't do here. That manual temp
scale is fighting back. And there is black holes in conf.cfc files. What might be after
.caps.config.image.zoom.maxFactor double 8 to the # IDXXXXXX? Somehow PIP too is not cooperative
with me... Or something is blocked in UI/conf.cfc whose contents I have no clue... yet
All other stuff might be done in near future.
Are you just guessing at what commands might work and what lines to add or do you have something to compare against like a dump of an actual e8 file and trying to copy them over and see if they work?
:box:Recent Zoro purchase arrived. 2.3.0 .
Not a big deal. Performed the upgrade on a win xp machine. Picture much better, Flir Tools reports full resolution. Thank you to everyone who contributed to that, and thank you to Flir for making this camera. Oh, I don't want to open debate about Flir downgrading units to make a range, but that noise generator is shocking. I can imagine Flir salesmen telling big lies to prospective customers "oh, look how much better picture is on E8". I don't feel so bad about upgrading my E4 resolution.
I also uploaded 2.3.0_Menu_5. It took a while to copy over, and I now note the "Special Editon" in place of the 2.3.0 revision on the boot up splash screen. The extra colour palettes are great. I am pleased.
Question: How do I revert camera to full original out of box condition? I assume I run 2.3.0 Fimware update as released by Flir. It would be good to be able to fully factory reset camera if I ever need to.
I tried running the 2.3.0_Menu_Restore (included with the Menu_5 zip), but it doesn't make any difference. I also note the camera fails to connect. I am only using RNDIS_temporary.
I don't want to break anything, so I have stopped fiddling with it for now. (Waiting for my lens to come from China for some close up PCB work and general electronics - what I want to use the camera for.)
It's a good idea "for all 2.3 owners, I think" to grab the firmware before it is updated so you can revert to the original 2.3.0 firmware incase the camera fails to boot. I've already had to do this once.
Make sure you are not in RNDIS mode and apply the firmware with FLIRInstallNet.exe
It takes a while so do not unplug or interrupt the process until completed. Also make sure you have the drivers installed, they can be found on page 1 of this thread.
Just to add another data point, I ordered from Zoro when the second 25% coupon code was posted. Shipped from Spartanburg, SC and arrived yesterday. Inside was an early Christmas present of 1.22 software with an April 2014 calibration date. I was eventually able to configure the camera with TiConfig (thanks marphy!). The hardest part was finding a working XP installation to get Flir's own drivers working. I was not able to to get them working in either Windows 8 or 10, they would install and recognize the camera then I would get the "ThermaCAM connecting to 192.xxxx" type message, but it would not connect to the camera, nor was the IP address ping-able. Finally got the drivers working in a Windows XP Pro virtual machine running under vmware.
I set out to do the FTP-based update from a Win 8 machine, and couldn't connect to the camera. This may have been because I didn't disable all my other network interfaces. I tried again on a Win7 machine, this time with TiConfig.