Perhaps you saw our press release today about our Integrated Development Environment for sensors?  If you didn’t, or you’re looking for more information, here’s why this is really, really exciting…

• All-in-one tool: The IDE is a one-stop shop for developing and implementing sensor algorithms into a QuickLogic sensor hubs.   It combines algorithm development and testing with the hardware to deploy those designs on – all from the same supplier.
• The IDE is specifically-purposed for QuickLogic sensor hub customization.   Our IDE is built specifically for sensor algorithms, and built specifically around our ArcticLink 3 S1 ultra-low power sensor hub line.  No laundry list of functions that clog up your hard drive and do nothing but confuse you.  The IDE is exactly what a sensor hub development engineer needs — nothing more, and certainly nothing less.
• IP Security: our customers take the security of their IP very, very seriously.  If you are a regular reader here at HotSpots, you’re likely accustomed to me saying “I can’t answer that due to NDA concerns”.  That extends even further — many of the system designers at our (potential or current) customers, even when under NDA, are still not allowed to share certain information with us.  The IDE addresses that — customers can use our FFEAT software to port their home-grown algorithms to our sensor hub — without QuickLogic ever being exposed to that code.  While we are always willing and able to assist our customers with these tasks (and certainly do), having a development environment operating on a customer’s computer is an invaluable selling tool.
• Engineers familiar with C/C++ are able to come up to speed on our programming language quickly.  As you can imagine, the public announcement of the IDE was preceded by introduction to key engineers at potential customers — after a short training, the general consensus of those engineers was (paraphrased) “this doesn’t look like a complicated learning experience.”

And finally, there are always going to be customers who don’t have internal algorithms, or need something quick — we always have our Always-on Context Aware Sensor Hub or Multi-axis Sensor Data Buffer Catalog CSSPs for that.  Fully compatible with the Android KitKat operating system, these Catalog CSSPs, along with traditional CSSPs developed on the S1 platform, offers the promise of always-on context awareness at <2% of the system battery life.