Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

AS235 and PROFIBUS-problems

Created by: AutoGen_432682 at: 10/9/2014 3:25 PM (5 Replies)

Rating (0)

Thanks 1

6 Entries

10/9/2014 3:25 PM	Rate (0)
AutoGen_432682 Posts: 5 Rating: (0)	Hei, I have a configuration with an AS235 on a PROFIBUS via a new CP581. PROFIBUS-slaves are ET200M, SIMOCODE, SIMOVERT (Masterdrive). Within the last months we had strange shutdowns of drives on SIMOVERTs, which look like a controled shutdown. Operators pretend not to have released any shutdown. Does anybody out there have any experience that points to the PROFIBUS communication in such a case? If yes, what could it be? I appreciate your feedback Regards HaSt
AutoGen_432682 Posts: 5 Rating: (0)
Suggestion To thank Quote Answer

10/13/2014 10:24 AM	Rate (0)
ram123., Posts: 56 Rating: (2)	Please give the following informations (1) when the sytem was commissioned first and how many days its is inservice (2) how many nodes are there (3) do u have a layout (4) what is the digonestic buffer information
ram123., Posts: 56 Rating: (2)
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users AutoGen_432682

10/13/2014 11:07 AM	Rate (0)
zahra hatampour Posts: 15 Rating: (3)	hi there I had dealt with such problem in profibus-DP. It seems that you have lost one of your slaves. in s7-300/400 we can check the diagnostic buffer of theCPU , if it happens it will be wrriten there by mentioning the slave number. It may happen because of loose connection in profibus connectors in that slave. I am not familiar with AS235 to help you about some programming tricks may cause that although it is unlikely.
zahra hatampour Posts: 15 Rating: (3)
Suggestion To thank Quote Answer

10/17/2014 4:09 PM	Rate (0)
AutoGen_432682 Posts: 5 Rating: (0)	Hi, thank you for your respons. I will try to give a brief answer to your questions. Maybe you or anybody will observe anything? 1. First commissioned approx. year 2000, modificationes performed in May 2014. (SIMOCODEs and ET200M separated onto different segments, as far as possible; Repeater at the end instead of active terminator.) 2. Total participants on this PROFIBUS: 19. No. 1 is the master, all others are slaves. See sketch in attachment. 3. See sketch in attachment. 4. I had no unexpected errors inside the message recording. ProfiTrace analysis and message record in the attachment. Attachment D:\Forum\Forum.zip (735 Downloads)
AutoGen_432682 Posts: 5 Rating: (0)
Suggestion To thank Quote Answer

10/17/2014 4:20 PM	Rate (0)
AutoGen_432682 Posts: 5 Rating: (0)	Hi Zahra, thanks for your answer. In the old TELEPERM M equipment we doesn't have as advanced and convenient analysis asthe S7. If you like, you could take a look into the attachment (analysis)to another answer I gave on this subject. Loose connection might be a point. We have to have a new check on that. Regards HaSt
AutoGen_432682 Posts: 5 Rating: (0)
Suggestion To thank Quote Answer

10/18/2014 5:12 AM	Rate (0)
ram123., Posts: 56 Rating: (2)	Dear sir, (1) While checking the profibus - Profitrace volatges are around 4.66 to 6.56 means that the profibus system is healthier condition (2) Only flying fault is coming. (3) We faced the same problem in our system several times and finally resolved after 7 months of trail and error method. (4)Please check the following (a) Chcek the 24V going to the modules (b) check the profibus cable has been laid in a root where is no power cable interference is there ( generally this faults will come when the power cable interference is there) (c) Some times this fault will exactly during the particular operation time only. If it happens in your system or not. (d) How the cables are laid.(wherther through the seperate GI pipe) (e) what is the approximate length of the cable between the different nodes? (g)is there any joints ie the cable laid directly to the module or through TB or joints
ram123., Posts: 56 Rating: (2)
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Related topics by keywords:

Follow us on