Tag Archives: cloud connectivity

Calling all Makers, visionaries and innovators up for a (IPSO) Challenge!


How do you IPSO? There are many problems in everyday life that can be solved by collecting data thru sensors, or by controlling smart objects based upon inputs from a variety of sources.


Once again, the IPSO Alliance has initiated its annual challenge, whose deadline for proposals is quickly approaching!

ipso2

The IPSO CHALLENGE was launched as a way to show what is possible utilizing the Internet Protocol (IP) and open standards in building the Internet of Things. Enter this global competition by submitting a proposal before July 15 2015 for a working prototype that is innovative, marketable and easy to use.

Just a few weeks ago, I had the opportunity to speak to a potential group of IPSO CHALLENGE participants in Colorado Springs, Colorado. This meetup was created to enable potential participants to learn about the challenge, mingle with like-minded individuals, find team members with the skills needed to implement ideas that are already being considered or to find those with like interests and come up with an innovative project proposal.

As a proud sponsor of the IPSO CHALLENGE 2015, my goal on behalf of Atmel was to describe how our wireless and MCU solutions can be used to form the basis of the hardware and software platforms that should be considered for a number of innovative IP-based challenge entries.

The incentive? Over $17,500 up for grabs in prizes with first taking home $10,000, $5,000 for the runner-up and $2,500 for third. There are many problems in everyday life that can be solved by collecting data thru sensors, or by controlling smart objects based upon inputs from a variety of sources. The Internet of Things and the Internet Protocol are a smart choice as the means to publish and subscribe to  sensor information, and make this available for processing in the cloud, or to deliver this information to mobile devices for viewing or notification anywhere in the world.

One of the development kits that is being promoted for use in the IPSO CHALLENGE is the ATSAMR21-XPRO evaluation board. This kit supports the ATSAMR21 (IEEE 802.15.4-compliant single-chip wireless solution) wireless “system in package” device.

SAMR21_XPRO

The device contains both an ARM Cortex M0+ microcontroller plus the AT86RF233 2.4ghz 802.15.4 radio. This combination makes the perfect solution where a low power wireless sensor or actuator is required ,as an element of the hardware platform needed to implement your CHALLENGE entry.

The SAM R21 is the ideal platform to support a 6LoWPAN wireless mesh network, with sensors that can be used to measure and collect  data, or control outputs, while also having the ability to transfer this information to the cloud, or to any PC or mobile device, that has an internet connection anywhere in the world.

SAM R21 device IO assignments:

SAMR21

Atmel recently released its SmartConnect 6LoWPAN, a wireless stack firmware package that provides an IPV6 6LoWPAN implementation running on the SAM R21 evaluation kit, among a number of other Atmel platforms. Additionally, there are a number of example applications for SmartConnect 6LoWPAN that are provided in the free Atmel Studio 6.2.

AtmelStudio6

The example that I demonstrated during the IPSO meetup was the MQTT (MQ Telemetry Transport) example. MQTT is a publish/ subscribe protocol that allows the SAM R21 SmartConnect 6LoWPAN solution to implement topics like /Atmel/IoT/temperature or  Atmel/IoT/LED and then subscribe to, or publish to these topics while also allowing other devices to also subscribe  or publish to these same topics. This enables all these devices to work together in collecting and processing the content of many distributed sensors.

This is a very simple protocol that needs only a small amount of memory resources, and allows one to create a very effective distributed processing solution, where IP is used to enable communication and data transfer between all of the elements contained within the network.

SmartConnect 6LoWPAN, as with most 6LoWPAN solutions, makes use of the RPL mesh networking routing protocol. This lets these low power SAM R21 (15.4) radios to have the ability to transfer data over longer distances thru the wireless mesh. Because one only has to transfer the data to its nearest neighbor or its parent, in  the network that was formed.

Let’s take a look at a simplistic example of a problem, with a 6LoWPAN wireless mesh network solution: Your children take a school bus to school every morning, and if you could know when the school bus was in the neighborhood, or approaching the nearest stop, life would be a lot easier in inclement weather.

So you gather together a few SAM R21 kits and battery packs, and start to think about a solution.

Since you would need to know where the bus is at some distance from your home, this would eliminate “wired’ solutions, and since you probably would not have access to “mains power” at many of the sensing locations, the solution would require low power battery operated wireless sensors.  As it just so happens, the SAM R21 would make a perfect low power battery operated “wireless” sensor.  The SmartConnect 6LoWPAN wireless mesh network firmware would allow you to cover an extended range, by placing additional routing sensors where needed to keep track of the bus, and to relay or route similar data from other sensors that are too far away by radio, to get all the way back to your home base unit.

Given that you will need access to a fence post, a mailbox or telephone pole on your neighbors property in order to mount your small wireless sensors, you can tell them that they also can access this data to keep track of the school bus, or just about anything in the neighborhood that has a mobile tag  placed on it, whether it’s a young child’s backpack or jacket, a pet’s collar, etc.)

