Skip to Content

SiePortal

The integrated platform for your product selection, buying and support workflow - bringing together Industry Mall and Online Support.

SiePortalDeutsch

Search

Home
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menu temporary not available
- Menue temporary not available
- {{item.title}}

Products & Services
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
MySiePortal MySiePortal
{{(apiData.MySiePortal | filter:{'rank':1}:true)[0].title}} MySiePortal
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Cart ({{apiData.CartCount}})

Navigation

Can see Profinet slave but not reachable online

Created by: FieryWind at: 7/13/2017 3:28 AM (4 Replies)

Rating (4)

Thanks 3

5 Entries

7/13/2017 3:28 AM	Rate (1)
FieryWind Posts: 1 Rating: (1)	Hi, I am using CPU315-2 PN/DP connected with an Anybus Profinet slave. By checking accessible devices, I can see the PLC, the hub and the slave device. So I set the IP address of the slave as 192.168.0.11, name as tm10e3. I can ping the device. However once I get online, then TIA Portal shows the slave is not reachable and communication is not successful. In the diagnostic status, it just shows "not reachable". Deep appreciation to any help of reminding me some settings that I missed. I attach some screenshot of the status and some settings. Attachment Assign name.png (981 Downloads)
FieryWind Posts: 1 Rating: (1)
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users jonesb

7/13/2017 10:18 AM	Rate (0)
Pittiplatsch Posts: 1368 Rating: (128)	Hello, normally I would says "Proof device name"...but in you case, it seems to be not the problem. You can Ping the device and the name seems correct. Do you can read out diagnostic data of Device AND Controller? Maybe, the online/offline configuration of device is not identical? Topology is wrong?
Pittiplatsch Posts: 1368 Rating: (128)
Suggestion To thank Quote Answer

10/3/2017 6:08 PM	Rate (0)
jonesb Posts: 2 Rating: (3)	I also have a similar problem. Running TIA Portal V13 SP2. TIA Portal reports that the Profinet block is "not reachable" but the processor is does not have a bus fault and I am receiving IO data from the block in question. So everything appears to be working but I cannot receive diagnostic data from the block in TIA Portal. I have about 12 other blocks that are set up the same way that are working properly and I can see diagnostics. The name and IP address are also correct in the profinet devices. I currently am not using the topology feature - the devices are not connected to each other on that page. FieryWind Hi, I am using CPU315-2 PN/DP connected with an Anybus Profinet slave. By checking accessible devices, I can see the PLC, the hub and the slave device. So I set the IP address of the slave as 192.168.0.11, name as tm10e3. I can ping the device. However once I get online, then TIA Portal shows the slave is not reachable and communication is not successful. In the diagnostic status, it just shows "not reachable". Deep appreciation to any help of reminding me some settings that I missed. I attach some screenshot of the status and some settings.
jonesb Posts: 2 Rating: (3)	Last edited by: jonesb at: 10/3/2017 6:11:26 PM
Suggestion To thank Quote Answer

10/3/2017 9:50 PM	Rate (3)
jonesb Posts: 2 Rating: (3)	Just as an update, I was able to fix my problem by re-compiling all hardware and downloading.
jonesb Posts: 2 Rating: (3)
Suggestion To thank Quote Answer
This contribution was helpful to 2 thankful Users wolves and hawks SirJack

2/4/2022 2:10 PM	Rate (0)
SirJack Posts: 2 Rating: (0)	jonesb Just as an update, I was able to fix my problem by re-compiling all hardware and downloading. Thank you! This helped me too.
SirJack Posts: 2 Rating: (0)
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on