EasyManua.ls Logo

MSA ProtoCessor FPC-ED2 - How to Implement and Test any ASP Protocessor

MSA ProtoCessor FPC-ED2
29 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
6.2.2 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.
MSA Safety programs, configures and tests the 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
ProtoCessor FPC-ED2. Most customers will want a proof concept before designing the ProtoCessor socket onto their
hardware. The ProtoCessor allows OEMs to quickly create a proof of concept to provide their management team.
MSA Safety ships a pre-programmed sample of a ProtoCessor FPC-ED2 with all the configurations for the OEM’s
product lines.
MSA Safety schedules a 60-minute walkthrough for setup and validation.
The OEM connects their device to the ProtoCessor 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.
MSA Safety 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 MSA Safety the csv file from the ProtoCessor:
No more changes to the config
Customer starts ProtoCessor socket board spin
Customer needs to purchase the PIC development tools
MSA Safety sends the customer the preprogrammed ASP
MSA Safety creates an ASP part number in Quick Base.
MSA Safety 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 FPC-ED2 module off the ProtoCessor 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:
The OEM must inform MSA Safety what alterations are required for each point
MSA Safety’s engineers will reprogram the ASP with the changes requested
MSA Safety sends the OEM a binary image to reprogram the ASP using the PIC tools
This process continues until no more changes are needed
MSA Safety freezes the code.
MSA Safety ships the first production order.
MSA Safety provides an installation manual, showing how to install the product on BACnet.
MSA Safety provides customized webinar training for the OEM’s support team such as how to install and diagnose
problems in the field.
ProtoCessor Design Guide 18

Table of Contents