Compliance testing of IO-devices ================================ All Profinet products need to be certified. That is done after testing by an accredited PROFIBUS & PROFINET International test lab (PITL). The full hardware, communication stack and application software is tested together. Each manufacturer of Profinet equipment needs a Vendor ID, which is obtained from the PI Certification Office. The tests checks the GSD file, the hardware interface and the Profinet behavior. The user manual must be available. The tests should be performed on a device from series production. The Profinet equipment also needs to fulfill parts of the IEEE802 standards, for example uniqueness of MAC addresses. This is not tested by the test lab. A detailed description of the certification process can be downloaded from https://www.profibus.com/download/how-to-get-a-certificate-for-a-profinet-device/ General requirements -------------------- It should be possible to do a factory reset without an engineering tool. For example a hardware switch can be used. Routing of Ethernet frames must not be affected by a factory reset. A Profinet signal LED must be visible on the IO-Device. A callback is available from p-net to control the signal LED, so you can implement your board specific hardware. Tool for pretesting -------------------- For Profinet members, the "Automated RT tester" tool is available for download. It is useful for pretesting before a full compliance test. Profinet devices must fulfill "Security Level 1" with regards to the net load. This is not tested by the "Automated RT tester" tool. Installation of Automated RT tester on a Windows PC --------------------------------------------------- Unzip the downloaded file, and double-click the "AutomatedRtTester_2.4.1.3_Setup.exe" file. Adjust the Ethernet network card on a Windows PC ------------------------------------------------ To use the "Automated RT tester" tool you need to adjust the Ethernet interface settings of your PC. In the properties for the driver, go to the "Advanced" tab. For the "Packet priority & VLAN" select "Packet priority & VLAN Disable". More details are given in the "Product Documentation" document for the tool. You might also need to turn off LLDP protocol for the selected network interface. Both Windows and Simatic TIA can have LLDP implemented. Set IP address of the Windows PC -------------------------------- TODO Describe which address to use Supported GSD versions ---------------------- The "Automated RT tester" tool is compatible only with a few versions of GSDML files. See the document "PN_Versions_for_certifications" included in the download. Create a project ---------------- Use the menu File > New > "Device Test Project". Follow the wizard. Enter the MAC address of the IO-Device. On the "Profinet settings" page, select the GSDML file for the IO-Device. Populate modules/submodules in slots/subslots by marking a module in the left column, and then click the -> arrow. To insert a submodule, mark the relevant submodule in the left column and mark the appropriate slot in the right column. To remove from a slot or subslot, mark it (in the right column) and press the <- arrow. Adjust settings --------------- You need to adjust the device MAC address. This is done via the menu Tools > Options > DUT. Enter the value and press OK. If the device does not have support for remote change of values, you might need to adjust the device station name, IP address and subnet mask. This is done via the menu Tools > Options > Setting. You might need to click the "Show expert settings". Run tests --------- Select the tests (in the left side menu) to run. Failing tests are time consuming, so start with a single test to verify the communication. Disable all tests by the left side menu. Press the "Deselect all" icon. Then open "Automated test cases" > "Standard Setup" > DCP, and enable "DCP - DCP_IDN". Use the menu Project > Run. When communication is verified, enable all tests. Tips and ideas -------------- If you end up with ``Pass with Hint "The device made a EPM Request from a not Profinet port"``, that means that wrong source port was used when sending UDP messages. See the page on Linux in this documentation on how to adjust the ephemeral port range.