The “nxtDbVerTS” tag is used to keep the host synchronized with the ENGAGE device. This timestamp is inserted into the URL by the ENGAGE device on each database request. When the ENGAGE device requests a database for the very first time, it does so with respect to a value of “0” for the “nxtDbVerTS” tag. The host responds by sending an initial database, and it includes an updated value for the “nxtDbVerTS” tag. When the lock makes the next database request, it includes the updated nxtDbVerTS in the URL. This process continues until a device reset occurs.
If the ENGAGE device is a networked offline device, the host must include in the database records the specific time that the device will request the next database. This is accomplished through the “dbDwnLdTm” database download time as shown in the table below.
Database Download Records | ||||
Tag | Short Tag | Type/Length (ASCII bytes) | Value | Device Exclusions |
Database Download Time | dbDwnLdTm | String/14 | YYYYMMDDHHMMSS – “20140704030000” July 4, 2014, 3:00:00 am | SC, MTB, MTKB |
Next Database Version Time Stamp | nxtDbVerTS | String/18 | Hexadecimal value, that starts with 0x, followed by 16 hex digits. (i.e. “0x08d16357eef73a69” ) | MTB, MTKB |
Last Modified: October 30, 2019