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.
TABLE OF CONTENTS 1 2 Protocol .................................................................................................................................................................4 1.1 Read/Write Parameters ...............................................................................................................................4 1.2 Read Only Parameters..................................................................................................................................
6.1 Character Set ..............................................................................................................................................20 6.2 Character Font Size ....................................................................................................................................21 7 External Flash .......................................................................................................................................................22 7.
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 1 4 1 0 - Default 2 64800 5 5 200 0x01 10 Max 4 2^32 5 5 10 1.3.
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.
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.
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 + π₯
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 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.
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.
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.
3.2.2.3 RFID Opcodes RFID opcodes allow a 2 byte interface into the tag. 6 Command Display Page Delete Page Announce Extended Data Word High Byte Low Byte 0x20 Page 0x28 Page 0x30 0x00 Data Byte 0xFF 7 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.
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.
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.
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.
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.
N Data N Table 10 Memory Layout Field #2 Field #1 Field #0 Header 5.
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.
6 TEXT RENDERING 6.1 Character Set Supported ASCII characters are listed in Table 12.
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.
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.
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.
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.
8.
TH_ANNOUNCE_NO_ACK LOG_CHANGE_ TH_PAGE_FLIP 1 5 5 0x75 LOG_CHANGE_ TH_RADIO_ON_TIME 1 5 20 0x76 LOG_CHANGE_ TH_TRIGGER_COUNT 1 5 5 0x77 LOG_CHANGE_TH_RESET 1 5 5 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 1 1 1 5 5 5 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 se
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.
9 9.
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 Watch
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.
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.
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.
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.
