AVEVA™ XR Studio

mwpl.bridge.core.ChannelMWPL

Save PDF

TABLE OF CONTENTS

mwpl.bridge.core.ChannelMWPL

Save PDF

Last UpdatedSep 03, 2025
2 minute read

The mwpl.bridge.core.ChannelMWPL is a channel to connect to MWPL bus.

Code example

This is a code example for mwpl.bridge.core.ChannelMWPL.

Parameters

These are parameters for the channel connection.

Parameter	Description	Use
name	The name of the channel.	Mandatory
class	This must be mwpl.bridge.core.ChannelMWP.	Mandatory
connectionName	This must be set to bridge.	Mandatory
connectionType	This can be client or server.	Mandatory
connectionHost	Host IP address or Hostname of the server of the Message Bus network. This field is used only if type is set to client.	Mandatory
connectionPort	The port to use for the connection. This value is 10666 for standard installations.	Mandatory
autoconnection	Set to True to automatically connect to MWPL bus when XR Bridge starts.	Mandatory
REPLAY_DELAY_TIME	The time to wait during scenario replay before considering the correct time arriving from AVEVA™ Dynamic Simulator. The default value is 2000.	Optional
encryption	Enables encryption on communication while transferring data. It supports channel encryption key using any of these: Secret protected on user scope using DPAPI. Cleartext encryption key specified in config (this option should be used only in cases where the deployment architecture allows the confidentiality of the secret by other means). For DPAPI, set the encryption key as: dpapi:<EncryptedKey> Note: EncryptedKey should have been obtained using a null or empty string as entropy. For Cleartext, set the value as: password:<encryptionKey> In cases where the configuration is empty or not present, the channel is not encrypted. Please make sure you understand the security implications if you use this option in any deployment.	Optional

Note: Always use the bridge channel in client connection mode to avoid XR Bridge having to handle both cross channel and 3D Realtime internal communication in server mode.

Simulation

Inside the <simulation> node, the channel can support almost all data types of variables. However, sfloat and sbool are most commonly used.

<mwpl>

</mwpl>

Variable parameters

All the variable types share the same attributes.

Code example

This is a code example for the query parameter.

Attribute	Description	Use
name	The name of the variable.	Mandatory
value	The starting value of the variable.	Optional
capture	The value to be registered, or not, into replay. The default value is true.	Optional

Cybersecurity Note Please note that Message Bus does not provide data confidentiality from potential cyber attacks. It is strongly advised not to use this communication means to share credentials or other sensitive data as it could be intercepted.

AVEVA™ XR Studio