Top Banner
IOT BEST PRACTICES: PICKING A PROTOCOL (for embedded development that sucks less) @farmckon @BuLogics
22

IoT Best Pratices Picking A Protocol

Aug 07, 2015

Download

Devices & Hardware

farmckon
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: IoT Best Pratices   Picking A Protocol

IOT BEST PRACTICES:PICKING A PROTOCOL

(for embedded development that sucks less)

@farmckon @BuLogics

Page 2: IoT Best Pratices   Picking A Protocol

PICKING THE RIGHT WIRELESS PROTOCOL IS KEYIt defines your ecosystem, your sales channel, and pretty much everything else.

Page 3: IoT Best Pratices   Picking A Protocol

Key factors determined by your wireless choice

• Device price • Sales channels, partners, integration

options• Physical Range, power lifetime (battery,

etc) • Debugging complexity• Debug and Development time

Page 4: IoT Best Pratices   Picking A Protocol

Most Common Wireless Protocols• WiFi• Bluetooth • Bluetooth LE • Z-Wave • Zigbee• Others (Thread, Instion, etc)

Page 5: IoT Best Pratices   Picking A Protocol

Key Metrics (in human terms)• Network Type• Mesh, Star, Point-to-Point, Tree, …

• Range:• A table, a room, a house, a block, several blocks

• Data Rate• A text, a photo, a song, choppy video, a movie

• Developer Tool Quality:• Anyone, Hobbyist, Pro, Grey-Beard

• Batterie Lifetime• an Hour, a few hours, a few days, 2 years, N/A

Page 6: IoT Best Pratices   Picking A Protocol

WiFi Overview• Stats:• Network: Star; Range: house• Data-rate: up to movie; Tools: anyone • Batteries: a few days*

• Well loved; 802.11 family of technologies• Wavelan (1991ish) -> 802.11b … profit? • Ubiquitous standard for wireless internet communication.• Well built and tools abound.

Page 7: IoT Best Pratices   Picking A Protocol

WiFi Weaknesses• Very energy intensive. Slow ramp-up time(~1 sec)

• Pairing securely or picking a network is a pain.

• Complexity of a whole networking stack.

• Point-to-point style network is a limit

• Bad for: Simple, battery-powered, cheap devices; fast-response behavior

Page 8: IoT Best Pratices   Picking A Protocol

WiFi Strengths• Great data through-put.

• Excellent standard; evolving and expanding.

• Ubiquitous in many homes & businesses.

• Good for: Wall-wart devices, streaming data, “cloud” connected devices or projects

Page 9: IoT Best Pratices   Picking A Protocol

Bluetooth Overview• Stats:• Network: Point-to-Point; Range: desk• Data-rate: song; Tools: pro • Batteries: a few years

• Since 1994. Invented by Ericsson.• “Replace USB cable” style communication• Lots of devices, good adoption in the phone world.• Bluetooth up to v3 is “Basic Bluetooth”.

Page 10: IoT Best Pratices   Picking A Protocol

Bluetooth Weaknesses• Device-to-host model is limiting.

• Phone-centric; few gateways or home-install devices.

• Bad for: Distance transmission, multiple devices, complex networks, large amounts of data

Page 11: IoT Best Pratices   Picking A Protocol

Bluetooth Strengths

• Device-to-host model is simple.

• Low power. Lots of devices to pair to.

• Easy to test. Lots of tools and developer kit.

• Good for: Audio streaming, data sensors, pico-networks, peripherals

Page 12: IoT Best Pratices   Picking A Protocol

Bluetooth LE Overview• Specs:• Network: Star; Range: desk+• Data-rate: photos; Tools: hobbyist, • Batteries: A few years

• Subsection of “Bluetooth 4” standard.• Was a separate standard “Wibre”.• Just reaching decent adoption with the latest phones.

Page 13: IoT Best Pratices   Picking A Protocol

Bluetooth LE Weaknesses• Not compatible with Bluetooth 3.0 or older.

• Potential problems in joining (or discovery).

• New standard. Still growing in adoption.

• No good “gateway” device available. (Yet.)

• Bad for: Streaming lots of data, long range, mesh scenarios

Page 14: IoT Best Pratices   Picking A Protocol

Bluetooth LE Strengths• Low power.

• Extensive (and growing) install base.

• Lots of familiarity in the mobile/app field.

• Good for: Rechargeable battery-powered sensors; data collection; simple, end-user devices

Page 15: IoT Best Pratices   Picking A Protocol

Z-Wave Overview• Stats:• Network: mesh; Range: house• Data-rate: text; Tools: super-pro*• Batteries: a few years

• Sigma Designs and the Z-Wave Alliance.• Well specified (private) protocol stack.

Page 16: IoT Best Pratices   Picking A Protocol

Z-Wave Weaknesses• Captive eco-system; no open standard.

• Developer kit is rough around the edges.

• Complexity for backwards compatibility.

• Bad for: Streaming video, wifi, long-range, pairing to phones

Page 17: IoT Best Pratices   Picking A Protocol

Z-Wave Strengths• Mesh network = More coverage

• 1,000 certified devices.

• Clear “Pass/Retry/Fail” certification.

• Good integration partners.

• Good for: Security systems, house control, simple sensor reports, scene/settings changes

Page 18: IoT Best Pratices   Picking A Protocol

Zigbee Overview• Stats:• Network: mesh(ish); Range: house • Data-rate: text; Tools: hobbyist • Batteries: a few years

• IEEE 802.15 based with “flavors”.• A mesh network system, but often used point-to-point.• Well liked by DIY and hobbyists.

Page 19: IoT Best Pratices   Picking A Protocol

Zigbee Weaknesses• Lots of “flavors” that can pass, but can’t parse other flavor messages.

• Not many controllers, integrators or gateways on the market.

• Bad for: Streaming video, wifi, long-range, pairing to phones

Page 20: IoT Best Pratices   Picking A Protocol

Zigbee Strengths

• Easy to get started with. Decent starter kit.

• Public standards; multiple vendors; no single gatekeepers, but there are per-flavor gatekeepers.

• Good for: Home automation, smart lighting, wireless sensor networks , DIY projects, remote control

Page 21: IoT Best Pratices   Picking A Protocol

Other Protocols• Thread

• 900MHz Random Stuff

• Instion

Page 22: IoT Best Pratices   Picking A Protocol

Questions? Comments?

Now Go Eat Cookies.@farmckon

Bulogics.comFarMcKon.net