BLEServer Component

Properties   Methods   Events   Config Settings   Errors  

TBD.

Syntax

TiplBLEServer

Remarks

TBD.

Property List


The following is the full list of the properties of the component with short descriptions. Click on the links for further details.

ListeningThis property indicates whether the component is listening for incoming connections on LocalPort.
ServerIdTBD.

Method List


The following is the full list of the methods of the component with short descriptions. Click on the links for further details.

AddCharacteristicTBD.
ConfigSets or retrieves a configuration setting.
DoEventsThis method processes events from the internal message queue.
StartListeningTBD.
StopListeningTBD.

Event List


The following is the full list of the events fired by the component with short descriptions. Click on the links for further details.

AdvertisementStatusChangedTBD.
ConnectedTBD.
DisconnectedTBD.
ErrorFired when information is available about errors during data delivery.
LogFires once for each log message.
ReadRequestedTBD.
SessionStatusChangedTBD.
SubscriptionChangedTBD.
WriteRequestedTBD.

Config Settings


The following is a list of config settings for the component with short descriptions. Click on the links for further details.

LogLevelThe level of detail that is logged.
BuildInfoInformation about the product's build.
CodePageThe system code page used for Unicode to Multibyte translations.
LicenseInfoInformation about the current license.
MaskSensitiveDataWhether sensitive data is masked in log messages.
UseInternalSecurityAPIWhether or not to use the system security libraries or an internal implementation.

Listening Property (BLEServer Component)

This property indicates whether the component is listening for incoming connections on LocalPort.

Syntax

property Listening: Boolean read get_Listening;

Default Value

false

Remarks

This property indicates whether the component is listening for connections on the port specified by the LocalPort property. Use the StartListening and StopListening methods to control whether the component is listening.

This property is read-only and not available at design time.

ServerId Property (BLEServer Component)

TBD.

Syntax

property ServerId: String read get_ServerId write set_ServerId;

Default Value

''

Remarks

TBD.

This property is not available at design time.

AddCharacteristic Method (BLEServer Component)

TBD.

Syntax

procedure AddCharacteristic(ServiceId: String; CharacteristicId: String; Props: Integer);

Remarks

TBD.

Config Method (BLEServer Component)

Sets or retrieves a configuration setting.

Syntax

function Config(ConfigurationString: String): String;

Remarks

Config is a generic method available in every component. It is used to set and retrieve configuration settings for the component.

These settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the component, access to these internal properties is provided through the Config method.

To set a configuration setting named PROPERTY, you must call Config("PROPERTY=VALUE"), where VALUE is the value of the setting expressed as a string. For boolean values, use the strings "True", "False", "0", "1", "Yes", or "No" (case does not matter).

To read (query) the value of a configuration setting, you must call Config("PROPERTY"). The value will be returned as a string.

DoEvents Method (BLEServer Component)

This method processes events from the internal message queue.

Syntax

procedure DoEvents();

Remarks

When DoEvents is called, the component processes any available events. If no events are available, it waits for a preset period of time, and then returns.

StartListening Method (BLEServer Component)

TBD.

Syntax

procedure StartListening(ServiceId: String);

Remarks

TBD.

StopListening Method (BLEServer Component)

TBD.

Syntax

procedure StopListening(ServiceId: String);

Remarks

TBD.

AdvertisementStatusChanged Event (BLEServer Component)

TBD.

Syntax

type TAdvertisementStatusChangedEvent = procedure (
  Sender: TObject;
  Status: Integer;
  Error: Integer
) of Object;

property OnAdvertisementStatusChanged: TAdvertisementStatusChangedEvent read FOnAdvertisementStatusChanged write FOnAdvertisementStatusChanged;

Remarks

TBD.

Connected Event (BLEServer Component)

TBD.

Syntax

type TConnectedEvent = procedure (
  Sender: TObject;
  const ClientId: String;
  StatusCode: Integer;
  const Description: String
) of Object;

property OnConnected: TConnectedEvent read FOnConnected write FOnConnected;

