April-10th-2019, 08:42 PM
In order to let TIA portal detect the netPI on PROFINET via the DCP protocol your netPI needs a physical connection to the PC the TIA portal is running on.
This can be done either via an ordinary ethernet switch or using the embedded switch of the S7 PLC in case it has two physical ethernet ports.
Also the example program needs to run, else the Industrial Ethernet controller in netPI stops all PROFINET communication. So make sure the PNS example program is up and running and printing to the console screen that it is triggering the watchdog.
Since setting a PROFINET name of a slave device over DCP protocol is a very common thing for Hilscher and all our provided PROFINET devices, also Hilscher offers a DCP detection and name setting tool for Windows here: https://kb.hilscher.com/download/attachm...msi?api=v2
Try this program instead of TIA and right click to the found netPI and set a device name with it.
Thx
This can be done either via an ordinary ethernet switch or using the embedded switch of the S7 PLC in case it has two physical ethernet ports.
Also the example program needs to run, else the Industrial Ethernet controller in netPI stops all PROFINET communication. So make sure the PNS example program is up and running and printing to the console screen that it is triggering the watchdog.
Since setting a PROFINET name of a slave device over DCP protocol is a very common thing for Hilscher and all our provided PROFINET devices, also Hilscher offers a DCP detection and name setting tool for Windows here: https://kb.hilscher.com/download/attachm...msi?api=v2
Try this program instead of TIA and right click to the found netPI and set a device name with it.
Thx
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
