eWON

The eWON communication driver implements communication with eWON’s historical data cloud. It synchronizes configured tags to a matching address in the cloud. It not only keeps the last value up-to-date, but it also downloads all of the tag's historical data in the DataMailbox. 

Summary Information

Communication Driver Name: eWON

Implementation DLL: T.ProtocolDriver.EWon.dll

Protocol: HTTP

Interface: TCP/IP

Protocol Options: None

Max number of nodes: User defined

PC Hardware requirements: Standard PC Ethernet interface board and internet connection

Channel Configuration

Protocol Options

None

Settings

A tag must be configured to enable it to download the historical data from eWON’s DataMailbox. On Points, the historian must be enabled in the tag setup, or the driver will not attempt to download the historical data.

In order to avoid any conflicts when saving historical values, it is recommended to disable the Save on Change and Save Trigger in the historical table configuration, or it will store the values that were downloaded from the driver and the values generated by the value change and trigger.

Node Configuration

Station Configuration

No IP (station) setting is necessary because it always communicate with the cloud service that has a fixed address

Account: The name of the account registered in eWON’s DataMailbox

Username: The name of the user associated with the account

Password: The User’s password to access the data

DeveloperId: The UID code for registered developers on eWON’s site

eWON_Name: In eWON’s DataMailbox, tags are grouped in eWON’s and each “device node” must have an associated eWON

Point Configuration

The syntax for the eWON communication points is: <Tagname>

Where:

• <Tagname> is the name of the tag setup in the DataMailbox for the node’s eWON

Troubleshoot

The status of the driver's execution can be observed through the diagnostic tools, which are:

• Trace window
• Property Watch
• Module Information

The above tools indicate if the operations have succeeded or have failed. A status of 0 (zero) means communication is successful. Negative values indicate internal driver errors, and positive values indicate protocol error codes.