Technical Forum

SIMATIC TDC, FM458, T400

Simadyn to Simadyn direct Profi connection

Thread Starter: SteveNordin   Started: 7/29/2011 1:31 AM   Replies: 9

« Previous thread Next thread »
Page 1 of 1 (10 items)
  7/29/2011, 1:31 AM
Joined 7/29/2011
Last visit: 7/29/2011
Posts: 2
Rating:
Rated: no ratings [0 out of 5 / rated 0 time(s)]. (0) 
Rated: no ratings [0 out of 5 / rated 0 time(s)]. (0) 

I am currently attempting to connect two Simadyn controllers together via Profibus, through an SS52 card in each rack.

One rack uses PM16 processors, the other a PM6.  I think I have properly set the Profibus communications up in each controller, but I keep getting flashing C's on initialization.  I am using ComProfibus 5.1 to configure the SS52 cards.

Has anyone ever successfully completed this task, and if so, how did you do it?  I'm going to continue trying different things, but I'm at a complete loss as to why it won't work.  Any help would be most appreciated.

Top
  7/29/2011, 5:25 AM
Joined 8/25/2006
Last visit: 5/18/2013
Posts: 898
Rating:
Rated: Excellent [4.2 out of 5 / rated 85 time(s)]. (85) 
Users with special expertise supervising conferences
Rated: no ratings [0 out of 5 / rated 0 time(s)]. (0) 
Hello.
Such configuration works well, even inside one rack with 2 SS52.
One SS52 should be a master and the other a slave. Check again your configuring, especially DP adresses, baudrates, AT/AR connectors and the matching of data lengths between racks and to ComProfibus configuration.
On what rack you have 'C'-error, master or slave? Look at outputs of @CSL2A block in that rack and post the values here. Also look at outputs of CTV/CRV blocks and post it here.



=== Edited by KSN @ 7/29/2011 5:40 AM [GMT ] ===


Top
Thank you for this post from:
  7/29/2011, 7:47 PM
Joined 7/29/2011
Last visit: 7/29/2011
Posts: 2
Rating:
Rated: no ratings [0 out of 5 / rated 0 time(s)]. (0) 
Rated: no ratings [0 out of 5 / rated 0 time(s)]. (0) 

Thanks for the quick reply.  At least I know this should work, and that I'm just not doing something right.

I've got the 16 bit rack looking okay, no 'C' on any processor, solid green and amber lights on the SS52, and 1's on the QTS and 578 and 612 on the YTS (no physical connection, due to the profi cable not being hooked up.)

On the 32 bit rack, I'm still getting a 'C' fault.  It looks to be something in the Profi configuration.  On the @csl2b ECL and ECO, I'm getting a 0 and a 1.  I checked the baud rates, both set to 1.5 mBaud, and I think I have the addressing correct.  I have the MAA at 11, and the ComProfibus configuration set to 11, also.  For the @crv/ctv blocks, there is no YTS, the QTS is 0 and the YEV is 00000000 00000001.

I think the probable issue is in the ComProfibus configuration.  I created a Profi network with the PM16 rack as a SS52 master, and the PM6 rack as a SS52 drive slave.  I then downloaded the same configuration file to both rack SS52's.  I think this is where I'm screwing up, but I have no idea of how to properly set this up.

Again, any help would be most appreciated. 

Top
  8/1/2011, 5:20 AM
Joined 8/25/2006
Last visit: 5/18/2013
Posts: 898
Rating:
Rated: Excellent [4.2 out of 5 / rated 85 time(s)]. (85) 
Users with special expertise supervising conferences
Rated: no ratings [0 out of 5 / rated 0 time(s)]. (0) 
Hello.
How do you load your ComProfibus configuration to each SS52? Using Profibus or using RS232?
I think you should pay attention when loading. If you load using Profibus, before loading to SS52 you must select in ComProfibus menu 'View' the right master system (e.g. Master system<1>, look at picture "2. Master system 1.jpg"), this is correspond to the master rack (in my example), and load to the SS52-master. Then you must select Master system<3> (look at picture "3. Master system 3.jpg") and load to the SS52-slave. If you load using RS232 you must create beforehand 2 separate .2bf files for each rack (again using menu 'View', switch between master/slave), and then load this two files to different SS52. I'm not sure, but I think you should also pay attention for address areas in slave properties in ComProfibus configuration. As I remember this areas should be filled (look at picture "4. Address areas.jpg").
I think your problem is that you load the same configuration (configuration for master rack) to the both SS52, that is selected by default in ComProfibus (look at picture "1. Network veiw.jpg").

Attachment: SS52.zip  (8 Downloads)



=== Edited by KSN @ 8/1/2011 5:33 AM [GMT ] ===



Top
  8/1/2011, 4:35 PM
Joined 9/24/2008
Last visit: 8/1/2011
Posts: 8
Rating:
Rated: no ratings [0 out of 5 / rated 0 time(s)]. (0) 
Rated: no ratings [0 out of 5 / rated 0 time(s)]. (0) 

Thanks for the information regarding the ComProfibus setup.

I'm using the RS232 connection, however I was not creating two separate files for the different SS52 cards.  I have done that, and have found what I think is my final issue (I hope.)

The @csl2b is now showung an ECO of 4, which is that my channels are not set up in struc for the channels expected by the ComProfibus setup.

I think this is an issue with my AR and AT addressing.  I cannot find anything that specifically shows how the 32 bit AT and AR are supposed to be configured.  I currently have them configured as

