DOCSLIB.ORG

Ios Hardware As a Sensor Platform: DMM Case Study

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Ios Hardware As a Sensor Platform: DMM Case Study iOS Hardware as a Sensor Platform: DMM Case Study Daniel Brateris Dwight Bedford, David Calhoun, Aaron Johnson, Atlanticus Innovations Nickolas Kowalski, Kelli Martino, Thomas Mukalian, 1082 Sky Hill Road Justin Reda, Anthony Samaritano and Robert R. Krchnavek Bridgewater, New Jersey 08807 Rowan University Email: [email protected] Glassboro, New Jersey USA http://www.atlanticusinnovations.com/contact Email: [email protected] Abstract—iOS is Apple’s mobile operating system and is communication hardware and functional user interfaces. In presently used on the iPhone, iPad, and iPod Touch. The hard- this context, an accessory is an attachment to the iOS hard- ware platforms associated with the iOS operating system provide ware. The attachment can be physical through the 30-pin a powerful platform for sensor applications. In this paper, we provide a case study on the development of a digital multimeter dock connector (UART serial data transfer or USB 2.0 data (DMM) using an iPod Touch. The DMM case study addresses the transfer) or virtual through a wireless (Bluetooth) connection major subsystems (hardware, software, and firmware) of a typical [2]. The accessory would contain the sensing elements as sensor platform and specific advantages of implementation using well as associated hardware. The designer can focus on the an iOS device. development of the electronics and instrumentation within the accessory. Once data is digitized or the control process can I. INTRODUCTION accept digital commands, then the device can be hooked up An embedded sensor system can often utilize a relatively to an iOS device to exchange data and be configured and simple, low-cost microcontroller to achieve the required mea- controlled. The device gains all the functionality offered by surement functionality. However, as the sensor increases in the iOS operating system. complexity, requiring network connectivity or a graphical user Apple’s iOS operating system is used on over 82 million interface, the processor requirements increase significantly and products. It has become one of the most ubiquitous operating so does development time. Communication protocols such as systems/hardware platforms. WiFi, Ethernet, and 3G require a large processing overhead. Some advantages: Graphical user interfaces have similar overheads while the • Low cost. An iPhone can be purchased for $200 (with core processing requirements of the sensor application remain a wireless plan). An iPod Touch running iOS can be relatively simple. purchased for $229. Developing sensor applications using Apple’s iOS system • Communications. An iPhone comes complete with Wi-Fi offers several advantages over traditional, high-performance, and 3G communication capabilities built in. An iPhone embedded system development. The combined feature set also includes Bluetooth technology. An iPod does not of the iOS operating system and associated devices offer a have 3G capability, but does include Bluetooth and Wi-Fi. highly attractive platform for embedded development. The • Camera/video and audio interface. core features offered in iOS devices are a high performance • Easy updates and distribution via the iTunes store or a ARM CPU, power supply, battery management, WiFi support, private distribution server. 3G support, rich touch-based user interface support and many • Software-defined interface. more. • Rigidly controlled and documented development tools. The iOS operating system is a fully featured modern oper- ating system, which is extensively documented and fully sup- II. CASE STUDY:DEVELOPMENT OF AN IOS-BASED DMM ported by Apple Inc. Offering more functionality for a lower development cost than many embedded operating systems, iOS The development of an iOS-based digital multimeter provides a unique alternative. Additionally, there are thousands (DMM) provides a comprehensive study of using iOS-based of application examples and hundreds of books written on devices for sensor platforms. Figure 1 is a block diagram indi- developing iOS applications. Overall, the operating system is cating the required subsystems for an iOS-based DMM. There state of the art and the hardware is proven, affordable, and are 4 essential subsystems. First, to attach a hardware device readily available [1]. to an iOS system, Apple requires an authentication routine Using an iOS accessory as the processing and connec- to be performed. Second, the attached hardware requires a tivity portion of a system will allow the designer to avoid microcontroller to handle communications between the iOS the difficulties normally encountered in developing reliable device and the sensor. Third, the sensor, in this case a DMM, 978-1-4244-8064-7/11/$26.00 ©2011 IEEE is required. And finally, an interface needs to be developed for B. DMM Development the iOS. Details on these subsystems are presented below. Single-chip solutions, e.g., Maxim 133, exist for DMM products. Unfortunately, we did not find a chip that worked Accessory Inputs and Outputs at less than 9 volts. For example, the MAX133 required a 9 V supply [5]. The voltage supplied from the connector on the iPod Touch is 3.3 V. Therefore, a system requiring 9 V would Sensor Elements either require a separate battery in the accessory or a DC/DC and Instrumentation Electronics boost conversion circuit to raise the voltage. Adding a separate 9 V battery significantly increases the size of the accessory. Even watch-type batteries in series add to the size of the accessory. A booster circuit has a minimal impact on size, but Accessory could potentially cause RF noise problems. These problems Microcontroller Authentication can cause performance issues when used with cellular devices Hardware like the iPhone. A second problem with using the MAX133 for this appli- cation is the inability to write information to the registers on 30-Pin Connector (USB, UART) or Bluetooth the device to control its functions. Our goal was to use the same microcontroller required for authentication to control the accessory. The MAX133 is primarily designed to be controlled 30-Pin Connector (USB, UART) or Bluetooth using a rotary switch. This significantly complicated the design goal of using a microcontroller to set the functions. WiFi and 3G With this in mind, we decided to create the DMM using a Operating System User Interface analog MUX to select resistor values followed by an ADC. iOS Hardware iOS The schematic of the DMM is shown in Fig. 2. Final part numbers, values, and DMM performance will be presented at Fig. 1. A block diagram indicating the major subsystems of the accessory SAS and in the final manuscript. and the iOS hardware. A. Authentication Membership in the Apple Made for iOS (MFi) program gives the licensed company access to the resources necessary to design, build and test an iOS accessory. This includes hard- ware components, technical documentation, technical support, and certification logos. After joining this program a licensed developer can build accessories that communicate with iOS applications through the 30-pin dock connector over USB, UART serial, or wirelessly over Bluetooth. Developers also have access to Developer Technical Support and Compatibility Labs to assist in product development and testing [3]. Membership in the program is a simple process and requires a day or two of effort between your company and Apple Inc. The technical materials required for development are confidential so your company must sign an NDA with Apple. Fig. 2. Schematic representation of the DMM circuit. Once completed, developing an accessory is a relatively easy process requiring a basic knowledge of microprocessors and a few simple communication protocols [2]. C. Microcontroller – Atmel AVR Mega Series Authentication is Apples unique way of controlling what devices are allowed to communicate with iOS applications The processor is the center of the accessory; it manages and Apple devices. Registered MFi developers have access communication between the iOS device and the electronics in to a microchip called the Authentication Coprocessor [4]. the accessory. For the DMM an Atmel AVR microprocessor This device stores proprietary algorithms and keys required was selected because of its low cost and relatively high for the authentication process. Details on the authentication performance in the 8-bit MCU realm. Selection of a processor process are provided to MFi members and development kits is entirely up to the designer of the accessory, only a few are available to speed product development [3]. criteria need to be met. For this design the criteria were: • At least one UART interface with simultaneous bi- are developed or the privacy of your protocols. This means directional support. an accessory can be developed to use a private or public 2 • Hardware I C or SPI support. protocol. As an example, the initial DMM accessory uses a • Extremely low power consumption. basic application that functions as a standard DMM. If we • Minimum of a 10-Bit linear ADC with multiple ADC were to publish our protocol, companies could develop their channels. own iOS applications to work with our DMM accessory. If a • Flexible boot loader with UART support for field company wanted a long term voltage recording system, they firmware upgrades. could design an iOS application to read and record the data • Flexible interrupt controller. over time and then send the data to a server every day. This • Minimal required external components and internal os- application could be built using the already existing DMM cillator. that
Load more

