TransCore AP4118 User manual

AP4118 Rail Tag Programmer
User Guide
TransCore
8600 Jefferson Street NE
Albuquerque, New Mexico 87113
January 2017
P/N 16-4118-001 Rev A

© 2005-2017 TransCore LP. All rights reserved. TRANSCORE, AMTECH, and EGO are registered
trademarks and are used under license. All other trademarks listed are the property of their respective owners.
Contents subject to change. Printed in the U.S.A.
For further information, contact:
TransCore
8600 Jefferson Street NE
Albuquerque, NM 87113 USA
Technical Support
Phone: [phone]
Web: transcore.com/rfidsupport

WARNING TO USERS IN THE UNITED STATES
FCC RADIO FREQUENCY INTERFERENCE STATEMENT
47 CFR §15.105(a)
NOTE: This equipment has been tested and found to comply with the limits for a Class A digital device
pursuant to Part 15 of the FCC rules. These limits are designed to provide reasonable protection against
harmful interference when the equipment is operated in a commercial environment. This equipment generates,
uses, and can radiate radio frequency (RF) energy and may cause harmful interference to radio
communications if not installed and used in accordance with the instruction manual. Operating this equipment
in a residential area is likely to cause harmful interference, in which case, depending on the regulations in
effect, the users may be required to correct the interference at their own expense.
NO UNAUTHORIZED MODIFICATIONS
47 CFR §15.21
CAUTION: This equipment may not be modified, altered, or changed in any way without permission from
TransCore, LP. Unauthorized modification may void the equipment authorization from the FCC and will void
the TransCore warranty.
USE OF SHIELDED CABLES IS REQUIRED
47 CFR §15.27(a)
NOTE: Shielded cables must be used with this equipment to comply with FCC regulations.
TransCore, LP
USA

1 Before You Begin
Purpose of This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Guide Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2 Programmer Basics
Factory Supplied Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Preventing Electrostatic Discharge Damage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Antistatic Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Using the ESD Wrist Strap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Antistatic Mat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Ionized Air Blower. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
ESD-Safe Tags Container . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Connecting the Host Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
AP4118 Host Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3 Configuring the AP4118 Rail Tag Programmer
Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
PT5780 and PT5785 Permissions Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Ordering a Permissions Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
AP4118 Rail Tag Programmer Control Number and Serial Number . . . . . . . . . . . 11
Permissions Tag Expiration Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Configuring the Rail Tag Programmer Using the Permissions Tag . . . . . . . . . . . . 12
Permissions Tag/Programmer Control Number Matching . . . . . . . . . . . . . . . . . . . 13
AAR Tag Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
AAR User Data Type Detection and Format Delimiting . . . . . . . . . . . . . . . . . . . . 14
AAR Rail Tag Security Character Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Generic/Non-AAR Tag Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
AP4118 Programmer CN and Permissions Tag ID Programming . . . . . . . . . . . 15
Safeguarding the Permissions Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

