The Value Simulator enables the simulation of a device connected to your solution that exchanges multiple data types with your application on the software platform. It allows configuration, management, and even more control for simulations and tests. It is a valuable tool for test tasks when developing your solutions. Check how to configure it into your solutions.
This document only has specific information about the target device's connection settings and address syntax. For more information, consult the Devices Module in the User Guide.
On this page:
Table of Contents maxLevel 3 style none
| Easy Heading Macro | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
This document has only specific information about the device connection settings and its address syntax.
Refer to the Developing Projects for more information on the Device Module.
Overview
The Simulator Driver gives you many options for data types and ranges, and it gives you control over which simulation values you can generate.
Pick from a list of data types — including Strings! — and set the Min & Max values you would like the data types to range through.
Do you want to simulate a real-world analog device and its response to a 4-20mA varying current? You can!
Or do you prefer to use a range that was 0-25 mA so you can simulate a wire break with 0 mA? Because you can too!Summary
| Communication Driver Information | |
|---|---|
Driver name | |
ValueSimulator | |
Assembly Name | T.ProtocolDriver. |
ValueSimulator | |
Assembly Version | 1.0.0. |
1 | |
Available for Linux | False |
Runtime only | |
Protocol interface | |
| Devices supported | N/A (Not Applicable) |
| Manufacturer | N/A (Not Applicable) |
Proprietary over TCP/IP | |
Requirements | Ethernet port |
Configuration
In the software platform, the Devices module manages communication with field devices through the Channels, Nodes, and Points by allowing stable and secure data exchange between multiple devices across different networks. Protocols define communication rules between the platform and devices. Channels define global parameters for the usage of a communication protocol. Nodes represent the physical field devices (like a PLC) with a unique field address (PrimaryStation). Points represent tags within a device. Additionally, AccessType defines how the device interacts with the platform (Read and/or Write).
All initial configurations for devices in the solutions on the software platform encompass the following workflow:
Channels
On the Designer workspace, navigate to Devices/Channels in Solution Explorer. Define a Channel using a target communication Protocol. This will create the base instance for linking a Node and does not require any additional configuration.
Nodes
On the Designer workspace, navigate to Devices/Nodes in Solution Explorer. Define the Node linked to the created Channel. It does not require additional configuration.
Points
On the Designer workspace, navigate to Devices/Points in Solution Explorer. Define the Point you would like to monitor. The Point controls the behavior of simulated data. You must map the Tag object to Point. After that, it requires the Address configuration.
Address
To configure it, go to Devices/Points and click on the Address column to edit. The syntax for the Address is:
<Type>:<Min>;<Max><Type> indicates the simulation type (BOOL, INTEGER, FLOAT, STRING, RAMP, SINE), while <Min> and <Max> set the minimum and maximum values for the data simulation, respectively.
The STRING data type uniquely features a custom StringLength, allowing the configuration of the string output to meet specific requirements.
Points configurations
Channels Configuration
Protocol Options
Not used in this driver.
Nodes Configuration
Primary Station
Not used in this driver.
Points Configuration
The syntax for the TSimulator communication points is: <Type>:<Min>;<Max>
Example:
Where:
- <Type>: Represents the Simulation Type:
- BOOL: The tag receives a random BOOL value, 0 or 1.
- INTEGER: The tag receives a random integer value from 0 to 5.
- FLOAT: The tag receives a random float value from 0 to 5.
- STRING: The tag receives a random string with 10 string lengths.
- RAMP: The tag receives values from 0 to 10 in ascending order.
- SINE: The tag receives values based on the sine function, its behavior is similar to a wave.
- <Min> and <Max>: Represents the upper and lower limits that the mapped tag can reach;
- <Step>: It's only used if the selected type is Ramp. It defines the value incremented at each step of the simulation (must be an integer value).
| Info | ||
|---|---|---|
| ||
|
examples
TagName | Node | Address | DataType | AccessType | Modifiers |
|---|---|---|---|---|---|
MySine | SimulatorNode | SINE:-50;50 | Native | Read | |
MyRamp | SimulatorNode | RAMP:0;100;10 | Native | Read | |
MyRamp2 | SimulatorNode | RAMP:0;179;13 | Native | Read | |
MyString | SimulatorNode | STRING: | Native | Read | StringLength=5 |
MyBool | SimulatorNode | BOOL: | Native | Read | |
MyInt | SimulatorNode | INTEGER:0;10 | Native | Read | |
MyFloat | SimulatorNode | FLOAT:-500;-100 | Native | Read |
Diagnostic Tools
Diagnostics tools refer to the Property Watch, Trace Window, and Module Information. These tools identify communication blocks and address errors, allow property access to pinpoint error causes, and display system messages for device management and troubleshooting, offering a comprehensive approach to device management and troubleshooting for Solutions on the software platform.
Module Information
This tool provides insights into module operations and communication channels, offering information about virtual reading groups, error codes, and communication events. It helps users identify communication blocks and effectively address errors in industrial automation systems.
Property Watch
This tool enables users to access, read, and write tags and internal properties of the system. It assists in identifying the root cause of errors through negative error codes, allowing for real-time adjustments and optimizations to the system configuration.
Trace Window
This tool displays system messages in a data grid interface, providing information about the status of reads, writes, and communication frames. It is particularly useful for various PLCs and communication protocols, as it presents invalid addresses in the configuration, assisting in device management and troubleshooting.
Driver
Driver Revision History
TSimulatorRevision History
Version | Notes | Updated |
|---|---|---|
1.0.0.1 | Initial release |
published according to new documentation standards. | February, 2023 |
1.0.0. |
3 | Update Ramp with Step parameter |
. | June, 2024 |
In this section
...:
| Page Tree | ||||
|---|---|---|---|---|
|