Updated Attachment J1 - DA2 Bluetooth Remote Control Specification.docx

Attachment J1 DA-2 Bluetooth Remote Control Specification

1. Scope This document covers the specification for a handheld Bluetooth remote control for the DA-2 Digital Talking Book Machine, produced for the National Library Service for the Blind and Print Disabled (NLS), Library of Congress.

The requirements of this specification, susceptible to objective and subjective evaluation, must be fulfilled. NLS may reject proposed design requirements that fail to address the specific needs of NLS users.

Contractors who consider submitting a bid to design and manufacture this remote control device should be cognizant of the consumer-responsive nature of the program, and that the design been developed must meet the special needs of users in the program. Contractors are expected to familiarize themselves with the equipment-handling practices of blind and physically handicapped clientele and ensure that the products they produce will stand up under this type of use. A high degree of quality workmanship and product reliability is mandated by the product design specifications, that includes labeling, packaging, and preparation for delivery.

2. Reference Documents The following documents and publications, of the issue in effect on the posting date of the RFP, form a part of this specification. In the event of conflict between the documents and publications referenced herein and the content of this specification, the content of this specification shall be considered a superseding requirement.

2.1 Specifications

2.2 Standard

American National Standards Institute (ANSI)

The document cited above is available from:

American Society for Quality Quality Press 611 East Wisconsin Ave.

P.O. Box 3005 Milwaukee, WI 53201-3005 Internet: www.asq.org/quality-press/

2.3 Definition of Terms

· EMI – Electromagnetic Interference

· ESD – Electrostatic Discharge

· IR – Infrared

· RF – Radio Frequency

· PCB – Printed Circuit Board

· RH – Relative Humidity

· System – Bluetooth transmitter and receiver

· HID – Human Interface Device

· BLE – Bluetooth Low Energy

· GATT – General Attribute

· SSP – Secure Simple Pairing

· DTBM – Digital Talking Book Machine

· DA-2 – Model of DTBM

3. Bluetooth Requirements

3.1 Protocol

The remote control shall operate using the Bluetooth protocol as defined in Bluetooth Core Specification 4.2. The remote control shall support Bluetooth Low Energy (BLE).

3.2 Frequency Band

The remote control shall operate between 2.400GHz to 2.4835GHz frequency band. The channels used are from 2.402GHz to 2.480GHz, with 1MHz increments for all 79 channels.

3.3 Antenna

The remote control shall support an internal antenna embedded within the remote control and not visible and not protrude outside of the remote.

3.4 Bluetooth Profile

The remote control shall support the Bluetooth HID profile.

3.5 Bluetooth Pairing

The remote control shall support Secure Simple Pairing (SSP) mode with “Just Works” requiring no input from the end user. The pairing and unpairing of the Bluetooth remote control from the DA-2 shall be initiated from the DA-2 through the DA-2 settings menu. The DA-2 Bluetooth settings have the option to pair new devices and delete Paired device. It lists the paired devices that need to be unpaired using voice prompt. The menu is controlled by the keypad and the user can scroll through the paired devices to delete the one he/she chooses. Once a device is chosen to be deleted from the paired device list, it is disconnected and removed from the paired list.

3.6 Bluetooth Unpairing

The remote control shall support unpairing of any paired Bluetooth device.

4. General Requirements

4.1 Operating Temperature

The remote control shall meet performance requirements when operating at temperatures between 0°C - 40ºC

4.2 Operating Environment

The remote control shall meet performance requirements when operating in environmental conditions at 20°C+ 5°C at a relative humidity of 10% - 90% (non-condensing)

4.3 Storage Environment

The remote control shall meet performance requirements after exposure to an environment of -45°C uncontrolled RH, 38°C 85% RH, 60°C uncontrolled RH.

4.4 Drop test

The remote control shall meet performance requirements after drop testing on all sides per section 12.1.4 of UL 60065 except that the surface is not covered with hardwood or plywood and the sample must survive 3 drops.

4.5 Vibration test

The remote control shall meet performance requirements after exposure to vibration cycling per section 12.1.2 Vibration Test of UL 60065.

4.6 Key presses

The remote control shall be able to distinguish between a key that is pressed and remains down (long press) and a key that is pressed repeatedly.

4.7 Operating distance

The remote control shall meet performance requirements when operating within 30 feet between remote control and the DA-2 DTBM.

4.8 Electronic components

a. The remote control shall meet performance requirements when exposed to EMI as prescribed in IEC 61000-6-1.

b. The remote control shall meet performance requirements after exposure to ESD as prescribed in IEC 61000-4-2.

c. The remote control shall comply with RoHS lead free directives, and solder-ability requirements

