Difference between revisions of "How to start with FMB devices and Beacons?"
m (Text replacement - "Bluetooth(?!®)" to "Bluetooth®") |
(Created page with "__TOC__ ==Beacon Configuration and data sending== <br> '''Beacon configuration'''<br> Below are short instructions which show how we recommend to configure the device to En...") |
||
(24 intermediate revisions by 8 users not shown) | |||
Line 1: | Line 1: | ||
__TOC__ | __TOC__ | ||
− | |||
− | == | + | ==Beacon Configuration and data sending== |
− | + | <br> | |
− | + | '''Beacon configuration'''<br> | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | Below are short instructions which show how we recommend to configure the device to Enable the Beacon functionality for testing. | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | Below are short instructions which show how we recommend | ||
[[Image:Beacon_project_V3.gif]] | [[Image:Beacon_project_V3.gif]] | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | '''Beacon data parsing'''<br> | |
− | Shown how Beacon data is represented on [[ | + | Shown how Beacon data is represented on [[Gurtam_Wialon_with_Fleet_Management_(FM)|Wialon platform]]. |
Line 57: | Line 22: | ||
==Parsing of Beacon records== | ==Parsing of Beacon records== | ||
− | Beacon records are sent as | + | Beacon records are sent as seperate Records with Event I/O ID 385 and also include I/O element 385 (Codec8 Extended has to be used, because the I/O element 385 uses Variable size IO element). |
Received data in hexadecimal stream: <br> | Received data in hexadecimal stream: <br> | ||
Line 68: | Line 33: | ||
<code>DE835D7F4965B5F06C2EDCB3A55300010080A501736B79686F73742E646B000010000128AD01000030CB</code> <br> <br> | <code>DE835D7F4965B5F06C2EDCB3A55300010080A501736B79686F73742E646B000010000128AD01000030CB</code> <br> <br> | ||
− | + | '''Example Beacon Record'''<br> | |
{| class="nd-othertables_2" style="width:100%;" | {| class="nd-othertables_2" style="width:100%;" | ||
|+ | |+ | ||
− | |||
! colspan="3" style="border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |AVL Data Packet | ! colspan="3" style="border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |AVL Data Packet | ||
|- | |- | ||
Line 136: | Line 100: | ||
| style="vertical-align: middle; text-align: center;" |NX of X Bytes IO | | style="vertical-align: middle; text-align: center;" |NX of X Bytes IO | ||
| style="vertical-align: middle; text-align: center;" |00 01 | | style="vertical-align: middle; text-align: center;" |00 01 | ||
− | |||
− | |||
− | |||
|- | |- | ||
| style="vertical-align: middle; text-align: center;" |Length of Variable Length IO | | style="vertical-align: middle; text-align: center;" |Length of Variable Length IO | ||
Line 152: | Line 113: | ||
| style="vertical-align: middle; text-align: center;" |00 00 30 CB | | style="vertical-align: middle; text-align: center;" |00 00 30 CB | ||
|- | |- | ||
− | |} | + | |} |
==Parsing Beacon data from record== | ==Parsing Beacon data from record== | ||
Line 166: | Line 127: | ||
|} | |} | ||
<br> | <br> | ||
− | + | '''Beacon Flags'''<br> | |
− | + | Below table represents possible Beacon flags. Supported Beacon protocols are iBeacon and Eddystone. | |
{| class="nd-othertables_2" style="width:25%;" | {| class="nd-othertables_2" style="width:25%;" | ||
|+ | |+ | ||
Line 177: | Line 138: | ||
|- | |- | ||
! rowspan="1" style="width:40%; vertical-align: middle; text-align: center;" |23 | ! rowspan="1" style="width:40%; vertical-align: middle; text-align: center;" |23 | ||
− | | style="vertical-align: middle; text-align: center;" |iBeacon with RSSI, | + | | style="vertical-align: middle; text-align: center;" |iBeacon with RSSI, Battery Voltage |
− | Battery Voltage | ||
|- | |- | ||
! rowspan="1" style="width:40%; vertical-align: middle; text-align: center;" |27 | ! rowspan="1" style="width:40%; vertical-align: middle; text-align: center;" |27 | ||
Line 192: | Line 152: | ||
| style="vertical-align: middle; text-align: center;" |Eddystone with RSSi, Battery Voltage, Temperature | | style="vertical-align: middle; text-align: center;" |Eddystone with RSSi, Battery Voltage, Temperature | ||
|} | |} | ||
− | |||
{| class="nd-othertables_2" style="width:100%;" | {| class="nd-othertables_2" style="width:100%;" | ||
|+ | |+ | ||
Line 202: | Line 161: | ||
| rowspan="50" style="vertical-align: middle; text-align: center;" | | | rowspan="50" style="vertical-align: middle; text-align: center;" | | ||
| style="vertical-align: middle; text-align: center;" |Data part<br> (First half byte – current data part, Second half byte – total number of data parts) | | style="vertical-align: middle; text-align: center;" |Data part<br> (First half byte – current data part, Second half byte – total number of data parts) | ||
− | | style="vertical-align: middle; text-align: center;" |11 | + | | style="vertical-align: middle; text-align: center;" |11 |
|- | |- | ||
Line 219: | Line 178: | ||
| style="vertical-align: middle; text-align: center;" |BLE Beacon RSSI #1 | | style="vertical-align: middle; text-align: center;" |BLE Beacon RSSI #1 | ||
| style="vertical-align: middle; text-align: center;" |<span style="background:#87CEEB">BA</span> - Signed 2's Complement -70 dBm | | style="vertical-align: middle; text-align: center;" |<span style="background:#87CEEB">BA</span> - Signed 2's Complement -70 dBm | ||
− | + | </span> | |
|- | |- | ||
| style="vertical-align: middle; text-align: center;" |BLE beacon flags #2<br> 21 - iBeacon, RSSI is sent | | style="vertical-align: middle; text-align: center;" |BLE beacon flags #2<br> 21 - iBeacon, RSSI is sent | ||
Line 324: | Line 283: | ||
|- | |- | ||
|} | |} | ||
− | |||
− |
Revision as of 09:39, 12 February 2020
Main Page > Frequently Asked Questions - FAQ > How to start with FMB devices and Beacons?Beacon Configuration and data sending
Beacon configuration
Below are short instructions which show how we recommend to configure the device to Enable the Beacon functionality for testing.
Beacon data parsing
Shown how Beacon data is represented on Wialon platform.
Parsing of Beacon records
Beacon records are sent as seperate Records with Event I/O ID 385 and also include I/O element 385 (Codec8 Extended has to be used, because the I/O element 385 uses Variable size IO element).
Received data in hexadecimal stream:
00000000000000D68E01000001701F9B3FA9000F0E5732209AB450006800290400000181000100000000000000000001018100A911214B5C049F515341
FCA950D2C264414E1000050006BA21E2C56DB5DFFB48D2B060D0F5A71096E000000000A92131A74BB76A79423196C916CFB9FAED45002D00159F0700112
233445566778899ABCDE0810047AE0BE80015210F86676BEC91420A94409110029AFAC415B31A0AA101DE9C18E92CA5AA689697365434663222BA21EBBB
DE835D7F4965B5F06C2EDCB3A55300010080A501736B79686F73742E646B000010000128AD01000030CB
Example Beacon Record
AVL Data Packet | ||
---|---|---|
AVL Data Packet Part | HEX Code Part | |
Zero Bytes | 00 00 00 00 | |
Data Field Length | 00 00 00 D6 | |
Codec ID | 8E (Codec8 Extended) | |
Number of Data 1 (Number of Total Records) | 01 | |
AVL Data | Timestamp | 00 00 01 70 1F 9B 3F A9 (GMT: Friday, 07 February 2020 12:23:53.001) |
Priority | 00 | |
Longitude | 0F 0E 57 32 | |
Latitude | 20 9A B4 50 | |
Altitude | 00 68 | |
Angle | 00 29 | |
Satellites | 04 | |
Speed | 00 00 | |
Event IO ID | 01 81 (385) | |
N of Total ID | 00 01 | |
N1 of One Byte IO | 00 00 | |
N2 of Two Bytes IO | 00 00 | |
N4 of Four Bytes IO | 00 00 | |
N8 of Eight Bytes IO | 00 00 | |
NX of X Bytes IO | 00 01 | |
Length of Variable Length IO | 00 A9 | |
Value of Variable Length IO | 11214B5C049F515341FCA950D2C264414E1000050006BA21E2C56DB5 DFFB48D2B060D0F5A71096E000000000A92131A74BB76A79423196C916CFB9FAED45002D00159F0700112233445566778899ABCDE081004 7AE0BE80015210F86676BEC91420A94409110029AFAC415B31A0AA101DE9C18E92CA5AA689697365434663222BA21EBBBDE835D7F4965B5 F06C2EDCB3A55300010080A501736B79686F73742E646B000010000128AD | |
Number of Data 2 (Number of Total Records) | 01 | |
CRC-16 | 00 00 30 CB |
Parsing Beacon data from record
Beacon data | ||
---|---|---|
Unparsed Beacon data | ||
11214B5C049F515341FCA950D2C264414E1000050006BA21E2C56DB5 DFFB48D2B060D0F5A71096E000000000A92131A74BB76A79423196C916CFB9FAED45002D00159F0700112233445566778899ABCDE081004 7AE0BE80015210F86676BEC91420A94409110029AFAC415B31A0AA101DE9C18E92CA5AA689697365434663222BA21EBBBDE835D7F4965B5 F06C2EDCB3A55300010080A501736B79686F73742E646B000010000128AD |
Beacon Flags
Below table represents possible Beacon flags. Supported Beacon protocols are iBeacon and Eddystone.
Flags | |
---|---|
21 | iBeacon with RSSI |
23 | iBeacon with RSSI, Battery Voltage |
27 | iBeacon with RSSi, Battery Voltage, Temperature |
01 | Eddystone with RSSI |
03 | Eddystone with RSSI, Battery Voltage |
07 | Eddystone with RSSi, Battery Voltage, Temperature |
Parsed Beacon data | ||
---|---|---|
Parsed Beacon data part | HEX Code Part | |
Data part (First half byte – current data part, Second half byte – total number of data parts) |
11 | |
BLE beacon flags #1 21 - iBeacon, RSSI is sent |
21 | |
BLE Beacon UUID #1 | 4B5C049F515341FCA950D2C264414E10 | |
BLE Beacon Major #1 | 0005 | |
BLE Beacon Minor #1 | 0006 | |
BLE Beacon RSSI #1 | BA - Signed 2's Complement -70 dBm
| |
BLE beacon flags #2 21 - iBeacon, RSSI is sent |
21 | |
BLE Beacon UUID #2 | E2C56DB5DFFB48D2B060D0F5A71096E0 | |
BLE Beacon Major #2 | 0000 | |
BLE Beacon Minor #2 | 0000 | |
BLE Beacon RSSI #2 | A9 - Signed 2's Complement -87 dBm | |
BLE beacon flags #3 21 - iBeacon, RSSI is sent |
21 | |
BLE Beacon UUID #3 | 31A74BB76A79423196C916CFB9FAED45 | |
BLE Beacon Major #3 | 002D | |
BLE Beacon Minor #3 | 0015 | |
BLE Beacon RSSI #3 | 9F - Signed 2's Complement -97 dBm | |
BLE beacon flags #4 07 - Eddystone, Battery Voltage, Temperature, RSSI is sent |
07 | |
BLE Beacon Namespace #4 | 00112233445566778899 | |
BLE Beacon Instance ID #4 | ABCDE0810047 | |
BLE Beacon RSSI #4 | AE - Signed 2's Complement -82 dBm | |
BLE Beacon Battery Voltage #4 | 0BE8 - 3048 mV | |
BLE Beacon Temperature #4 | 0015 - 21°C | |
BLE beacon flags #5 21 - iBeacon, RSSI is sent |
21 | |
BLE Beacon UUID #5 | 0F86676BEC91420A94409110029AFAC4 | |
BLE Beacon Major #5 | 15B3 | |
BLE Beacon Minor #5 | 1A0A | |
BLE Beacon RSSI #5 | A1 - Signed 2's Complement -95 dBm | |
BLE beacon flags #6 01 - Eddystone, RSSI is sent |
01 | |
BLE Beacon Namespace #6 | DE9C18E92CA5AA689697 | |
BLE Beacon Instance ID #6 | 365434663222 | |
BLE Beacon RSSI #6 | BA - Signed 2's Complement -70 dBm | |
BLE beacon flags #7 21 - iBeacon, RSSI is sent |
21 | |
BLE Beacon UUID #7 | EBBBDE835D7F4965B5F06C2EDCB3A553 | |
BLE Beacon Major #7 | 0001 | |
BLE Beacon Minor #7 | 0080 | |
BLE Beacon RSSI #7 | A5 - Signed 2's Complement -91 dBm | |
BLE beacon flags #8 01 - Eddystone, RSSI is sent |
01 | |
BLE Beacon Namespace #8 | 736B79686F73742E646B | |
BLE Beacon Instance ID #8 | 000010000128 | |
BLE Beacon RSSI #8 | AD - Signed 2's Complement -83 dBm |