How the A1 Tag Works

Gateway Interaction

By default, the A1 tag updates its data every 15 minutes, giving it a battery life of 30 days. When there are no gateways within transmission range, however, an A1 tag may acknowledge up to 100 other A1 tags as log records in its built-in memory. After reaching this limit, the tag begins writing over the older log records. When a gateway is within transmission range, the tag unburdens its log records to the closest gateway.

The A1 tag connects to a gateway in range of -75dBm or better. Unloading the tag’s logs takes 3 - 4 seconds at its 15-minute update intervals. A1 tags get a server acknowledgement via the gateway. The confirmation causes the tag to flash a BLUE/RED LED (that looks close to pink) at the 5 o’ clock position with a triple ascending beep.

When the server acknowledges an A1 tag, the contact (log) data is cleared if the tag is no longer in contact with another A1 tag. A1 tags remain in contact if they are within contact range. If the tag is not able to connect to a gateway within 24 hours, the tag removes its contacts data and no longer report previous contacts.

You can update the tag reporting interval using the sofia’s Settings > Device Settings to send an Update <Use Case> Settings command to a tag group.

Interaction with BLE Compatible Access Points (Aruba and Meraki)

The tag’s interaction with BLE compatible access points functions similarly as above, reporting contact information at every report interval. The compatible infrastructure reports the information to the sofia server in real time. However, the tag displays no server confirmation because there is no connection between the tags and the compatible access point. The tag’s beacon and the access point get the data via their BLE radio signal. 

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.