Value Simulator Connector

Generates simulated values for solution testing

Overview

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

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 a point, navigate to Devices > Points, then click on the Address column to edit it. Use the following syntax for the Address:

<Type>;<Min>;<Max>  
<Type>;<Min>;<Max>;<Step>  (Only for RAMP type)

• <Type> specifies the simulation type: BOOL, INTEGER, FLOAT, STRING, RAMP, or SINE. From FrameworX 10.1.6a, the address can also be a function, described in Function addresses below.

• <Min> and <Max> define the minimum and maximum values for the simulation.

• <Step> (only used with the RAMP type) is the number added to the value each time the point is read, which is once per read polling period of the point’s AccessType.

From FrameworX 10.1.6a, Min, Max and Step accept decimals, written with a dot as the decimal separator, for example FLOAT;70.5;95.5;1 or RAMP;0;1;0.1. An address with a non-numeric Min, Max or Step, for example RAMP;abc;def;1, is invalid. The point is left out of communication, its tag does not report Good quality, and the Devices trace in the Trace Window reports the address as invalid.

For the STRING type, you can specify a custom StringLength to control the length of the generated string according to your requirements.

Function addresses

From FrameworX 10.1.6a, a point address can be a function written as name(argument, argument, ...). The function name ignores letter case, arguments are separated by commas, and an empty numeric argument takes its default. Numbers use a dot as the decimal separator. A function address contains no semicolon or colon. Periods are in seconds. The address dialog in the Points table shows the fields of the selected function.

RAMP, SINE and INTEGER behavior

From FrameworX 10.1.6:

• A RAMP point starts at Min. Each later read adds Step.

• With a Step of 0 or more, a read whose value would pass Max returns Min instead, so the value never goes past Max. For example, RAMP;0;100;7 goes from 98 back to 0, and RAMP;0;179;13 goes from 169 back to 0.

• A Step of 0, or a Step larger than the range between Min and Max, keeps the value at Min.

• A negative Step lowers the value at each read, with no lower limit.

• Each RAMP or SINE point progresses on its own, also when several points share one channel.

• INTEGER random values include Max, and random points read at the same time return independent values.

Points configurations examples

Result example

All type values are plotted in the trend chart below for clearer visualization.

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 Revision History

In this section...