d. The PCBs of the remote control shall provide connections for programming and loading firmware via a computer.

e. The remote control shall comply with FCC Part 15 requirements for a class B device.

4.9 Firmware

The remote control’s firmware bootloader shall include the ability to upgrade to a new version of the firmware. The vendor shall provide a PC based software tool for the remote control firmware upgrade by connecting the remote control to the PC via hardware cable. In the event of a corrupted bootloader, the entire firmware image of the remote control shall be upgradeable via a recovery mechanism.

3.11 Safety

a. The remote control shall not be constructed of materials which are flammable per applicable specifications in UL 60065

b. The remote control shall not be constructed of materials which may cause bodily harm by contact, inhalation, or ingestion.

c. The remote control shall not be constructed of materials which will outgas hazardous vapors in excess of 0.1% collected volatile condensable material or in excess of 1% total material loss, when tested to ASTM E595-93.

5. Physical Requirements

5.1 Weight

The remote control shall weigh no more than 0.25 lbs (115 grams) nominal (batteries included).

5.2 RF Energy Exposure Limit

The remote control shall meet the RF energy exposure limit in terms of Specific Absorption Rate (SAR) limit set by FCC guidelines. The remote control shall meet the allowable FCC SAR limit of 1.6 watts per Kilogram (W/kg) as averaged over one gram of tissue.

5.3 Provision for a lanyard

The remote control shall include a provision for a 2 feet lanyard that will allow remote control to be worn around neck, shoulder, or wrist. It is required for the lanyard to be included with the device and for it to be attachable to the device.

5.4 Key debounce

The remote control firmware shall employ key debouncing on button press to prevent spurious key events.

5.5 Key life expectancy

The remote control keys shall meet performance requirements for at least 100,000 cycles.

5.6 Battery System

The remote control shall operate via battery power. The battery system shall meet the following requirements:

a. Two AA alkaline cells

b. Battery life shall be at least 2 years (Normal usage)

c. DC Current consumption shall not exceed 10mA max, and 20µA max when idle (nominal)

d. Design to incorporate reverse battery polarity protection.

e. Batteries shall be replaceable by users with minimal manual dexterity and shall not require the use of hand tools.

5.7 Size

The remote control‘s total size shall not exceed the following dimensions:

Width: 2 in Height: 1.2 in Length: 6.8 in Note: (All dimensions are nominal maximums)

5.8 Stability

The remote control shall not rock or slide on a flat surface.

5.9 Audible feedback

The remote control shall provide audible feedback to the user for indication of a button press. The feedback shall be able to be turned on and off by the user via the use of a sliding switch.

5.10 Key Pad

a. Shape:

The shape of the keys for the keypad shall match the shape and proportionality of the keys for the NLS digital talking book machine (DTBM) model DA-2. An image of the DA-2 keypad is below.

Contractors are able to propose their own layout designs for the buttons as long as they fit within the size parameters of the device.

b. Braille dots:

The keys shall have braille dots molded into them or in the plastic casing next to it. Each key shall contain the braille dot pattern that represents the first letter of function (e.g. V for volume, T for tone, S for speed, etc.) The exception shall be the book mark key which shall have M for mark.

c. Control functions:

The remote control shall provide keys to control all of the functions of the DTBM model DA-2.

d. Color: Keys shall be color coded to match colors of the keys on the DTBM.

e. Key actuation force:

f. Material: Silicon rubber or equivalent and shall be resistant to sunlight and fluorescent lamp. (Sample of existing keypad for digital talking-book machine available upon request)

5.11 HID Key Mapping

The remote control shall use following mapping table for HID key mapping. The values for the Standard and DA2 Custom keys are defined in the attached source code file in Appendix A.

Mode

KEY_BARD

Tone up

KEY_TONE_UP

6. Packaging

6.1 Shipping carton

The remote control shall be packaged in an individual shipping carton.

The shipping carton shall meet the following requirements:

a. The carton shall contain individual inserts to protect the remote control during shipping.

b. The carton shall have markings indicating the material is eligible for shipping via USPS Free Matter for the Blind

c. The carton shall have a blank space available for application of a shipping label.

The final dimensions and artwork of the shipping carton shall be submitted to NLS for approval.

6.2 Overpack (Master box)

The individually packaged remote controls shall be packaged together in an overpack or master box. The number of individual units packaged together shall be determined such that the weight of the overpack does not exceed 15 pounds. The overpack container shall meet the following requirements:

d. The container shall have markings indicating the material is eligible for shipping via USPS Free Matter for the Blind

e. The container shall have a blank space available for application of a shipping label.

The final dimensions and artwork of the overpack container shall be submitted to NLS for approval.

