BlePeriph command group
This command group is available in our standard firmware since version 2.13.
With this command group, you can implement your own BLE peripheral protocol, i.e. your own BLE service (with its own characteristics), which will be advertised by the reader.
Before BLE can be activated via BlePeriph.Enable, you have to define your service via BlePeriph.DefineService. This will create an internal database of characteristics that can be accessed from the BRP host with the commands BlePeriph.WriteCharacteristic and BlePeriph.ReadCharacteristic.
As soon as BLE is activated via BlePeriph.Enable and a BLE Central connects to your reader, it also has access to this internal database of characteristcs. If it connects to the reader, disconnects, or modifies a characteristic, you'll be informed via BlePeriph.GetEvents.
If the BLE peripheral functionality is used in parallel with Mobile ID: It is not possible to use the Mobile ID app and the app to interact with the BLE peripheral on a mobile device simultaneously! If you want to use the BLE peripheral app to interact with the reader, you have to disable the Mobile ID app (e.g. via the Disable app option in Settings ) or vice versa.
WARNING: This command set is not available in all Baltech reader firmware variants.
Status codes
| BRP status | BRP Library Error Code | Mnemonic | Description |
|---|---|---|---|
| 0x01 | 0x4B01 (19201) | BlePeriph.ErrNotEnabled | The command could not be executed because BLE is currently not enabled. |
| 0x02 | 0x4B02 (19202) | BlePeriph.ErrNotConnected | The reader is currently not connected with a BLE central. |
| 0x03 | 0x4B03 (19203) | BlePeriph.ErrInvalidCharacteristicNdx | The given characteristic index is invalid. |
| 0x04 | 0x4B04 (19204) | BlePeriph.ErrWriteCharacteristic | The characteristic value could not be written because the given offset or length exceeds the characteristic size. |