Panasonic of North America CP8564 Active RF Security Tag User Manual
Omni-ID USA Inc. Active RF Security Tag
User Manual
| Download: |  |
| Mirror Download [FCC.gov] | |
| Document ID | 2658282 |
| Application ID | BsR0pyLtoiOh6/yXaViQ7A== |
| Document Description | User Manual |
| Short Term Confidential | No |
| Permanent Confidential | No |
| Supercede | No |
| Document Type | User Manual |
| Display Format | Adobe Acrobat PDF - pdf |
| Filesize | 84.4kB (1054993 bits) |
| Date Submitted | 2015-06-25 00:00:00 |
| Date Available | 2015-06-28 00:00:00 |
| Creation Date | 2015-04-07 14:29:20 |
| Producing Software | Microsoft® Word 2010 |
| Document Lastmod | 2015-04-07 14:29:20 |
| Document Title | User Manual |
| Document Creator | Microsoft® Word 2010 |
| Document Author: | Jeffrey Orvek |
OMNI-ID, INC
VIEW 4 & VIEW 3 USER MANUAL
Document Revision: Draft
Date: April 7, 2015
Omni-ID, Inc.
1200 Ridgeway Avenue
Rochester, NY
www.Omni-ID.com
Author: Jeffrey Orvek
TABLE OF CONTENTS
Protocol .................................................................................................................................................................4
1.1
Read/Write Parameters ...............................................................................................................................4
1.2
Read Only Parameters..................................................................................................................................4
1.3
433MHz Radio ..............................................................................................................................................4
1.3.1
Announce Timing .....................................................................................................................................4
1.3.2
Announce Reasons...................................................................................................................................5
1.4
Requested Operations .................................................................................................................................5
1.5
Commanded Operations ..............................................................................................................................7
FW Upgrade ...........................................................................................................................................................9
2.1 ..............................................................................................................................................................................9
Triggers ................................................................................................................................................................10
3.1
Magnetic Switch .........................................................................................................................................10
3.2
RFID ............................................................................................................................................................10
3.2.1
NXP IC (Gen 1 HW) .................................................................................................................................10
3.2.2
Monza (Gen 1.5 HW) .............................................................................................................................12
Event Macros .......................................................................................................................................................15
4.1
Events .........................................................................................................................................................15
4.2
Operations..................................................................................................................................................15
4.3
Memory Layout ..........................................................................................................................................16
Templates ............................................................................................................................................................17
5.1
Template Fields ..........................................................................................................................................17
5.2
Template Data ............................................................................................................................................17
5.3
Memory Layout ..........................................................................................................................................18
5.4
Commands .................................................................................................................................................18
5.5
Limitations ..................................................................................................................................................19
Text Rendering .....................................................................................................................................................20
6.1
Character Set ..............................................................................................................................................20
6.2
Character Font Size ....................................................................................................................................21
External Flash .......................................................................................................................................................22
7.1
Memory Map .............................................................................................................................................22
7.2
Space Between Images ..............................................................................................................................22
7.2.1
Image Dirty Byte ....................................................................................................................................23
7.2.2
Template Dirty Byte ...............................................................................................................................23
Event Log .............................................................................................................................................................24
8.1
Overview ....................................................................................................................................................24
8.2
Cheat Sheet ................................................................................................................................................25
8.3
Log Header .................................................................................................................................................27
8.4
LOG_CHANGE_ ...........................................................................................................................................27
Internal Flash .......................................................................................................................................................28
9.1
Address Map ..............................................................................................................................................28
9.2
Calibration Data â.infoDâ ...........................................................................................................................31
9.3
HW Configuration.......................................................................................................................................31
10
Testing ............................................................................................................... Error! Bookmark not defined.
11
Power Measurements ....................................................................................................................................32
11.1
Revision 01.03.00.00 ..................................................................................................................................32
1
1.1
PROTOCOL
Read/Write Parameters
Parameter
Awake Dwell
Sleep Dwell
Retry Dwell
Retry Count
ACK Listen Time
RF Channel
TX Power
Units
Seconds
Seconds
Seconds
Attempts
mS
1.2
Read Only Parameters
1.3
433MHz Radio
Min
Default
64800
200
0x01
10
Max
2^32
10
1.3.1 Announce Timing
Figure 1
If any valid message is received by the tag within the first 100mS after announcing, then the tag will listen consider
the announce a success and listen for the full Awake Dwell before going to sleep. If no valid message is seen within
the ACK listen time then the tag will go to sleep for the Retry Dwell before attempting another announce. If The
Retry Count is reached, then the tag will listen for the full Awake Dwell regardless if a valid message is received in
the ACK listen time.
After an announce it is recommended to send a TAG_GO_TO_SLEEP operation as the last command to the
tag. This will save battery life by putting the tag back to sleep much sooner than the Awake Dwell would
allow.
1.3.2 Announce Reasons
Reason
TIMEOUT
REQUESTED
RFID
EXIT_RESET
MACRO_EVENT
BUTTON_1_PRESSED
Value
0x01
0x05
0x06
0x09
0x0A
0x10
Table 1
1.4
Requested Operations
Command
Value
Length
TAG_DISPLAY_PAGE
TAG_PAGES_LOADED
TAG_PAGE_LIST
0x20
0x21
0x26
Length (1)
Length (1)
Length
TAG_DISPLAY_TYPE
0x53
Length (1)
TAG_MAX_PAGES
0x54
Length (1)
TAG_SLEEP_DWELL
0x22
Length (4)
Page
Total
List âŚ
Display
Type
Max
Pages
TAG_AWAKE_DWELL
0x23
Length (1)
TAG_RETRY_INTERVAL
0x29
Length (1)
Retry
Interval
mS
TAG_RETRY_COUNT
0x2A
Length (1)
TAG_RF_CHANNEL
TAG_TX_POWER
TAG_HW_VERSION
0x40
0x41
0x50
Length (1)
Length (1)
Length (1)
Retry
Attempts
Channel
Power
Rev
TAG_FW_VERSION
0x51
Length (8)
Board ID
TAG_BATTERY_LEVEL
TAG_TEMPERATURE
TAG_LAST_RX_RSSI
TAG_RFID_COUNT
0x52
0x55
0x43
0x45
Length (1)
Length (1)
Length (1)
Length (4)
Level
Temp
RSSI
Multi-Byte data is Big Endian
Sleep Dwell Seconds
Awake
Dwell
Seconds
Raw Data Bytes1
Major
Rev
Minor
Rev
Lifetime RFID Triggers
Year
TAG_AWAKE_TIME
TAG_ANNOUNCE_COUNT
TAG_PAGE_FLIPS_COUNT
TAG_RESET_COUNT
0x49
0x4A
0x4B
0x57
Length
Length
Length
Length
(4)
(4)
(2)
(2)
Lifetime Awake Total
Lifetime Announce Total
Lifetime Page Flips
Lifetime Resets
1.5
Commanded Operations
FW Name
OpCode
Length
TAG_DISPLAY_PAGE
TAG_DELETE_IMAGE
0x20
0x28
Length (1)
Length (1)
Page
Page
TAG_IMAGE_LINE
0xA0
Length
Page
Line Number
TAG_IMAGE_BLOCK
TAG_TEMPLATE_WRITE
TAG_TEMPLATE_DATA
TAG_IMAGE_ASCII
TAG_WRITE_MEMORY
0xA1
0xA8
0xA9
0xA2
0xAA
Length
Length
Length
Length
Length
Page
Page
Page
Page
Page
X Coordinate
Data
âŚ
Field #
Data
X Coordinate
Type4
TAG_SLEEP_DWELL
0x22
Length (4)
Sleep Dwell Seconds
TAG_TEMPORARY_SLEEP_DWELL 0x4C
Length (5)
Sleep Dwell Seconds
TAG_AWAKE_DWELL_SECONDS
0x23
Length (1)
TAG_AWAKE_DWELL_MILLI_SEC
0x4E
Length (2)
TAG_RETRY_INTERVAL
0x29
Length (1)
TAG_RETRY_COUNT
0x2A
Length (1)
Awake
Dwell
Seconds
Awake Dwell
Milliseconds
Retry
Interval
mS
Retry
Attempts
Multi-Byte data is Big Endian
Supported Compression Formats {0:None}
Supported Memory Types (0:RFU, 1:Image, 2:Macro}
Raw Data Bytes2
Compression
Data
Format3
Y Coordinate
âŚ
Y Coordinate
Address
Number of
Announces
Compression Format
Data
âŚ
Font Size
Data
Data
âŚ
âŚ
âŚ
TAG_DATA_REQUEST
0x33
Length
TAG_RF_CHANNEL
TAG_TX_POWER
0x40
0x41
Length (1)
Length (1)
SOFTWARE_RESET
0x5F
Length (0)
TAG_FIRMWARE_CRC
0xB1
Length
TAG_FIRMWARE_DATA
TAG_FIRMWARE_ERASE_DATA
TAG_SAVE_NVM
TAG_GO_TO_SLEEP
BEACON_SLEEP_DWELL
0xB0
0xB2
0x34
0x2C
0x4D
Length
Length (0)
Length (0)
Length (0)
Length
Requested Requested Requested
Tag 1
Tag 2
Tag âŚ
Channel
Power
TAG_CRC
(0x01)
Address
CRC5
Data
âŚ
Table 2
đ(đĽ) = đĽ 32 + đĽ 26 + đĽ 23 + đĽ 22 + đĽ 16 + đĽ 12 + đĽ 11 + đĽ 10 + đĽ 8 + đĽ 7 + đĽ 5 + đĽ 4 + đĽ 2 + đĽ + 1
If fed a string of â123456789â, the calculated CRC should equal 0xCBF43926
TAG_COMPATIBLE_HW
Length
(0x02)
ListâŚ
2
FW UPGRADE
FW can be upgraded by using TAG_FIRMWARE_ERASE_DATA (0xB2), TAG_FIRMWARE_DATA (0xB0) and
TAG_FIRWMARE_CRC (0xB1) operations.
2.1
TAG_FIRMWARE_ERASE_DATA
This operation does not delete the running FW, but it deletes all previously downloaded FW from the external flash
buffer.
2.2
TAG_FIRWMARE_DATA
This operation allows binary data to be downloaded to the tag and stored in a buffer in external flash
2.3
TAG_FIRWMARE_CRC
This operation commands the tag to compute a CRC from the data previously downloaded into the external flash
buffer. If the CRC computed by the tag matches the CRC given with this operation, then the tag will erase and then
reprogram itself.
2.3.1 HW Configuration Compatibility
A list of compatible HW versions is downloaded with the CRC and indicates to the tag which versions the new FW
supports. This allows existing FW to refuse to update if the HW version is not supported even if the CRC
successfully matches.
3
3.1
TRIGGERS
Magnetic Switch
The magnetic switch is primarily used to flip the image, but if it is held long enough a diagnostic screen is printed,
and if held even longer the tag will reset.
Figure 2
3.2
RFID
3.2.1 NXP IC (Gen 1 HW)
RFID Dynamic Back Off
6000
Time (mS)
5000
4000
3000
2000
1000
100
200
300
400
500
600
700
Triggers
Average Time Between Triggers
Delay Between Announces
Figure 3
In existing Gen 1 HW with the NXP passive RFID IC, a dumb trigger is used to wake up the tag in the presence of a
865-928MHz signal. Because there can be many sources for this, the tag has to balance between a fast response
Omni-ID, Inc
Confidential Information
Page | 10
time and conserving power. To allow for this, a dynamic back off is used to increase the responsiveness of the tag.
In the presence of a constant RFID field, the tag is initially responsive but the time between announces will slowly
increase to a max value of 25 Seconds. Once 25 seconds has elapsed since the last RFID trigger, the back off time is
reset.
It is important to note that once the delay time has passed, the tag announces immediately upon being triggered.
This allows for immediate responsiveness when triggered, with a gradual back off to conserve energy.
Omni-ID, Inc
Confidential Information
Page | 11
3.2.2 Monza (Gen 1.5 HW)
The Monza allows communication over RFID by utilizing the user memory bank in the passive IC as a pass-through
to the micro.
3.2.2.1 Address Map
Table 3 describes the layout of memory in the User Bank of the Monza.
Word
0d-3d
4d-5d
6d
6d
7d
8d
I C Byte
40d-47d
48d-51d
52d
53d
54d
56d-57d
Description
Active radio ID
Firmware revision
Operation Register
Response Register
Extended Data Registers
Memory map type
9d
58d-73d
UUID
Default
00 00 00 00 00 00 00 00h
00 00 00 00h
Word 32d
Word 33d
Word 34d
EA 0Xh
A0 BF DA F8 50 04 40 7C
A3 EA B8 0B AC C2 17 14h
Table 3
3.2.2.2 Algorithm
The flowchart in Figure 4 describes the method of commanding operations using the User Memory Bank of the
RFID interface as a pass through.
If successful, then the response register will contain a copy of the value written to the operation register.
Figure 4
Omni-ID, Inc
Confidential Information
Page | 12
3.2.2.3 RFID Opcodes
RFID opcodes allow a 2 byte interface into the tag.
Command
Display Page
Delete Page
Announce
Extended Data
Word
High Byte
Low Byte
0x20
Page
0x28
Page
0x30
0x00
Data Byte
0xFF
Length
Response
-1 = CRC mismatch
-2 = Length longer than buffer
Figure 5
3.2.2.3.1 Announce
An announce over the 433MHz interface can be triggered by writing 0x3000 to the Operation Register (32d).
3.2.2.4 Extended Opcodes
Extended data allows the existing 433MHz protocol to be used by tunneling through the RFID interface. An
additional 16-bit CRC after the commanded data is used to allow the micro to verify the data. Table 4 shows an
example of template data being commanded through the Monza.
Byte
Use
Command
Page
Length
Field #
Data 0
Data Body
âŚ
âŚ
N+1
N+2
N+3
Data N
Byte Stuff to force 16-bit boundary
CRC
89
Example
0xA9 (Template Data Cmd)
0x48 (âHâ)
0x45 (âEâ)
Template Data
0x4C (âLâ)
0x4C (âLâ)
0x4F (â0â)
0x00
0x8C
0xA9
Table 4
3.2.2.4.1 Extended Opcode Response
Words are Big Endian
Maximum length is 100 Words (200 bytes)
CRC as described in section 3.2.2.5
CRC is Big Endian
Omni-ID, Inc
Confidential Information
Page | 13
If a response was requested through the extended data operation, then the extended response will be placed
starting at the Extended Data Register (34d). The first byte will be the byte length of the response.
3.2.2.5 CRC-CCITT
The CRC-CCITT algorithm is used, based on the polynomial shown in Equation 1.
đ(đĽ) = đĽ 16 + đĽ 12 + đĽ 5 + 1
Equation 1
It is seeded with 0xFFFF, and a reference string of â123456789â should produce a CRC of 0x29B1.
Omni-ID, Inc
Confidential Information
Page | 14
4
EVENT MACROS
Event macros allow a very limited scripting capability to handle event triggers. Each event is compared against a
lookup table that indicates the macro to execute. If no event is registered in the lookup table, then the default
action occurs (e.g. Button 1 announces, Button 2 flips the image).
4.1
Events
Event
RFU
SYSTEM_RESET_EVENT
RFID_EVENT
BUTTON_1_EVENT
BUTTON_2_EVENT
EVENT_LOOKUP_END
Value
0x00
0x01
0x02
0x04
0x05
0xFE
Table 5
4.2
Operations
10
Operation
RFU
PAGE_FORWARD
MACRO_GOTO_ADDRESS
MACRO_ANNOUNCE
MACRO_DELAY
MACRO_IF_PAGE_EQUALS
MACRO_SET_PAGE
MACRO_DELETE_PAGE
MACRO_RADIO_MSG
MACRO_END
Command
0x00
0x01
0x04
0x07
0x09
0x0A
0x20
0x28
0x70
0xFE
Bytes
Extended Data
Address
11
Address if failed
Seconds
Page
Address
Page
Page
Length
DataâŚ
Table 6
10
11
Multi-Byte data is big Endian
Address to branch to if announce fails
Omni-ID, Inc
Confidential Information
Page | 15
4.3
Memory Layout
Event 1
Event 2
Event Lookup Table
Header
Error! Reference source not found. shows an example layout for the event macros. The header is used to indicate
to FW the formatting used as well as the complete length of the table. This is followed by the lookup table to link
the event with a specific macro address. The end of this table must contain the EVENT_LOOKUP_END operation.
Macro 1
Macr
o2
Macros
End
Byte
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
12
Data
Version
Example
0x00
0x
Length to End
RFU
Event
Macro Address
RFU
Event
Macro Address
RFU
EVENT_LOOKUP_END
MACRO_SET_PAGE
Page
MACRO_ANNOUNCE
Address to branch to if
Announce Failed
MACRO_SET_PAGE
Page
MACRO_GOTO_ADDRESS
Address
MACRO_SET_PAGE
Page
MACRO_END
PAGE_FORWARD
MACRO_END
0x04 (Button 1)
0x00
12
0x0C
0x05 (Button 2)
0x00
26
0x1A
0xFE
0x20
0x07
0x00
0x17
23
0x20
0x04
0x00
0x19
25
0x20
0xFE
0x01
0xFE
Table 7
12
Multi-Byte data is big Endian
Omni-ID, Inc
Confidential Information
Page | 16
5
TEMPLATES
The template is downloaded into flash along with the background image and dictates how Template Data is
formatted onto the display. This example uses two text fields of different sized text. Numbers larger than 8-bits
are Big Endian.
5.1
Template Fields
These are the different Field Types supported.
Field Type
RFU
OpCode
0x00
Byte 0
Byte 1
Byte 2
Byte 3
Text
0x01
X Coordinate
Y Coordinate
Barcode
0x02
Starting X
Coordinate
Starting Y
Coordinate
Byte 4
Byte 5
Font Size
Max Text
Length
Y Size
Byte 6
Max
Data
Length
Table 8
5.2
Template Data
Template Data is commanded through any interface (RF or RFID) and includes a Field number and data. The Field
number indicates which template field should be used to format the data. The example shown in Table 9 and
Table 13 is based on the example template in Table 11.
Byte
Text Field Example
Data
Template Command
Length (N â 1)
Page
Referenced Field Number
Data 0
âŚ
âŚ
Data N
Example
0xA9
0x48 (âHâ)
0x45 (âEâ)
0x4C (âLâ)
0x4C (âLâ)
0x4F (â0â)
Table 9
Byte
âŚ
Omni-ID, Inc
Barcode Field Example
Data
Template Command
Length (N â 1)
Page
Referenced Field Number
Scale Size
Data 0
âŚ
Confidential Information
Example
0xA9
10
âŚ
Page | 17
N
Data N
Table 10
Memory Layout
Field #2
Field #1
Field #0
Header
5.3
Byte
10
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
Data
Template Format
Number of Fields
Template Length
Field Number
Field Type
X Coordinate
Y Coordinate
Font Size
Max Text Length
Field Number
Field Type
X Coordinate
Y Coordinate
Font Size
Max Text Length
Field Number
Field Type
Starting X Coordinate
Starting Y Coordinate
Y Size (in pixels)
Max Data Length
Example
25
0x01 (Text)
0x00
85
0x55
0x00
130
0x82
4 (32x32 Pixel characters)
10
0x01 (Text)
0x00
40
0x28
0x00
230
0xE6
6 (48x48 Pixel characters)
0x02 (Barcode)
0x00
20
0x14
0x00
200
0xC8
0x00
16
0x10
10
0x0A
Table 11
5.4
Commands
Templates are located within the image address space, so it is important to follow the proper flow.
1.)
2.)
3.)
4.)
Delete Page
Download Image if required (e.g. TAG_IMAGE_LINE, TAG_IMAGE_BLOCK)
Download Template (e.g. TAG_TEMPLATE_WRITE)
Download dynamic data for the fields (e.g. TAG_TEMPLATE_DATA)
Omni-ID, Inc
Confidential Information
Page | 18
5.) Flip to page to generate the new image
5.5
Limitations
ďˇ
ďˇ
ďˇ
ďˇ
Maximum of 10 Fields
Each Field can have a maximum of 20 bytes of data
Maximum template size of 100 bytes
FW only holds the dynamic data for one page at a time. Flipping to any other page results in dynamic data
previously downloaded via the TAG_TEMPLATE_DATA
Omni-ID, Inc
Confidential Information
Page | 19
6
TEXT RENDERING
6.1
Character Set
Supported ASCII characters are listed in Table 12. All other characters will be displayed as a checkered pattern:
Character
Hex
0x30
0x31
0x32
0x33
0x34
0x35
0x36
0x37
0x38
0x39
0x3A
0x41
0x42
0x43
0x44
0x45
0x46
0x47
0x48
Dec
48
49
50
51
52
53
54
55
56
57
58
65
66
67
68
69
70
71
72
Character
13
Hex
0x49
0x4A
0x4B
0x4C
0x4D
0x4E
0x4F
0x50
0x51
0x52
0x53
0x54
0x55
0x56
0x57
0x58
0x59
0x5A
0x61
Dec
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
97
Character
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
Hex
0x62
0x63
0x64
0x65
0x66
0x67
0x68
0x69
0x6A
0x6B
0x6C
0x6D
0x6E
0x6F
0x70
0x71
0x72
0x73
0x74
Dec
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
Character
13
13
13
13
13
13
Hex
0x75
0x76
0x77
0x78
0x79
0x7A
Dec
117
118
119
120
121
122
Table 12
13
Lowercase letters are replaced with Uppercase letters when displayed
Omni-ID, Inc
Confidential Information
Page | 20
6.2
Character Font Size
A scalable 8-pixel font is used allowing multiple font sizes. Table 13 shows a range of font sizes with their
correlating pixel size.
Font Size
Pixel Size
8x8
16x16
24x24
32x32
40x40
48x48
56x56
âŚ
Table 13
Figure 6
Omni-ID, Inc
Confidential Information
Page | 21
7
7.1
EXTERNAL FLASH
Memory Map
Address
RFU
(32KB)
Scratch
Pad
(32KB)
Images
(384KB)
Log
(64KB)
2.7â
264 x 176 Pixel
4.41â
400 x 300 Pixel
0x00000
0x07FFF
0x08000
0x0FFFF
0x10000
0x11FFF
0x12000
0x13FFF
âŚ
0x6C000
0x6DFFF
0x6E000
0x6FFFF
0x70000
0x7FFFF
Page 1
Page 1
Page 2
âŚ
âŚ
Page 47
Page 24
Page 48
Table 14
7.2
Space Between Images
Page
Address
Offset
0x0000
0x16AF
0x16B0
0x16B1
0x16B2
0x16BF
0x16C0
0x1FFF
0x2000
0x3A97
0x3A99
0x3A9A
0x3A9B
0x3AA7
0x3AA8
0x3FFF
2.7â
264 x 176 Pixel
4.41â
400 x 300 Pixel
Page 1 Image
Image Dirty Byte
Template Dirty Byte
RFU
Page 1 Image
Template Space
Image Dirty Byte
Template Dirty Byte
RFU
Template Space
Table 15
Omni-ID, Inc
Confidential Information
Page | 22
7.2.1 Image Dirty Byte
The image dirty byte is set to flag if the image is valid. It is also used to flag if the space is still valid and being used
for other purposes, such as memory storage, but should not be displayed.
Value
0x00
0x01
0xFF
Meaning
RFU
Valid Image
No Valid Image
Table 16
7.2.2 Template Dirty Byte
The template dirty byte is set to flag if there is a valid template that needs to be processed on an image update.
Value
0x00
0x01
0xFF
Meaning
RFU
Valid Template
No Valid Template
Table 17
Omni-ID, Inc
Confidential Information
Page | 23
8
8.1
EVENT LOG
Overview
Events are logged to external flash (see Table 14 for address) serially. An event is triggered when a preset
threshold is reached. For example, every 100 announces a LOG_ANNOUNCE is saved in the event log. Combined
with a LOG_TIMESTAMP saved once per day, this gives a fairly detailed account of the tagâs life.
Omni-ID, Inc
Confidential Information
Page | 24
8.2
Cheat Sheet
REASON
Default
Cadence
Max
Lifetime
Expected
Max
Expected
Log Size
Raw Data Bytes14
LOG_RFU
Code
0x00
LOG_HEADER
0x01
LOG_TIMESTAMP
LOG_ANNOUNCE
LOG_ANNOUNCE_NO_ACK
LOG_PAGE_FLIP
LOG_RADIO_ON_TIME
LOG_TRIGGER_COUNT
LOG_FW_VERSION
Every 1
5 Years
Day
100
285,000
200
2,900,000
Every 10 120,000
Every 5
8,333
Minutes Minutes
200
2,900,000
1825
0x02
2850
14,500
12,000
0x03
0x04
0x05
1,666
0x06
14,500
0x07
20
0x08
LOG_RESET_POWER_ON
0x09
LOG_RESET_REASON
LOG_FLASH_ON_TIME
LOG_CHANGE_TH_TIMESTAMP
LOG_CHANGE_
TH_ANNOUNCE_NO_ACK
LOG_CHANGE_
20
5 Years
20
0x0A
0x0E
0x72
0x73
0x74
14
15
2 3 4
Notes
Reserved
Log
Version
Time in seconds
Time in seconds
FW Version (App
Type, Major Rev,
Minor Rev, Sub Rev)
Separate from
LOG_RESET_REASON so we
can distinguish brown out
resets
Reason15
New Threshold
New
Threshold
New
Multi-Byte data is stored little Endian
Reasons {0:RFU, 1:Unused, 2:Unexpected RF Interrupt, 3:FW Update, 4:Requested, 5:MagSwitch/Button, 6:Unexpected Interrupt}
Omni-ID, Inc
Confidential Information
Page | 25
TH_ANNOUNCE_NO_ACK
LOG_CHANGE_ TH_PAGE_FLIP
0x75
LOG_CHANGE_ TH_RADIO_ON_TIME
20
0x76
LOG_CHANGE_ TH_TRIGGER_COUNT
0x77
LOG_CHANGE_TH_RESET
0x79
LOG_CHANGE_TH_FLASH
LOG_CHANGE_NAH_TIMESTAMP
LOG_CHANGE_NAH_PAGE_FLIP
LOG_CHANGE_NAH_RADIO_ON_TIME
LOG_CHANGE_NAH_FLASH_ON_TIME
LOG_UNUSED
40
40
40
0x7E
0x42
0x45
0x46
0x4E
0xFF
Threshold
New
Threshold
New Threshold
New
Threshold
New
Threshold
New Threshold
New nAh per second
New nAh per tick
New nAh per second
New nAh per second
Table 18
Omni-ID, Inc
Confidential Information
Page | 26
8.3
Log Header
The log header is used to indicate that the logging format was changed. This allows FW updates in the field that
impact the event logger without negating the old log data.
8.4
LOG_CHANGE_
The LOG_CHANGE_ operations allow changes in the hardcoded thresholds and expected nAh battery usage to be
logged. This allows FW to parse the log at runtime and react to threshold and power differences between FW
updates.
Omni-ID, Inc
Confidential Information
Page | 27
9
9.1
INTERNAL FLASH
Address Map
Info D
(Calibration)
Info C
(Parameters)
Omni-ID, Inc
Address
0x1800
0x1801
0x1802
0x1803
0x1804
0x1805
0x1806
0x1807
0x1808
0x1809
0x180A
0x180B
0x180C
0x180D
0x180E
âŚ
0x187F
0x1880
0x1881
0x1882
0x1883
0x1884
0x1885
0x1886
0x1887
0x1888
0x1889
0x188A
0x188B
0x188C
Uses
Type 0
Type 1
Type 2
UID
UID
UID
RfFreq2
RfFreq1
RfFreq0
RfMaxPower
RfFreq2
RfFreq1
RfFreq0
RfMaxPower
HwVersion
RfFreq2
RfFreq1
RfFreq0
RfMaxPower
HwVersion
Type 0
Type 1
Type 2
Type 3
Type 4
SleepDwell
SleepDwell
SleepDwell
SleepDwell
SleepDwell
AwakeDwell
RetryInterval
AwakeDwell
RetryInterval
AwakeDwell
RetryInterval
AwakeDwell
RetryInterval
RetryInterval
BeaconPeriod
BeaconPeriod
BeaconPeriod
FamilyValue
FamilyValue
FamilyValue
DomainValue
DomainValue
DomainValue
Confidential Information
AwakeTime
Page | 28
0x188D
0x188E
0x188F
0x1890
0x1891
0x1892
0x1893
0x1894
0x1895
0x1896
0x1897
0x1898
0x1899
0x189A
0x189B
0x189C
0x189D
0x189E
0x189F
0x18A0
0x18A1
0x18A2
0x18A3
0x18A4
0x18A5
0x18A6
0x18A7
0x18A8
0x18A9
0x18AA
0x18AB
0x18AC
0x18AD
0x18AE
0x18AF
0x18B0
Omni-ID, Inc
BeaconCount
BeaconCount
BeaconCount
CurrentPage
RetryCount
RfChannel
TxPower
CurrentPage
RetryCount
RfChannel
TxPower
CurrentPage
RetryCount
RfChannel
TxPower
RFIDTriggerCount
RFIDTriggerCount
RFIDTriggerCount
WatchdogExpireCount
WatchdogExpireCount
WatchdogExpireCount
awakeTimeCount
awakeTimeCount
announceCount
announceCount
pageFlipCount
pageFlipCount
BeaconCount
CurrentPage
RetryCount
RfChannel
TxPower
CurrentPage
RetryCount
RfChannel
TxPower
button1Presses
button2Presses
Confidential Information
Page | 29
Info B
(Debug)
Info A
Omni-ID, Inc
0x18B1
âŚ
0x18FF
0x1900
0x1901
0x1902
0x1903
0x1904
0x1905
0x1906
âŚ
0x197F
0x1980
0x19FF
ResetCount
FailureCode
StateTransition
State
OTState
Confidential Information
Page | 30
9.2
Calibration Data â.infoDâ
Unused
9.3
HW Configuration
HW Configuration is set at manufacturing and allows a single base FW to decide at run time which HW options to
utilize. For example, the micro must know if the mag switch is populated or not and can determine this by the HW
Configuration version.
Product
Version
Value
Magswitch
Buttons
P3
P3
A1
A2
0x01
0x02
NO
YES
NO
NO
P3
A3
0x03
YES
YES
P3
P3
A4
A5
0x04
0x05
YES
YES
YES
NO
P3
A6
0x06
YES
YES
P4
P4
P4
P4
A1
A2
A3
A5
0x11
0x12
0x13
0x14
NO
YES
YES
YES
NO
NO
YES
NO
P4
A6
0x15
YES
YES
L3
L4
A1
A1
0x21
0x31
Prototypes Never
in Production
In Production
Notes
Inverted Discharge
Inverted LED & Button
input
Inverted Discharge
Monza (I2C)
Display Power moved.
Flash Power Enable
added.
Monza (I2C)
Display Power moved.
Flash Power Enable
added.
Table 19
Omni-ID, Inc
Confidential Information
Page | 31
10 POWER MEASUREMENTS
Power usage is tracked in FW to allow an estimation of battery life remaining. This value is a very rough estimate
based on typical power measurements, and only accounts for power used in a few operations.
10.1 Revision 01.03.00.00
Monitored
Page Flip
Standby
Standby In constant RFID
Radio On Time
Flash On Time
Reset per mS
Current
2.8uA
10uA
19mA
Measured
mAh
0.01555555
0.00000077
0. 00000277
0.00529288
0.00527777778
Calculated in FW
nAh
15700 per Flip
2 per Second
5300 per Second
5300 per Second
1.378mA Running no flash
20uA Flash on in sleep
18.2mA flash on no read
18.5mA flash on constant read
20.6 flash write
Omni-ID, Inc
Confidential Information
Page | 32
FCC Compliance
This device complies with part 15 of the FCC Rules. Operation is subject to the
following two conditions:
(1) This device may not cause harmful interference, and (2) this device must accept any
interference received, including interference that may cause undesired operation.
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 energy and, if not installed and used in accordance with the
instruction manual, may cause harmful interference to radio communications.
Operation of this equipment in a residential area is likely to cause harmful interference
in which case the user will be required to correct the interference at his own expense.
Industry Canada Compliance
This device complies with Industry Canada license-exempt RSS standard(s). Operation
is subject to the following two conditions:
(1) this device may not cause interference, and
(2) this device must accept any interference, including interference that may cause
undesired operation of the device.
Le prĂŠsent appareil est conforme aux CNR d'Industrie Canada applicables aux appareils
radio exempts de licence. L'exploitation est autorisĂŠe aux deux conditions suivantes :
(1) l'appareil ne doit pas produire de brouillage, et
(2) l'utilisateur de l'appareil doit accepter tout brouillage radioĂŠlectrique subi, mĂŞme si
lebrouillage est susceptible d'en compromettre le fonctionnement.
Under Industry Canada regulations, this radio transmitter may only operate
using an antenna of a type and maximum (or lesser) gain approved for the
transmitter by Industry Canada.
To reduce potential radio interference to other users, the antenna type and its
gain should be so chosen that the equivalent isotropically radiated power
(e.i.r.p.) is not more than that necessary for successful communication.
ConformĂŠment Ă la rĂŠglementation d'Industrie Canada, le prĂŠsent ĂŠmetteur
radio peut fonctionner avec une antenne d'un type et d'un gain maximal (ou
infĂŠrieur) approuvĂŠ pour l'ĂŠmetteur par Industrie Canada.
Dans le but de rĂŠduire les risques de brouillage radioĂŠlectrique Ă l'intention des
autres utilisateurs, il faut choisir le type d'antenne et son gain de sorte que la
puissance isotrope rayonnĂŠe ĂŠquivalente (p.i.r.e.) ne dĂŠpasse pas l'intensitĂŠ
nĂŠcessaire Ă l'ĂŠtablissement d'une communication satisfaisante.
Omni-ID, Inc
Confidential Information
Page | 33
This radio transmitter 10336A-VIEW4 has been approved by Industry Canada to
operate with the antenna types listed below with the maximum permissible gain and
required antenna impedance for each antenna type indicated. Antenna types not
included in this list, having a gain greater than the maximum gain indicated for that
type, are strictly prohibited for use with this device.
Le prĂŠsent ĂŠmetteur radio (identify the device by certification number, or model
number if Category II) a ĂŠtĂŠ approuvĂŠ par Industrie Canada pour fonctionner avec les
types d'antenne ĂŠnumĂŠrĂŠs ci-dessous et ayant un gain admissible maximal et
l'impĂŠdance requise pour chaque type d'antenne. Les types d'antenne non inclus dans
cette liste,
ou dont le gain est supĂŠrieur au gain maximal indiquĂŠ, sont strictement interdits pour
l'exploitation de l'ĂŠmetteur.
Copyright Š2015 Omni-ID, Cayman, Ltd. All rights reserved.
The information in these pages are furnished for informational use only, are subject to
change without notice, and should not be construed as a commitment by Omni-ID,
Cayman, Ltd.
Omni-ID, Cayman, Ltd. assumes no responsibility or liability for any errors or
inaccuracies. Every effort has been made to supply complete and accurate information.
Omni-ID assumes no responsibility for its use, or for any infringements of patents or
other rights of third parties, which would result.
Omni-ID
1200 Ridgeway Ave.
Suite 106
Rochester, NY 14615
www.omni-id.com
Omni-ID, Inc
Confidential Information
Page | 34
Source Exif Data:
File Type : PDF File Type Extension : pdf MIME Type : application/pdf PDF Version : 1.5 Linearized : No Page Count : 34 Language : en-US Tagged PDF : Yes Author : Jeffrey Orvek Creator : Microsoft® Word 2010 Create Date : 2015:04:07 14:29:20-04:00 Modify Date : 2015:04:07 14:29:20-04:00 Producer : Microsoft® Word 2010EXIF Metadata provided by EXIF.tools