Changes

After the FM device and EyeBeacons are configured, the FM device will be able to read EyeBeacon data and send it to the server, where distance and positioning calculations are to be performed. Depending on the beacon mode parameter setting on the FM device, Beacon data will be sent to the server in a variable length packet AVL ID: 385 or AVL ID 548.

After the FM device and EyeBeacons are configured, the FM device will be able to read EyeBeacon data and send it to the server, where distance and positioning calculations are to be performed. Depending on the beacon mode parameter setting on the FM device, Beacon data will be sent to the server in a variable length packet AVL ID: 385 or AVL ID 548.

<br>

<br>

if advanced beacon mode is selected, beacon data is packed into AVL ID: 548. Advanced beacon mode allows the user to configure beacon data capturing manually.

•if advanced beacon mode is selected, beacon data is packed into AVL ID: 548. Advanced beacon mode allows the user to configure beacon data capturing manually.

<br>

<br>

if simple mode is selected, beacon data is packed into AVL ID: 385. Using simple mode, beacon parsing is done automatically (Eddystone and iBeacon protocols are supported).

•if simple mode is selected, beacon data is packed into AVL ID: 385. Using simple mode, beacon parsing is done automatically (Eddystone and iBeacon protocols are supported).

<br>

<br>

In order to make sense of the data sent to the server for the calculation to be made, packets need to be parsed. Depending on the selected beacon protocol, packet structure will differ. Provided below are examples of parsing a packet containing Beacon data.

In order to make sense of the data sent to the server for the calculation to be made, packets need to be parsed. Depending on the selected beacon protocol, packet structure will differ. Provided below are examples of parsing a packet containing Beacon data.