Line 9: |
Line 9: |
| *Authorized driving - track who is driving your vehicle. You will receive a card ID every time a driver applies a card to NBL-3 reader. | | *Authorized driving - track who is driving your vehicle. You will receive a card ID every time a driver applies a card to NBL-3 reader. |
| *Private mode – this solution will allow your company car to be used by employees for personal purposes without violating the EU General Data Protection Regulations by masking all the personal data while vehicle is used in Private mode. Moreover, self-employed people can easily convert their own car into a business asset and ensure that the data provided (Example - distance traveled) is correct and shown only working hours' driven distance. Private/business mode can be easily switched by any of the NBL-3 buttons. | | *Private mode – this solution will allow your company car to be used by employees for personal purposes without violating the EU General Data Protection Regulations by masking all the personal data while vehicle is used in Private mode. Moreover, self-employed people can easily convert their own car into a business asset and ensure that the data provided (Example - distance traveled) is correct and shown only working hours' driven distance. Private/business mode can be easily switched by any of the NBL-3 buttons. |
− | *ID read notification functionality | + | *ID read notification functionality works when |
| | | |
| | | |
Line 17: |
Line 17: |
| *Bluetooth low energy module | | *Bluetooth low energy module |
| *Operating frequency - 13,56MHz | | *Operating frequency - 13,56MHz |
− | *Built in two LED indicators | + | * Built in two LED indicators |
− | *Built in two buttons | + | * Built in two buttons |
| *Built in light sensor | | *Built in light sensor |
− | *UID and card DATA available | + | * UID and card DATA available |
| *Configure via BL link | | *Configure via BL link |
| *Firmware update via Bluetooth | | *Firmware update via Bluetooth |
Line 91: |
Line 91: |
| [[Private/Business Driving Mode Functionality|More information about Private/Business Driving Mode Functionality.]] | | [[Private/Business Driving Mode Functionality|More information about Private/Business Driving Mode Functionality.]] |
| | | |
− | == NBL-3 broadcasting behavior == | + | ==NBL-3 broadcasting behavior== |
| When NBL-3 device captures RFID value it keeps broadcasting it for roughly a minute (it varies). As of 2023.07.20 NBL-3 manufacturer Netronix states that it is currently impossible to detect when the same RFID is attached to NBL-3 device again (when RFID value is still present after first read). New RFID read can only indicated after NBL-3 value retention timeout is finished. | | When NBL-3 device captures RFID value it keeps broadcasting it for roughly a minute (it varies). As of 2023.07.20 NBL-3 manufacturer Netronix states that it is currently impossible to detect when the same RFID is attached to NBL-3 device again (when RFID value is still present after first read). New RFID read can only indicated after NBL-3 value retention timeout is finished. |
| | | |
− | ==NBL-3 packet== | + | ==Testing NBL-2== |
| + | '''1. Using the Configurator''' |
| + | |
| + | Power up the FMB device, connect it to PC and open Configurator application. Configure devices as shown above. |
| + | |
| + | When the RFID card is not enabled, the BLE RFID #1 parameter (AVL ID: 451) will show a specific value. |
| + | |
| + | Example (Status tab => I/O Info): |
| + | |
| + | [[File:NBL-2 cfg1.png|frameless|900x900px]] |
| + | |
| + | When the RFID card is activated (card touched to NBL-2 and followed by two beeps) BLE RFID #1 parameter should look like this: |
| + | |
| + | [[File:NBL-2 cfg2.png|frameless|900x900px]] |
| + | |
| + | |
| + | '''2. Using the Terminal application''' |
| + | |
| + | Power up the FMB device, connect it to PC and start logging it into the Terminal application. |
| + | |
| + | When the RFID card is not enabled, the BLE RFID #1 parameter (AVL ID: 451) will show a specific value. |
| + | |
| + | Example: |
| + | |
| + | ''IO ID[451]: 0x0000000000000000'' |
| + | |
| + | When the RFID card is activated (card touched to NBL-2 and followed by two beeps) BLE RFID #1 parameter should look like this: |
| + | |
| + | ''IO ID[451]: 0x0004193EF2576680'' |
| + | |
| + | |
| + | When Private/Business mode is enabled (Button1 or Button2 is pressed): |
| + | |
| + | ''IO ID[451]: 0x0000000000000000'' |
| + | |
| + | and |
| + | |
| + | ''IO ID[391]: 1'' |
| + | |
| + | ==NBL-3 packet == |
| NBL-T data is being read via broadcast packets only. The packet structure is described below: | | NBL-T data is being read via broadcast packets only. The packet structure is described below: |
| {| class="wikitable" | | {| class="wikitable" |