Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

Schenck Master DISOCONT as DP Slave

Created by: G_R_E_Y_31 at: 3/6/2015 7:14 AM (4 Replies)

Rating (1)

Thanks 5

5 Entries

3/6/2015 7:14 AM	Rate (0)
G_R_E_Y_31 Bronze Member Joined: 5/26/2011 Last visit: 8/5/2024 Posts: 456 Rating: (7)	Hello experts! Does anyone have an example of Schenck Master DISOCONT integration to S7-400 via PCS7 as Profibus DP Slave? I'm given the GSD file attached which consists of 4 different data lenght of the same title (DISOCONT MASTER PCI, 32 bytes/64bytes/32words/64words input and output module). We've tried first the 32-bytes one but it has an error (red slash on HWConfig online). Then we tried the 64 words and the error was eliminated. We used SFC14 and 15 since the GSD says consistent. The HWConfig address of the 64W input module starts with 1270 and output 656 so we put 16#6B8 and 16#290 on the SFC input "LADDR" respectively. We created a shared DB for input and output (DB202 and DB203) which contain 128 byte (64words) and that's what we put on the SFC "RECORD" (in PCS7 you the textual value field isn't configure unlike on Step 7 so we interconnected the RECORD to the DB202, which seems the only address acceptable, instead of inputing textually P#DB202.DBX0.0 byte 128 as the help says) and we have 0 Retval to both SFC14 and 15/no error). Now everything is fine, or so it seems.. We cannot read any inputs from the Schenck Master DISOCONT! We don't have any value (0) monitoring on the absolute address (on GSD via HWConfig monitor) or on the destination DB202. This means there's a problem since if we established the communication successfully, we should have values somewhere. We also tried to give command but also failed. Where do you think we failed? Also please check the Schenck Master DISOCONT integration manual, on the address list (P.8 onwards), I noticed the output (command) seems exactly 32 bytes (8x4-bytes groupings) but the input (returnings) seems more than 64 words! (both including "KME" optionals on count, whatever that is). But even not including KME, inputs and outputs aren't identical in lenght as the GSD file. Is it possible we are using the wrong GSD file? Thanks for any response! Attachment Schenck Master GSD and Manual.zip (450 Downloads)

Suggestion To thank Quote Answer

3/9/2015 7:14 AM	Rate (0)
G_R_E_Y_31 Bronze Member Joined: 5/26/2011 Last visit: 8/5/2024 Posts: 456 Rating: (7)	Anyone please?

Suggestion To thank Quote Answer

6/2/2015 9:59 AM	Rate (1)
G_R_E_Y_31 Bronze Member Joined: 5/26/2011 Last visit: 8/5/2024 Posts: 456 Rating: (7)	Just want to update, this configuration we did was actually correct, the failure to communicate or read/write was due to settings on the Schenck side. What I also learned here is that the data could actually be monitored on Simatic Manager Hardware Configuration already (on the Schenck GSD file), which has also similar value to the consistent read/write SFC14/15 input/output DB, that is, it would seem that we could actually have done this communication without the use of those SFC (at least we have confirmed it on the read, since it seems it's better to use DB on write due to data retention of DBs).

Suggestion To thank Quote Answer
This contribution was helpful to 2 thankful Users S_Moderator Samit84

8/23/2016 5:12 PM	Rate (0)
Samit84 Member Joined: 10/28/2010 Last visit: 4/7/2024 Posts: 1 Rating: (0)	Kindly share a sample of codes exchanging a particular data like "Set point" or "Acknowledge Error". It will be really helpful. Thanks.

Suggestion To thank Quote Answer

9/1/2016 10:46 AM	Rate (0)
aag_03 Posts: 84 Rating: (2)	Hello! See my old step7 program with Schenk Disocont slaves in attachment please. Look in FC1, FC2, DB11, DB12 etc. It works properly from 2008 till present. May be it will be useful for you. Attachment DOZ_b2.zip (262 Downloads)
aag_03 Posts: 84 Rating: (2)
Suggestion To thank Quote Answer
This contribution was helpful to 3 thankful Users rb4 Mentor ISFAHAN

|

Share this page:

Share this page on...

Follow us on