Create your first configuration in Anybus Studio
This example shows how to create a basic Anybus Studio configuration for simulated communication between Modbus RTU and PROFINET on the Evaluation Board.
It includes values you can use directly to create a working configuration.
The configuration is the same as the pre-installed one on Anybus ONE SoM. You can also download it, see Example configuration: download and use.
For detailed information about Anybus Studio configuration, see Configuration workflow.
Before you begin
Create an Anybus Studio account and login. See also Create your Anybus Studio account.
Modbus RTU host interface
Go to Host interface > Modbus RTU.
Parameters
![]() |
In the Parameters tab, add four Holding registers:
InputParam1
InputParam2
OutputParam1
OutputParam2
Use these values:
Direction | Address | Name | Type | Access | Default |
|---|---|---|---|---|---|
Modbus RTU → PROFINET | 0x123 | InputParam1 | UINT16 | R | - |
Modbus RTU → PROFINET | 0x124 | InputParam2 | UINT16 | R | - |
PROFINET → Modbus RTU | 0x125 | OutputParam1 | UINT16 | R/W | 0x2222 |
PROFINET → Modbus RTU | 0x126 | OutputParam2 | UINT16 | R/W | 0x2223 |
Data sets
![]() |
In the Data sets tab, create two data sets:
InputDataSet
Assign parameters: InputParam1, InputParam2
OutputDataSet
Assign parameters: OutputParam1, OutputParam2
Use these values:
Data set name | Access type | Direction | Parameters | Offline action |
|---|---|---|---|---|
InputDataSet | Cyclic and acyclic | Input | InputParam1 InputParam2 | - |
OutputDataSet | Cyclic and acyclic | Output | OutputParam1 OutputParam2 | Use default values |
Settings
![]() |
In the Settings tab, configure the communication settings:
Modbus Node ID: 1
Register order: Most significant register first
Bit rate (bps): 115 200
Parity & stop bits: E1
Timeout (ms): 500
Retries: 2
PROFINET data mapping
Go to Network protocol > PROFINET.
Modules

In the Modules tab, create two modules with submodules:
InputModule with InputSubmodule
OutputModule with OutputSubmodule
Use the following values:
Module ID | Module name | Submodule ID | Submodule name | Data (In) | Data (Out) | Virtual |
|---|---|---|---|---|---|---|
0x00000001 | InputModule | 0x00000001 | InputSubmodule | InputDataSet | - | ✓ |
0x00000002 | Output Module | 0x00000001 | OutputSubmodule | - | OutputDataSet | ✓ |
Device Access Point (DAP) module
The Device Access Point (DAP) module is predefined and cannot be changed.
Module ID | Module name | Submodule ID | Submodule name | Virtual |
|---|---|---|---|---|
0x80001000 | Device Access Point (DAP) | 0x00000001 | DAP | ✓ |
0x00000002 | Interface | - | ||
0x00000003 | Port 1 | - | ||
0x00000004 | Port 2 | - |
Slots

In the Slots tab, create two slots and assign modules:
InputSlot assigned to InputModule
OutputSlot assigned to OutputModule
Use the following values:
Slot ID | Name | Modules | Plugging rule |
|---|---|---|---|
0x0001 | Input Slot | InputModule | Fixed in |
0x0002 | Output Slot | OutputModule | Fixed in |
DAP slot
The DAP slot is predefined and cannot be changed or removed.
Slot ID | Name | Modules | Plugging rule |
|---|---|---|---|
0x0000 | Device Access Point | Device Access Point (DAP) | Fixed in |
Subslots

In the Subslots tab, create one subslots in each module and assign submodules:
InputSubslot
OutputSubslot
Subslot ID | Subslot name | Module | Submodule |
|---|---|---|---|
0x0001 | InputSubslot | InputModule | InputSubmodule |
0x0001 | OutputSubslot | OutputModule | OutputSubmodule |
Identification

Use default values unless specified:
Identification setting | Data type | Sourse type | Source / Constant value |
|---|---|---|---|
Vendor ID | UINT16 | Constant | 268 |
Vendor name | STRING | Constant | HMS |
Device ID | UINT16 | Constant | 38 |
Product family | STRING | Constant | EVK Demo |
Order ID | STRING | Constant | My Order Number |
Hardware revision | UINT16 | Constant | 0 |
Software revision | UINT32 | Constant | 256 |
Serial number | UINT32 | Built-in | Managed internally |
Result
Two Modbus input parameters mapped to PROFINET input data
Two Modbus output parameters mapped to PROFINET output data
Download configuration files and signing tool
Go to Finalize configuration and download the configuration files.
![]() |
The download zip includes the unsigned configuration HIFF file, PROFINET GSDML file, and the Anybus ONE Signing tool.
See also Download configuration files.
Sign configuration HIFF file
Extract the configuration files (.zip) folder and run the AnybusONE-SigningTool.exe.
The unsigned HIFF file and the private and public key files are selected by default.
The preselected private key is an example key provided with the Anybus Studio output. In a production configuration, this key is replaced with a user-generated private key.
Click .
![]() |
The signed HIFF file is automatically saved in the extracted configuration files folder.
See also Sign configuration files.
To do next
Install the signed configuration HIFF file on the Evaluation Board SoM. See Install a configuration on the Evaluation Board SoM.