Remarks

TBD.

Disconnected Event (BLEServer Component)

TBD.

Syntax

type TDisconnectedEvent = procedure (
  Sender: TObject;
  const ClientId: String;
  StatusCode: Integer;
  const Description: String
) of Object;

property OnDisconnected: TDisconnectedEvent read FOnDisconnected write FOnDisconnected;

Remarks

TBD.

Error Event (BLEServer Component)

Fired when information is available about errors during data delivery.

Syntax

type TErrorEvent = procedure (
  Sender: TObject;
  ErrorCode: Integer;
  const Description: String
) of Object;

property OnError: TErrorEvent read FOnError write FOnError;

Remarks

The Error event is fired in case of exceptional conditions during message processing. Normally the component raises an exception.

The ErrorCode parameter contains an error code, and the Description parameter contains a textual description of the error. For a list of valid error codes and their descriptions, please refer to the Error Codes section.

Log Event (BLEServer Component)

Fires once for each log message.

Syntax

type TLogEvent = procedure (
  Sender: TObject;
  LogLevel: Integer;
  const Message: String;
  const LogType: String
) of Object;

property OnLog: TLogEvent read FOnLog write FOnLog;

Remarks

This events fires once for each log message generated by the component. The verbosity is controlled by the LogLevel setting.

LogLevel indicates the level of the Message. Possible values are:

0 (None) No events are logged.
1 (Info - default) Informational events are logged.
2 (Verbose) Detailed data is logged.
3 (Debug) Debug data is logged.

The default log level, Info, provides information when most BLE operations begin and end, and should be sufficient to get a good idea of what the component is doing at a high level.

The Verbose log level adds a few extra operation timing messages, and adds more detail to some messages logged at the Info level.

The Debug log level causes the component to output as much information as possible about what it is doing at all times. All BLE communications, even those which are typically abstracted away by the API, are logged in full detail. Typically the additional information added by this log level is not helpful to the end user, and would only be necessary to capture if you wish to report an issue to the support team.

LogType identifies the type of log entry. Possible values are:

  • Scanning: Messages relating to scanning and advertisements.
  • Connection: Messages relating to connecting, disconnecting, and connection failures.
  • Discovery: Messages relating to any service, characteristic, or descriptor discovery process.
  • Read: Messages relating to reading values from the remote device.
  • Write: Messages relating to writing values to the remote device.
  • Subscriptions: Messages relating to subscribing to and unsubscribing from characteristics.
  • Info, Verbose, and Debug: Miscellaneous messages fired at the applicable log level concerning internal component operations.

ReadRequested Event (BLEServer Component)

TBD.

Syntax

type TReadRequestedEvent = procedure (
  Sender: TObject;
  const ClientId: String;
  const ServiceId: String;
  const CharacteristicId: String;
  var ResponseValue: String;
  var Accept: Boolean
) of Object;

property OnReadRequested: TReadRequestedEvent read FOnReadRequested write FOnReadRequested;

Remarks

TBD.

SessionStatusChanged Event (BLEServer Component)

TBD.

Syntax

type TSessionStatusChangedEvent = procedure (
  Sender: TObject;
  const ClientId: String;
  Status: Integer;
  Error: Integer
) of Object;

property OnSessionStatusChanged: TSessionStatusChangedEvent read FOnSessionStatusChanged write FOnSessionStatusChanged;

Remarks

TBD.

SubscriptionChanged Event (BLEServer Component)

TBD.

Syntax

type TSubscriptionChangedEvent = procedure (
  Sender: TObject;
  const ServiceId: String;
  const CharacteristicId: String;
  IsSubscribed: Boolean
) of Object;

property OnSubscriptionChanged: TSubscriptionChangedEvent read FOnSubscriptionChanged write FOnSubscriptionChanged;

Remarks

TBD.

WriteRequested Event (BLEServer Component)

TBD.

Syntax

