Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

SFC 51 or SFC 59????

Created by: Maselo at: 2/4/2013 8:28 PM (14 Replies)

Rating (5)

Thanks 1

Result pages:: |; 1 | 2; |

15 Entries

Entries per page: 10 | all

2/4/2013 8:28 PM	Rate (0)
Maselo Experienced Member Joined: 1/12/2011 Last visit: 3/14/2023 Posts: 68 Rating: (0)	Dear experts! We have a S7 with: Rack0: CPU 317-2 PN/DP + 8x 8BH10-0AB0 Rack 1: 2x 8BH10-0AB0 So, total = 160 output channels to wire-break monitoring. We need to read only wire-break diagnostics (see Byte 9 to 24 - data record 1 - from the attached doc). What is the best: SFC 51: SSL_ID W#16#00B3 (All diagnostics data of 1 module) with a DB block to storage all the 16 channels faults... But, how can I check all these 10 modules if SFC 51 accepts only 4 jobs by project? Or... is SFC 59 (module by module too) better?? Regards Attachment 6ES7322-8BH10-0AB0.pdf (476 Downloads)
	Last edited by: Maselo at: 2/15/2013 12:19 PM Last edited by: Maselo at: 2/6/2013 1:11 PM Last edited by: Maselo at: 2/5/2013 7:21 PM
Suggestion To thank Quote Answer

2/14/2013 8:36 PM	Rate (0)
Maselo Experienced Member Joined: 1/12/2011 Last visit: 3/14/2023 Posts: 68 Rating: (0)	No ideas???? Ok, I will summarize my question... We know that is possible to use OB 82 with SFC 51, but how to use just one SFC 51 job to check 10 modules if the CPU accepts up to 4 SFC 51 jobs??? Please, see the example of of Module Diagnostics in attached PDF file. Regards. Attachment SFC 51.pdf (779 Downloads)

Suggestion To thank Quote Answer

2/28/2013 4:57 PM	Rate (1)
Cicero Gold Member Joined: 10/10/2005 Last visit: 3/16/2023 Posts: 1909 Rating: (132)	Hello, I think it is better to call for each module the system function SFC51 and use for each module an own structured variable. So you can avoid to overwrite one variable with an other diagnosic module. See also an example: http://support.automation.siemens.com/WW/view/de/31895566 With best regards Cicero

Suggestion To thank Quote Answer

3/6/2013 1:32 PM	Rate (0)
Maselo Experienced Member Joined: 1/12/2011 Last visit: 3/14/2023 Posts: 68 Rating: (0)	Hello Cicero! I'll take a look to check how it works! Thanks!

Suggestion To thank Quote Answer

