Use this area to work with the shared driver communication layer that connects the runtime to external meters, readers, sensors, lights, drives, HMIs, and similar field devices.
Use it when a product needs external field communication through shared device models, profiles, slots, addresses, and monitoring rules.
Start Here
Use these pages as the main entry points for supported device families, profile setup, and monitoring behavior.
Each configured external device uses one driver profile. A driver profile combines:
the selected device model
the selected network profile
an optional gateway profile
the slot used by the product runtime
the device address
optional timeout, retry, interval, and owner-group overrides
Use Device Model Setup to select the model-specific communication values, check known factory values in Defaults, then configure them on the Settings page.
Timeout and Retry Behavior
Timeout and retry values control how quickly the communication layer treats a profile as failed and how much extra communication it will try before that happens.
A shorter timeout can detect communication problems faster, but it can also increase communication load and make slow equipment appear unstable.
A higher retry count gives the profile more chances to recover after a temporary fault, but it also increases the time before a real fault is treated as failed.
After an offline timeout or read failure, the default wait before the next retry cycle is 20 seconds.
After the profile has already received valid data, the reconnect wait is reduced to 5 seconds.
When a driver profile is updated, its communication state is reset before reinitialization.
Keep the default values unless the selected equipment, transport path, or project requirements clearly justify a different balance.
Owner Groups
The runtime distributes driver profiles across owner groups so several communication types can run in parallel.
Owner group 1 is the standard wired group.
Owner group 2 is the priority group.
Owner group 3 is used for wireless and related profiles.
Owner group 4 is used for DALI and related profiles.
Automatic owner selection is the normal mode. Use a manual owner group only when engineering requires a specific override.
Monitoring And Logging
The communication layer also provides generic monitoring settings for supported driver profiles.
Vika Help uses necessary browser storage and, if you allow it, statistics cookies for Google Analytics. You can accept all, reject all, or open settings.
Cookie settings
Choose which categories may be used on Vika Help.
NecessaryAlways on. Required to remember your consent choice and keep the documentation shell working as intended.
Allows Google Analytics to measure aggregate use of the documentation site.