Texas Instruments FPTVEH Software Specification
A92FPTVEH – Attachment 3
TI PROPRIETARY T E X A S I N S T R U M E N T S
INFORMATION
T I R I S
Internal Data S P E C I F I C A T I O N July 14, 1999
Originator:
Phillip LaCroix
Effective Date:
Software Specification
for
LUHF Vehicle Transponder (U.S.)
RI-TRP-VUSA
PRINTED COPIES OF THIS SPECIFICATION
ARE NOT CONTROLLED DOCUMENTS.
VERIFY THEIR CORRECT REVISION BEFORE USING.
Revision: Date:
Approval: Approval: Approval:
Function: Engineering Function: Operations Function: Software
Name: Loek D’Hont Name: Paul Angelo Name: Krishna D.
Date: Date: Date
RI-TRP-VUSA – Software Specification Page 1 of 16 11-09-05-701
A92FPTVEH – Attachment 3
TI PROPRIETARY T E X A S I N S T R U M E N T S
INFORMATION
Revision:
T I R I S
Internal Data S P E C I F I C A T I O N
TABLE OF CONTENTS
1. INTRODUCTION …………………………………………………………………………………. 1
1.1 SCOPE........................................................................................................................... 4
1.2 APPLICABLE DOCUMENTS ................................................................................................ 4
1.3 DEFINITIONS, ACRONYMS AND ABBREVIATIONS.................................................................. 4
2. PROTOCOL …………………………………………………………………………………………5
2.1 DOWNLINK ..................................................................................................................... 5
2.1.1 Downlink Formats....................................................................................................................... 5
2.1.2 Downlink Messages Ending....................................................................................................... 6
2.1.3 Downlink Messages ................................................................................................................... 6
2.1.3.1 Identification (Type 0)..................................................................................................... 6
2.1.3.2 Authentication (Type 1) .................................................................................................. 6
2.1.3.3 Account Data (Type 2).................................................................................................... 6
2.1.3.4 Reserved for Future Use (Types 3-7).............................................................................. 7
2.1.4 Customer Page ......................................................................................................................... 7
2.1.5 Encryption Key.......................................................................................................................... 7
2.2 UPLINK .................................................................................................................................. 7
2.2.1 Uplink formats ............................................................................................................................ 7
2.2.2 Uplink Message Beginning.........................................................................................................8
2.2.3 Uplink Messages........................................................................................................................ 8
2.2.3.1 Identification (Type 0)............................................................................................................. 8
2.2.3.2 Authentication (Type 1).......................................................................................................... 9
2.2.3.3 Account Data (Type 2).................................................................................................... 9
2.2.3.4 Reserved for Future Use (Types 3 - 15).......................................................................... 9
3. FUNCTIONAL REQUIREMENTS
…………………………………………………………….…..10
3.1 SOFTWARE OVERVIEW ...................................................................................................10
3.1.1 WAKE-UP................................................................................................................................ 12
3.1.2 WAIT........................................................................................................................................ 12
3.1.3 RECEIVE................................................................................................................................. 12
3.1.4 MESSAGE PROCESSING...................................................................................................... 13
3.1.5 RESPONSE ............................................................................................................................ 13
3.1.5.1 VCO Control.................................................................................................................13
3.1.6 DST ENCODER...................................................................................................................... 13
3.1.7 SLEEP.....................................................................................................................................14
4 MICROCONTROLLER HARDWARE INTERFACE …………………………………………..15
5 QUALITY ASSURANCE PROVISIONS ………………………………………………………..16
RI-TRP-VUSA – Software Specification Page 2 of 16 11-09-05-701
TI PROPRIETARY T E X A S I N S T R U M E N T S
INFORMATION
T I R I S
Internal Data S P E C I F I C A T I O N
A92FPTVEH – Attachment 3
Revision:
RI-TRP-VUSA – Software Specification Page 3 of 16 11-09-05-701
A92FPTVEH – Attachment 3
TI PROPRIETARY T E X A S I N S T R U M E N T S
INFORMATION
T I R I S
Internal Data S P E C I F I C A T I O N
Revision:
1. INTRODUCTION
1.1 SCOPE
This document describes the LUHF Vehicle Transponder Software Specification definition to
implement the TIRIS Automatic Recognition of Consumers (ARC) system. The scope of this
document extends from the Vehicle Transponder Hardware Specification. The interrelationships and
interfaces between the Vehicle Transponder Hardware Specification and this software specification
are defined in detail. The relationships of this software specification within the ARC system are
contained in the higher-level specifications (see 1.2 Applicable Documents, below).
If anything in this document is ambiguous or incorrect, it should be immediately reported to the
Project Managers for the Texas Instruments ARC Team, and corrected. This document is a TI
internal document only.
1.2 APPLICABLE DOCUMENTS
The hierarchy of documentation pertaining to this specification is depicted below.
Document
Number
06-01-02-700 ARC System Specification (U.S)
11-09-05-700 Hardware Specification for LUHF Vehicle Transponder
11-09-05-701 Software Specification for LUHF Vehicle Transponder
24-09-05-012 TIRIS Digital Signature Transponder Algorithm and Software Requirement
TQM TIRIS QUALITY MANUAL
1.3 DEFINITIONS, ACRONYMS, AND ABBREVIATIONS
ARC Automatic Recognition of Consumers
CRC Cyclic Redundancy Check
Downlink RF Data Transmission from Dispenser to Transponder (134 kHz Carrier)
LSB Least Significant Bit
LUHF Low / Ultra High Frequency
MSB Most Significant Bit
PLL Phase-Locked Loop
RFU Reserved for Future Use
TIRIS Texas Instruments Registration and Identification System
Uplink RF Data Transmission from Transponder to Dispenser (902.8 MHz Carrier)
VCO Voltage-Controlled Oscillator
Document Title
RI-TRP-VUSA – Software Specification Page 4 of 16 11-09-05-701
TI PROPRIETARY T E X A S I N S T R U M E N T S
INFORMATION
T I R I S
Internal Data S P E C I F I C A T I O N
2. PROTOCOL
The protocol to be used by the transponder is as follows:
A92FPTVEH – Attachment 3
Revision:
Downlink Message Downlink Type Downlink
Format
Identification 0 1 Identification 0 1
Authentication
(first challenge)
Authentication
(second & subsequent)
Account Data 2 2 Account Data 2 1
Reserved for Future
Use
The Downlink messages are defined in section 2.1 and the Uplink messages are defined in section 2.2
2.1 DOWNLINK
The Downlink Messages or Polls shall conform to the defined message types and its associated
message format. The messages shall be transmitted most significant bit first.
2.1.1 Downlink Formats
Format 1
Data Field Length Description
Preamble 12 bits Always E1A
Message type 3 bits Always 0002 : Type 0 – Identification
Customer Page 5 bits Transponder must have corresponding Customer Flag and
Station 3 bits Station Number
Dispenser ID 4 bits Dispenser ID Number
1 2 none - 1
1 2 Authentication 1 1
3-7 - none - -
Customer Mask enabled to answer.
Uplink Message Uplink
Type
16
Uplink
Format
Dispenser Side 1 bit
CRC 8 bits CRC-8 polynomial (x8 + x2 + x1 + 1) over entire message,
Total 36 bits
RI-TRP-VUSA – Software Specification Page 5 of 16 11-09-05-701
0 : SIDE A
1 : Side B
excluding preamble. Start value = 0xFF MSB sent first
Loading...