I called PASS in the UK today, which is where I got my E4, to place an order for some Fluke gear.
The salesman got chatting about the E4 and the hack and said "you were lucky, the next lot are going to be hack proof"..to which the answer would be "well good luck with selling those then..."
Yes I was very tempted!
The salesman got chatting about the E4 and the hack and said "you were lucky, the next lot are going to be hack proof"
Btw - did anybody have success in taking a look into an Exx series model yet?
I'd really love to know what wlan/bt hardware is beeing used there - and where it is connected
Btw - did anybody have success in taking a look into an Exx series model yet?
I'd really love to know what wlan/bt hardware is beeing used there - and where it is connected
But Flir tools doesn't seem to be very useful for anything so not a big deal.
Ah well, even if FLIR does make the E4 "hack-proof," I'm sure there will be other ways to hack it.
since there will still be a way to update the firmware the easiest thing would be to have the 1.18 firmware look like 1.22 and 'update' the camera with that.
Btw - did anybody have success in taking a look into an Exx series model yet?
I'd really love to know what wlan/bt hardware is beeing used there - and where it is connected
I can probably help with an E8 but it all hinges on the E4 i've got on order being co-operative or not.
Has anyone looked further into the role the I2C EEPROM is playing? Mike's earlier comments on it were interesting. It looks like one of you guys with an already co-operative E4 could explore the bus with i2c.exe.
If the rumor is true, it may be possible to add some interesting features to Ex series.
If the rumor is true, it may be possible to add some interesting features to Ex series.
I would raise that from rumor to very likely, but perhaps a different FPGA? Take a look at the Exx series firmware for proof and have a dig around in the .fif files.
The Exx firmware also has additional FPGA .bin files fpga_c4_55.bin & fpga_c55.bin. Looks like it went through a hardware change too, as those seperate files relate to different revisions of the Exx camera. Also, c4_55 and c_55 look like they might relate to some of Altera's own part codes (i'm not an FPGA guy)?
Many of the error strings in the Ex firmware reference features that are only available on the Exx.
The Exx firmware also has additional FPGA .bin files fpga_c4_55.bin & fpga_c55.bin. Looks like it went through a hardware change too, as those seperate files relate to different revisions of the Exx camera. Also, c4_55 and c_55 look like they might relate to some of Altera's own part codes (i'm not an FPGA guy)?
I noticed that after charging, a ghost image of the battery symbol that's shown during loading is still visible when the camera is active.
Does this happen only for me?
I tried stuff like switching to digital camera mode and watching a white wall hoping the "burnt in" image would go away, but no success so far.
apt-get install tofrodos
Btw - did anybody have success in taking a look into an Exx series model yet?
I'd really love to know what wlan/bt hardware is beeing used there - and where it is connected
I can probably help with an E8 but it all hinges on the E4 i've got on order being co-operative or not.
Has anyone looked further into the role the I2C EEPROM is playing? Mike's earlier comments on it were interesting. It looks like one of you guys with an already co-operative E4 could explore the bus with i2c.exe.
The trick is obviously to use winscp as ftp client because winscp doesn't suck, but mostly ..... use flir/3vlig (aka not what you used).
Damn it, "3lvig" is given several times in this thread. So obviously the the one time it worked I misspelled it and by chance got the correct "3vlig" spelling this way.
Thanks, I was about to get crazy.