Appendix A: input_event.h /* SPDX-License-Identifier: GPL-2.0-only WITH Linux-syscall-note */

* Input event codes

* *** IMPORTANT ***

* This file is not only included from C-code but also from devicetree source

* files. As such this file MUST only contain comments and defines.

* Copyright (c) 1999-2002 Vojtech Pavlik

* Copyright (c) 2015 Hans de Goede <hdegoede@redhat.com>

* This program is free software; you can redistribute it and/or modify it

* under the terms of the GNU General Public License version 2 as published by

* the Free Software Foundation.

#ifndef _INPUT_EVENT_CODES_H #define _INPUT_EVENT_CODES_H

* Device properties and quirks

* Event types

* Synchronization events.

* Keys and buttons

* Most of the keys/buttons are modeled after USB HUT 1.12

* (see https://urldefense.com/v3/__http://www.usb.org/developers/hidpage__;!!EDx7F7x-0XSOB8YS_BQ!f4TzQeo_vpp44TnwI4x8iokn6HdtRoFVbCtaaKs00rpvR8IjGyJguVFElkn3dA7HnG-E56HSTbF7ycKtoqpwC2c$ ).

* Abbreviations in the comments:

* AC - Application Control

* AL - Application Launch Button

* SC - System Control

#define KEY_BATTERY 236

#define KEY_UNKNOWN 240

#define KEY_MICMUTE 248 /* Mute / unmute the microphone */

/* Code 255 is reserved for special needs of AT keyboard driver */

/* Diagonal movement keys */

#define KEY_ROOT_MENU 0x26a /* Show Device's Root Menu */ /* Show Top Menu of the Media (e.g. DVD) */

* Toggle Audio Description: refers to an audio service that helps blind and

* visually impaired consumers understand the action in a program. Note: in

* some countries this is referred to as "Video Description".

* Control a data application associated with the currently viewed channel,

* e.g. teletext or data broadcast application (MHEG, MHP, HbbTV, etc.)

/* Electronic privacy screen control */ #define KEY_PRIVACY_SCREEN_TOGGLE 0x279

/* Select an area of screen to be copied */ #define KEY_SELECTIVE_SCREENSHOT 0x27a

* Some keyboards have keys which do not have a defined meaning, these keys

* are intended to be programmed / bound to macros by the user. For most

* keyboards with these macro-keys the key-sequence to inject, or action to

* take, is all handled by software on the host side. So from the kernel's

* point of view these are just normal keys.

* The KEY_MACRO# codes below are intended for such keys, which may be labeled

* e.g. G1-G18, or S1 - S30. The KEY_MACRO# codes MUST NOT be used for keys

* where the marking on the key does indicate a defined meaning / purpose.

* The KEY_MACRO# codes MUST also NOT be used as fallback for when no existing

* KEY_FOO define matches the marking / purpose. In this case a new KEY_FOO

* define MUST be added.

* Some keyboards with the macro-keys described above have some extra keys

* for controlling the host-side software responsible for the macro handling:

* -A macro recording start/stop key. Note that not all keyboards which emit

* KEY_MACRO_RECORD_START will also emit KEY_MACRO_RECORD_STOP if

* KEY_MACRO_RECORD_STOP is not advertised, then KEY_MACRO_RECORD_START

* should be interpreted as a recording start/stop toggle;

* -Keys for switching between different macro (pre)sets, either a key for

* cycling through the configured presets or keys to directly select a preset.

* Some keyboards have a buildin LCD panel where the contents are controlled

* by the host. Often these have a number of keys directly below the LCD

* intended for controlling a menu shown on the LCD. These keys often don't

* have any labeling so we just name them KEY_KBD_LCD_MENU#

/* We avoid low common keys in module aliases so they don't get huge. */

* Relative axes

* 0x0a is reserved and should not be used in input drivers.

* It was used by HID as REL_MISC+1 and userspace needs to detect if

* the next REL_* event is correct or is just REL_MISC + n.

* We define here REL_RESERVED so userspace can rely on it and detect

* the situation described above.

* Absolute axes

#define ABS_VOLUME 0x20

#define ABS_MISC 0x28

* 0x2e is reserved and should not be used in input drivers.

* It was used by HID as ABS_MISC+6 and userspace needs to detect if

* the next ABS_* event is correct or is just ABS_MISC + n.

* We define here ABS_RESERVED so userspace can rely on it and detect

* the situation described above.

#define ABS_RESERVED 0x2e

* Switch events

#define SW_JACK_PHYSICAL_INSERT 0x07 /* set = mechanical switch set */

* Misc events

* LEDs

* Autorepeat values

* Sounds

#endif image1.jpeg