bluetoothLENode
Description
Use the bluetoothLENode object to create and configure a
Bluetooth® low energy (LE) node. This feature also requires the Wireless Network
Toolbox™ product.
Creation
Syntax
Description
creates a default
Bluetooth LE node object with a LENode = bluetoothLENode"peripheral" role.
creates a Bluetooth LE node object with the Role
property set to LENode = bluetoothLENode(role)role.
sets writable properties
using one or more name-value arguments, in addition to any combination of input arguments
from previous syntaxes. For example, LENode = bluetoothLENode(___,Name=Value)TransmitterPower=0 sets the
transmitter power of the Bluetooth LE Node to 0 dBm.
As long as the Role property is not
"broadcaster-observer", you can use this syntax to generate a row
vector of Bluetooth LE node objects by specifying the Position property.
Name-Value Arguments
Specify optional pairs of arguments as
Name1=Value1,...,NameN=ValueN, where Name is
the argument name and Value is the corresponding value.
Name-value arguments must appear after other arguments, but the order of the
pairs does not matter.
Example: bluetoothLENode(InterferenceModeling="non-overlapping-adjacent-channel")
sets the type of interference modeling to
"non-overlapping-adjacent-channel".
Type of interference modeling, specified as
"overlapping-adjacent-channel" or
"non-overlapping-adjacent-channel".
"overlapping-adjacent-channel"— The object considers signals overlapping in time and frequency to be interference. In this figure, fS, fE, and fC are the starting, ending, and center frequencies of the signal of interference (SOI), respectively."non-overlapping-adjacent-channel"— In addition to signals that satisfy the conditions described under"overlapping-adjacent-channel", the object considers signals that overlap with the SOI in time and with the interval [fS – fD, fE + fD] in frequency to be interference. fS, fE, and fC are the starting, ending, and center frequencies of the SOI, respectively. fD is the value of theMaxInterferenceOffsetproperty.
This name-value argument sets the InterferenceModeling property.
Data Types: char | string
Maximum frequency offset for determining signal interference, specified as a
nonnegative scalar. Units are in Hz. This property specifies the offset between the
edge of the SOI frequency and the edge of the interfering signal. If you specify
this property as Inf, the object considers all the signals that
overlap in time, regardless of their frequency, to be interference. If you specify
this property as a finite nonnegative scalar, the object considers all the signals
overlapping in time and with frequency in the range [(f1 –
),
(f2 +
MaxInterferenceOffset)], to be
interference.MaxInterferenceOffset
This name-value argument sets the MaxInterferenceOffset property.
Dependencies
To use this argument, you must specify the InterferenceModeling argument as
"non-overlapping-adjacent-channel".
Data Types: double
Properties
This property is read-only.
Role of the Bluetooth LE node, specified as one of these values.
Role Value | Description |
|---|---|
"central" | Simulate Bluetooth LE piconet (data and audio) |
"peripheral" | Simulate Bluetooth LE piconet (data and audio) |
"broadcaster" | Simulate Bluetooth LE node scenario with periodic or legacy advertisements |
"observer" | Simulate Bluetooth LE node scenario with periodic advertisements |
"isochronous-broadcaster" | Simulate Bluetooth LE broadcast audio network |
"synchronized-receiver" | Simulate Bluetooth LE broadcast audio network |
"broadcaster-observer" | Simulate Bluetooth LE mesh network |
The role argument sets the value of this property.
Data Types: char | string
Node Position in 3-D Cartesian coordinates, specified as a numeric
N-by-3 matrix. N specifies the number of
Bluetooth LE nodes. This value specifies the position of the node in Cartesian x-, y-,
and z-coordinates. When you specify this value as a matrix with N >
1, you create a 1-by-N vector of the bluetoothLENode
object. Units are in meters. Note that if the Role
value is "broadcaster-observer" and you specify the MeshConfig property to create mesh nodes, you can only create one node at
a time, and N must be 1.
Data Types: double
Node name, specified as a character vector, string scalar, string vector, or cell
array of character vectors. The default format of this value is
"NodeN", where N is the
node identifier specified by the ID
property. When you specify the Position
property to create a row vector of the bluetoothNode objects, you can
simultaneously name each node in the vector by providing this value as a string vector
or a cell array of character vectors. If you specify this value as a vector that exceeds
the number of nodes, the object does not use the surplus names. Conversely, if you
specify this value as a vector that is smaller than the number of nodes, the object
assigns default names to the additional nodes.
Note
Since R2026a, you can set this property only when you create the object. After creation, the property is read-only. In releases R2025b and earlier, after creating the object, you can set the value of this property for one Bluetooth LE node object at a time.
Data Types: char | string
Signal transmission power, specified as a scalar in the range [-20, 20]. Specify this value in dBm. This value specifies the average power that the transmitter applies to the Bluetooth LE signal before sending it to the antenna.
Data Types: double
Transmitter antenna gain, specified as a finite numeric scalar. Specify this value in dB.
Data Types: double
Note
The Bluetooth LE node transmits each packet at a total power equal to the sum of its
TransmitPower and TransmitGain
properties.
Receiver antenna gain, specified as a finite numeric scalar. Specify this value in dB.
Data Types: double
Receiver sensitivity, specified as a finite numeric scalar. Specify this value in dBm. This property sets the minimum received power to detect the incoming signal. If the received power of an incoming signal is below this value, the node considers the signal invalid.
Data Types: double
Noise figure, specified as a finite nonnegative numeric scalar. Specify this value in dB. Use this value to add thermal noise to the received signal.
Data Types: double
Periodic interval between consecutive advertising events, specified as a scalar in the range [0.02, 10485.759375]. Specify this value in seconds. You must set this value as an integer multiple of 0.625 milliseconds. This value specifies the interval of an advertising event during which the transmission of advertising packets occurs.
Data Types: double
Random selection of advertising channels, specified as 0
(false) or 1 (true). To model
the random selection of advertising channels, set this value to
true.
Data Types: logical
Interval between consecutive scan events, specified as a scalar in the range [0.0025, 40.960]. Specify this value in seconds. You must set this value as an integer multiple of 0.625 milliseconds. This value specifies the interval in which the node listens for the advertising packets.
Data Types: double
Bluetooth mesh profile configuration parameters, specified as a bluetoothMeshProfileConfig object.
Dependencies
To enable this property, set the Role
property to "broadcaster-observer".
Since R2026a
Bluetooth LE generic access profile (GAP) configuration parameters for the
connection procedure, specified as a bluetoothLEGAPConfig object.
This property is read-only.
Type of interference modeling, specified as
"overlapping-adjacent-channel" or
"non-overlapping-adjacent-channel".
"overlapping-adjacent-channel"— The object considers signals overlapping in time and frequency to be interference. In this figure, fS, fE, and fC are the starting, ending, and center frequencies of the signal of interference (SOI), respectively."non-overlapping-adjacent-channel"— In addition to signals that satisfy the conditions described under"overlapping-adjacent-channel", the object considers signals that overlap with the SOI in time and with the interval [fS – fD, fE + fD] in frequency to be interference. fS, fE, and fC are the starting, ending, and center frequencies of the SOI, respectively. fD is the value of theMaxInterferenceOffsetproperty.
Data Types: char | string
This property is read-only.
Maximum frequency offset for determining signal interference, specified as a
nonnegative scalar. Units are in Hz. This property specifies the offset between the edge
of the SOI frequency and the edge of the interfering signal. If you specify this
property as Inf, the object considers all the signals that overlap in
time, regardless of their frequency, to be interference. If you specify this property as
a finite nonnegative scalar, the object considers all the signals overlapping in time
and with frequency in the range [(f1 –
),
(f2 +
MaxInterferenceOffset)], to be
interference.MaxInterferenceOffset
Dependencies
To enable this property, set the InterferenceModeling property to
"non-overlapping-adjacent-channel".
Data Types: double
This property is read-only.
Node identifier, returned as an integer. This value specifies a unique identifier for the node in the simulation.
Note
If you create and store the Bluetooth LE nodes in an uninitialized matrix, the IDs that this property allocates to the nodes can be nonsequential because of the memory allocation to the object in the matrix. For more information about MATLAB memory allocation, see How MATLAB Allocates Memory.
Data Types: double
This property is read-only.
Bluetooth LE LL connection configuration parameters, returned as a bluetoothLEConnectionConfig object.
Dependencies
To enable this property, set the Role
property to "central" or "peripheral".
This property is read-only.
Connected isochronous stream (CIS) connection configuration object, specified as a
bluetoothLECISConfig object or a vector of objects of the type
bluetoothLECISConfig. To configure multiple CIS connections, set this
property as a vector of objects of the type bluetoothLECISConfig. Note
that you can configure a maximum of 31 CIS connections.
Dependencies
To enable this property, set the Role
property to "central" or "peripheral".
This property is read-only.
Periodic advertising configuration object, returned as an object or a vector of
objects of the type bluetoothLEPeriodicAdvConfig. This property specifies the synchronization
information shared between the Broadcaster and Observer as part of the periodic
advertisements establishment process.
Dependencies
To enable this property, set the Role
property to "broadcaster" or "observer".
This property is read-only.
Bluetooth LE BIG configuration parameters, returned as a bluetoothLEBIGConfig object.
Dependencies
To enable this property, set the Role
property to "isochronous-broadcaster" or
"synchronized-receiver".
This property is read-only.
Friendship configuration object for Friend and LPN, returned as a bluetoothMeshFriendshipConfig object.
Dependencies
To enable this property, set the Role
property to "broadcaster-observer".
Since R2026a
Node mobility model, represented as an object of a subclass of
wnet.Mobility class.
Note
Only the bluetoothLENode subclass can set the
Mobility property in its constructor or methods. The addMobility object function of the bluetoothLENode
object adds a mobility model to Bluetooth LE nodes.
Since R2026a
This property is read-only.
Node velocity in 3-D Cartesian coordinates, represented as a three-element numeric row vector. The units are in meters per second.
Data Types: double
Object Functions
addMobility | Add random waypoint mobility model to Bluetooth LE node |
addTrafficSource | Add data traffic source to Bluetooth LE node |
updateChannelList | Provide updated channel list to Bluetooth LE node |
kpi | Returns key performance indicators (KPIs) for Bluetooth LE nodes |
registerEventCallback | Register callback for event from Bluetooth LE node |
statistics | Get statistics of Bluetooth LE node |
Examples
This example enables you to:
Create and configure a Bluetooth LE piconet with Central and Peripheral nodes.
Create and configure a link layer (LL) connection between Central and Peripheral nodes.
Add application traffic from the Central to Peripheral nodes.
Create a custom channel, and plug it into the wireless network simulator.
Simulate Bluetooth LE network and retrieve the statistics of the Central and Peripheral nodes.
Create a wireless network simulator.
networkSimulator = wirelessNetworkSimulator.init;
Create a Bluetooth LE node, specifying the role as "central". Specify the name and position of the node.
centralNode = bluetoothLENode("central",Name="CentralNode"); centralNode.Position = [0 0 0]; % In x-, y-, and z-coordinates in meters
Create a Bluetooth LE node, specifying the role as "peripheral". Specify the name and position of the node.
peripheralNode = bluetoothLENode("peripheral",Name="PeripheralNode"); peripheralNode.Position = [10 0 10] % In x-, y-, and z-coordinates in meters
peripheralNode =
bluetoothLENode with properties:
TransmitterPower: 20
TransmitterGain: 0
ReceiverGain: 0
ReceiverSensitivity: -100
NoiseFigure: 0
InterferenceModeling: "overlapping-adjacent-channel"
Role: "peripheral"
ConnectionConfig: [0×0 bluetoothLEConnectionConfig]
CISConfig: [0×0 bluetoothLECISConfig]
Position: [10 0 10]
Name: "PeripheralNode"
Mobility: []
Read-only properties:
ID: 2
Velocity: [0 0 0]
Add a random waypoint mobility model to the Bluetooth peripheral node. Set the shape of the node's mobility area to "circle".
addMobility(peripheralNode,BoundaryShape="circle",RefreshInterval=0.1)Create a default Bluetooth LE configuration object to share the LL connection between the Central and Peripheral nodes.
cfgConnection = bluetoothLEConnectionConfig;
Specify the connection interval and connection offset. Throughout the simulation, the object establishes LL connection events for the duration of each connection interval. The connection offset is from the beginning of the connection interval.
cfgConnection.ConnectionInterval = 0.01; % In seconds cfgConnection.ConnectionOffset = 0; % In seconds
Specify the active communication period after the connection event is established between the Central and Peripheral nodes.
cfgConnection.ActivePeriod = 0.01 % In secondscfgConnection =
bluetoothLEConnectionConfig with properties:
ConnectionInterval: 0.0100
AccessAddress: "5DA44270"
UsedChannels: [0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36]
Algorithm: 1
HopIncrement: 5
CRCInitialization: "012345"
SupervisionTimeout: 1
PHYMode: "LE1M"
InstantOffset: 6
ConnectionOffset: 0
ActivePeriod: 0.0100
MaxPDU: 251
TIFS: 1.5000e-04
TMCES: 1.5000e-04
Configure the connection between Central and Peripheral nodes by using the configureConnection object function of the bluetoothLEConnectionConfig object.
configureConnection(cfgConnection,centralNode,peripheralNode);
Create a networkTrafficOnOff (Wireless Network Toolbox) object to generate an On-Off application traffic pattern. Specify the data rate in kb/s and the packet size in bytes. Enable packet generation to generate an application packet with a payload.
traffic = networkTrafficOnOff(DataRate=100,PacketSize=10);
Add application traffic from the Central to the Peripheral node by using the addTrafficSource object function.
addTrafficSource(centralNode,traffic,DestinationNode=peripheralNode);
Create a Bluetooth LE network consisting of a Central and a Peripheral node.
nodes = {centralNode peripheralNode};Add the Central and Peripheral nodes to the wireless network simulator.
addNodes(networkSimulator,nodes)
Add the custom channel to the wireless network simulator.
addChannelModel(networkSimulator,@addImpairment);
Set the simulation time in seconds and run the simulation.
simulationTime = 0.5; run(networkSimulator,simulationTime)
Retrieve application, link layer (LL), and physical layer (PHY) statistics corresponding to the Central and Peripheral nodes. For more information about the statistics, see Bluetooth LE Node Statistics.
centralStats = statistics(centralNode)
centralStats = struct with fields:
Name: "CentralNode"
ID: 1
App: [1×1 struct]
LL: [1×1 struct]
PHY: [1×1 struct]
peripheralStats = statistics(peripheralNode)
peripheralStats = struct with fields:
Name: "PeripheralNode"
ID: 2
App: [1×1 struct]
LL: [1×1 struct]
PHY: [1×1 struct]
Follow these steps to create a custom channel that models Bluetooth path loss for an industrial scenario.
Create a custom function with this syntax:
rxData = customFcnName(rxInfo,txData). TherxInfoinput specifies the receiver node information as a structure, and thetxDatainput specifies the transmitted packets as a structure. The simulator automatically passes information about the receiver node and the packets transmitted by a transmitter node as inputs to the custom function. For more information about creating custom channel, see theaddChannelModel(Wireless Network Toolbox) object function.Use the
bluetoothPathLossConfigobject to set path loss configuration parameters for an industrial scenario.Calculate path loss between the Central and Peripheral nodes using the
bluetoothPathLossfunction. Specify the transmitter and receiver positions.Apply path loss to the transmitted packets.
function rxData = addImpairment(rxInfo,txData) pathlossCfg = bluetoothPathLossConfig(Environment="Industrial"); % Apply path loss and update output signal rxData = txData; % Calculate the distance between transmitter and receiver in meters distance = norm(rxData.TransmitterPosition - rxInfo.Position); pathloss = bluetoothPathLoss(distance,pathlossCfg); rxData.Power = rxData.Power-pathloss; % In dBm scale = 10.^(-pathloss/20); [numSamples,~] = size(rxData.Data); rxData.Data(1:numSamples,:) = rxData.Data(1:numSamples,:)*scale; end
More About
Events are occurrences that the object triggers in response to an action such as a change in a property value or a user interaction with the application program. Listeners execute functions when notified that the event of interest occurs. Listeners respond by executing a callback function that has at least two input arguments defined, the event source object handle and the event data. For more information about events and listeners, see Overview Events and Listeners and Event and Listener Concepts.
The bluetoothLENode object defines these events.
PacketTransmissionStartedWhen a node starts transmitting a packet, the object triggers the
PacketTransmissionStarted event. This event passes an event notification
and this structure as event data to the registered callback.
| Field | Value | Description |
|---|---|---|
NodeName | character vector | Node name, specifying the Name property of the Bluetooth LE node that starts the packet
transmission |
NodeID | scalar positive integer | Unique node identifier, specifying the ID property of the Bluetooth LE node that starts the packet transmission |
CurrentTime | scalar positive integer | Current time of the simulation in seconds |
PDU | binary column vector | Protocol data unit (PDU) bits to be transmitted |
AccessAddress | character vector representing a 4-octet hexadecimal number | Access address of the Bluetooth LE packet |
ChannelIndex | integer in the range [0, 39] | Channel index for transmission |
PHYMode |
| Physical layer (PHY) transmission mode |
TransmittedPower | scalar | Transmit power in dBm |
PacketDuration | scalar positive integer | Packet duration in seconds. |
PacketReceptionEndedWhen the reception of a packet ends, the object triggers the
PacketReceptionEnded event. This event passes an event notification and
this structure as event data to the registered callback.
| Field | Value | Description |
|---|---|---|
NodeName | character vector | Node name, specifying the Name property of the Bluetooth LE node that receives the
packet |
NodeID | scalar positive integer | Unique node identifier, specifying the ID property of the Bluetooth LE node that receives the packet |
CurrentTime | scalar positive integer | Current time of the simulation in seconds |
SourceNode | character vector | Name of the source node, specifying the Name property of the Bluetooth LE node that starts the packet
transmission |
SourceID | scalar positive integer | Unique node identifier, specifying the ID property of the Bluetooth LE node that starts the packet transmission |
SuccessStatus | logical scalar | Flag indicating the success status of the packet |
PDU | binary column vector | PDU bits received |
AccessAddress | character vector representing a 4-octet hexadecimal number | Access address of the packet |
ChannelIndex | integer in the range [0, 39] | Channel index for reception |
PHYMode |
| PHY reception mode |
PacketDuration | positive scalar or | Duration of the received packet in seconds |
ReceivedPower | scalar | Received power in dBm |
SINR | scalar | Signal-to-interference plus noise ratio in dB |
ChannelMapUpdatedWhen the node starts using the updated channel map of the link, the object triggers
the ChannelMapUpdated event. This event passes an event notification and
this structure as event data to the registered callback.
| Field | Value | Description |
|---|---|---|
NodeName | character vector | Node name, specifying the Name property of the Bluetooth LE node at which the channel map is
updated |
NodeID | scalar positive integer | Unique node identifier, specifying the ID property of the Bluetooth LE node at which the channel map is updated |
CurrentTime | scalar positive integer | Current time of the simulation in seconds |
PeerNode | character vector | Name of the peer node, specifying the Name property of the Bluetooth LE at which the channel map is
updated |
PeerID | scalar positive integer | Unique node identifier of the peer node, specifying the ID property of the Bluetooth LE node at which the channel map is updated |
UpdatedChannelList | vector of integers in the range [0, 36] | List of good channels |
AppDataReceivedWhen there is data for the application from the node, the object triggers the
AppDataReceived event. This event passes an event notification and this
structure as event data to the registered callback.
| Field | Value | Description |
|---|---|---|
NodeName | character vector | Node name, specifying the Name property of the Bluetooth LE node at which the application
data is destined |
NodeID | scalar positive integer | Unique node identifier, specifying the ID property of the Bluetooth LE node at which the application data is destined |
CurrentTime | scalar positive integer | Current time of the simulation in seconds |
SourceNode | character vector | Name of the source node, specifying the Name property of the Bluetooth LE node whose application data is
received. |
ReceivedData | vector of integers in the range [0, 255] | Received application data in decimal bytes |
MeshAppDataReceivedWhen application data is received for a mesh node, the object triggers the
MeshAppDataReceived event. This event passes an event notification and
this structure as event data to the registered callback.
| Field | Value | Description |
|---|---|---|
NodeName | character vector | Node name, specifying the Name property of the Bluetooth LE node at which the application
data is destined |
NodeID | scalar positive integer | Unique node identifier, specifying the ID property of the Bluetooth LE node at which the application data is destined |
CurrentTime | scalar positive integer | Current time of the simulation in seconds |
Message | vector of integers in the range [0, 255] | Received access message |
SourceAddress | character vector representing a 2-octet hexadecimal number | Source address of the message, specifying the Name property of the Bluetooth LE node that is the destination for
the application data |
DestinationAddress | character vector representing a 2-octet hexadecimal number | Destination address of the message, specifying the Name property of the Bluetooth LE node at which the application
data is destined |
ConnectionEventEndedWhen the connection event ends, the object triggers the
ConnectionEventEnded event. This event passes an event notification and
this structure as event data to the registered callback.
| Field | Value | Description |
|---|---|---|
NodeName | character vector | Node name, specifying the Name property of the Bluetooth LE node at which the connection
event ends |
NodeID | scalar positive integer | Unique node identifier, specifying the ID property of the Bluetooth LE node at which the connection event ends |
CurrentTime | scalar positive integer | Current time of the simulation in seconds |
Counter | scalar positive integer in the range [0, 65535] | Current connection event counter |
TransmittedPackets | scalar nonnegative integer | Number of transmitted packets in the connection event |
ReceivedPackets | scalar nonnegative integer | Number of received packets in the connection event |
CRCFailedPackets | scalar nonnegative integer | Number of received packets with cyclic redundancy check (CRC) failure |
References
[1] Bluetooth Technology Website. “Bluetooth Technology Website | The Official Website of Bluetooth Technology.” Accessed January 10, 2026. https://www.bluetooth.com/.
[2] Bluetooth Core Specifications Working Group. "Bluetooth Core Specification" v6.1. https://www.bluetooth.com/specifications/specs/core-specification-6-1/.
Version History
Introduced in R2022aStarting in R2026a, this feature is available in Bluetooth Toolbox and also requires a Wireless Network Toolbox license. In prior releases, the feature is available through the Communications Toolbox™ Wireless Network Simulation Library add-on.
The property will be removed in
a future release. To retrieve the number of Peripheral nodes associated with the Central
node, use the PeripheralCountConnectionConfig property instead. This table shows the change in syntax after
this update.
| Syntax Before This Update | Syntax After This Update |
|---|---|
numPeripherals = node.PeripheralCount |
numPeripherals = numel(node.ConnectionConfig) |
The property will be removed in a
future release. To restrict the packet reception range of the node, use the ReceiverRangeaddChannelModel (Wireless Network Toolbox)
object function of the wirelessNetworkSimulator (Wireless Network Toolbox) object instead.
The property will be removed in a
future release. To read packets scheduled for the transmission by the node, use the
TransmitBufferpullTransmittedPacket (Wireless Network Toolbox) object function of the wnet.Node (Wireless Network Toolbox) object.
Note that the pullTransmittedPacket object function also empties the
packet from the transmission buffer. This table shows the change in syntax after this
update.
| Syntax Before This Update | Syntax After This Update |
|---|---|
txData = node.TransmitBuffer |
txData = pullTransmittedData(nodeObj) |
To configure the InterferenceModeling and
MaxInterferenceOffset properties, you must now specify the InterferenceModeling and MaxInterferenceOffset name-value arguments, respectively, at object creation.
In prior releases, you can specify these properties after object creation by using dot
notation.
The new GAPConfig
property configures the bluetoothLENode object with GAP configuration
parameters and enables you to establish new asynchronous connection oriented (ACL)
connections while maintaining existing connections between the Central and Peripheral
nodes.
Since R2026a, you can set the value of the Name property only when
you create the object. After creation, the property is read-only. In releases R2025b and
earlier, after creating the object, you can set the value of this property for one Bluetooth
LE node object at a time.
The property has been
removed. Use the new InterferenceFidelityInterferenceModeling property
instead. For code that uses the default interference modeling, you do not need to make any
changes as the object manages the transition internally. However, if you have explicitly set
the InterferenceFidelity property, you must change the property name
from InterferenceFidelity to InterferenceModeling,
and modify the value from 0 or 1 to
"overlapping-adjacent-channel" or
"non-overlapping-adjacent-channel", respectively. This table shows the
change in syntax after this update.
| Syntax Before This Update | Syntax After This Update |
|---|---|
bluetoothLENode(“central”,InterferenceFidelity=0) |
bluetoothLENode(“central”,InterferenceModeling=”overlapping-adjacent-channel”) |
bluetoothLENode(“peripheral”,InterferenceFidelity=1) |
bluetoothLENode(“peripheral”,InterferenceModeling=”non-overlapping-adjacent-channel”) |
The property issues a
warning that it will be removed in a future release. Use the new InterferenceFidelityInterferenceModeling property
instead. For code that uses the default interference modeling, you do not need to make any
changes as the object manages the transition internally. However, if you have explicitly set
the InterferenceFidelity property, you must change the property name
from InterferenceFidelity to InterferenceModeling,
and modify the value from 0 or 1 to
"overlapping-adjacent-channel" or
"non-overlapping-adjacent-channel", respectively. This table shows the
change in syntax after this update.
| Syntax Before This Update | Syntax After This Update |
|---|---|
bluetoothLENode(“central”,InterferenceFidelity=0) |
bluetoothLENode(“central”,InterferenceModeling=”overlapping-adjacent-channel”) |
bluetoothLENode(“peripheral”,InterferenceFidelity=1) |
bluetoothLENode(“peripheral”,InterferenceModeling=”non-overlapping-adjacent-channel”) |
These two new properties of the bluetoothLENode object enable you to
model interference by considering signals overlapping in the time and frequency domains.
InterferenceModeling— Use this property to set the type of interference modeling.— Use this property to specify the offset between the edge of the SOI frequency and the edge of the interfering signal.MaxInterferenceOffset
The property will be
removed in a future release. Use the new InterferenceFidelityInterferenceModeling property
instead. For code that uses the default interference modeling, you do not need to make any
changes as the object manages the transition internally. However, if you have explicitly set
the InterferenceFidelity property, you must change the property name
from InterferenceFidelity to InterferenceModeling,
and modify the value from 0 or 1 to
"overlapping-adjacent-channel" or
"non-overlapping-adjacent-channel", respectively. This table shows the
change in syntax after this update.
| Syntax Before This Update | Syntax After This Update |
|---|---|
bluetoothLENode(“central”,InterferenceFidelity=0) |
bluetoothLENode(“central”,InterferenceModeling=”overlapping-adjacent-channel”) |
bluetoothLENode(“peripheral”,InterferenceFidelity=1) |
bluetoothLENode(“peripheral”,InterferenceModeling=”non-overlapping-adjacent-channel”) |
The bluetoothLENode object now supports adding a random waypoint
mobility model to Bluetooth LE nodes through the addMobility object function.
See Also
Objects
wirelessNetworkSimulator(Wireless Network Toolbox) |bluetoothNode|bluetoothLEGAPConfig|bluetoothLEConnectionConfig|bluetoothLEBIGConfig|bluetoothMeshProfileConfig|bluetoothMeshFriendshipConfig|bluetoothLECISConfig|bluetoothLEPeriodicAdvConfig
Topics
- Create, Configure, and Simulate Bluetooth LE Network with Custom Channel
- Create, Configure, and Simulate Bluetooth LE Broadcast Audio Network
- Create, Configure and Simulate Bluetooth Mesh Network
- Estimate Packet Delivery Ratio of LE Broadcast Audio in Residential Scenario
- Establish Friendship Between Friend Node and LPN in Bluetooth Mesh Network
MATLAB Command
You clicked a link that corresponds to this MATLAB command:
Run the command by entering it in the MATLAB Command Window. Web browsers do not support MATLAB commands.
Web サイトの選択
Web サイトを選択すると、翻訳されたコンテンツにアクセスし、地域のイベントやサービスを確認できます。現在の位置情報に基づき、次のサイトの選択を推奨します:
また、以下のリストから Web サイトを選択することもできます。
最適なサイトパフォーマンスの取得方法
中国のサイト (中国語または英語) を選択することで、最適なサイトパフォーマンスが得られます。その他の国の MathWorks のサイトは、お客様の地域からのアクセスが最適化されていません。
南北アメリカ
- América Latina (Español)
- Canada (English)
- United States (English)
ヨーロッパ
- Belgium (English)
- Denmark (English)
- Deutschland (Deutsch)
- España (Español)
- Finland (English)
- France (Français)
- Ireland (English)
- Italia (Italiano)
- Luxembourg (English)
- Netherlands (English)
- Norway (English)
- Österreich (Deutsch)
- Portugal (English)
- Sweden (English)
- Switzerland
- United Kingdom (English)