type TWriteRequestedEvent = procedure (
  Sender: TObject;
  const ClientId: String;
  const ServiceId: String;
  const CharacteristicId: String;
  const Value: String;
  const ValueB: TBytes;
  WithResponse: Boolean;
  var Accept: Boolean
) of Object;

property OnWriteRequested: TWriteRequestedEvent read FOnWriteRequested write FOnWriteRequested;

Remarks

TBD.

Config Settings (BLEServer Component)

The component accepts one or more of the following configuration settings. Configuration settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the component, access to these internal properties is provided through the Config method.

BLEServer Config Settings

LogLevel:   The level of detail that is logged.

This setting controls the level of detail that is logged through the Log event. Possible values are:

0 (None) No events are logged.
1 (Info - default) Informational events are logged.
2 (Verbose) Detailed data is logged.
3 (Debug) Debug data is logged.

The default log level, Info, provides information when most BLE operations begin and end, and should be sufficient to get a good idea of what the component is doing at a high level.

The Verbose log level adds a few extra operation timing messages, and adds more detail to some messages logged at the Info level.

The Debug log level causes the component to output as much information as possible about what it is doing at all times. All BLE communications, even those which are typically abstracted away by the API, are logged in full detail. Typically the additional information added by this log level is not helpful to the end user, and would only be necessary to capture if you wish to report an issue to the support team.

Base Config Settings

BuildInfo:   Information about the product's build.

When queried, this setting will return a string containing information about the product's build.

CodePage:   The system code page used for Unicode to Multibyte translations.

The default code page is Unicode UTF-8 (65001).

The following is a list of valid code page identifiers:

