ProtoCessor FFP
Flexibility in meeting customer's needs
The ProtoCessor FFP (Full Function ProtoCessor) provides OEM manufacturers the ability to fully configure the OEM protocol gateway module via a downloadable file or a host PC. The ProtoCessor FFP OEM protocol gateway includes a variety of features that results in greater flexibility for the OEM making it a better solution for lower volume applications where the OEM needs to make more modifications to specific products or groups of products.
Learn more about the ProtoCessor FFPcapability and how it can meet your specific needs. Request information now
The OEM using ProtoCessor has to be flexible in meeting the needs of their customer. The particular device utilizing ProtoCessor might not always be using the same protocol for every customer. For instance, in a Building Automation application, one customer might require Metasys N2 by JCI, another might need BACnet MS/TP, and a third might need Modbus RTU. All three protocols utilize the same ProtoCessor hardware, but the configuration is completely different. In addition, there might be certain features of the manufacturer's product that are available in certain application but not in others.
ProtoCessor FFP provides the manufacturer the ability to change configurations to meet specific product, customer or application needs yet still utilize the same socket and the same hardware. The manufacturer would download the new configuration to the ProtoCessor prior to shipment and the device arrives at the customer ready to use!
The ProtoCessor FFP is BTL Marked ant the ProtoCessor LonWorks version is LonMark Certified.
The ProtoCessor ASP (Application Specific ProtoCessor) is the best solution for high-volume/cost-sensitive applications. The ProtoCessor ASP is hard-coded with the configuration but with the use of DIP switches the manufacturer can select from multiple hard-coded solutions.
| FFP | |||||||
|---|---|---|---|---|---|---|---|
| Configuration | Fully configurable via downloadable file or by Host CPU via PCP driver | ||||||
| CPU | 32 bit ARM-7 CPU | ||||||
| Program memory | 2 MB | ||||||
| RAM | 8 MB | ||||||
| Downloadable configuration | Yes - over Ethernet | ||||||
| Remote diagnostics | Full | ||||||
| Multiple simultaneous drivers | Yes | ||||||
| Ethernet configuration port always included | Yes | ||||||
| Cost per unit | Higher | ||||||
| Point count | 1000's | ||||||
For non-OEM applications please check out the full line of protocol gateways at FieldServer Technologies.
| OEM's Host Serial Protocols | Field Protocols | Field Protocols | ||||||
|---|---|---|---|---|---|---|---|---|
| BACnet MS/TP | Allen Bradley DF1 | LonWorks | ||||||
| DF1 | BACnet MS/TP | Metasys N2 by JCI | ||||||
| DNP3 | BACnet PTP | Modbus ASCII | ||||||
| LonWorks | BACnet/IP | Modbus RTU | ||||||
| Metasys N2 by JCI | DNP3 Serial or Ethernet | Modbus TCP | ||||||
| Modbus RTU | EtherNet/IP | OPC | ||||||
| ProtoCessor PSP | GE-EGD | SNMP | ||||||
| Your own custom Serial Driver* | JBus | And many more | ||||||
Choose any of the protocols in the first column to act as the interface between the Host System and the ProtoCessor. Then choose a protocol in the the next columns to be supported by your equipment.
For non-OEM applications please check out the full line of protocol gateways at FieldServer Technologies.
*Small NRE to port custom host protocol to the ProtoCessor Full Function and Application Specific Families
ProtoCessor's Configuration Auto-Selector is a feature not found on other products. This feature makes it easy for OEMs to select specific protocols and configurations for their applications while stocking and supplying a single component. With Configuration Auto-Selector the manufacturer can pre-load multiple predefined configurations and multiple protocols and then, using DIP switches or even a register on the OEM unit to select the proper configuration for their customer's specific needs. For further information, select the Configuration Auto-Selector to the right.