Recommended publications
  • Mfi Licensing Handbook – Development Licensees
    MFi Licensing Handbook – Development Licensees Release R1.2 October 7, 2013 MFi Licensing Handbook - Development Licensees R1.2 Apple Need-to-Know Confidential 1 Table of Contents MFi Development License Overview 4 How to Work with an MFi Manufacturing Licensee ................................................4 If You Will Develop the Accessory Yourself ...............................................................................................5 If You Will Not Develop the Accessory Yourself .........................................................................................5 If Your Manufacturer is not an MFi Manufacturing Licensee .....................................................................5 MFi Accessory Lifecycle ...........................................................................................5 What is a Product Plan? ............................................................................................................................6 MFi Link .......................................................................................................................6 Managing Your Company’s MFi Portal Account 7 MFi Program Confidentiality .....................................................................................7 Who May Access the MFi Portal ..............................................................................7 Multiple Corporate Domain Names ...........................................................................................................7 Who May Not Access the MFi Portal
    [Show full text]
  • Working with Ios Accessories
    Working with iOS Accessories Session 201 Emily Schubert Manager, Accessory Interface iPod | iPhone | iPad Accessories These are confidential sessions—please refrain from streaming, blogging, or taking pictures 1 Introduction • iOS provides interfaces for applications to interact with external devices • New opportunities in iOS 5 2 Working with iOS Accessories • AirPlay • Bluetooth • Accessory updates 3 AirPlay Peter Langenfeld Feature Manager iPod | iPhone | iPad Accessories 4 5 Audio Video Photos Mirroring 6 Supports standard Wi-Fi 7 Audio • Multiple endpoints in sync • Discrete volume control • Remote app • ALAC and AAC ■ ~2 second latency Mac and PC 8 Audio • Stream audio • Volume control • Any app can route audio • ALAC and AAC ■ ~2 second latency 9 Video • Stream video • Any app can route video ■ Local content ■ Web apps 10 Photos • Stream photos • Play slideshows • Use transitions 11 AirPlay Mirroring • Just like wired mirroring • Games, web, apps • Rotate screen on TV • Any app can route dedicated screen UI ■ ~100ms latency 12 AirPlay Accessories 13 AirPlay Accessories 14 Audio Video Photos Mirroring 15 Using AirPlay 16 Using AirPlay 17 Using AirPlay 18 Using AirPlay 19 Using AirPlay 20 Using AirPlay 21 Using AirPlay in Your App • Audio ■ Use MPVolumeView • Video ■ Use MPMoviePlayerController or AV Foundation • System handles the rest ■ Presence of AirPlay devices triggers route button appearance ■ User can access system volume levels, video routes, and audio routes 22 Adding a Volume View to Your Hierarchy • Make sure you do not
    [Show full text]
  • SKAA Wireless Audio Standard
    SKAA Wireless Audio Standard Bluetooth and AirPlay are the dominant wireless audio standards today, but are still challenged by closed platforms or low quality audio. Will SKAA rise as a viable alternative? Executive Summary Two dominant consumer wireless audio standards exist in the installed base today, Bluetooth and Apple’s Airplay. In spite of their popularity, neither standard was developed to deliver minimal setup or high quality audio across a myriad of different products. SKAA is an alternative wireless audio standard that could challenge both Bluetooth and AirPlay. The two primary reasons for this are SKAA’s focus on ease of connection, synchronized broadcast capability and quality of service. Moor Insights & Strategy is recommending that the consumer audio ecosystem take another look at the SKAA consumer wireless audio standard for their premium audio implementations. Bluetooth Bluetooth is an industry standard managed by the Bluetooth SIG which has 18,000 members. The wireless standard is a broad-based design with many uses in cars, exercise equipment, computers, consumer electronics, health and fitness devices, phones, tablets, and printers. The standard is extremely pervasive with the Bluetooth SIG announcing there are 2.5B end points since inception. Those aren’t the amount of devices in use, but those devices that have been sold. Because Bluetooth can carry very sensitive data, it requires pairing between devices. It can take up to five different steps to pair devices the first time. Once a device is paired the first time, it should stay in place for the next time, but as many have experienced, this connection is very unreliable.
    [Show full text]
  • Iphone Developer Program License Agreement
    PLEASE READ THE FOLLOWING LICENSE AGREEMENT TERMS AND CONDITIONS CAREFULLY BEFORE DOWNLOADING OR USING THE APPLE SOFTWARE. THESE TERMS AND CONDITIONS CONSTITUTE A LEGAL AGREEMENT BETWEEN YOU AND APPLE. iPhone Developer Program License Agreement Purpose You would like to use the Apple Software (as defined below) to develop one or more Applications (as defined below) for the iPhone and ¡Pod touch. Apple is willing to grant You a limited license to use the Apple Software to develop and test Your Applications on the terms and conditions set forth in this Agreement. Applications developed under this Agreement can be distributed in two ways: (1) through the App Store, if selected by Apple, and (2) on a limited basis for use on Registered Devices (as defined below). Applications that meet Apple's Documentation and Program Requirements may be submitted for consideration by Apple for distribution via the App Store. If submitted by You and selected by Apple, Your Applications will be digitally signed by Apple and distributed through the App Store. Distribution of free (no charge) Applications will be subject to the distribution terms contained in Schedule 1 to this Agreement. If You would like to distribute Applications for which You will charge a fee, You must enter into a separate agreement with Apple ("Schedule 2"). 1. Accepting this Agreement; Definitions 1.1 Acceptance In order to use the Apple Software and related services, You must first agree to this License Agreement. If You do not or cannot agree to this License Agreement, You are not permitted to use the Apple Software or related services.
    [Show full text]
  • Wiirelless Accessory Confiiguratiion User Manual
    Wireless Accessory Configuration User Manual March 2016 silabs.com | Building a more connected world. Wireless Accessory Confi guration User Manual About this Document This document gives an overview of the Apple MFI program implemented for Redpine’s n-Link module and gives the user information on how to configure the n- Link module using WAC. silabs.com | Building a more connected world. Page 3 Wireless Accessory Confi guration User Manual Table Of Contents 1 Introduction ........................................................................ 5 2 Application Overview ........................................................... 6 2.1 Setup Required ................................................................... 6 2.2 Software / Utilities Required............................................... 6 2.3 Installing the required utilities ............................................ 6 3 Compiling the driver and the application ............................. 8 4 Executing the Application .................................................... 9 5 Limitations......................................................................... 14 silabs.com | Building a more connected world. Page 4 Wireless Accessory Confi guration User Manual 1 Introduction The Apple MFi program is a licensing program for iOS device accessories and technologies manufactured by third party companies. The acronym MFi stands for “Made for iPod”, “Made for iPhone” or “Made for iPad”. It is designed to set up the wireless accessories with the credentials stored in the iPhone/iPad. After configuring the module using the iPhone/iPad, this accessory can only be accessed/operated using the iPhone/iPad. More information can be obtained from WAC_POSIX_Server_1.22 documentation. silabs.com | Building a more connected world. Page 5 Wireless Accessory Confi guration User Manual 2 Application Overview The application developed is used to demonstrate how to configure the nLink module using WAC. 2.1 Setup Required 1. Linux machine. 2. n-Link module, with the IAP chip integrated to the I2C interface.
    [Show full text]
  • Apple Developer Enterprise Program License Agreement
    CHIEDIAMO ALL’UTENTE DI LEGGERE ATTENTAMENTE I SEGUENTI TERMINI E CONDIZIONI DELL’ACCORDO DI LICENZA PRIMA DI SCARICARE O UTILIZZARE IL SOFTWARE APPLE. I PRESENTI TERMINI E CONDIZIONI COSTITUISCONO UN CONTRATTO LEGALE TRA L’AZIENDA O ORGANIZZAZIONE DELL’UTENTE E APPLE. Apple Developer Enterprise Program License Agreement (per applicazioni aziendali a uso interno per i dipendenti) Scopo L’azienda, organizzazione o istituto scolastico dell’Utente desidera utilizzare il Software Apple (come definito di seguito) per sviluppare una o più Applicazioni a uso interno (come definite di seguito) per prodotti a marchio Apple con iOS, watchOS, tvOS, iPadOS e/o macOS e per distribuire all’interno dell’azienda, organizzazione o istituto scolastico queste Applicazioni esclusivamente per uso interno da parte dei dipendenti oppure per un uso limitato come espressamente stabilito nel presente documento. Apple è disposta a concedere una licenza limitata per utilizzare il Software Apple per sviluppare e testare le Applicazioni a uso interno dell’Utente e per distribuire tali Applicazioni internamente, nonché come consentito ai sensi dei termini e delle condizioni stabiliti nel presente Accordo. L’Utente può inoltre creare Pass (come definiti di seguito) da utilizzare su prodotti a marchio Apple che eseguono iOS o watchOS ai sensi del presente Accordo. Le Applicazioni a uso interno sviluppate per macOS possono essere distribuite ai sensi del presente Accordo utilizzando un Certificato Apple oppure possono essere distribuite separatamente. Nota: Questo Programma è per applicazioni personalizzate a uso interno, sviluppate per scopi aziendali specifici e per l’uso esclusivo da parte dei dipendenti e, in casi limitati, da alcune altre parti come stabilito nel presente documento.
    [Show full text]
  • Apple Developer Program License Agreement Terms and Conditions Carefully Before Downloading Or Using the Apple Software Or Apple Services
    PLEASE READ THE FOLLOWING APPLE DEVELOPER PROGRAM LICENSE AGREEMENT TERMS AND CONDITIONS CAREFULLY BEFORE DOWNLOADING OR USING THE APPLE SOFTWARE OR APPLE SERVICES. THESE TERMS AND CONDITIONS CONSTITUTE A LEGAL AGREEMENT BETWEEN YOU AND APPLE. Apple Developer Program License Agreement Purpose You would like to use the Apple Software (as defined below) to develop one or more Applications (as defined below) for Apple-branded products. Apple is willing to grant You a limited license to use the Apple Software and Services provided to You under this Program to develop and test Your Applications on the terms and conditions set forth in this Agreement. Applications developed under this Agreement for iOS Products, Apple Watch, or Apple TV can be distributed in four ways: (1) through the App Store, if selected by Apple, (2) through the Custom App Distribution, if selected by Apple, (3) on a limited basis for use on Registered Devices (as defined below), and (4) for beta testing through TestFlight. Applications developed for macOS can be distributed: (a) through the App Store, if selected by Apple, (b) for beta testing through TestFlight, or (c) separately distributed under this Agreement. Applications that meet Apple's Documentation and Program Requirements may be submitted for consideration by Apple for distribution via the App Store, Custom App Distribution, or for beta testing through TestFlight. If submitted by You and selected by Apple, Your Applications will be digitally signed by Apple and distributed, as applicable. Distribution of free (no charge) Applications (including those that use the In-App Purchase API for the delivery of free content) via the App Store or Custom App Distribution will be subject to the distribution terms contained in Schedule 1 to this Agreement.
    [Show full text]
  • Bluetooth® Modules That Simply Work with Iphone®, Ipad®, and Ipod® Devices
    Bluetooth® Modules That Simply Work with iPhone®, iPad®, and iPod® Devices Summary Microchip’s Bluetooth APL modules natively support iAP (iPod Accessory Protocol) data connections and directly manage authentication, reducing engineering effort and cost, and simplifying accessory product design. Apple® iOS devices such as the iPhone freely connect via the Bluetooth hands-free and headset profiles. However, establishing Bluetooth data connections with an iPhone, iPad or iPod requires a specific discovery class and authentication. Every Bluetooth accessory must have an Apple authentication co-processor. APL modules are based on the standard RN41-I/RM and RN42-I/RM, making them footprint compatible. Power, ground and UART connections are identical, and connection of the Apple authentication IC is direct to the module via a 2-wire interface. The Apple authentication IC is not part of the module. Customer must join and purchase authentication ICs through the MFi program. Features ■ Discoverable/Connectable with iPhone, iPod or iPad ■ Dual profile allows Bluetooth connections to other smartphone or computing platforms ■ Automatically stores Bluetooth address of the last paired device, for quick reconnection ■ Secure Simple Pairing (SSP) enables ‘no PIN code required’ operation Product Selector ■ Supports complete Microchip Bluetooth feature set Module Class Typ. Range Development Kit ■ Direct hardware connection to the authentication co-processor RN41APL-I/RM Class 1 ~100m RN-41-APL-EVAL* ■ Authentication without iAP firmware development RN42APL-I/RM Class 2 ~30m RN-42-APL-EVAL* *MFi membership is required to purchase the development kit of modules. Please check with your Development Tools Microchip Sales representative for availability: www.microchip.com/sales.
    [Show full text]
  • Mfi) Accessories FTF-CON-F0019
    Develop Made For iPod (MFi) Accessories FTF-CON-F0019 Rudan Bettelheim | Business Development Manager A P R . 2 0 1 4 TM External Use Agenda • Introduction to the Made For iPod (MFi) Program • Freescale MFi Solution Philosophy • Freescale MFi Solution Development Hardware • Freescale MFi Solution Software Support • Freescale MFi Solution Development Tools • Freescale MFi Solution Application Examples and Demos • Solution Support and Professional Services • Processor Families Supported by MFi Solution TM External Use 1 Introduction to the Made For iPod (MFi) Program TM External Use 2 Made For iPod (MFi) Program To develop Accessories or App-based accessories for iPhone®, iPad® or iPod® devices, a company needs an MFi (Made For iPod) license from Apple TM External Use 3 MFi Accessory Connection Options Wired Wireless Connection Lightning 30-pin BLE BT BT (MFi) WiFi MFi License Yes Yes No No Yes Yes Required Analog and Audio Digital No Yes Yes AirPlay Digital Wearables, MFi BT Some MFi Notes/ Supports all Home A2DP audio, Connection, Streaming functions not Comments MFi functions Automation, Handsfree Gaming audio supported iBeacon controllers TM External Use 4 https://developer.apple.com/programs/mfi/ TM External Use 5 Freescale MFi Solution Philosophy TM External Use 6 Freescale MFi Solution Philosophy • Develop a flexible solution supporting the full range of possible accessories, including but not limited to audio • Develop a solution supporting a wide range of existing Freescale MCU and MPU products, and capable of rapidly supporting
    [Show full text]
  • Ios Accessories
    iOS Accessories Session 701 Edwin Foo Manager, Accessory Interface iPod, iPhone, and iPad Accessories These are confidential sessions—please refrain from streaming, blogging, or taking pictures Introduction • How to make your app take advantage of iOS accessories ■ Use the External Accessory framework ■ Provide Now Playing metadata ■ Handle remote-control events • How to get started developing your own iOS accessories ■ Made for iPod/iPhone/iPad (MFi) ■ Bluetooth on iOS ■ AirPlay Working with iOS Accessories External Accessory Framework External Accessory (EA) Framework At a glance • Declare supported protocols • Handle connections • Open sessions • Interact with streams External Accessory Framework Backgrounded operation • Start/Stop UI required External Accessory Framework Backgrounded operation • Start/Stop UI required • Declare UIBackgroundModes key External Accessory Framework Backgrounded operation • Start/Stop UI required • Declare UIBackgroundModes key • Accessories must use different protocols for each concurrent app Accessory External Accessory Framework Backgrounded operation • Start/Stop UI required • Declare UIBackgroundModes key • Accessories must use different protocols for each concurrent app Accessory External Accessory Framework Backgrounded operation • Start/Stop UI required • Declare UIBackgroundModes key • Accessories must use different protocols for each concurrent app Accessory External Accessory Framework Backgrounded operation • Start/Stop UI required • Declare UIBackgroundModes key • Accessories must use different
    [Show full text]
  • 710 What's New in Homekit 04 FINAL
    System Frameworks Session #WWDC16 What’s New in HomeKit Session 710 Dennis Mathews HomeKit Engineering © 2016 Apple Inc. All rights reserved. Redistribution or public display not permitted without written permission from Apple. Overview Home Database Home Database Home Database Home Database Home Sharing Home Sharing Sharing Home Sharing Sharing • Owner invites users Home Sharing Sharing • Owner invites users • User accepts invitation Common Protocol Common Protocol Common Protocol Accessory Communication Accessory Communication Wi-Fi Bluetooth Low Energy Remote Access Apple TV Remote Access Apple TV Remote access gateway Security Security End-to-end secure Security End-to-end secure Perfect Forward Secrecy Security End-to-end secure Perfect Forward Secrecy Data is private HomeKit Accessories HomeKit Accessories What’s New in HomeKit What’s New in HomeKit What’s New in HomeKit Platform What’s New in HomeKit Platform New Accessories What’s New in HomeKit Platform New Accessories Framework Updates What’s New in HomeKit Platform New Accessories Framework Updates Platform Platform Home App Platform Home App Home App NEW iOS devices Home App NEW iOS devices Home App NEW Apple Watch Control Center NEW Platform Remote Access and Automation Remote Access and Automation Apple TV Remote Access and Automation NEW Apple TV Remote Access and Automation NEW Apple TV Remote access Remote Access and Automation NEW Apple TV Remote access Automation Remote Access and Automation NEW Apple TV Remote access Automation • Event & timer triggers Remote Access
    [Show full text]
  • Designing Accessories for Ios and OS X
    Core OS #WWDC14 Designing Accessories for iOS and OS X Session 701 Robert Walsh Manager, Platform Accessories © 2014 Apple Inc. All rights reserved. Redistribution or public display not permitted without written permission from Apple. Introduction Accessory interfaces Accessory protocols What’s new in iOS 8 and OS X Yosemite Program information and wrap up Glucose meters Health thermometers App-enabled accessories Wireless speakers Light bulbs Blood pressure monitors Speakers Storage devices Audio devices Garage door openers Headphones Heart rate monitors Hearing aids Game controllers iBeacon Video devices Thermostats Cases Glucose meters Health thermometers App-enabled accessories Wireless speakers Light bulbs Blood pressure monitors Speakers Storage devices Audio devices Garage door openers Headphones Heart rate monitors Hearing aids Game controllers iBeacon Video devices Thermostats Cases Accessory Interfaces Wireless • Bluetooth • Wi-Fi Wired • Lightning connector • USB • Thunderbolt 2 • Headphone remote and mic Bluetooth Bluetooth Low Energy Supported features iOS OS X App framework For more information General communication with apps ✓ ✓ Core Bluetooth Bluetooth Design Guidelines Apple Notification Center Service (ANCS) ✓ Notification Center Bluetooth Design Guidelines Hearing aid audio transport ✓ Core Audio MFi Program Bluetooth Design HealthKit HealthKit ✓ Guidelines MFi Program HomeKit ✓ HomeKit MFi Program iBeacon ✓ Core Location iBeacon Licensing Bluetooth Low Energy Supported features iOS OS X App framework For more information
    [Show full text]