The DEVICE TYPE determines the Protocol used by WebAccess to communicate with the automation device. The Protocol is software and hardware dependent.  The Protocol determines how the 1 and 0 (the bits) are converted into meaningful numbers and characters.  Modbus RTU is an example of a Serial Communications protocol.  The Protocol is specified when you ADD DEVICES to the comport (see Device Properties).

The protocol of the device and the WebAccess Device Driver must be the same. The protocol is tremendously variable among manufactures. For example, it is almost impossible to convert an Echelon LON protocol into a Siemens S7.  There are exceptions; for example, there are Modbus RTU to Allen-Bradley Data Highway converters.  But these exceptions are rare.

The Device configuration fields differ (and appearance of the page will change) depending on the port type: Serial, TCP/IP, API or OPC.   For example, Devices attached to Serial ports will include baud rate, parity, stop bit, while Device connected to TCP/IP ports will require fewer fields.

The choice of Device Types available from pull down lists will also change based on the port type.  Not all Devices support all Port Types.

Once a device is added to a Port, only that device type (or compatible device types with compatible communications protocols) can be added to that Com Port.

Refer to the Device Guide for you specific device type for detailed information on configuring communications to your device

The Device Configuration Fields will appear similar for all devices on a similar ComPort Type:

3.4.1.1Device Properties - API Port

3.4.1.2Device Properties - OPC Port

3.4.1.3Device Properties - Serial Port

3.4.1.4Device Properties - TCP/IP Port