Configure the Simulator Connector

Generate random values and counters in SIA Connect for testing mappings, data logging, dashboards, and destination Connectors.

+ More

The Simulator Connector generates test values without connecting SIA Connect to a physical device. Use it to test configurations, mappings, data storage, dashboards, and destination Connectors before live equipment is available.

The Connector can generate random integer values within a configured range or a counter that increases each time the item is read.

Simulator items should be configured as read-only. The Connector accepts no meaningful writes, and writing to an item does not change or reset its generated value.

Use cases

The Simulator Connector is useful when you need predictable test data or changing values without depending on an industrial device.

Test mappings: Use generated values as mapping sources while building conditions, transformations, triggers, and templates.
Test destination Connectors: Send simulated values to MQTT, databases, cloud services, or other destinations before connecting a production data source.
Test dashboards: Populate charts, gauges, and tables with changing values during dashboard development.
Test data logging: Confirm logging mode, retention, and data export behavior with a controlled stream of values.
Test thresholds and alarms: Use a random range that crosses configured thresholds to check how downstream logic responds.
Demonstrations and training: Build repeatable examples without requiring a PLC, sensor, or other field device.
Test discovery: Use the built-in instance and item candidates to verify the Edge Portal discovery workflow.

Use a random item when you need changing values across a range. Use a counter when you need an ordered sequence that makes missing or repeated reads easier to identify.

Before you begin

Install the Simulator Connector. See Install and manage Connectors.
Decide whether the test requires random values or an increasing counter.
For random values, choose the minimum and maximum integer values.
Choose an item update interval that matches the test.

The Simulator Connector does not require a network connection to another device and does not have Connector-specific instance parameters.

Discover and add the Simulator instance

Discovery is the quickest way to create a working Simulator instance. The Connector returns one instance named Simulator.

In the sidebar, expand Workspace and select Instances.
Select Discover instances.
Select the Simulator Connector.
Start the discovery.
Select the Simulator candidate.
Add the selected instance.

The discovered instance uses simulator as its address. The address is an identifier for this simulated instance and is not used for a network connection.

For details about discovery sessions, candidates, and import results, see Discover instances and items.

Create a Simulator instance manually

In the sidebar, expand Workspace and select Instances.
Select Create instance.
Select the Simulator Connector.
Enter a unique name for the instance.
Enter simulator in Address if the field is required.
Create the instance.

The Connector ignores the instance address because it does not connect to external equipment.

Discover Simulator items

The Connector provides two ready-made item candidates:

Item	Configuration	Result
Random 0 to 1024	Min `0`, Max `1024`, Count up disabled	Generates a random integer in the configured range.
Counter	Count up enabled	Generates an integer that increases by one for each read.

Open the Simulator instance.
Open the Items section.
Select Add item.
Select Discover items.
Start the discovery.
Select one or both item candidates.
Add the selected items.

The discovered items use the Integer data type and read-only access.

Create a Simulator item manually

Open the Simulator instance.
Open the Items section.
Select Add item.
Select the manual item option.
Enter a name for the item.
Set the item to read-only operation and use the Integer data type.
Configure the Simulator parameters described below.
Create the item.

Parameter	Default	Accepted values	Description
Min	`0`	Integer	Lower limit used when Count up is disabled.
Max	`0`	Integer	Upper limit used when Count up is disabled.
Count up	Disabled	Disabled or enabled	When enabled, the item returns an increasing counter instead of a random value. Min and Max are ignored.

For general item settings such as update interval, logging mode, units, limits, and tags, see Create and edit items.

Configure a random-value item

Create or edit a Simulator item.
Set Count up to disabled.
Enter the lowest required integer in Min.
Enter the highest required integer in Max.
Save the item.

The item generates a new value from the configured range each time SIA Connect reads it. The frequency therefore depends on the item's update interval.

Example: Set Min to 0 and Max to 100 to simulate a percentage-like value for testing. Add the unit separately if the test requires one.

Configure a counter item

Create or edit a Simulator item.
Set Count up to enabled.
Save the item.

A new counter starts at 0 when no previous value is available. It increases by one each time the item is read. Min and Max do not affect a counter item.

When the Connector restarts, it initializes the counter from the item's most recently stored value. The first value after a restart can therefore repeat the last stored value once before counting continues.

The counter measures reads, not elapsed time. A shorter update interval makes it increase faster.

Use simulated values in a mapping

Create the required Simulator item.
Confirm that the item receives values.
Create or open the destination instance and item.
Create a mapping from the Simulator item to the destination item.
Add any required condition, trigger, or transformation.
Enable the mapping and confirm that the destination receives the simulated values.

See Create and edit mappings for the complete mapping procedure.

Verify the configuration

Enable the Simulator instance.
Open the item list.
Wait for the configured update interval.
Confirm that a random item stays within the intended range.
Confirm that a counter item increases by one for each read.
If the item is used in a mapping, confirm that the destination receives the expected values.

Troubleshoot the Simulator Connector

Symptom	Cause and action
The item always returns 0	Count up may be disabled while Min and Max are both `0`. Set different limits for a random item or enable Count up.
The values do not stay within the intended range	Confirm that Min contains the lower value and Max contains the higher value. Make sure Count up is disabled.
Min and Max have no effect	Count up is enabled. Disable it to generate random values from the configured range.
The counter does not start at 0	The Connector resumes from the item's most recently stored value when one is available. Create a new counter item if the test must begin without previous item history.
The counter repeats one value after a Connector restart	The first read can return the most recently stored value before the counter continues. Account for this behavior when using the counter to detect missing samples.
The counter increases too quickly or too slowly	The counter increases once per read. Adjust the item update interval to change the rate.
Writing a value has no effect	This is expected. The Simulator write function does not change the generated value. Configure the item as read-only.
No Simulator instance appears during discovery	Confirm that the current Simulator Connector is installed and enabled. Restart the discovery after the Connector has finished loading.
No items appear during item discovery	Confirm that Discover items was opened from a Simulator instance. The discovery requires the target instance context even though the Connector does not use a network connection.
The value changes less often than expected	Confirm the item update interval and that the instance and item are enabled. Also check for instance, item, or mapping errors.

If a problem continues, see Troubleshoot Connector, instance, item, and mapping errors.

connector counter random data simulation simulator testing troubleshooting

Contact Us