- •1.1 Objective
- •1.2 Scope
- •1.3 Reference
- •1.4 Acronyms and Definitions
- •2.0 The Compliance Statement
- •2.1 Test Results
- •2.2 IrLAP Questions
- •2.3 IrLMP Questions
- •3.0 Test Environment
- •3.1 Physical Setup
- •3.2 Electromagnetic Interference Sources
- •3.3 Test Personnel
- •4.0 Discovery
- •4.1 Secondary (DS Series)
- •4.2 Primary Only (DP Series)
- •5.0 Connection
- •5.1 Secondary (CS Series)
- •5.2 Primary only (CP Series)
- •6.0 Information Exchange
- •6.1 Secondary (IS Series)
- •Device Busy
- •Invalid Nr
- •Test Frames
- •Link Management (LM Series)
- •Reverse Data
- •LM Disconnect (LD Series)
- •IAS (IA Series)
- •Role Exchange (RX series)
- •Secondary
- •Primary
- •Sniffing (SN series)
- •Secondary
- •Primary
- •Connectionless Data Tx
- •Connectionless Data Rx
IA6. |
Verify that the DUT will respond with NoSuchAttribute if a query is made to an attribute |
|
it does not have. |
Role Exchange (RX series)
Secondary
RX1. Confirm the ability to exchange roles by accepting data from a Primary device, request Role Exchange and send data back to what is now the Secondary.
RX2. Confirm the ability to recover from a denied request for Role Exchange by accepting data from a Primary, requesting Role Exchange, have the Primary send DXCHG. Show the ability to recover and accept data from the Primary.
Primary
RX1. Respond to a Secondary’s request for Role Exchange (XCHG), accept data after the exchange to confirm the Role Exchange.
Sniffing (SN series)
Secondary
SN1. Demonstrate the proper time sequencing and format of the sniffing procedure.
SN2. Perform sniffing with a Primary that supports sniffing. Respond properly to the SNRM and develop a connection without going through the Discovery procedure.
SN3. Perform sniffing with a Primary that doesn’t support sniffing. Respond properly to a Discovery procedure and develop a connection.
Primary
SN1. Demonstrate the ability to connect to a device whose address was discovered through sniffing.
Connectionless Data Tx
From within a LAP connection send a UI frame to the connetionless LSAP 0x70. Ensure that the Nr/Ns counters are unaffected.
Connectionless Data Rx
Receive data on the connectionless LSAP 0x70. Ensure that the Nr/Ns counters are unaffected.
17
When Your Infrared Device Isn’t “Fully” IrDA Compliant ...
What you can do
If you have run your device against the IrDA certification test bucket and it failed to pass all of the tests, you can explain your deviation and ask for an exception be granted.
Typical grounds for an exception being granted:
1.Illogical case for your product to support
2.You don’t intend to support this particular case
3.Non-fatal errors
4.(what else?)
Where you can send your request/explanation
Send your request (by mail) to: |
IrDA Protocol Compliance Committee |
|
c/o IrDA |
|
Number Street |
|
City, State Zip |
Send your request (by e-mail) to: |
IRDA@NETCOM.COM |
You need to explain both the problem (giving the exact reason for the non-compliance) and your position.
What will happen to your request
This information will be distributed to the IrDA Protocol Compliance Committee for review and a response.
You can expect the committee to either approve your deviation or request that you make a change to improve/correct the deviation.
What response time you can expect
You can expect a response in two to four weeks.
07/27/95
18