Infrared Data Association

Serial Infrared Protocol Layer

Test Guidelines

October 1995

© Copyright 1995, Infrared Data Association

1

1.0 INTRODUCTION		4
1.1 OBJECTIVE		4
1.2	SCOPE	4
1.3	REFERENCE	4
1.4 ACRONYMS AND DEFINITIONS		4
2.0 THE COMPLIANCE STATEMENT		5
2.1 TEST RESULTS		5
2.2 IRLAP QUESTIONS		5
2.3 IRLMP QUESTIONS		6
3.0 TEST ENVIRONMENT		7
3.1	PHYSICAL SETUP	7
3.2	E-M SOURCES	7
3.3	TEST PERSONNEL	7
4.0 DISCOVERY		8
4.1	SECONDARY (DS SERIES)	8
4.2 PRIMARY ONLY (DP SERIES)		8
5.0 CONNECTION		9
5.1	SECONDARY (CS SERIES)	9
5.2	PRIMARY ONLY (CP SERIES)	10
6.0 INFORMATION EXCHANGE		10
6.1	SECONDARY (IS SERIES)	10
DEVICE BUSY		13
INVALID NR		13
TEST FRAMES		14
LINK MANAGEMENT (LM SERIES)		14
REVERSE DATA		15
LM DISCONNECT (LD SERIES)		15
IAS (IA SERIES)		16
ROLE EXCHANGE (RX SERIES)		17
SECONDARY		17
PRIMARY		17
SNIFFING (SN SERIES)		17

2

SECONDARY	17
PRIMARY	17
CONNECTIONLESS DATA TX	17
CONNECTIONLESS DATA RX	17

3

1.0Introduction

1.1Objective

The purpose of this specification is to define the minimum behaviors that should be required of a device in order to receive the IrDA logo. The testing process is a verification of the claims made on the Compliance Statement. This specification will focus on the Protocol implementation.

IrDA believes that Testing to the Protocol is the most reliable means of assuring interoperability and compatibility between devices.

1.2 Scope

This document does not in any way replace or modify the IrLAP or the IrLMP Protocol specifications. If this Test Specification requires behaviors that conflict with the behaviors defined in the Protocol specifications, the Protocol specifications will prevail and the Test specification will be changed.

It is assumed that each implementer has thoroughly tested their device during and after development. The test cases defined herein do not exercise every combination of commands and parameters that are possible to encounter during a given transaction. The requirement of demonstrating the behaviors defined below will give IrDA, its member organizations and the end user a certain level of confidence that a device bearing the IrDA logo will interoperate with other devices having complementary functions.

Test cases that have been defined in this specification are intended to exercise, at some level, all of the behaviors that a device must support. Where optional behaviors are claimed to be supported by a device they must also be tested to ensure that they conform to the Protocol specifications.

All IrDA devices must be able to assume the Secondary role. Since the capabilities of a Primary device exceed the capabilities of a Secondary Only device, there will be additional tests required of a Primary.

Interoperability testing should be a part of the Compliance process. This specification does not attempt to define the method or extent of interoperability testing to be required. Implementers should attempt to create environments and conditions that will reflect the most common usage of their device. Successes and failures of their implementations should be noted on the Compliance Statement. Implementers should diagnose the failures to help identify shortcomings in either the devices involved or the Protocol itself.

1.3 Reference

The Test case results are assumed to be interpreted in the context of :

•The IrDA Link Access Protocol (IrLAP) version 1.0 dated June 23, 1994

•The IrDA Link Management Protocol (IrLMP) version 1.0 dated August 12, 1994

•Errata Changes to these documents dated TBD.

1.4 Acronyms and Definitions

BOF	Beginning of Frame character. Can be 0xC0 or 0xFF. Last one must be 0xC0.
bps	Bits per second.
C/R bit	Command/Response bit. When set to one it indicates the frame is a Command frame.
CRC	Cyclic Redundancy Check. Used to verify the integrity of the data in a frame.

4