LocalSense

Gregory Menvielle

Unknown

2 1

Bringing localization and communications to people who want to keep their resources safe and secured ...learn more

Mobile, RealSense™, Networking, Internet of Things

Overview / Usage

At the core of LocalSense is the drive towards using IoT to keep people safer in very specific environments where administrators need to know about people and devices’ whereabouts to better inform, prevent, and react.

Check out our intro video here: https://youtu.be/EQ38igNJVCs

LocalSense was born during the Dublin Innovators' Summit when different people in our group realized they had recently met with customers facing a very real problem that could be solved using different tools available in our respective repertoires.

Hardware:
LocalSense is at the POC level so we are using readily available hardware. Because we are taking a “component-first” approach, it would be simple to switch the hardware components around.
For example, a given device may use too much power in certain environments. That’s ok, just switch it and LocalSense will keep on rollin’

· We use Real-Sense technology for face-recognition and voice synthesis.
In a production case, we go with the Intel SR-300 because of its advanced recognition capabilities. Though in demos you should be able to get away with a lower res camera (we use the one on our MacBook Pro as well).

· IoT devices were connected to Intel Edison using an arduino shield and the Grove Seed Kit. Obviously other cards should work. We’ve run a few tests on the Intel Galileo as well.

· For beacons we selected Estimotes. Many companies are entering the Beacons’ business both as iBeacons for iOS and their Android counterpart. As long as you get the right technical spec about the beacons you can use anything you want. Technically you can even turn an Edison into a beacon if you are so inclined.

· Intel NUC act as local servers where we store some data that we do not want broadcast to an external network (someone’s face data for example)

Software:
· Intel XDK IoT edition where we build the code deployed on the Edison. We also use the XDK to emulate + test our companion App
· Node.js on the Edison server. Again, you could use something else as long as you can make REST/HTTP calls

Communication and Device management:

From the get-go we knew that communication routing would be one of the challenge of the projects. We are using SmartNotify™ patent-pending technology to route communications and events between humans and machines. Gregory is part of SmartNotify™