4 Operating the Programmer
Before You Program Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Indicator Lights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Sign-On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Command Execution Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
RS–232 Command Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Enable Tone Generator (#120<cr>) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Disable Tone Generator (#121<cr>) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Program Tag Using TransCore 6-Bit ASCII Format (#200xxx...<cr>) . . . . . . . . . . 19
Program Tag Using 4-Bit ASCII Hex Format (#201xxx...<cr>) . . . . . . . . . . . . . . . . 19
Read/Verify Tag Data Using TransCore 6-Bit ASCII Format (#210<cr>) . . . . . . . . 19
Read/Verify Tag Data Using 4-Bit ASCII Hex Format (#211<cr>) . . . . . . . . . . . . . 20
Write a Page of Data Using Hex Format (#220yyxxxx…<cr>) . . . . . . . . . . . . . . . . 20
Write a Byte of Data Using Hex Format (#221yyxx<cr>) . . . . . . . . . . . . . . . . . . . . 21
Read a Page of Data Using Hex Format (#230yy<cr>) . . . . . . . . . . . . . . . . . . . . . 21
Read a Byte of Data Using Hex Format (#231yy<cr>) . . . . . . . . . . . . . . . . . . . . . . 23
System Reset (#30<cr>) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Display System Status (#40<cr>) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Display Tag Door Switch Status (#42<cr>) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Request Control Number (#43<cr>) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Request Expiration Date (#44<cr>) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Request Programming Mode (#45<cr>) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Programming a Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Verifying Tag Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Security Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
A Tag Programmer Specifications
Tag Programmer Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Environmental . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
B RS–232 Connector Pin-outs
RS–232 Connector Pin-outs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

C TransCore 6-Bit ASCII Format
TransCore 6-Bit ASCII Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
D 4-Bit ASCII Hex Codes
4-Bit ASCII Hex Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
E Programmer Response Codes
Programmer Response Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
F Security Characters
Security Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
List of Figures
Figure 1 Programming Workstation with ESD Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Figure 2 Serial Interface Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Figure 3 Tag Programming Host Software Main Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Figure 4 Permissions Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Figure 5 AP4118 Tag Programmer LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Figure 6 Permissions Tag Being Slid into Tag Holder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Figure 7 AP4118 Rail Tag Programmer Indicator Lights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Figure 8 Tag Being Slid into Tag Holder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Figure 9 Programmer Adapter and AT5549 EOT Tag Being Slid into Tag Holder . . . . . . . . . . 26
List of Tables
Table 1 Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Table 2 PC Interface Protocol Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Table 3 Data Format Code, AP4118 Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Table 4 Rail Tag Page 3 Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Table 5 Troubleshooting Problems and Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Table A-1 AP4118 Rail Tag Programmer Physical and Environmental Specifications . . . . . . . 29
Table B-1 RS–232 Connector Pin-outs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Table C-1 6-Bit ASCII Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Table D-1 4-Bit ASCII Hex Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Table E-1 Programmer Response Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Table F-1 ASCII Security Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

1
Chapter 1
Before You Begin
The AP4118 Rail Tag Programmer User Guide provides information
necessary for installing, operating, and troubleshooting the AP4118 Rail
Tag Programmer.
Purpose of This Guide
This AP4118 Rail Tag Programmer User Guide discusses the proper setup and opera-
tion of the AP4118 Rail Tag Programmer. This guide also provides procedures useful
in troubleshooting any problems encountered after installation.
Intended Audience
The AP4118 Rail Tag Programmer User Guide is designed to be used by technical
personnel responsible for setting up and operating theAP4118 Rail Tag Programmer
and related software.
Related Documents
AP4118 Rail Tag Programming Host Software User Guide
Guide Topics
This document presents the following information:
Chapter 1 – Before You
Begin Describes the purpose, intended audience, guide topics, related
documentation, and document conventions
Chapter 2 – Setting Up
the Programmer Describes how to set up the tag programmer, prevent electrostatic discharge
damage to tags, and connect the programmer to a host computer system
Chapter 3 – Permissions Defines permissions and instructs how to configure the AP4118 Rail Tag
Programmer using a PT5780 or PT5785 Permissions Tag
Chapter 4 – Operating
the Programmer Describes how to program a tag and how to verify or read the data. This
chapter also lists the RS–232 command set and describes the security
character operation
Chapter 5 – Trouble-
shooting Procedures Lists problems that may be encountered during tag programmer operation and
suggested solutions

Before You Begin
2
Typographical Conventions
Table 1 lists the conventions used in this manual.
Appendix A – Program-
mer Specifications Provides the programmer’s physical and environmental specifications
Appendix B – RS–232
Connector Pin-outs Describes the cable interface configuration to a host computer
Appendix C – TransCore
6-Bit ASCII Format Lists TransCore’s 6-bit ASCII character codes
Appendix D – 4-Bit ASCII
Hex Codes Lists TransCore’s 4-bit hexadecimal formats
Appendix E – Program-
mer Response Codes Lists the tag programmer response codes
Appendix F – Security
Characters Lists the 6-bit security character codes
Table 1 Typographical Conventions
Convention Indication
This procedure might cause harm to the equipment and/or
the user.
Concerns about a procedure
Code Code, including keywords and variables within text and as
separate paragraphs, and user-defined program elements
within text appear in courier typeface.
Dialog Box Title Title of a dialog box as it appears on screen
Function Starts with the characters, G4, which are in mixed case with
no underscores, and include parentheses after the name, as
in G4FunctionName().
Menu Item Appears on a menu. Capitalization follows the interface.
Note Auxiliary information that further clarifies the current
discussion. These important points require the user’s
attention. The paragraph is in italics and the word Note is in
boldface.
NUL Zero-value ASCII character or a zero-value byte

Before You Begin
3
NULL Zero-value pointers. Null-terminated string refers to strings
of printable ASCII characters with a zero-value byte placed
in memory directly after the last printable character of the
string.
Table 1 Typographical Conventions (continued)
Convention Indication

Programmer Basics
4
Chapter 2
Programmer Basics
This chapter lists the factory-supplied and optional equipment for the
AP4118 programmer, and describes how to prevent electrostatic
discharge (ESD) damage to tags, connect to a host computer, and install
optional TransCore tag programming software to the host computer.
Factory Supplied Equipment
The programmer is shipped with the items listed here. When unpacking your order,
make sure all of the items are included:
•AP4118 Rail Tag Programmer
•Programmer Accessory Kit (P/N 19094-01) includes:
• Power transformer and cable to convert AC voltage to 12V DC
•Powercord
• Programmer-to-PC RS–232 connecting cable
• Static-suppression wrist strap with cord
• TransCore USB flash drive with:
– AP4118 Tag Programmer Host Software
– AP4118 Programmer User Guide
If any of the above items are missing from your order, contact your TransCore distributor.
If you did not purchase TransCore P/N 14-4118-002 and you want to program the
AT5549 End-of-Train Tag, you will also need anAT5549 End-of-Train Tag
Programmer Adapter (TransCore P/N 20-4118-001), which is required to seat the
AT5549 tag during programming.
To use the AP4118 programmer you need either a host system, such as a personal
computer (PC), or a communications terminal to operate the programmer. TransCore
does not supply this equipment for the AP4118 Rail Tag Programmer.
Preventing Electrostatic Discharge Damage
Caution
TransCore tags are sensitive to ESD, and precautions are necessary to ensure
proper tag programming operation. Use the grounded ESD static-suppression wrist
strap when using the programmer. Additional protection from ESD is recom-
mended where practical.

Programmer Basics
5
Static is generated by friction. Some causes of static include the following:
•Shoes moving across a carpeted or plastic floor
•Hot air blowing into a room from a hot-air duct
•Rubbing tags together
•Rubbing tags across a table top
•Wearing certain types of clothing
ESD may cause significant damage to the tag and will adversely affect a tag’s
operating performance. Typical symptoms of ESD include the following:
•Inability to program the tag
•Greatly reduced operating range
•Tag operating failure
Antistatic Workstation
In a factory or fixed indoor environment, position the programmer in an antistatic
workstation. Well-designed workstations use a system of multiple precautions against
ESD. Figure 1 shows an antistatic workstation.
Figure 1 Programming Workstation with ESD Controls
Contact TransCore Technical Support if you have any questions concerning the
suitability of your programming station or environment.

Programmer Basics
6
You can take several precautions to prevent ESD from affecting programming
operations. The most effective precautions are listed below. The potential for ESD
damage decreases when two or more precautions are used together.
Using the ESD Wrist Strap
Caution
You should always attach the ESD wrist strap before beginning programming oper-
ations in any setting.
1. Be sure the programmer is connected to an earth ground.
2. Connect the banana plug of the ESD wrist strap to the ESD jack on the front of
the unit.
3. Attach the ESD strap to your wrist by adjusting the hook and loop material.
Antistatic Mat
The antistatic work mat on which your programmer sits should be connected to earth
ground through the standard 1 M-Ohm resistance that should be provided with the
mat. The mat also should be clean and free of any electrical path to direct earth
ground.
Ionized Air Blower
You may choose to set up an ionized air blower at your workstation to provide
additional ESD protection. Ionized air blowers neutralize tags from static build-up
before programming.
ESD-Safe Tags Container
Keep tags in the original box on an antistatic mat or within an ESD-safe container
until they are programmed. Grounded metallic containers are best for inhibiting ESD.

Programmer Basics
7
Connecting the Host Device
The programmer requires connection to a host device — a host computer or
communications terminal — for normal operation. Figure 2 shows the connector from
the programmer to the host.
Figure 2 Serial Interface Connector
If the host system is a PC or a communications terminal, then you do not need to use a
null modem.
The tag programmer’s PC interface complies with the RS–232 standard for data
terminal equipment and uses the protocol settings listed in Table 2. Refer to Appendix
B for specifications of the programmer’s RS–232 pin-outs.
Table 2 PC Interface Protocol Settings
Protocol Setting
Data Rate 9600 bps
Data Bits 8
Parity None
Stop Bits 1
Software Flow Control None
Hardware Flow Control None

Programmer Basics
8
To connect the programmer to the host computer
1. Connect the RS–232 cable from the unit to the host computer system.
2. Switch on power to the programmer. You should see the POWER then READY
LEDs illuminate. When the READY LED illuminates, you can begin using the
tag programmer. The tag programmer has factory default settings installed to
allow tag reads only.
To configure the tag programmer for your tag requirements, you will need to use
either a PT5780 or PT5785 Permissions Tag1to program specific operational and
security information into the programmer. Chapter 3, “Configuring the AP4118
Rail Tag Programmer,” instructs the user in configuring the tag programmer using
this tag.
If the READY LED does not illuminate or if the host system cannot communicate
with the tag programmer, refer to Chapter 5, “Troubleshooting.”
AP4118 Host Software
TheAP4118 Tag Programmer Host Software can be found on the provided TransCore
USB Drive. The host software is not necessary to use the AP4118 Rail Tag Program-
mer. Many customers prefer to use their specific host software to communicate with
the tag programmer.
To Install the Host Software
1. Switch on the host computer.
2. Insert the TransCore USB flash drive into a USB slot on the host computer.
3. Open the USB drive folder on the host computer and locate the AP4118 Tag
Programmer Host Software.
4. Click and drag the host software to the desired location on the host computer to
begin the download.
5. Double-click on the AP4118 icon or select Start > Programs > AP4118 >
AP4118 to launch the tag programming software.
1. Use the PT5780 tag if configuring the AP4118 programmer for 902 to 928 MHz frequency
band tags and the PT5785 tag if configuring the AP4118 programmer for 860 to 880 MHz fre-
quency band tags.

Programmer Basics
9
Figure 3 shows the host software main screen.
Figure 3 Tag Programming Host Software Main Screen
For complete instructions to install and operate the tag programming host software,
refer to AP4118 Rail Tag Programmer Host Software User Guide.

10
Chapter 3
Configuring the AP4118 Rail Tag Programmer
This chapter briefly defines permissions and instructs how to configure
the AP4118 Rail Tag Programmer using an PT5780 or PT5785
Permissions Tag.
Permissions
An AP4118 Rail Tag Programmer requires specific setup data before it can be used to
program tags. Configuration of the programmer is done using a permissions tag. The
permissions tag transfers parameters, such as permissions expiration date, program-
ming session duration, programmer control number, and application tag permissions
(read/write/authentication access rights, and ownership matching) to the rail tag pro-
grammer via a RF signal. Initial tag programmer configuration can be performed at
the factory or at the customer site using a permissions tag.
Note: Use the PT5780 tag if configuring the AP4118 programmer for 902 to 928 MHz
frequency band tags and the PT5785 tag if configuring the AP4118 programmer for
860 to 880 MHz frequency band tags.
PT5780 and PT5785 Permissions Tags
TransCore’s permissions tag (Figure 4) is designed specifically to configure the
AP4118 Rail Tag Programmer. During programmer configuration, the permissions tag
data is validated by the programmer and, if valid, stored in the AP4118 tag program-
mer’s nonvolatile memory.
Figure 4 Permissions Tag
Tag programmer configuration information transferred from the permissions tag to the
tag programmer can include:

Configuring the AP4118 Rail Tag Programmer
11
•Rail tag owner values
•Rail tag ATA frame security character values
•Rail tag read and write access, by page
•Rail tag programmer control number (CN) matching
•Rail tag programmer lifetime and session dates/durations
•Rail tag programmer control/configuration
•ATA mode programming permissions
•Generic/non-AAR programming enable/disable
A permissions tag can be used once during a programmer’s expected life cycle, or
may be required on an ongoing basis during programmer use.Also, a different permis-
sions tag can be used at any time in the programmer’s lifetime to update or reconfigure
the programmer. In some cases, multiple permissions tags for a single programmer
may be required at a given site to enable tag programming by multiple owners, or to
selectively enable or disable various programmer features.1
Ordering a Permissions Tag
Permissions tags may be obtained from TransCore Order Administration. An order
form is available online at www.transcore.com/downloads.html under the USER and
INSTALLATION MANUALS > Miscellaneous menu. Select PT5780/PT5785 Tag
Order Form from the Miscellaneous pull-down list.
AP4118 Rail Tag Programmer Control Number
and Serial Number
The CN is an eight-character alphanumeric string and is printed on a label on the rear
panel of the AP4118 Rail Tag Programmer (e.g., CN: 43213131). The Serial Number
is printed on the same label (e.g., Serial No. 545445456).
Permissions Tag Expiration Date
The expiration of the permissions tag can vary according to customer requirements.
Depending on customer requirements, a tag permissions period may range from two
years to an indefinite programming period. The expiration date, which is laser etched
into the tag face, should coincide with the expiration or termination of the tag pro-
gramming certification or authorization. The expiration date appears in the following
1. Use the PT5780 tag if configuring the AP4118 programmer for 902 to 928 MHz fre-
quency band tags and the PT5785 tag if configuring the AP4118 programmer for 860
to 880 MHz frequency band tags.

Configuring the AP4118 Rail Tag Programmer
12
date format EXP: DD/MM/YYYY, for instance, 22/11/2009.
Once validated, the permissions tag settings are stored in the tag programmer. Nonvol-
atile permissions tag settings, including duration/expiration settings, will survive
power cycles, resets, soft or warm boot, and flash application code download opera-
tions.
Configuring the Rail Tag Programmer Using the
Permissions Tag
This section instructs how to configure the AP4118 Rail Tag Programmer using the
permissions tag. For complete instructions on the operation of anAP4118 Rail Tag
Programmer, refer to “Request Control Number (#43<cr>)” on page 24.
To use a Permissions Tag.
1.
Switch on the tag programmer and wait for the READY LED to light (Figure 5) .
Figure 5 AP4118 Tag Programmer LEDs

Configuring the AP4118 Rail Tag Programmer
13
2. Insert the permissions tag into the tag holder and close the door (Figure 6).
Figure 6 Permissions Tag Being Slid into Tag Holder
3. Wait 10 seconds.
4. Remove the permissions tag from the tag holder.
5. Insert a rail tag into the tag holder and close the door.
6. Start the tag programmer application, for instance, TransCore’s host software
program or terminal emulation software program, and test the programmer
permissions by writing to and/or reading from the rail tag. See “RS–232
Command Set” on page 18 for programming and verifying tags.
If the AP4118 tag programmer did not accept the permissions tag, you will not be
able to program or read rail tags. Check the permissions tag expiration date
(etched into the tag face) to ensure the tag is valid. You can enter the #44 Request
Expiration Date to retrieve the permissions expiration. See “Request Expiration
Date (#44<cr>)” on page 24 for more information. Finally, compare the
permissions tag CN to the tag programmer CN(located on label affixed to back of
tag programmer) to ensure they match.
Note: If the permissions tag has not expired and its CN matches the tag programmer
CN, contact TransCore Technical Support.
Permissions Tag/Programmer Control Number Matching
TheAP4118 tag programmer checks the permission tag’s CN against its own CN prior
to implementing the permissions tag settings. If the permissions tag CN value does not
match or is invalid, then the permissions tag settings are discarded. If the permissions
tag CN value matches, the tag programmer implements the permissions tag data.

Configuring the AP4118 Rail Tag Programmer
14
AAR Tag Programming
Note: This information applies to AAR-compliant tag programming, with the permis-
sions tag settings as required to support AAR-compliant tag programming.
AAR-compliant programming requires validation and evaluation of some of the
incoming data, as described in the following section.
AAR User Data Type Detection and Format Delimiting
The AP4118 tag programmer supports only two basic AAR programming modes:
•programming of rail tag as an AAR-compliant rail tag, or
•programming of rail tag as an ASCII tag, according to the AAR Standard for
Automatic Equipment Identification (S-918) definition.
The programmer evaluates the incoming data as being in one of the two programming
mode categories, or responds with an error condition and prevents improper tag pro-
gramming. Upon receiving a legacy AP4110 Tag Programmer-compatible command,
the tag programmer evaluates the incoming user data to determine the data format
code (DFC) value as specified inAAR Specification S-918. Table 3 lists the supported
DFC values.
If the DFC is any value not listed in Table 3, the AP4118 creates an error condition
and #ERROR response, and tag programming stops.
AAR Rail Tag Security Character Handling
Upon receiving a legacyAP4110-compatible tag programming command, theAP4118
programmer checks the incoming security characters embedded in the user data. If the
incoming characters are secure, the AP4118 programmer then checks the secure char-
acters against the security characters in the permissions tag. The data remains the
same if a match is made; otherwise, an immediate data compare error occurs. This
error is due to security characters being replaced by space characters.
Table 3 Data Format Code, AP4118 Handling
6-BitBinary
DFC Value Value Definition (per AAR Standard S-918) AP4118 Handling
000000 6-bit ASCII format Allow programming; security character enforcement
required. Tag type handling not required.
110011 AAR-compliant: other; non-dynamic,
non-passive alarm; AAR/ATA/ISO Allow programming; enforce tag type and security characters. (This is the predominant DFC value for a
rail tag.)
110100 AAR rail: toll road Allow programming; enforce tag type and security
characters