3/27/2013 9:23 PM	Rate (0)
Maselo Experienced Member Joined: 1/12/2011 Last visit: 3/14/2023 Posts: 68 Rating: (0)	Dear Experts! I mounted a rack with 1 CPU 317-2 PN/DP and 1 8BH10 (with diagnostics enabled). Is working fine, without no fault red LEDs. I wrote a STL program with OB82 (SFC 51 inside) and SFC 59 inside OB1, to get data record 1 of the system data. I choose 2 DB blocks with 25 bytes each to storage all the card diagnostics. In both SFCs I got the same code error (RET_VAL) = 877F that means "CONNECT parameter: Internal error such as an invalid ANY reference", for Ethernet FB 65 "TCON" (I'm not using it!)... Because this error, when I disconnect a wire from 1 or more channels was nothing in the DBs blocks (I did DR = DB1), just 00h in all bytes... I'm not using the Ethernet comms, but is it really necessary to config FB 65 "TCON" to fix this error to the SFCs working well?? Thx All!

Suggestion To thank Quote Answer

5/21/2013 6:18 AM	Rate (0)
Maselo Experienced Member Joined: 1/12/2011 Last visit: 3/14/2023 Posts: 68 Rating: (0)	Hi, all! Please, see these print screens images (inside attached zip file): SFC59 - normal but code 877F.jpg - The CPU and DO cards normal, faulty LEDs off, but SFC59 returns 877F error code (communication). SFC51 - normal no event.jpg - OB82 was not called yet, so no error code. SFC51 - wire break incoming.jpg - SFC51 returns the same 877F (34687) code. SFC51 - wire break outgoing.jpg - SFC51 returns 877F again!!??? I did this test using another CPU (315-2 DP) and the problem kept... Page 23 from "Open TCP/IP Communication via Industrial Ethernet" manual ( http://a248.e.akamai.net/cache.automation.siemens.com/dnl/jM2MTI2NDMA_22146612_DL/T-Bausteine_e.pdf ) 877F - CONNECT parameter: Internal error such as an invalid ANY reference Please, any suggestions??? Attachment SFC51&59.zip (297 Downloads)

Suggestion To thank Quote Answer

5/21/2013 10:39 AM	Rate (1)
Aret Posts: 2348 Rating: (259)	index =16#8000 is clearly not correct, here should be logical base address SZL header created as struct of 2 words or just as dword? DB1 and DB2 are downloaded to PLC? Can try to use P#DB1.DBX0.0 BYTE 16 for DR1 What diagnostic options you enabled in module properties in HWKonfig? Upd. Error 87xx means there is a problem with 7th parameter - DR, so please check carefully is you created this as struct with proper data
Aret Posts: 2348 Rating: (259)	Last edited by: Aret at: 5/21/2013 10:43 AM
Suggestion To thank Quote Answer

5/21/2013 4:44 PM	Rate (0)
Maselo Experienced Member Joined: 1/12/2011 Last visit: 3/14/2023 Posts: 68 Rating: (0)	Thanks Aret Aret index =16#8000 is clearly not correct, here should be logical base address I used a Siemens manual example for SSL list (See SFC 51.pdf file in the 2nd topic post) . See the OB82_example.jpg from print_screens.zip attached file. I copied this example from the manual "Help on Standard and System Functions" (Example of Module Diagnostics with SFC51 (RDSYSST)) but it not work... So I did some changes and created 2 separeted DBs without success... Aret SZL header created as struct of 2 words or just as dword? 2, see: SZL_HEADER : STRUCT LENTHDR : WORD ; N_DR : WORD ; END_STRUCT ; Aret DB1 and DB2 are downloaded to PLC? Yeah! Aret Can try to use P#DB1.DBX0.0 BYTE 16 for DR1 I will try it! Aret What diagnostic options you enabled in module properties in HWKonfig? See the attached files Diagnostics.jpg, CPU_channel_error.jpg and DO_channel_error.jpg from print_screens.zip Aret Upd. Error 87xx means there is a problem with 7th parameter - DR, so please check carefully is you created this as struct with proper data Ok, I will check it! Attachment print_screens.zip (216 Downloads)

Suggestion To thank Quote Answer

5/22/2013 8:18 AM	Rate (1)
Aret Posts: 2348 Rating: (259)	Well, in Siemens example they just set highest bit with OW 16#8000. I would really recommend placing SFC51 call in OB1 (you can exclude OB82 call-ups then) and use logical address of module in INDEX field just as SFC51 help says. IOID should be 55 for output module. When this will work you can think about moving this code to OB82.
Aret Posts: 2348 Rating: (259)	Last edited by: Aret at: 5/22/2013 8:32 AM
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users amcorgd

5/22/2013 2:05 PM	Rate (0)
Maselo Experienced Member Joined: 1/12/2011 Last visit: 3/14/2023 Posts: 68 Rating: (0)	Aret Well, in Siemens example they just set highest bit with OW 16#8000. I would really recommend placing SFC51 call in OB1 (you can exclude OB82 call-ups then) and use logical address of module in INDEX field just as SFC51 help says. IOID should be 55 for output module. When this will work you can think about moving this code to OB82. Thanks! I already had done this forSFC59 in OB1, but returned the same constant error 877F (without or with wire break) .. But now I did a new test for SFC51 in OB82 using P#DB1.DBX0.0 BYTE 25 for DR1 and it works without errors!!! ... So the problem was this DR1 parameter as you asked me to try! Many thanks! After this success I tried to do the same for SFC59 in OB1 and the error was changed from 877F to 00C4 (without wire break) and to 8090 (with wire break). Maybe it needs to work in OB82 (calls only when a fault occurs). I will do more tests. Well, I need to choose what is better to use in my project: SFC51 or 59... Best regards!

Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Related topics by keywords:

Follow us on