Serial
DataMiner supports serial communication, allowing protocols to define one or more connections of type "serial". DataMiner runs a process called "SLPort", which takes care of all communication to and from devices connected to either a serial port or an IP port.
When communicating with a serial device, a DataMiner Agent will send commands to the device and the latter will reply with a response for each command. Serial devices cannot send unsolicited messages to a DataMiner Agent; devices only send responses to commands sent by DataMiner.
The communication will occur over TCP/IP, UDP, or, less commonly, over a serial cable.
Note that devices supporting serial communication often implement a proprietary, vendor-specific serial communication protocol. However, public standardized protocols are also possible (e.g., Modbus).
Important
IPv6 destinations are supported for plain TCP/IP connections. However, IPv6 destinations are not yet supported for:
- TCP/IP connections with SSL/TLS enabled.
- UDP/IP connections.
Use IPv4 destinations for these connection types.
Tip
It is possible to create a serial simulation using an element stream or DataMiner simulation file as input for our Skyline Serial Simulator protocol (link accessible for Skyline employees only).
See also
DataMiner Protocol Markup Language:
- Protocol.Commands
- Protocol.Responses
- Protocol.Pairs
- Protocol.Pairs.Pair@options:
- Protocol.Type: serial and serial single
- Protocol.Type@communicationOptions:
- chunkedHTML (obsolete)
- closeConnectionOnResponse (obsolete)
- makeCommandByProtocol
- redundantPolling
- Protocol.Triggers.Trigger.On
- Protocol.Actions.Action.Type:
- Protocol.Actions.Action.On: response
- Protocol.Params.Param.Type:
- Protocol.Params.Param.Type@times
- Protocol.Params.Param.Type@options: