User's Manual

The effect of command “PS” could only be shown after a valid “PC” command and
after power cycle.
Command “PS” expects one parameter, which is 128-bit UUID for private service.
The UUID generation process is the same as that of private characteristics. Please
refer to Wikipedia for details
(http://en.wikipedia.org/wiki/Universally_unique_identifier).
Example: PS,010203040506070809000A0B0C0D0E0F
// Define a private service with UUID 0x010203040506070809000A0B0C0D0E0F
3.3.4.3 PZ
Command “PZ” clears all settings of private service and private characteristics. A
power cycle is required afterwards to make the changes effective.
Example: PZ // Clear all private service and characteristics
// settings.
3.3.5 Microchip MLDP Commands
3.3.5.1 Microchip MLDP Profile
Built on top of BTLE GATT, Microchip developed private service MLDP to simulate
operation of Serial Port Profile (SPP).
To enable MLDP, the MLDP bit has to be enabled (Check section 3.2.1.12 Command
“SR”).
To run MLDP between two RN4020 modules, both devices must have MDLP feature
enabled. RN4020 could also simulate SPP with any third-party BTLE device (such as
an iPhone) as client role, which could support private service. MLDP on RN4020 is
implemented as a private service. The third-party client BTLE device needs to
enable notification or indication once connection is established. Third party BTLE
device will use “write” operation to send data stream and receive data stream by
notification or indication.
The throughput of MDLP communication is highly depends on the connection
parameters, which decides the frequency of communication between central and
peripheral (Check command “T” in section 3.3.2.11). High MLDP throughput
requires frequent communications between two devices, therefore consumes more