There needs to be one root location where all of the sensor data is transferred to, and this location will act as the  border router ( or dag root ) of the 6LoWPAN network. This is also implemented using the SAM R21 evaluation kit along with an Ethernet 1 XPRO interface board. This border router hardware would be located in your house, and plugged into a spare Ethernet port of the home access point that provides internet service to your home. Future options could also allow using Wi-Fi instead of Ethernet to make the connection to your home Wi-Fi access point.

A mobile sensor/tag will need to be placed on the bus (hopefully you can get permission, to place a small sensor using double sided tape inside the bus, or maybe ask the nice bus driver if he/she would carry it, or have one of the kids that gets on the bus early in the bus route for our neighborhood,  clip the mobile sensor to their backpack or belt .  How and where to place these mobile tag sensors, may actually be one of the most difficult parts to solve for this solution.

Once you have the mobile sensors in place on the bus, kids, dogs,  and cats, now you need to set up the sensor mesh around the neighborhood.

Atmel provides a tool call Atmel Wireless Composer.

WirelessComposer

This free tool  has a very nice feature that allows range testing to be done by one person.  Place one SAM R21 device in a fixed location and then take a battery operated remote node for a walk in your neighborhood.  You can  use this method to determine the typical range that you can achieve and  check potential mounting spots within the neighborhood. This can be used to insure that you can establish reliable wireless communications, and to find the location of where to place the  nearest neighboring node.

Remember to ask permission, before you mount the sensor node on someone else’s property.

As you turn on the remote nodes they will make their presence know to the network, and a route will be discovered back to the root node at your home.

mesh

Once you have established your network, a number of SmartConnect 6LoWPAN Example applications can be used to move the data around the network. By using the MQTT example previously mentioned, units can publish information as to which “mobile” tags are within wireless range of the sensor, thus providing a coarse location system, to notify those that are subscribing to a particular topic, as to the current location of the bus, child, dog or cat.

You can find the Example projects within Atmel Studio 6 as shown below:

ExampleProj

ExampleProj1

The power of  The Internet Protocol and the Cloud in this system is that each individual sensor has its own IPV6 address, and the data collected by the end sensor nodes is packaged into an IP frame, and  transferred thru the wireless network, and then thru the border router to the wired Internet. Then finally to the Cloud without having to convert or change protocols.  Today, there are so many devices that can make use of this data, including devices such as smartphone’s, tablets, laptops, and home automation hubs and gateways, What you can do with this data has endless possibilities.

Applications for these internet connected devices can be created to show the location of the bus or pet on a map, or maybe just send a simple notification of “School bus currently at the Smith family residence”….  Again the possibilities are endless.

Maybe you would also like to turn on your house lights or open your garage door when you approach your house from your car with a sensor mounted in the car. The info in the cloud can be integrated with your home automation system to control the lights and garage door.

Now that you have completed the proof of concept using  the Atmel | SAM R21 evaluation boards, or hopefully now that you have won the IPSO CHALLENGE!, you will want to turn your prototype into a deploy-able product.

Atmel has the solution for you.  SAM R21 “modules” are being developed in a small form factor that will allow the creation of a small battery operated mobile tag or sensor unit, and these modules come with an FCC certification ID, and a proven RF design, to eliminate the challenge, cost, and time required to develop a wireless product from scratch.

Feeling inspired? Submit your idea today before time runs out!

5 challenges of IoT connectivity

At last month’s MIT Technology Review Digital Summit, PubNub CEO Todd Greene discussed the importance of connecting Internet of Things embedded devices on a reliable and secure realtime network. CPU, battery, and bandwidth consumption, as well as security are all paramount considerations that need to be taken into account when connecting low-powered embedded devices.

You’ll find that when developing and networking Internet of Things devices in the lab, connectivity is fairly seamless. You may have a few embedded devices connected to a backend server, so latency isn’t an issue.

Internet of Things

However, deploying that IoT app on a global scale, to thousands or even millions of users simultaneously, is a whole other ball game. Unfortunately, the Internet isn’t just one big network, but rather is composed of an infinite amount of heterogeneous networks, including proxy servers, firewalls, cell towers, and WiFi networks, all slower and faster than one another.

As a result, there are 5 major challenges when it comes to Internet of Things connectivity. Keep scrolling down to see them, or watch the video below:

At PubNub, we think a lot about IoT connectivity and how we can make it as reliable, secure, and fast as possible. So to make PubNub the best network for connecting and signaling between Internet of Things devices, we first had to understand the challenges of doing so. Presenting the 5 challenges of IoT connectivity:

1. Signaling

When connecting IoT embedded devices, you need to start with bidirectional signaling to collect and route data between devices. Whether it’s embedded devices talking to a server to collect data, or devices signaling one another, you need to stream IoT signals and data quickly and reliably. You need to be 100% sure that that stream of data or signal is going to arrive at its destination every time.

2. Security

Security is a huge umbrella, but it’s paramount in Internet of Things connectivity and should be forethought, not an afterthought. For example, what good is a smart home if anyone can open your garage door? Here are three considerations for IoT security:

  • Authorization: When publishing or subscribing to stream of data or IoT signal, it’s essential to make sure that the IoT device or server has proper authorization to send or receive that stream of data.
  • Encryption: You need end-to-end encryption between devices and servers.
  • Open ports: An IoT device is dangerously vulnerable when it’s sitting and listening to an open port out to the Internet. You need birectional communication, but you don’t want to have open ports out to the Internet.

3. Presence Detection

Who’s there, (or in terms of IoT, what device is there)? It’s important to immediately know when an IoT device drops off the network and goes offline. And when that device comes back online, you need to know that as well.

Presence detection of IoT devices gives an exact, up to the second state of all devices on a network. This gives you the ability to monitor your IoT devices and fix any problems that may arise with your network.

4. Power consumption

IoT embedded devices are small and expensive, so CPU and power consumption need to be considered. When you have hundreds or even thousands of devices sending data and signaling one another, it takes a toll on power and CPU consumption. You need to maximize efficiency while minimizing power and CPU drain.

5. Bandwidth

In addition to power and CPU, bandwidth consumption is another challenge for IoT connectivity. Bandwidth on a cellular network is expensive, especially with hundreds of thousands of IoT devices on a network sending request/response signals to your server.

That’s a huge server issue and a requires a large scale server farm handling all this data. You need a lightweight network that can seamlessly transfer data between devices and servers.

Connecting IoT Devices with PubNub

Connecting devices in the lab is one thing, but once they’re out in the wild, it’s a whole new ballgame. So where do you start? Having a scalable IoT network to connect embedded devices and servers is especially critical for IoT applications with a large user base.

These are the types of Internet of Things challenges we’ve solved at PubNub. With over two hundred million connected devices connected to our global realtime network in fourteen data centers, we average 50 to 60 thousand transactions per second, peaking at over 3 million. PubNub is used to stream data and signal for hundreds of different IoT uses cases including:

  • Automotive: Connected cars need a realtime communication layer to stream data and signal between their fleet, dispatch, and the consumer on the app. Examples: Sidecar, Lyft, Easy Taxi, Gett, Zoomy
  • Home Automation: A realtime network can be used to signal and trigger actions for smart devices and home automation solutions. Examples: Insteon, Revolv, Vivint
  • Wearables: IoT wearables require a low latent, lightweight network to stream data between the device and a server. Battery, CPU, and bandwidth consumption are all important considerations that must be taken into account. Examples: 3rd Eye

By 2020, it’s estimated that there will be between 20 and 30 billion connected devices on the Earth. As a result, how we connect those devices should take precedence as the IoT field grows exponentially.

Crowdfunding the Open Enigma Project



An Enigma machine refers to a family of related electro-mechanical rotor cipher machines used in the 20th century for enciphering and deciphering secret messages.

The original Enigma was invented by the German engineer Arthur Scherbius at the end of World War I. According to Wikipedia, early models were used commercially from the early 1920s, although they were later adopted by a number of militaries and governments around the world.

Designed by the ST-Geotronics crew, the Open Enigma (M4) Project – powered by an Atmel-based Arduino Mega (ATmega1280) – first surfaced towards the end of 2013.

The project, which only recently hit Kickstarter, has already managed to exceed its original crowdfunding goal of $20,000. Stretch goals are now in effect, allowing the ST-Geotronics team to focus on delivering Enigma software enhancements (M3 emulation, Telex behavior, Cloud connectivity) and a new hardware version that uses the physical Plugboard.

“Even in today’s world of fast computers that can encrypt at exceptional levels like 68 bits, 128 bits, 256 bits, etc used for WEP, WPA, or even AES, the Enigma still offers decent and capable encryption capabilities. Any three of the 8 numbered rotors can be placed in any of the three positions on the shaft,” an ST-Geotronics rep explained on the project’s official Kickstarter page.

“There are 8x7x6 = 336 possible sequences of 3 rotors [and] 26 possible internal settings on each of the three rotors. This gives 26 to the third power = (17,576) possible settings. There are 26 possible external settings for each of the three rotors. This gives 26 to the third power = (17,576) possible settings. There are anywhere from 0 to 10 plug wires which can be inserted into any of the 26 sockets, [offering] roughly 532,985,208,200,576 possible settings. Combining these possibilities give us a total of 26,672,901,348,424,004,787,290,112 or about 10 to the 26 power possible starting settings.”

ST-Geotronics says it is committed to producing a goal of 100 units by hand, before shifting to less expensive factory manufactured units.

Interested in learning more? You can check out our original write up on Bits & Pieces here and the project’s official Kickstarter page here.