A
simple ASCII protocol that provides a simple way to communicate with a ProtoCessor
The PCP Serial Protocol is designed to achieve the following:
- Read a Customer Device’s Database of data objects
- Determine if the database has changed
- Allow data transfer (read and write) between the Driver and the customer Device
This driver utilizes these protocol capabilities to achieve the following
- Read a customer device database
- Auto create a client configuration to read the values/states of the data objects
discovered
- Auto create a BACnet Server side connection, node and objects to make the customer
device available to upstream BACnet clients.
The driver can also be used in a simple mode to poll for specific data from a customer device.
To achieve this, the data objects in the customer device must be known in advance.
The protocol is node-less. This means that messages do not contain source/destination node addresses and hence it would not be possible to differentiate messages from multiple devices
on the same connection. Thus only one node may be defined per connection.
The driver provides both client and server emulation. The server side of the driver is intended to
support FieldServer’s Quality Assurance program and is not intended to provide complete
emulation of a PCP Server. Thus the server side is not fully documented. At a customer’s
request the server side functionality can be documented and enhanced. If you are interested in
this functionality, then please contact FieldServer’s sales group.
The protocol specification document is available from FST. Please request the document
named: PS002 - PCP Driver Spec (FS-8700-109)
Formal Driver Type: Serial, Client or Server
Connection type: RS-232 or RS-485
