Has anybody figured out if the E4 sensor is capable of 30 FPS (or at least north of 9 FPS), and is just being firmware limited?
I hope if anybody has figured it out, they'll keep it nice and quiet! Publication of such a hack would surely bring the federal heat against FLIR who would then have no choice but to lock the next firmware down tight, and likely put much tighter protection on future models, too. And this party in many respects is just getting started. (I have two more friends who've bought E4's in the last week because of it.)
Without any inside knowledge, the only things we know for certain are that they are not so concerned about it that they are in any hurry to change the current situation (from which we can probably reasonably infer that a framerate hack is probably not viable) , and that they have sold a number of additional units that they wouldn't otherwise have sold as a direct result of hackability.
Speaking of buying cameras, given the CES announcement, this hack serves them doubly: First, it gets a bunch of people outside their traditional market talking about the tech, enjoying their products, and popularizing their brand. Second, it clears out a bunch of low-end stock that might become difficult to sell once the iphone thingus is on the market. The cellphone gizmo isn't gonna eat much into Exx sales, but it'll certainly take a bite of E4's lunch. Who knows how many E4 housings, slightly-bad FPAs, etc, they have sitting around that they're now able to sell to us?
.power.settings: (12)
laserAllowed true <-- useless
laserEnable false <-- useless
My dad's older FLIR has a laser-pointer, which personally I find to be a gimmick, but his clients love it. ("High-tech" is apparently a very subjective thing, needing only be "higher tech than the observer encounters on a frequent basis".) Might its presence in these files perhaps suggest a function for some of those unpopulated pads on the board?
Some Ex0 model would be nice to check what's beeing used as WLAN / BT
I wouldn't be surpised if the double-digit series cameras would be built around the same core design - display and sensor specs look identical to me.
Wouldn't surprise me either. With a bit of luck they use it as bluetooth uart with bspserial. If so, then even if you couldn't get the exact same module you would probably still be able to rig up something decent. That said, it would be really nice if someone could check what bluetooth module is being used in the higher end models.
Speaking of unpopulated pads! Yeah, this is my next big area of interest. They'd probably not bother with different bluetooth chipsets (and thus drivers and debugging effort) between models, at least not without a good reason (and part obsolescence would be one, but let's hope not!). So if we can get a peek at the chips in one of the BT-equipped units, it seems reasonable that grafting a similar chip into an E4++ might yield paydirt.
Anyone? Anyone? Bueller?
I *hate hate hate* having to plug in my USB cable to get images off this thing. Bluetooth would be sweet. An SD slot (into which I could drop an eyefi/pqi/transcend wireless SD card) would be even sweeter, because then I control the card's behavior. (the latter cards run linux, btw.)
Sooo. Any hints that this board shares anything with SD-slot-equipped models? The USB cable opening at the top is suspiciously big; I wouldn't be surprised if there was a daughterboard. Are there any hints of SD capability in the configs, etc? I haven't gone digging, this is all just wishful thinking on my part.
Hey, anyone tried a USB OTG cable on this sucker yet? I don't have one handy but might poke at that tomorrow.