5 Implement the ProtoCessor from a Software Perspective
OEMs need to select a common host side protocol that the ProtoCessor can understand. ProtoCessor supports a wide
range of legacy host protocols (like Modbus), but for OEM devices that do not have host protocol, 2 alternatives are
available:
• Implement our PSP ASCII protocol. (ProtoCessor Simple Protocol). It takes about 1 day to implement. Refer to
Section 7 ProtoCessor Simple Protocol (PSP) Specification for the protocol spec.
• If the OEM has a proprietary host protocol, FieldServer can write the driver on the ProtoCessor Host/Socket platform
for an NRE fee.
5.1 ProtoCessor Supported Host & Field Protocol Communications
The following table lists the currently supported OEM’s Host/Socket and Field Protocols. The list of supported protocols is
constantly increasing and it is advisable to contact ProtoCessor or refer to the website for a more updated list.
NOTE:Visit the MSA Safety website for the complete list of supported protocols.
OEM’s Host Serial or Ethernet
Protocols
Serial Field
Protocols
Ethernet Field
Protocols
FieldBus
Protocols
Modbus RTU BACnet MS/TP Modbus TCP/IP LonWorks
Modbus ASCII BACnet PTP Allen Bradley DF1
ProtoCessor PSP Driver Modbus RTU DNP 3.0
BACnet MS/TP Modbus ASCII BACnet/IP
Metasys N2 Open BACnet MS/TP BACnet Ethernet
XML over HTTP Metasys N2 Open EtherNet/IP
Allen Bradley DF1 Allen Bradley DF1 Allen Bradley CSP
Modbus TCP/IP DNP 3.0 Serial DNP 3.0 Ethernet
BACnet/IP J-Bus GE-SRTP
LonWorks GE-EGD
EtherNet/IP Omron FINS
Allen Bradley CSP SNMP Ver 1 & 2C
DNP 3.0 Serial or Ethernet XML over HTTP
GE-SRTP JSON
GE-EGD
SNMP Ver 1 & 2C
OEM’s Custom Serial Driver
JSON
13 ProtoCessor Design Guide
To Next Page