Skip to content

Connection Management

A connection is the communication channel to a field device or system. Each connection uses a protocol and is bound to a project.

Connection List

Menu: Runtime → Connections → New Connection

FieldRequiredDescription
NameYesConnection name (unique within the project)
ProtocolYesCommunication protocol
IPDepends on protocolTarget IP address
PortDepends on protocolTarget port number
DescriptionNoDescription
ProtocolUse CaseTypical Device
MODBUS TCPIndustrial automationPLC, energy analyzer, drive
MODBUS UDPApplications requiring fast readsEnergy meter
MODBUS RTU over TCPSerial communication gatewayRTU, serial device
DNP3Energy distributionRTU, protection relay
IEC 60870-5-104Energy transmission/distributionRTU, SCADA gateway
IEC 61850SubstationIED, protection relay
OPC UAOpen standardPLC, DCS, SCADA
OPC DAWindows COM/DCOMLegacy OPC servers
OPC XMLHTTP/SOAP basedWeb service OPC
S7Siemens PLCS7-300, S7-400, S7-1200, S7-1500
MQTTIoT / message-basedGateway, sensor, broker
EtherNet/IPRockwell/Allen-BradleyLogix 5000+ series
FatekFatek PLCFBs, FBe series
LOCALSimulation / calculationInternal variable

Detailed protocol settings: Protocols →

StateDescription
ConnectedConnection is active, data is being read
DisconnectedConnection is lost
ErrorConnection error (timeout, authorization, etc.)
{
"id": 153,
"name": "LOCAL-Energy",
"protocol": "LOCAL",
"ip": "127.0.0.1",
"port": 0,
"projectId": 153,
"dsc": "Local protocol connection for energy simulation"
}

Connections can be managed from the interface or via scripts:

// Query status
var status = ins.getConnectionStatus("LOCAL-Energy");
// → "Connected"
// Stop and restart
ins.stopConnection("MODBUS-PLC");
java.lang.Thread.sleep(2000);
ins.startConnection("MODBUS-PLC");

Connection parameters can be dynamically changed during runtime:

// Change IP address
ins.updateConnection("MODBUS-PLC", {
"ip": "192.168.1.100",
"port": 502
});

Detailed API: Connection API →