Clients

This page enables your SCADA project to operate as a “Standard Client”. In this mode, the SCADA continues to manage its own field PLCs while simultaneously connecting to other Wise SCADA servers to read or write specific data.

IMPORTANT NOTE: If you want to make this computer a complete copy (Mirror) of the main server, do not use this page. For the full mirroring process, activate the Setup > Client Mode option.

Configuration Parameters

The following table describes the parameters required to connect to an external server:

Parameter	Description
No	The sequence number of the client connection.
Symbol	The name given to the connection (e.g., “Boiler_Room_Server”). This name appears in the logs.
Protocol	The communication protocol used by the remote server. (Usually, Wise SCADA is selected).
Server Addresses	The IP Address:Port information of the server to connect to (e.g., 192.168.1.100:8000). Multiple IP addresses can be defined. If the system cannot reach the first IP, it automatically switches to the second and tries sequentially until a connection is established.
Type	Determines the communication type (TCP or UDP).
Method	Determines how data exchange will occur: • GET: Used to read data from the server. Fetches data at defined periods. • PUT: Used to write data to the server. Triggered when a tag changes within the SCADA. • DYNAMIC: Triggered reading method. Instead of continuous fetching, it reads instant data from the server only when the “Trigger” condition is met.
Tag List	The list determining which data will be fetched from or written to the server. Instead of “All Tags“, a Custom List containing only the necessary tags should be selected.
Enable	Activates or deactivates the defined row. If unchecked, the connection is not deleted, but communication stops.
Trigger	The trigger tag that starts or stops communication.
Period (ms)	The frequency of data reading (Milliseconds). Tip: If Period = 0, communication does not work based on time; operations are performed only when the “Trigger” tag is active.
Timeout (ms)	The maximum time to wait for a response from the server. If this time expires, a Fault is generated.
Retry Count	Determines how many times the system will retry before falling into “Error” status when the connection is lost or an error is received.
Disconnect	(Saving Mode) Closes the connection after every data packet. • Used to avoid occupying the line in very slow communications (e.g., sending data every 10 minutes).
Event Recording	Logs connection statuses (Connected/Disconnected).
Activate	Starts the client service.
Connected	Information lights indicating the current status of the connection.
Fault	If an error occurs during connection, error information is displayed in this field.
Connected IP	Shows which IP address is currently being communicated with.
Comment	A description field where the user can take private notes.

Method (Data Transfer Methods)

This is the most critical setting determining when and how data is transferred. You must select one of the following three methods according to your project’s needs.

A. GET (Continuous Monitoring)

Used to fetch data from the server at regular intervals (Polling).

• When to use? If you want to monitor the level of a remote tank, temperature values, or continuously changing analog data live on the screen.
• Working Logic: Tells the server “Send data” every time the Period time expires.

B. PUT (Send on Change)

Writes data to the server only when the tag value within SCADA changes (Event-Driven).

• When to use? To start/stop a remote motor or send a set value.
• Advantage: Does not send continuous data; uses the network only when there is a change. It does not burden the bandwidth.

C. DYNAMIC (Triggered Reading)

Does not perform continuous reading; fetches instant data only when the “Trigger” condition is met.

• When to use? When current values are required upon pressing a “Get Report” button or when data needs to be read when a specific machine starts.

Diagnostics

After activating the connection (with the “Activate” button), you can follow the status from the indicators on the right side of the row.

Column	Description
No	The transaction sequence number.
Time	Shows the time the event occurred (with millisecond precision).
Request	Shows the request sent to the server. • Connection: The IP address of the connecting device (e.g., 127.0.0.1). • Data: The request message from the client (e.g., “The client read 7 tags…”).
Response	Shows the response the server gave to this request. • When data is sent: “Sent 7 tag values to the client.” • In case of error: Error code or description.
Description	Summarizes the result of the operation (e.g., Success or Fail). Green rows represent successful connections, while red rows represent errors.