AT= SEND11.64.@2.D0400C.X03
AR =RECV11.64@2.D0400C.X03

Where SEND11 and RECV11 are my Channel names, 64 is the telegram length, 2 is the other node on the profibus network, and D0400C.X03 is the CS7 and SS52 card positions.

I'm pretty sure I have this incorrect, but I can't find anything to decscribe how to configure this.

Regards,
Steve

Top
  8/1/2011, 4:45 PM
Joined 8/25/2006
Last visit: 5/18/2013
Posts: 898
Rating:
Rated: Excellent [4.2 out of 5 / rated 85 time(s)]. (85) 
Users with special expertise supervising conferences
Rated: no ratings [0 out of 5 / rated 0 time(s)]. (0) 
snordin wrote:
AT= SEND11.64.@2.D0400C.X03
AR =RECV11.64@2.D0400C.X03

Hello.
That is the problem.
It shoul be:
AT=SEND11.0.0
AR=RECV11.0.0

where first "0" indicates that the channel operates itself as slave,
second "0" - means byte order (1- Motorola, 0 - Intel - for Simadyn D).



=== Edited by KSN @ 8/1/2011 5:02 PM [GMT ] ===


Top
Thank you for this post from:
  8/1/2011, 5:06 PM
Joined 9/24/2008
Last visit: 8/1/2011
Posts: 8
Rating:
Rated: no ratings [0 out of 5 / rated 0 time(s)]. (0) 
Rated: no ratings [0 out of 5 / rated 0 time(s)]. (0) 
KSN,

Thank you so much for your help.  I am now talking between my two test racks.  The addressing was the final piece that I needed.

I do have one last question, as this test was only part of my overall plan.  My goal is to link 7 Simadyn racks together on one Profi network.  If I understand everything I have learned from this, the only thing I should need to do differently between this 2 rack setup and the 7 rack setup is make 7 ComProfibus files, each one viewed from the respective controller.  Regarding the struc setup, address the 16 bit master just as I have it set now (RECVxx.xx.1/SENDxx.xx.1), and the 32 bit slaves as the 32 bit test rack is (RECVxx.0.0/SENDxx.0.0)   Is there anything else I should look for when moving from 2 racks connected to 7?

Thanks,
Steve
Top
  8/1/2011, 5:20 PM
Joined 8/25/2006
Last visit: 5/18/2013
Posts: 898
Rating:
Rated: Excellent [4.2 out of 5 / rated 85 time(s)]. (85) 
Users with special expertise supervising conferences
Rated: no ratings [0 out of 5 / rated 0 time(s)]. (0) 
AT, AR have the following syntax:

Channel_name.Address_stage1.Address_stage2, where

Channel_name - channel name - max. 8 characters,
Address_stage1 - slave address (3-123), or 0 if this channel operates as slave,

wrote:
Address_stage2 consists of a maximum of two characters:

1st. Character: Decentral peripheral device ("0") or drive ("1"). This merely defines the data location within the telegram. The data for a decentral peripheral device is deposited in "Intel Format" (low byte in front of high byte). The data for a drive are deposited according to the PROFIBUS profile Drive Technology (PPO types) in "Motorola Format" (high byte in front of low byte).

2nd. Character: If no specification is made, then the access to the Slave occurs as a parameter setting Master. The specification "R" implies that the access occurs as a read accessing second Master. The specification "R" is only possible for receive channels ("Shared Input").

Top
  8/1/2011, 6:26 PM
Joined 9/24/2008
Last visit: 8/1/2011
Posts: 8
Rating:
Rated: no ratings [0 out of 5 / rated 0 time(s)]. (0) 
Rated: no ratings [0 out of 5 / rated 0 time(s)]. (0) 
KSN,

Again, thank you for the information.  I have one more question, which I think I understand, but I have no way of testing beforehand to verify.

My plan is to have the 16 bit processor master, with the 6 32 bit processors as slaves.  I would also like to have each of the 7 processors talk to a iba DPM-s.  If I undertand correctly, I should be able to address each rack to rack communication as above, and then configure the DPM-s communication as if each rack is a master (SENDIBA.22.0 if IBA was node 22) and then configure the IBA module slave nodes to its respective rack.  Is there anything wrong with having the SS52 card act as a slave for some communications, and a master for others?
Top
  8/2/2011, 5:38 AM
Joined 8/25/2006
Last visit: 5/18/2013
Posts: 898
Rating:
Rated: Excellent [4.2 out of 5 / rated 85 time(s)]. (85) 
Users with special expertise supervising conferences
Rated: no ratings [0 out of 5 / rated 0 time(s)]. (0) 
Hello.
SS52 can be operated as master and as slave simultaneously, so I think your configuration will work. But may be you will need to change byte order for iba-slaves (SENDIBA.22.1 instead of SENDIBA.22.0).

snordin wrote:
Regarding the struc setup, address the 16 bit master just as I have it set now (RECVxx.xx.1/SENDxx.xx.1), and the 32 bit slaves as the 32 bit test rack is (RECVxx.0.0/SENDxx.0.0)

You must select the same byte order, when configuring data exchange between Simadyn racks, RECVxx.xx.1/SENDxx.xx.1 in master and slave or RECVxx.xx.0/SENDxx.xx.0 in master and slave.



=== Edited by KSN @ 8/2/2011 6:18 AM [GMT ] ===


Top
Page 1 of 1 (10 items)
Actions