IdentifierName
037IBM EBCDIC - U.S./Canada
437OEM - United States
500IBM EBCDIC - International
708Arabic - ASMO 708
709Arabic - ASMO 449+, BCON V4
710Arabic - Transparent Arabic
720Arabic - Transparent ASMO
737OEM - Greek (formerly 437G)
775OEM - Baltic
850OEM - Multilingual Latin I
852OEM - Latin II
855OEM - Cyrillic (primarily Russian)
857OEM - Turkish
858OEM - Multilingual Latin I + Euro symbol
860OEM - Portuguese
861OEM - Icelandic
862OEM - Hebrew
863OEM - Canadian-French
864OEM - Arabic
865OEM - Nordic
866OEM - Russian
869OEM - Modern Greek
870IBM EBCDIC - Multilingual/ROECE (Latin-2)
874ANSI/OEM - Thai (same as 28605, ISO 8859-15)
875IBM EBCDIC - Modern Greek
932ANSI/OEM - Japanese, Shift-JIS
936ANSI/OEM - Simplified Chinese (PRC, Singapore)
949ANSI/OEM - Korean (Unified Hangul Code)
950ANSI/OEM - Traditional Chinese (Taiwan; Hong Kong SAR, PRC)
1026IBM EBCDIC - Turkish (Latin-5)
1047IBM EBCDIC - Latin 1/Open System
1140IBM EBCDIC - U.S./Canada (037 + Euro symbol)
1141IBM EBCDIC - Germany (20273 + Euro symbol)
1142IBM EBCDIC - Denmark/Norway (20277 + Euro symbol)
1143IBM EBCDIC - Finland/Sweden (20278 + Euro symbol)
1144IBM EBCDIC - Italy (20280 + Euro symbol)
1145IBM EBCDIC - Latin America/Spain (20284 + Euro symbol)
1146IBM EBCDIC - United Kingdom (20285 + Euro symbol)
1147IBM EBCDIC - France (20297 + Euro symbol)
1148IBM EBCDIC - International (500 + Euro symbol)
1149IBM EBCDIC - Icelandic (20871 + Euro symbol)
1200Unicode UCS-2 Little-Endian (BMP of ISO 10646)
1201Unicode UCS-2 Big-Endian
1250ANSI - Central European
1251ANSI - Cyrillic
1252ANSI - Latin I
1253ANSI - Greek
1254ANSI - Turkish
1255ANSI - Hebrew
1256ANSI - Arabic
1257ANSI - Baltic
1258ANSI/OEM - Vietnamese
1361Korean (Johab)
10000MAC - Roman
10001MAC - Japanese
10002MAC - Traditional Chinese (Big5)
10003MAC - Korean
10004MAC - Arabic
10005MAC - Hebrew
10006MAC - Greek I
10007MAC - Cyrillic
10008MAC - Simplified Chinese (GB 2312)
10010MAC - Romania
10017MAC - Ukraine
10021MAC - Thai
10029MAC - Latin II
10079MAC - Icelandic
10081MAC - Turkish
10082MAC - Croatia
12000Unicode UCS-4 Little-Endian
12001Unicode UCS-4 Big-Endian
20000CNS - Taiwan
20001TCA - Taiwan
20002Eten - Taiwan
20003IBM5550 - Taiwan
20004TeleText - Taiwan
20005Wang - Taiwan
20105IA5 IRV International Alphabet No. 5 (7-bit)
20106IA5 German (7-bit)
20107IA5 Swedish (7-bit)
20108IA5 Norwegian (7-bit)
20127US-ASCII (7-bit)
20261T.61
20269ISO 6937 Non-Spacing Accent
20273IBM EBCDIC - Germany
20277IBM EBCDIC - Denmark/Norway
20278IBM EBCDIC - Finland/Sweden
20280IBM EBCDIC - Italy
20284IBM EBCDIC - Latin America/Spain
20285IBM EBCDIC - United Kingdom
20290IBM EBCDIC - Japanese Katakana Extended
20297IBM EBCDIC - France
20420IBM EBCDIC - Arabic
20423IBM EBCDIC - Greek
20424IBM EBCDIC - Hebrew
20833IBM EBCDIC - Korean Extended
20838IBM EBCDIC - Thai
20866Russian - KOI8-R
20871IBM EBCDIC - Icelandic
20880IBM EBCDIC - Cyrillic (Russian)
20905IBM EBCDIC - Turkish
20924IBM EBCDIC - Latin-1/Open System (1047 + Euro symbol)
20932JIS X 0208-1990 & 0121-1990
20936Simplified Chinese (GB2312)
21025IBM EBCDIC - Cyrillic (Serbian, Bulgarian)
21027Extended Alpha Lowercase
21866Ukrainian (KOI8-U)
28591ISO 8859-1 Latin I
28592ISO 8859-2 Central Europe
28593ISO 8859-3 Latin 3
28594ISO 8859-4 Baltic
28595ISO 8859-5 Cyrillic
28596ISO 8859-6 Arabic
28597ISO 8859-7 Greek
28598ISO 8859-8 Hebrew
28599ISO 8859-9 Latin 5
28605ISO 8859-15 Latin 9
29001Europa 3
38598ISO 8859-8 Hebrew
50220ISO 2022 Japanese with no halfwidth Katakana
50221ISO 2022 Japanese with halfwidth Katakana
50222ISO 2022 Japanese JIS X 0201-1989
50225ISO 2022 Korean
50227ISO 2022 Simplified Chinese
50229ISO 2022 Traditional Chinese
50930Japanese (Katakana) Extended
50931US/Canada and Japanese
50933Korean Extended and Korean
50935Simplified Chinese Extended and Simplified Chinese
50936Simplified Chinese
50937US/Canada and Traditional Chinese
50939Japanese (Latin) Extended and Japanese
51932EUC - Japanese
51936EUC - Simplified Chinese
51949EUC - Korean
51950EUC - Traditional Chinese
52936HZ-GB2312 Simplified Chinese
54936Windows XP: GB18030 Simplified Chinese (4 Byte)
57002ISCII Devanagari
57003ISCII Bengali
57004ISCII Tamil
57005ISCII Telugu
57006ISCII Assamese
57007ISCII Oriya
57008ISCII Kannada
57009ISCII Malayalam
57010ISCII Gujarati
57011ISCII Punjabi
65000Unicode UTF-7
65001Unicode UTF-8
The following is a list of valid code page identifiers for Mac OS only:
IdentifierName
1ASCII
2NEXTSTEP
3JapaneseEUC
4UTF8
5ISOLatin1
6Symbol
7NonLossyASCII
8ShiftJIS
9ISOLatin2
10Unicode
11WindowsCP1251
12WindowsCP1252
13WindowsCP1253
14WindowsCP1254
15WindowsCP1250
21ISO2022JP
30MacOSRoman
10UTF16String
0x90000100UTF16BigEndian
0x94000100UTF16LittleEndian
0x8c000100UTF32String
0x98000100UTF32BigEndian
0x9c000100UTF32LittleEndian
65536Proprietary

