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

HW Compilation error (SOLVED!!)

Created by: Bryll at: 8/30/2014 5:09 PM (5 Replies)

Rating (0)

Thanks 2

6 Entries

8/30/2014 5:09 PM	Rate (0)
Bryll Posts: 168 Rating: (5)	Hi I got this error (picture) when I recompiled the hardware after changing addresses for I/O data for profibus communication with a couple of inverters. I also added three new components to communicate on the profibus network. No changes have been made to the profinet settings, or the two ET200S units on the profinet. Attachment hw error.jpg (159 Downloads)
Bryll Posts: 168 Rating: (5)	Last edited by: Bryll at: 8/31/2014 9:34 AM
Suggestion To thank Quote Answer

8/30/2014 5:50 PM	Rate (0)
Bryll Posts: 168 Rating: (5)	The hardware error disappeared I disconnected the CPU from the profinet connection, and then reconnected it and the ET200S units. Now all is up and workinng, but I don't know the real reason for the error.
Bryll Posts: 168 Rating: (5)
Suggestion To thank Quote Answer

8/30/2014 6:21 PM	Rate (0)
William_B Posts: 5225 Rating: (1202)	Thank you for letting us know. Please consider editing the title of this thread and putting "solved" in there. Greetings. w
William_B Posts: 5225 Rating: (1202)
Suggestion To thank Quote Answer

8/31/2014 9:35 AM	Rate (0)
Bryll Posts: 168 Rating: (5)	Sorry for that, I've corrected it now
Bryll Posts: 168 Rating: (5)
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users William_B

8/31/2014 12:21 PM	Rate (0)
0_Einstein Diamond Expert Joined: 7/7/2010 Last visit: 3/20/2025 Posts: 15736 Rating: (2488)	Bryll Sorry for that, I've corrected it now I do not pretend to know profinet (there is a communications conference... they will understand it better). However, I understand practical issues around profinet communications. If you have a working profinet system where all the devices have been joined together into a profi"net" during their device startups and begin communicating because some profinet "master" (your plc) has the proper profinet name and ip address configured. When the master (plc) goes into run mode, it starts the profinet startup or connection process. It does a special setup with each profinet device to establish all the diagnostics, health, and so forth to verify what telegrams they will share, get it all setup and ready to go. Once each device and the plc "agree", the diagnostics for that device goes "green" in portal and telegrams are being shared at whatever speed they have agreed upon during their "getting to know one another" connection startup. Now that each device is happy, imagine taking the plc offline and changing the hardware configuration and downloading again. It may very well upset all those profi"net" devices who had agreed "this is how we will talk to each other". There may be a profinet reset connection option for each field device, but that is apparently an advanced topic that portal does not seem to directly address as it does not give us "reset connection" option anywhere I have seen. By power cycling the remote devices, they restart their connection with the plc and get into a new agreement. The new agreement may look just like the old one, but with the plc having new hardware configuration downloaded and plc restarted, the remote device may think of that as a new plc device. Again it is just a practical approach. In summary, if you have a advanced network like profinet and the plc hardware configuration is downloaded, you may need to power cycle any profinet field devices to restore communications. At the very least, pull the network connection and reinsert just to see if that does a "reset" for you as well. Any profinet expert is most welcome to amend, correct, and expand on my practical approach. [please]
	science guy
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users William_B

8/31/2014 6:18 PM	Rate (0)
William_B Posts: 5225 Rating: (1202)	Hi huggy_d1. Profinet is not just putting Profibus on an ethernet line. The trouble is that the Profinet network has x3 modes of operation. For an explaination of sorts see [LINK]. Something that you have to remember about Ethernet TCP/IP (one of Profinet bases) is that the role of sender an receiver is in flux. There is no real fixed master as we see in Modbus RTU and Profibus. But I think this discussion is beyond what was asked in this thread. As for your descriptions.. in principle the restart re-initialised the communications and established the network in a proper way much as you are explaining. Greetings. w
William_B Posts: 5225 Rating: (1202)
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on