 |
|
 |
| |
PROFINET CBA OVERVIEW |
| |
PROFInet Unplugged – An introduction to PROFInet CBA |
|
| Page 13 of 13 | first page | « previous page | next page » | last page |
|
PROFINET CERTIFICATION |
| |
Unlike Profibus, all PROFInet devices must pass certification prior to product launch. The Certification Office of the Profibus User Organization is responsible for establishing test centers where PROFInet devices can be certified. The first PROFInet test center is located in Germany. A US Test Center is expected in late 2003.
Certification of a PROFInet device is a three step process. First, the parts of the PROFInet software core modified by the developer and the PROFInet Object Model are tested for compliance with standards. Second, the XML file supplied by the product developer is used with an Engineering tool to test interoperability. In this test interconnections are made between the interfaces of the Device Under Test (DUT) and other PROFInet devices. Third, the PROFInet device is connected to a network of other PROFInet devices to determine how well the device works on a loaded network. |
| |
|
| |
HOW TO GET STARTED |
| |
The PROFInet Runtime Core software can be downloaded free of charge (membership required) from Profibus International as a zip file. Porting PROFInet to a specific RTOS requires the developer to port each PROFInet component. The components to port include the DCOM, RPC, Auto Marshaller and the ACCO. The PROFInet Integration manual provides individual instructions for the porting of each of these components.
Prior to starting this effort the developer should have a background in the Microsoft RPC, COM, DCOM and C++. An extensive background in the specific operation of your RTOS, the operation of your TCP/IP stack and the fundamentals of your processor are also important.
PROFInet implementation is not without challenges. Porting of your PROFInet core to your embedded RTOS is a significant challenge. The PROFInet core is designed for windows. Cores for embedded systems are not yet available as of this writing (February 2003). It is a major effort to port the PROFInet core to a non-windows RTOS. Some of the more challenging aspect of this integration effort include mapping of the Windows memory management services, real time clock functions and DCOM to the embedded system. Significant resources are required of the target device. The PROFInet core contains a large number of source files with significant code and memory requirements including non-volatile memory. |
| |
|
| |
Contact  for specific requirements. |
|
|
Solutions: |
|
|
|
| |
|
|
|
|
| Page 13 of 13 | first page | « previous page | next page » | last page |
 top of page |
|
|
