Difference between revisions of "NBL-2"

From Wiki Knowledge Base | Teltonika GPS
m (Text replacement - "Bluetooth(?!®)" to "Bluetooth®")
m
(32 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
==Introduction to the product==
 
==Introduction to the product==
−
[[File:NBL-2 3.png|right|frameless|300x300px]]
+
 
  
 
'''Description:'''
 
'''Description:'''
 +
[[File:Nbl.png|alt=|right|280x280px]]
 +
Netronix NBL-2 -  wireless RFID reader with Bluetooth.
  
−
Netronix NBL-2 -  wireless Bluetooth® RFID reader with additional buttons.
 
  
 
'''NBL-2 is great in these use cases:'''
 
'''NBL-2 is great in these use cases:'''
−
* Authorized driving - track who is driving your vehicle. You will receive a card ID every time a driver applies a card to NBL-2 reader.
+
* Authorized driving - keep track of who is driving your vehicle according to the NBL-2 ID they use to authenticate themselves.
−
* 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-2 buttons.
+
* Private mode – gives ability to mask all the personal data while vehicle is used in Private mode.
 +
 
 +
 
 +
 
 +
 
  
  
−
'''Futures:'''
 
  
−
* Mifare® Classic, Desfire card supports
 
−
* Bluetooth® low energy module
 
−
* Operating frequency - 13,56MHz
 
−
* Built in two LED indicators
 
−
* Built in two buttons
 
−
* UID and card DATA available
 
−
* Configure via BL link
 
−
* Firmware update via Bluetooth®
 
 
==Product Specification==
 
==Product Specification==
 
{| class="wikitable"
 
{| class="wikitable"
 +
|Operating frequency
 +
|13,56MHz
 +
|-
 +
|Supported standards
 +
|MIFARE® Classic
 +
MIFARE® DESFire
 +
|-
 +
|Interface
 +
|Bluetooth
 
|-
 
|-
 
|Supply voltage
 
|Supply voltage
Line 36: Line 41:
 
|Size (mm)
 
|Size (mm)
 
|58 x 99 x 19
 
|58 x 99 x 19
−
|-
 
−
|Weight
 
−
|43.78 g
 
 
|-
 
|-
 
|Type
 
|Type
Line 44: Line 46:
 
|}
 
|}
  
−
==NBL-2 Configuration==
+
==NBL-2 configuration==
−
 
 
−
'''For the NBL Tools application, contact the Netronix NBL manufacturer.''' 
 
−
 
 
−
First, you have to make sure that NBL-2 firmware version is updated to 1.3.
 
−
 
 
−
If the firmware version is lower than 1.3, it is necessary to update the device.
 
  
  
 
'''1.    Updating NBL-2'''
 
'''1.    Updating NBL-2'''
  
−
Go to NBL Tools application -> Device -> Characteristic -> Device Information Service -> Firmware Revision String.
+
First, you have to make sure that NBL-2 firmware version is updated to 1.3. Go to NBL Tools application -> Device -> Characteristic -> Device Information Service -> Firmware Revision String.
  
 
[[File:NBL_conf1.jpg.jpg|alt=|frameless|520x520px]]  [[File:NBL_conf2.jpg.jpg|alt=|border|frameless|520x520px]]  [[File:NBL_conf3.jpg.jpg|alt=|frameless|519x519px]]
 
[[File:NBL_conf1.jpg.jpg|alt=|frameless|520x520px]]  [[File:NBL_conf2.jpg.jpg|alt=|border|frameless|520x520px]]  [[File:NBL_conf3.jpg.jpg|alt=|frameless|519x519px]]
Line 65: Line 61:
 
If it is 1.2, then update NBL-2 according to these steps:
 
If it is 1.2, then update NBL-2 according to these steps:
  
−
1.      Run the NBL Tools application
+
1.      Run NBL Tools application
  
−
2.      Update the firmware database (tap: Manager Firmware -> Update the database -> Start). Select NBL-2 and check 1.3 firmware version.
+
2.      Update the firmware database (tap: Menager Firmware -> Update the database -> Start). Select NBL-2 and check 1.3 firmware version.
  
 
[[File:NBL conf4.jpg.jpg|frameless|519x519px]]  [[File:NBL conf5.jpg.jpg|frameless|519x519px]]  [[File:NBL conf6.jpg.jpg|frameless|519x519px]]
 
[[File:NBL conf4.jpg.jpg|frameless|519x519px]]  [[File:NBL conf5.jpg.jpg|frameless|519x519px]]  [[File:NBL conf6.jpg.jpg|frameless|519x519px]]
  
−
3.      Back to the main menu.
+
3.      Back to main menu.
  
−
4.      Tap the Device option.
+
4.      Tap Device option.
  
 
[[File:NBL conf7.jpg.jpg|frameless|520x520px]]
 
[[File:NBL conf7.jpg.jpg|frameless|520x520px]]
  
−
5.      Wake up the device - for example, by applying a card to it.
+
5.      Wake up the device - eg entering it into the bootloader mode.
  
−
6.      Select the device from the list, then select Update firmware from the drop-down menu and press the Start button.
+
6.      Select the device from the list (long press), then select Update firmware from the drop-down menu and press Start button.
  
 
[[File:NBL conf9.jpg.jpg|frameless|520x520px]]  [[File:NBL conf8.jpg.jpg|frameless|519x519px]]
 
[[File:NBL conf9.jpg.jpg|frameless|520x520px]]  [[File:NBL conf8.jpg.jpg|frameless|519x519px]]
  
 
7.      Correct firmware update will be signaled by device start-up led message.
 
7.      Correct firmware update will be signaled by device start-up led message.
−
 
−
'''2.    Power OFF /Reset to default settings'''
 
−
 
−
To set factory defaults and unpairing both buttons must be pressed for 5 seconds additionally button 1 (blue) must be pressed first. It is also factory/transport configuration.
 
−
 
−
Procedure:
 
−
# Press Button1 and hold
 
−
# Press Button2 and hold
 
−
# Keep the buttons pressed for 5 seconds
 
−
# The return to the factory settings will be signaledby flashing LED1 and LED2
 
−
 
−
 
−
'''3.    Power ON (After Powered OFF)'''
 
−
 
−
Procedure:
 
−
# Press Button 2 and hold
 
−
# Keep the button pressed for 5 seconds
 
−
# The Power On will be signaled by flashing LED1 and LED2
 
−
 
−
 
−
'''4.    Paring'''
 
−
 
−
When device have defaults settings, reader waits for button then sends advertising packet for 50 seconds and blinks LEDs. First connection in this state is pairing process. Paring mode used: No Pin.
 
−
 
−
When the device is paired, the pairing mode is changed to pairing using the PIN. This prevents the pairing of additional devices
 
−
 
 
==Device configuration==
 
==Device configuration==
−
This functionality is available from firmware version FMB.Ver.03.28.05.Rev.04
+
Setting up NBL-2 device to connect with FMB device. Go to Teltonika configurator -> Bluetooth 4.0 and set it up like it shown in this screenshot (MAC adress will depend on your particular NBL sensor):[[File:NBL conf10.jpg.png|frameless|1128x1128px]]
−
 
 
−
Setting up NBL-2 device to connect with FMB device.  
 
−
 
 
−
Go to Teltonika configurator -> Bluetooth® 4.0 and set it up like it shown in this screenshot (MAC address will depend on your particular NBL sensor):
 
−
 
 
−
[[File:Nbl2 1.png|frameless|660x660px]]
 
−
 
 
−
'''Mandatory setting condition: Non Stop Scan'''
 
−
 
 
−
[[File:Nbl2 2.png|frameless|350x350px]]
 
  
 
Then go to I/O settings:  
 
Then go to I/O settings:  
  
−
Make sure to enable the BLE RFID #1 parameter (ID: 51740). We would recommend to set the operand to „[[Template:FMB I/O settings#Operand On Change|On Change]]“.
+
Make sure to enable BLE Custom 1 parameter (ID: 51190) and set operand to „On Change“.
  
−
[[File:Nbl2 3.png|frameless|999x999px]]
+
[[File:NBL conf11.jpg.png|frameless|1127x1127px]]
  
 
==Setting up Private/Business mode==
 
==Setting up Private/Business mode==
−
Make sure to enable Private/Business mode in Trip/Odometer settings. It can be done using SMS commands or a configurator. Not every device has these parameters visible in the configurator, therefore they should be configured via SMS commands. It can be done by sending  ''setparam'' SMS (how to send SMS commands: [[FMB120 SMS/GPRS Commands|https://wiki.teltonika-gps.com/view/FMB120_SMS/GPRS_Commands]]). Set it to High or Low priority (parameter ID: 11850). Enable triggers as NBL-1 Button1 or NBL-1 Button2 (parameter ID: 11811).
+
Make sure to enable Private/Business mode in Trip/Odometer settings. It can be done using SMS commands or configurator. Not every device has these parameters visible in the configurator, therefore they should be configured via SMS commands. It can be done by sending  ''setparam'' SMS (how to send SMS commands: [[FMB120 SMS/GPRS Commands|https://wiki.teltonika-gps.com/view/FMB120_SMS/GPRS_Commands]]). Set it to High or Low priority (parameter ID: 11850). Enable triggers as NBL-1 Button1 or NBL-1 Button2 (parameter ID: 11811).
−
 
+
[[File:NBL conf12.jpg.png|none|thumb|500x500px]]
−
[[File:NBL_conf12.jpg.png|alt=|frameless|500x500px]]
+
Don‘t forget to save all these changes to device and you are ready to test NBL-2 sensor.
−
 
 
−
Don't forget to set up data masking in Private mode if necessary.
 
−
 
 
−
[[File:Nbl2 4.png|frameless|335x335px]]
 
−
 
 
−
 
 
−
Don‘t forget to save all these changes to the device and you are ready to test the NBL-2 sensor.
 
−
 
 
−
[[Private/Business Driving Mode Functionality|More information about Private/Business Driving Mode Functionality.]]
 
  
 
==Testing NBL-2==
 
==Testing NBL-2==
−
'''1.    Using the Configurator'''
+
Power up FMB device and start logging it in Terminal application. When RFID card is not enabled, BLE Custom 1 parameter (AVL ID: 331) will show a specific value. Example:
  
−
Power up the FMB device, connect it to PC and open Configurator application. Configure devices as shown above.
+
''IO ID[331] Length[   0]: NaN''
  
−
When the RFID card is not enabled, the BLE RFID #1 parameter (AVL ID: 451) will show a specific value.
+
When RFID card is activated (card touched to NBL-2 and followed by two beeps) BLE Custom 1 parameter should look like this:
  
−
Example (Status tab => I/O Info):
+
''IO ID[331] Length[   8]: 00h 19h 3Eh F2h 57h 66h 80h 00h''
−
 
 
−
[[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):
 
When Private/Business mode is enabled (Button1 or Button2 is pressed):
  
−
''IO ID[451]: 0x0000000000000000''
+
''IO ID[331] Length[   8]: 00h 00h 00h 00h 00h 00h 00h 00h''
−
 
 
−
and
 
−
 
 
−
''IO ID[391]: 1''
 
−
==NBL-2 packet==
 
−
NBL-T data is being read via broadcast packets only. The packet structure is described below:
 
−
{| class="wikitable"
 
−
|+
 
−
!EIR Type
 
−
!Description / Value
 
−
!LEN
 
−
|-
 
−
|Flags – 0x01
 
−
|0x06
 
−
GeneralDiscoverable,
 
−
 
 
−
BrEdrNotSupported
 
−
|3B
 
−
|-
 
−
|Complete name – 0x09
 
−
|‘NBL-2’ (for NBL-2 device)
 
−
|7B
 
−
|-
 
−
|Service data – 0x16
 
−
|Data format
 
−
{| class="wikitable"
 
−
!BYTE:
 
−
!0..1
 
−
!2
 
−
!3
 
−
!4
 
−
!5
 
−
!6
 
−
![7..8]
 
−
!9
 
−
!10..18
 
−
|-
 
−
|Field:
 
−
|UUID
 
−
|Status
 
−
|Batt
 
−
|X
 
−
|Y
 
−
|Z
 
−
|0
 
−
|CID_Len
 
−
|CID
 
−
|}
 
−
{| class="wikitable"
 
−
!Field
 
−
!Description
 
−
|-
 
−
|UUID
 
−
|‘NX’
 
−
|-
 
−
|Status
 
−
|Data format:
 
−
{| class="wikitable"
 
−
|+
 
−
!MSB
 
−
!
 
−
!
 
−
!
 
−
!
 
−
!
 
−
!
 
−
!LSB
 
−
|-
 
−
|Motion
 
−
|Card
 
−
|Confirm
 
−
|0
 
−
|0
 
−
|0
 
−
|B1
 
−
|B2
 
−
|}
 
−
• '''Motion''' – if 1, sensor detect movement
 
−
 
 
−
• '''Card''' – if 1, the ID is read
 
−
 
 
−
• '''Btn1''' – state of button 1
 
−
 
 
−
• '''Btn2''' – state of button 2
 
−
 
 
−
 
 
−
|-
 
−
|Batt
 
−
|Battery level in %
 
−
|-
 
−
|X
 
−
|X Axis acceleration
 
−
|-
 
−
|Y
 
−
|Y Axis acceleration
 
−
|-
 
−
|Z
 
−
|Z Axis acceleratio
 
−
|-
 
−
|CID_Len
 
−
|ID length
 
−
|-
 
−
|CID
 
−
|ID card number
 
−
|}
 
−
|21B
 
−
|}
 
−
Total packet length: 31B.
 
−
[[Category:Accessories]]
 

Revision as of 14:11, 4 November 2022

Main Page > Accessories > NBL-2

Introduction to the product

Description:

Netronix NBL-2 -  wireless RFID reader with Bluetooth.


NBL-2 is great in these use cases:

  • Authorized driving - keep track of who is driving your vehicle according to the NBL-2 ID they use to authenticate themselves.
  • Private mode – gives ability to mask all the personal data while vehicle is used in Private mode.




Product Specification

Operating frequency 13,56MHz
Supported standards MIFARE® Classic

MIFARE® DESFire

Interface Bluetooth
Supply voltage two AAA batteries
Sensor Accelerometer

Low battery voltage

Operating temperature -20ºC to +70ºC
Size (mm) 58 x 99 x 19
Type RFID reader

NBL-2 configuration

1.    Updating NBL-2

First, you have to make sure that NBL-2 firmware version is updated to 1.3. Go to NBL Tools application -> Device -> Characteristic -> Device Information Service -> Firmware Revision String.


Note: If the firmware version is 1.1 or 1.0, it is not possible to update it.

If it is 1.2, then update NBL-2 according to these steps:

1.      Run NBL Tools application

2.      Update the firmware database (tap: Menager Firmware -> Update the database -> Start). Select NBL-2 and check 1.3 firmware version.

NBL conf4.jpg.jpg NBL conf5.jpg.jpg NBL conf6.jpg.jpg

3.      Back to main menu.

4.      Tap Device option.

NBL conf7.jpg.jpg

5.      Wake up the device - eg entering it into the bootloader mode.

6.      Select the device from the list (long press), then select Update firmware from the drop-down menu and press Start button.

NBL conf9.jpg.jpg NBL conf8.jpg.jpg

7.      Correct firmware update will be signaled by device start-up led message.

Device configuration

Setting up NBL-2 device to connect with FMB device. Go to Teltonika configurator -> Bluetooth 4.0 and set it up like it shown in this screenshot (MAC adress will depend on your particular NBL sensor):NBL conf10.jpg.png

Then go to I/O settings:

Make sure to enable BLE Custom 1 parameter (ID: 51190) and set operand to „On Change“.

NBL conf11.jpg.png

Setting up Private/Business mode

Make sure to enable Private/Business mode in Trip/Odometer settings. It can be done using SMS commands or configurator. Not every device has these parameters visible in the configurator, therefore they should be configured via SMS commands. It can be done by sending  setparam SMS (how to send SMS commands: https://wiki.teltonika-gps.com/view/FMB120_SMS/GPRS_Commands). Set it to High or Low priority (parameter ID: 11850). Enable triggers as NBL-1 Button1 or NBL-1 Button2 (parameter ID: 11811).

NBL conf12.jpg.png

Don‘t forget to save all these changes to device and you are ready to test NBL-2 sensor.

Testing NBL-2

Power up FMB device and start logging it in Terminal application. When RFID card is not enabled, BLE Custom 1 parameter (AVL ID: 331) will show a specific value. Example:

IO ID[331] Length[   0]: NaN

When RFID card is activated (card touched to NBL-2 and followed by two beeps) BLE Custom 1 parameter should look like this:

IO ID[331] Length[   8]: 00h 19h 3Eh F2h 57h 66h 80h 00h


When Private/Business mode is enabled (Button1 or Button2 is pressed):

IO ID[331] Length[   8]: 00h 00h 00h 00h 00h 00h 00h 00h

Retrieved from "https://wiki.teltonika-gps.com/index.php?title=NBL-2&oldid=77779"