LicenseInfo:   Information about the current license.

When queried, this setting will return a string containing information about the license this instance of a component is using. It will return the following information:

  • Product: The product the license is for.
  • Product Key: The key the license was generated from.
  • License Source: Where the license was found (e.g., RuntimeLicense, License File).
  • License Type: The type of license installed (e.g., Royalty Free, Single Server).
  • Last Valid Build: The last valid build number for which the license will work.
MaskSensitiveData:   Whether sensitive data is masked in log messages.

In certain circumstances it may be beneficial to mask sensitive data, like passwords, in log messages. Set this to True to mask sensitive data. The default is True.

UseInternalSecurityAPI:   Whether or not to use the system security libraries or an internal implementation.

When set to False, the component will use the system security libraries by default to perform cryptographic functions where applicable.

Setting this configuration setting to True tells the component to use the internal implementation instead of using the system security libraries.

This setting is set to False by default on all platforms.

Trappable Errors (BLEServer Component)

BLEServer Errors

600   Invalid UUID.
601   Invalid Id.
602   Action not allowed. See error message for more details.
603   Scanning error. See error message for more details.
604   Connection error. See error message for more details.
605   Must be connected to a device to perform the requested action.
606   Error during communication. See error message for more details.
607   Device unreachable during communication attempt.
608   Error during discovery. See error message for more details.
609   Component detected a cycle of included services.
610   General read error. See error message for more details.
611   General write error. See error message for more details.
612   Application-specific protocol error. This error code indicates that a protocol error code in the range 0x80-0x9F was returned during a BLE communication. Such error codes are reserved for applications to use as they see fit. Refer to the documentation of your remote device for more information.
613   Bluetooth low energy not supported.
701   Invalid Handle: The attribute handle given was not valid on this server.
702   Read Not Permitted: The attribute cannot be read due to its permissions.
703   Write Not Permitted: The attribute cannot be written due to its permissions.
704   Invalid PDU: The attribute PDU was invalid.
705   Insufficient Authentication: The attribute requires authentication before it can be read or written.
706   Request Not Supported: Attribute server does not support the request received from the client.
707   Invalid Offset: Offset specified was past the end of the attribute's value.
708   Insufficient Authorization: The attribute requires authorization before it can be read or written.
709   Prepare Queue Full: Too many prepare writes have been queued.
710   Attribute Not Found: No attribute found within the given attribute handle range.
711   Attribute Not Long: The attribute cannot be read or written using the Read Blob Request.
712   Insufficient Encryption Key Size: The Encryption Key Size used for encrypting this link is insufficient.
713   Invalid Attribute Value Length: The attribute value length is invalid for the operation.
714   Unlikely Error: The attribute request that was requested has encountered an error that was unlikely, and therefore could not be completed as requested.
715   Insufficient Encryption: The attribute requires encryption before it can be read or written.
716   Unsupported Group Type: The attribute type is not a supported grouping attribute as defined by a higher layer specification.
717   Insufficient Resources: Insufficient Resources to complete the request.
952   Write Request Rejected: A requested write operation could not be fulfilled for reasons other than its permissions.
953   Client Characteristic Configuration Descriptor (CCCD) Improperly Configured: The CCCD is not configured according to the requirements of the profile or service.
954   Procedure Already in Progress: A profile or service request cannot be serviced because a previously triggered operation is still in progress.
955   Out of Range: An attribute value is out of range (as defined by a profile or service specification).