WinTr stations can communicate with each other as a client and server. This flexible connections has some rules. First thing that shoud know at client – server communication there is no difference whether if it is over local network or internet.
  • WinTr Server license is sold as an option.
  • Client is standart feature and free.
  • Client and server stations may have different tag counts. For example you can connect with 64 tag WinTr to 1024 tag WinTr. Thus you can control and monitor 1024 + 64 tag.
  • Unlimited client can connect a one server.
  • One client can connect up to 1000 different server.
  • Client - Server connection can only be with selected tags.
  •  Client - Server connection can be redundant.  There is no limitation on the number of Redundant partner. Redundant partner tag number don’t have to match with the server. It can also be minimum.
  • At the same time, client station can connect to multiple server as a redundant.
  • Client and server stations can make cross connection with each other. For Example: WinTr A station can connect to the specific tags of B station. Also B station can connect to the specific tags of A station.  Such a requirement may occur as the processes needed. It will be described later section with detail.
Large capacity server client connection is limited to your ethernet bandwith and imagination. Such a large capacity of communication can put your project into infinite loop. Carefully check the  Synchronized tags.

How to enable Server & Client Relations: Firstly, WinTr must be installed on two different computers. While experiments two different WinTr can run on one computer.  WinTr works by sending queries from client stations to the server stations with TCP/IP protocol. Since server WinTr started, it will wait for the requests from the clients. It doesn’t require being Runtime or Connect state. Clients communicate with server when they are runtime or connect state. They do not produce a query at the other states.
You can specify 4 different mode for WinTr Server & Client.
Local (Disable Remote Connection): No network can be used.
Server (Enable Remote Connection): Shares tags with client stations as a server.
Client (Only Connection Server): Shares tags with server stations as a client.
Server and Client (Enable Remote Connection and Connected Server): Runs as a server and client. Communicates with server for sharing data and shares data with the clients who accessed itself.

To set WinTr station as a Server: Check “Server (Enable Remote Connection)”. If you want to limit to clients who access this server “Disable Multiple Connection” must be unchecked and client IP address must be entered. If multiple client will connect to the server this box must be checked and it must become “Enable Multiple Connection”. You can allow multiple connection when working with one client.  TCP/IP Port number is the gate for catching requests by WinTr. If you make connection over Internet this port number must be introduced ADSL modem for routing requests. At Local or internet connections TCP/IP port number must be same at the client and server. Other program which uses this port number shouldn’ t be run. One port can only be used by one program. When modify server connection reset the system by clicking “Restart”. It is normal to have “WSACancelBlockingCall” call interruption warning. This warning indicates that the process is successful so far.  Now system is ready for working as a server. You can create tags and make other operations.

To set WinTr station as a Client: Check “Client (Only Connection Server)” box. Write the IP address and TCP/IP port number to connect. If Tag count is high at the connected server, poll time period may not be sufficent. You need to specify this period according to tag count. 500 ms is suitable for 256 tag. For 2048 tag 1000 ms is good. This period and timeout period is from our Internet tests.  But you should set it according your internet connection. When click on connect Connect button, WinTr will connect to the server and get all tags on the server to the datagrid. If there is an error on the connection or server is shut down an error message will shown at the textbox. This proses may take a long time according to your fetched tag count.
The tags that belong to multiple servers are listed here. At Each connect operation concurrent tags with the IP adress becomes blue, new added ones become green, tags that not found on the server are become red. You can delete the tags that will not synchronized. When you right click on this list operation menu opens.
Tag Synchronization: This is active when one line selected. Selected tag synchronized with local tag. Only appropriate  type tags can be synchronized.
Add New Tag in Client: Creates new tags for server tags at selected lines. It is tried to make same as server tag name. If same name tag exist new named tags created.
Remove Synchronization: Deletes synchronous connection of the selected tags on the list.
Clear All Asynchronous Tag: Deletes all tags that not synchronized from the list..
Delete: Deletes selected tags and removes it’s synchronous connections.

When you complete your work on the list finish by clicking “Tag Synchronization Table and Tag List Synchronized” button. If you do not click this, your work just stays on the list.

Read/Write: Synchronization can be in three ways.
Read Only: For this tag, client can only read from server. Can not change this tag’s value. When you assigned new value to this tag at client station then you read from server, the value will be removed. You can use this feature to define the problem on the server connection.
Write Only: Client doesn’ t read this tag value from the server. When client first started, transfers all “Write Only” tag values to the server. Then trasfers only tag’s value changed. When data written on this type tags from the server, value stays on server screen it doesn’t transmitted on the client screen. Until client station transferred new value to this tag, tag values between client and server will be different. Make sure that data is not written on this type tags by servers.
Read Write: Client continuously read this tag value from the server, when data changed on the client side,  writes it to the server. As long as data does not change transfer is one-sided.

When client and server connection can not be established tag values can not be transferred but will continue to work on own computer. When connection established read-only and read write type tag’s values will fetched from the server. If there is a changed write tag values in the period of the connection was broken, they will written to server. Tags that values not changed will not written.

Note: The tag which read from the server will be transferred to synchronous tag by client. If this tag synchronized with other tags data will transferred here as well. Synchronized tag may not be internal. It may connected automation device.At this situation new value will transferred here. Same way, tag values that written to the server by client, will transferred all related partners.You can create infinite loops via thiscompletely  automatic operation.  Follow the connections carefully.
       
Client stations connect to servers and check  tag configurations when runtime first started or communication started via connect button. When connection can not established or synchronous tag do not suitable, this server cancelled and do not connected again. To connect again, runtime must be restarted or disconnected and connected again. After the connection established, an  error message can appear that about  not connected. The errors at this level, do not disable the connection. Client attemps to connect again. Once this error message appear, it blocks itself. When connection established and lost, it appears again. By writing values to the read-only tags, you can test if there is a connection errors.



shape
Server Client
WinTr Scada Logo