This Document is uncontrolled unless over stamped "CONTROLLED DOCUMENT"
4.7 16-BIT SYSTEM FILE TYPES
The 16-bit control system firmware uses 3 files for operation. A summary of these are given in the table below.
Configuration
(<Serial
Number> -
<CPSN Number>
- <Firmware
Version>.TKCcfg)
Contains the system configuration i.e
number of receptor strips, door
configuration, card reader settings
etc. In addition it allows cost options
to be unlocked; cost options include
Fault Logging, Key Booking, X-iFob
Authorisers etc. There is no limit
(aside from where certain options
would conflict) to the number of cost
options that can be enabled at a
single time. View Firmware Options &
Settings for the various options
available.
Each Traka system must have its own
dedicated configuration file and be
registered to the Traka32 database.
The file contains a CPSN (Control PCB
Serial Number) that must match the
CPSN stored in the 16-bit Control PCB
hardware for operation.
The configuration file will be required when
commissioning a new system.
This is because It needs to be registered to the
new Traka32 Database even if the system was
shipped with a configuration file in. View Adding a
New System for more information on this.
An updated version of the configuration file will be
required to enable new cost options. Please
provide Traka (U.K) or your distributor (outside
U.K) with the System Serial Number along with a
Purchase Order No. for the options required. A
new configuration file will be emailed to you.
Distributors can also download .cfg files from
http://www.traka.com/support.
The configuration file is easily loaded using the
16bit Configure Firmware Wizard. View Changing
Firmware Settings for more information on this.
Application
Firmware
(<Version> -
<Date>.MOT)
Generic file that contains the program
code that operates the Traka
system. Note that unlike the 8-bit
system, all of the program code for
the cost options is contained within
this single file. This then allows the
cost options to be 'unlocked' using the
small configuration file.
The application firmware file will only be needed to
upgrade the application to include a brand new
feature or bug fix. For a list of new features and
any bug fixes please visit
http://www.traka.com/support
Bootloader
a. (<Version> -
<Date> .em0
b. (<Version> -
<Date> .rom)
Basic input/output operating system
providing an interface for the firmware
application file.
The bootloader should never need to be changed
unless there is a major change to the basic
input/output operating system. In which case it is
perhaps more likely that the 16-bit Control PCB
would be changed instead of a field upgrade of the
bootloader.
Also View...
16bit Configure Firmware Wizard
Adding a New System
Changing Firmware Settings
Firmware Options & Settings
16bit Control PCB Overview
To Next Page
