Page is loading ...
Document Revision: 9.D
T18601
ProtoCessor
Design Guide
This manual explains the function and Set-up of the following ProtoCessor products:
FFP-485 ProtoCessor (FPC-ED2)
ASP-485 ProtoCessor (FPC-AD2)
FFP-ETH ProtoCessor (FPC-F03)
FFP-LON ProtoCessor (FPC-ED4)
APPLICABILITY & EFFECTIVITY
Effective for all systems manufactured after February 2020.
ProtoCessor Design Guide
Contact Information
Technical Support
Please call us for any technical support needs related to the FieldServer product.
MSA Safety
1991 Tarob Court
Milpitas, CA 95035
Website: www.sierramonitor.com
U.S. Support Information:
+1 408 964-4443
+1 800 727-4377
Email: smc-support@msasafety.com
EMEA Support Information:
+31 33 808 0590
Email: smc-support.emea@msasafety.com
ProtoCessor Design Guide
Table of Contents
TABLE OF CONTENTS
Certification .......................................................................................................................................... 5
1.1 BTL Mark – BACnet Testing Laboratory......................................................................................... 5
1.2 LonMark Certification ...................................................................................................................... 5
ProtoCessor Family Overview ............................................................................................................ 6
2.1 ProtoCessor Product Lines ............................................................................................................. 6
2.1.1 ProtoCessor Embedded Modules ........................................................................................... 6
2.1.2 ProtoCarrier Daughter Cards .................................................................................................. 6
2.2 ProtoCessor Family of Modules ..................................................................................................... 7
2.2.1 FFP-485 ProtoCessor (FPC-ED2)........................................................................................... 7
2.2.2 FFP-LON ProtoCessor (FPC-ED4) ......................................................................................... 7
2.2.3 FFP-ETH ProtoCessor (FPC-F03) .......................................................................................... 7
2.2.4 ASP-485 ProtoCessor (FPC-AD2) .......................................................................................... 7
Implement the ProtoCessor from a Hardware Perspective ............................................................. 8
3.1 How to Implement the ProtoCessor Socket on OEM Hardware .................................................... 8
ProtoCessor Socket PCB Footprint – Layout ................................................................................... 9
4.1.1 Pin Assignment – ProtoCessor TTL Socket for 2x10 Header Pins ......................................... 9
4.1.2 ProtoCessor Pin Voltage Levels............................................................................................ 10
4.1.3 ProtoCessor Pin Headers ...................................................................................................... 10
4.2 ProtoCessor Socket Pin Locations ............................................................................................... 11
4.3 Location of Pins on the ProtoCessor ............................................................................................ 12
4.3.1 FPC-AD2 (ASP-485) ............................................................................................................. 12
4.3.2 FPC-ED2 (FFP-485) .............................................................................................................. 12
4.3.3 FPC-F03 (FFP-ETH) ............................................................................................................. 12
4.3.4 FPC-ED4 (FFP-LON) ............................................................................................................ 12
4.4 Standoff Dimensions..................................................................................................................... 13
ProtoCessor Power Requirements .................................................................................................. 14
Implement the ProtoCessor from a Software Perspective ............................................................ 15
6.1 ProtoCessor Supported Host & Field Protocol Communications ................................................. 15
6.2 ProtoCessor Device/Field Supported Protocols ........................................................................... 16
6.3 ProtoCarrier Device/Field Supported Protocols ........................................................................... 16
How ProtoCessor Works ................................................................................................................... 17
7.1 Introduction ................................................................................................................................... 17
7.1.1 Full Function ProtoCessor (FFP) ........................................................................................... 17
7.2 Configuration File for FFPs and ProtoCarriers ............................................................................. 18
7.2.1 Application Specific ProtoCessor (ASP) ............................................................................... 19
7.2.1.1 How to Implement and Test Any ASP ProtoCessor ........................................................ 20
Appendix A. ProtoCessor Simple Protocol (PSP) Specification .......................................................... 21
Appendix A.1. Purpose of the Protocol ................................................................................................... 21
Appendix A.2. Protocol Description ......................................................................................................... 21
Appendix A.2.1. Quick Start – Demonstrates the Simplicity of the Application ................................... 21
Appendix A.2.2. Serial Parameters ...................................................................................................... 21
Appendix A.2.3. Message Structure .................................................................................................... 22
Appendix A.2.4. Binary Packed Messages .......................................................................................... 22
Appendix A.2.5. Payload Contents ...................................................................................................... 22
Appendix A.2.6. Writing to Output Data Objects ................................................................................. 23
Appendix A.3. Error Conditions ............................................................................................................... 24
Appendix A.3.1. Format of the Error Response ................................................................................... 24
Appendix A.3.2. Error Response Table ............................................................................................... 24
Appendix A.4. Using Change of Value Reads ........................................................................................ 25
ProtoCessor Design Guide
Table of Contents
Appendix B. Recommended Connectors, Cables and Mechanics ...................................................... 26
Appendix B.1. ProtoCessor Pin Headers ................................................................................................ 26
Appendix B.2. Expansion Connector for ASP – FPC-AD4 and FPC-AD5 .............................................. 26
Appendix B.3. Expansion Cable For ASP – FPC-AD4 and FPC-AD5 .................................................... 26
Appendix B.4. Mechanics – Standoff ...................................................................................................... 26
Appendix C. Enclosure – Mechanical Design ........................................................................................ 27
Appendix D. Mechanical Drawings – ProtoCessor and ProtoCarrier .................................................. 28
Appendix D.1. Mechanical Dimension Drawing FPC-F03 ....................................................................... 28
Appendix D.2. Mechanical Dimension Drawing FPC-ED2 ...................................................................... 28
Appendix D.3. Mechanical Dimension Drawing FPC-ED4 ...................................................................... 29
Appendix D.4. Mechanical Dimension Drawing FPC-AD2 ...................................................................... 29
LIST OF FIGURES
Figure 1: Diagram of ProtoCessor Socket Layout ........................................................................................ 8
Figure 2: ProtoCessor Socket Footprint ........................................................................................................ 9
Figure 3: Pin Locations ............................................................................................................................... 11
Figure 4: Attached ProtoCessor .................................................................................................................. 11
Figure 5: Standoff Dimensions .................................................................................................................... 13
Figure 6: Enclosure Dimensions ................................................................................................................. 27
Figure 7: FPC-F03 Dimensions................................................................................................................... 28
Figure 8: FPC-ED2 Dimensions .................................................................................................................. 28
Figure 9: FPC-ED4 Dimensions .................................................................................................................. 29
Figure 10: FPC-AD2 Dimensions ................................................................................................................ 29
ProtoCessor Design Guide
Page 5 of 29
CERTIFICATION
1.1 BTL Mark – BACnet Testing Laboratory
The BTL mark is a symbol that indicates to a consumer that a product has
passed a series of rigorous tests conducted by an independent laboratory which
verifies that the product correctly implements the BACnet features claimed in the
listing. The mark is a symbol of a high-quality BACnet product.
Go to www.BACnetInternational.net for more information about the BACnet
Testing Laboratory. Click here for the BACnet PIC Statement.
1.2 LonMark Certification
LonMark International is the recognized authority for certification, education, and
promotion of interoperability standards for the benefit of manufacturers,
integrators and end users. LonMark International has developed extensive
product certification standards and tests to provide the integrator and user with
confidence that products from multiple manufacturers utilizing LonMark devices
work together. MSA Safety has more LonMark Certified gateways than any other
gateway manufacturer, including the ProtoCessor, ProtoCarrier and ProtoNode
for OEM applications and the full featured, configurable gateways.
ProtoCessor Design Guide
Page 6 of 29
PROTOCESSOR FAMILY OVERVIEW
ProtoCessor is a family of embedded or external low cost, high performance Building and Industrial
Automation multi-protocol gateways.
With one part number, the ProtoCessor products are pre-programmed to automatically support one to
many of the same or different OEM products to multiple different protocols.
This guide provides an overview to the ProtoCessor family of protocol gateway solutions and the steps
required to utilize each gateway option.
By adopting the ProtoCessor solution 140+ Industrial and Building Automation protocols are instantly
available. The ProtoCessor solution translates from a common Serial or Ethernet protocol on the OEM’s
controller to the desired field protocol (Serial, Ethernet or LonWorks).
The ProtoCessor is cloud ready and connects with MSA Safety’s SMC Cloud.
NOTE: For SMC Cloud information, refer to the SMC Cloud Start-up Guide online at
sierramonitor.com.
2.1 ProtoCessor Product Lines
2.1.1 ProtoCessor Embedded Modules
TTL to Serial, Ethernet and LonWorks (Section 6.2)
Marketing
Name
Ordering
Name
Interface Connections
Certifications
Serial
TTL
RS-485
RS-422
Ethernet
LonWorks
KNX
M-Bus
BACnet
BTL
LonMark
FFP-485
FPC-ED2
1
1
1
Yes
FFP-LON
FPC-ED4
1
1
1
Yes
Yes
FFP-ETH
FPC-F03
1
1
Yes
ASP-485
FPC-AD2
1
1
2.1.2 ProtoCarrier Daughter Cards
These cards are equipped with 3 ports (Section 6.3)
ProtoCarrier
Interface Connections
Certifications
RS-232
RS-485
RS-422
Ethernet
LonWorks
KNX
M-Bus
BACnet BTL
LonMark
Data
Boards
FPC-C34
2
1
Yes
FPC-C35
1
1
1
Yes
Yes
FPC-C36
1
1
1
Yes
FPC-C37
1
1
1
Yes
FPC-C38
1
1
1
Yes
FPC-C39
1
1
1
Yes
Yes
FPC-C40
1
1
1
Yes
FPC-C41
1
1
1
Yes
FPC-C42
1
1
1
Yes
FPC-C43
1
1
1
Yes
ProtoCessor Design Guide
Page 7 of 29
2.2 ProtoCessor Family of Modules
Full Function ProtoCessor (FFP) and Application Specific ProtoCessor (ASP): These modules are
designed on the OEM’s controller by implementing a ProtoCessor serial TTL socket (5V DC). See voltage
ranges in Section 4.1.2.
Marketing
Name
Ordering
Name
Interface Connections
Certifications
Serial
TTL
RS-485
RS-422
Ethernet
LonWorks
KNX
M-Bus
BACnet BTL
LonMark
FFP-485
FPC-ED2
1
1
1
Yes
FFP-LON
FPC-ED4
1
1
1
Yes
Yes
FFP-ETH
FPC-F03
1
1
Yes
ASP-485
FPC-AD2
1
1
2.2.1 FFP-485 ProtoCessor (FPC-ED2)
2.2.2 FFP-LON ProtoCessor (FPC-ED4)
2.2.3 FFP-ETH ProtoCessor (FPC-F03)
2.2.4 ASP-485 ProtoCessor (FPC-AD2)
ProtoCessor TTL socket
(underneath) - supporting RX
and TX signals – 5VDC
Ethernet port for field
protocol support and
diagnostics
ProtoCessor TTL socket
(underneath) - supporting RX and
TX signals – 5VDC
RS-485 (+-SG) port
for field serial
protocol support
Dip Switches for setting Node-ID,
BACnet MS/TP, MAC Address and
baud rate
ProtoCessor TTL socket
(underneath) - supporting RX and
TX signals – 5Vdc
Ethernet port for diagnostics and
host or field protocol support
20 Pin GIO expansion connector
(underneath)
Ethernet port for diagnostics and
Host or Field protocol support
RS-485 (+-SG) port
for field serial
protocol support
ProtoCessor TTL socket
(underneath) - supporting RX
and TX signals – 5VDC
LonWorks port (2-wire)
for field LonWorks
protocol support
LonWorks service pin
to commission chip
ProtoCessor Design Guide
Page 8 of 29
IMPLEMENT THE PROTOCESSOR FROM A HARDWARE PERSPECTIVE
3.1 How to Implement the ProtoCessor Socket on OEM Hardware
The OEM needs to implement a ProtoCessor socket on the board consisting of u-shaped 2 x 10 and 1 x 8
pin headers (reserved pins) which include the TX/RX signals power supply.
• This socket will accommodate any current and future ProtoCessor.
• The socket is populated only when the need for the protocol exists.
EMBEDDED SYSTEM
TTL LEVEL
SOCKET
PROTOCOL
Rx
Tx
APPLICATION CPU
(MICROCHIP PIC
AVR
8051
DS80C400 ETC)
Field Interface
(Modbus TCP/IP,
BACnet, EtherNet/IP,
etc.)
ProtoCessor
GND
0V
10
9
8
7
6
5
4
3
2
1
28 27 26 25 24 23 22 21
11
12
13
14
15
16
17
18
19
20
FRAME
GND
Rx
Tx
+5VDC @
500mA
Figure 1: Diagram of ProtoCessor Socket Layout
ProtoCessor Design Guide
Page 9 of 29
PROTOCESSOR SOCKET PCB FOOTPRINT – LAYOUT
4.1.1 Pin Assignment – ProtoCessor TTL Socket for 2x10 Header Pins
PIN #
Function
Direction
DTE Label
Comments
1
Frame Ground (FG)
Not DC Ground (0V)
2
VIN
3.3V-5.0V ±10%
3
TX
From ProtoCessor
TxD (out)
4
RX
To ProtoCessor
RxD (in)
5
CTS
To ProtoCessor
CTS (in)
6
RTS
From ProtoCessor
RTS (out)
7
DIO1
DSR (in)
Alternative I/O: SPI-SCK
8
DIO2
DTR (out)
Alternative I/O: SPI-CS
9
DIO3
DCD (in)
10
Reserved
11
0V
Circuit Ground
12
SCL
I2C Clock line – Open Drain,
10k Pull-up to VIN
13
SDA
I2C Data Line – Open Drain,
10k Pull-up to VIN
14
DIO4
RI (in)
Alternative I/O: SPI-MISO
15
DIO6
16
DIO7
17
DIO5
Alternative I/O: SDI-MOSI
18
DIO8
19
Reserved
20
Reserved
Figure 2: ProtoCessor Socket Footprint
ProtoCessor Design Guide
Page 10 of 29
21
RS-485 + (ISO)
I/O
Pass through Connection from Terminal
Block
22
RS-485 - (ISO)
I/O
Pass through Connection from Terminal
Block
23
RS-485 GND (ISO)
GND
Pass through Connection from Terminal
Block
24
RS-232 TX
OUT
Reserved (Not used)
25
RS-232 TX
INT
Reserved (Not used)
26
RS-232 TX
IN
Reserved (Not used)
27
RS-232 TX
OUT
Reserved (Not used)
28
Spare
I/O
Reserved (Not used)
Serial Peripheral Interface (SPI) is supported with signals: SCK, CS, MISO and MOSI
4.1.2 ProtoCessor Pin Voltage Levels
Description
Pin #
Min
Max
Unit
Input High Voltage
4, 5
2
5.5
V
Input Low Voltage
4, 5
0
0.8
V
Input High Voltage
All other inputs
2
3.6
V
Input Low Voltage
All other inputs
0
0.8
V
Output High Voltage
All Outputs except pins 12, 13
2.4
3.6
V
Output Low Voltage
All Outputs except pins 12, 13
0
0.8
V
4.1.3 ProtoCessor Pin Headers
ProtoCessor recommends use of the following SAMTEC Pin Headers on host board:
Part Numbers
TLW-1xx-x-S or MTLW-1xx-x-S
Manufacturer
SAMTEC
Link to Data Sheets
www.samtec.com/ftppub/pdf/tsw_th.pdf
ProtoCessor Design Guide
Page 11 of 29
Pin 20
Pin 10
4.2 ProtoCessor Socket Pin Locations
Once the headers are integrated onto the OEM’s PCB as shown in Figure 3, the ProtoCessor board will
then fit onto the header pins to provide embedded protocol support for the OEM product, shown in Figure
4. From a software prospective, there must be a serial protocol that is common to the OEM’s product and
the ProtoCessor on the TTL signals. (Section 3)
Pin 11
Header Pins
Samtec Part #
MTLW-110-05-T-S-195
Pin 1
Figure 3: Pin Locations
Figure 4: Attached ProtoCessor
ProtoCessor Design Guide
Page 12 of 29
Pin 21
Pin 20
Pin 10
Pin 1
Pin 10
Pin 21
Pin 28
(not shown)
Pin 11
Pin 20
Pin 10
Pin 1
Pin 20
Pin 11
4.3 Location of Pins on the ProtoCessor
4.3.1 FPC-AD2 (ASP-485)
4.3.2 FPC-ED2 (FFP-485)
4.3.3 FPC-F03 (FFP-ETH)
4.3.4 FPC-ED4 (FFP-LON)
Pin 28
Pin 11
Pin 1
Pin 21
Pin 1 (not shown)
Pin 10
Pin 28
Pin 11
Pin 20 (not shown)
ProtoCessor Design Guide
Page 14 of 29
PROTOCESSOR POWER REQUIREMENTS
1
Power Requirement for ProtoCessor ASP at 3.3V through 5 VDC
Standalone ProtoCessor
Combined with ProtoCarrier 485 V2
ProtoCessor Type Mk 2
3.3VDC
5 VDC
12VDC/VAC
24VDC/VAC
30VDC
FPC-AD2 (Typical)
100mA
120mA
80mA
40mA
40mA
FPC-AD2 (Maximum)
120mA
140mA
90mA
50mA
50mA
NOTE: These values are ‘nominal’ and a safety margin should be added to the power supply of
the host system. A safety margin of 25% is recommended.
Power Requirement for ProtoCessor FFP-Modules
Standalone ProtoCessor
ProtoCessor Type Mk 3
5 VDC
FFP-ED2 (Typical)
280mA
FFP-ED2 (Maximum)
350mA
FPC-ED4 (Typical)
280mA
FPC-ED4 (Maximum)
350mA
NOTE: These values are ‘nominal’ and a safety margin should be added to the power supply of
the host system. A safety margin of 25% is recommended.
1
Visit www.sierramonitor.com for the latest information.
ProtoCessor Design Guide
Page 15 of 29
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 Appendix A for 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.
6.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.
2
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
KNX-Device
ProtoCessor PSP Driver
Modbus RTU
DNP 3.0
M-Bus
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
KNX - ProtoNode/ProtoCarrier
KNX – Gateway -
ProtoNode/ProtoCarrier
M-Bus - ProtoNode/ProtoCarrier
JSON
2
Visit www.sierramonitor.com for the complete list of supported protocols.
ProtoCessor Design Guide
Page 16 of 29
6.2 ProtoCessor Device/Field Supported Protocols
6.3 ProtoCarrier Device/Field Supported Protocols
ProtoCessor Design Guide
Page 17 of 29
HOW PROTOCESSOR WORKS
7.1 Introduction
From a software standpoint, all three families of ProtoCessor work in the same fashion. ProtoCessor
functions as an embedded gateway, enabling the OEM’s equipment to rapidly utilize different protocols to
interface with various Building and Industrial Automation networks. The ProtoCessor solves
communication and protocol conversion problems, while enabling the OEM’s to focus on their core
expertise. The ProtoCessor’s extensive driver library provides a wide range of interoperability solutions.
The way our devices work is as follows:
• We take a CSV file and we map the memory registers of the OEM’s device to the various field
protocols properties.
• The CSV file gets down loaded to the ProtoCessor over Ethernet and the memory registers are
stored/managed in a data array inside the ProtoCessor.
• The ProtoCessor can be a master or a slave depending on what the OEM device is (master or a
slave).
• We poll the OEM’s device and continually update the registers in the data array. When the front
end (BMS) polls us on the field protocol side, we will server up to the front the most recent data
that is stored in the data array.
• This implementation allows the OEM the ability to instantly support any protocols that we support.
For the latest list of available drivers visit our website at www.sierramonitor.com.
7.1.1 Full Function ProtoCessor (FFP)
The FFP is user configurable, has more memory and supports multiple protocols. All modules have an
Ethernet port for remote diagnostics and configuration.
ProtoCessor Design Guide
Page 18 of 29
7.2 Configuration File for FFPs and ProtoCarriers
The driver configuration file (CONFIG.CSV) is in comma-delimited format which can be edited using
spreadsheet programs or any text editor.
Every FFP ProtoCessor has an Ethernet port. The port is used for remote configuration, diagnostics and
Ethernet protocol translation.
ProtoCessor point counts & certifications:
ProtoCessor
Point Count
Level 1
Level 2
Level 3
FFP-ETH
1200
N/A
N/A
FFP-485
1500
5000
10000
FFP-LON
1000
2500
4096
The CONFIG.CSV file is loaded into these devices through the Ethernet port. It can be retrieved using the
FieldServer FS-GUI (Graphic User interface) via Ethernet. Refer to the Sierra Monitor web page for more
information. Contact FieldServer technical services for assistance in mapping the configuration file to a
particular application.
FS-GUI’s most significant features:
• Set IP Address for field protocol.
• Generate XIF files for LonWorks network.
• Transfer files (CSV configuration, firmware, etc.) to and from the ProtoCessor.
• Monitor the ProtoCessor’s internal data and parameters, including Socket communications.
These are the communications between ProtoCessor and the Host CPU. It displays the TX and
RX packet communications, as well as the total number of bad packets.
• Change or update ProtoCessor internal data parameters.
• Delete files on a ProtoCessor.
• Restart the ProtoCessor.
• Create serial and Ethernet data captures for diagnostics.
• View error messages.
ProtoCessor Design Guide
Page 19 of 29
7.2.1 Application Specific ProtoCessor (ASP)
The ASP ProtoCessor has been designed specifically for OEMs with high-volume/cost sensitive products
requiring efficient but affordable protocol support. The ASP has been designed for “Plug and Play”
installation – no software is required. This is to ensure ease of installation and support by the OEM and
their customers.
The ASP supports up to 100-150 points mapped to the desired field protocol. The ProtoCessor is
programmed at the factory with a static mapping configuration which cannot be changed in the field.
Several different static mappings are supported via the DIP switch user defined functions. The two banks
of DIP switches enable the users to quickly configure the serial protocol settings without the need for any
3rd party software.
Settings available via the DIP switches include:
• BACnet MS/TP MAC Address
• Baud rate (including auto-baud setting for BACnet MS/TP)
• Node-ID
Four special user defined functions can be selected via the DIP switches. These functions could be
protocol or device related. For example, the same ASP ProtoCessor can be used on four different chiller
models. The DIP switches can be used to select the specific profile used on a specific model of chiller.
ASP’s have an optional 20-pin Expansion I/O Interface that includes:
• Twelve GPIO pins that can support any combination of 12 Digital I/O or Analog Inputs.
• Eight power pins (4 ground and four 3.3V pins) that can be used to power an external device up
to 500 mA at 3.3V (LED’s).
• To access the 20 pins, the 20 socket can be laid directly on OEM hardware or can be connected
with the use of a ribbon cable (needs to be purchased separately). Refer to Appendix B for
connectors and cables.
ProtoCessor Design Guide
Page 20 of 29
7.2.1.1 How to Implement and Test Any ASP ProtoCessor
• The OEM provides the Modbus register list for the product that the ASP-485 will be designed into.
• SMC programs, configures and tests the ProtoNode gateway with the Modbus register list that
was provided to support BACnet MS/TP. The ASP is not field programmable so the OEM must do
the testing for configuration on the ProtoNode or ProtoCessor FFP-485. Most customers will want
a proof concept before designing the ProtoCessor socket onto their hardware. The ProtoNode
allows OEMs to quickly create a proof of concept to provide their management team.
• SMC ships a pre-programmed sample of a ProtoCessor FFP-485 or ProtoNode with all the
configurations for the OEM’s product lines.
• SMC schedules a 60-minute walkthrough for setup and validation.
• The OEM connects their device to the ProtoNode via RS-232 or RS-485. The OEM can also wire
TTL signals that come off their micro controller and connect them to the ProtoCessor TTL socket.
All of this can be done without designing a ProtoCessor socket.
• SMC provides a BACnet Explorer that allows the OEM to fully test their product on BACnet
MS/TP from their office.
• Once the proof of concept is completed, the customer sends SMC the csv file from the ProtoNode
or ProtoCessor:
o No more changes to the config
o Customer starts ProtoCessor socket board spin
o Customer needs to purchase the PIC development tools
o SMC sends the customer the preprogrammed ASP
• SMC creates an ASP part number in Quick Base.
• SMC gets a blanket order.
• The OEM’s board comes back with the ProtoCessor socket on it.
• To validate the new hardware, the OEM can take the FFP-485 module off the ProtoNode and put
it on their new hardware to validate that the hardware is complete/functioning.
• The OEM then puts the ASP-485 on the hardware and validates it with the BACnet Explorer to
test that everything is working.
• The ASP-485 programming may need some scaling correction. When changes are needed:
o The OEM must inform SMC what alterations are required for each point
o SMC’s engineers will reprogram the ASP with the changes requested
o SMC sends the OEM a binary image to reprogram the ASP using the PIC tools
o This process continues until no more changes are needed
• SMC freezes the code.
• SMC ships the first production order.
• SMC provides an installation manual, showing how to install the product on BACnet.
• SMC provides customized webinar training for the OEM’s support team such as how to install and
diagnose problems in the field.
/
