Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

Using SFC14 and SFC15 in 1200 program.

Created by: Gabriel de Oliveira at: 1/3/2012 2:15 PM (14 Replies)

Rating (7)

Thanks 10

Result pages:: |; 1 | 2; |

15 Entries

Entries per page: 10 | all

1/3/2012 2:15 PM	Rate (0)
Gabriel de Oliveira Bronze Member Joined: 2/16/2011 Last visit: 1/13/2025 Posts: 229 Rating: (28)	Hi; With S7300, I used the SFC14 and SFC15 to read a Profinet Slave and Works. But with S71200 and the same Slave when I use SCF14 and SFC15 it's return error code W#16#809, but the length of data is 6 bytes, that is more then 4 bytes. There are a special way to write and read data from a profinet slave with s71200 and with data consistency? Thanks
	Gabriel de Oliveira It Works? Rate It.
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users PiotrBzdrega

1/3/2012 2:52 PM	Rate (0)
not_my_fault Bronze Member Joined: 6/13/2006 Last visit: 9/17/2024 Posts: 123 Rating: (28)	Hi Gabriel, for consistent read/write of more than 64 bytes you have to use DPRD_DAT / DPWR_DAT (s. manual, page 269). Greetings, not_my_fault

Suggestion To thank Quote Answer

1/3/2012 6:12 PM	Rate (0)
Gabriel de Oliveira Bronze Member Joined: 2/16/2011 Last visit: 1/13/2025 Posts: 229 Rating: (28)	Thanks, OK,DPRD_DAT = SCF14,DPWR_DAT = SFC15 and, "If required, theseinstructions can be used for data areas of 1 byte or greater"(s.manual, page 269). But still not working. Att.
	Gabriel de Oliveira It Works? Rate It.
Suggestion To thank Quote Answer

1/3/2012 8:48 PM	Rate (0)
Denilson Pegaia Platinum Expert Joined: 9/23/2005 Last visit: 1/24/2025 Posts: 4397 Rating: (1464)	Hi, let me know if I undersoond correctly: 1 - You have PROFINET devices 2 - Youneed to read data consistently. 2 - You can use PROFIBUS blocks to do it ( DPRD_DAT and DPWR_DAT) is it? I suppouse that you don't need to use blocks to read PN data if it stay in the process image (read with Ix.y or IWz), can you test this supposition?
	Denilson Pegaia Siemens Industry Sector Technical Support
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users Tomy Master

1/5/2012 3:03 PM	Rate (0)
Gabriel de Oliveira Bronze Member Joined: 2/16/2011 Last visit: 1/13/2025 Posts: 229 Rating: (28)	Hello Mr. Pegaia; The device's adress is 256, so I've to use PIW256, or PIB256 or PIDW256. and works. wat's the process image range? I wanted to move the values to a struct with range of 3 DWords, so I'm using SFC14 and SFC15. Regards.
	Gabriel de Oliveira It Works? Rate It.
Suggestion To thank Quote Answer

1/5/2012 3:39 PM	Rate (0)
Denilson Pegaia Platinum Expert Joined: 9/23/2005 Last visit: 1/24/2025 Posts: 4397 Rating: (1464)	Hi, I suggest you try to address these values from process image (as IB256, IW256, ID256) directlly.
	Denilson Pegaia Siemens Industry Sector Technical Support
Suggestion To thank Quote Answer

1/11/2012 7:58 PM	Rate (2)
dsout Posts: 66 Rating: (5)	Hi Gabriel, Gabriel de Oliveira The device's adress is 256, so I've to use PIW256, or PIB256 or PIDW256. and works I'm glad you found a solution to your problem by using the process image. That's probably the best way to approach this. However, it might be useful to understand why SFC14 did not work like you expected. I think I can guess the problem. You used "256" as the "LADDR" input to SFC14. I can understand why you would do that. On page 269, the manual states s71200_system_manual Configured start address from the "I" area of the module from which the data will be read (DPRD_DAT) I think the manual is confusing on this point because a footnote on page 72 states s71200_system_manual The laddr input contains the hardware identifier of the device or functional unit which returned the error. The hardware identifier is assigned automatically when components are inserted in the device or network view and appears in the Constants tab of PLC tags. A name is also assigned automatically for the hardware identifier. These entries in the Constants tab of the PLC tags cannot be changed. So the LADDR is just some ID that was automatically generated. It is NOT the process image address. To find the LADDR id for your device, open "PLC tags->Default tag table" and then click the "System constants" tab at the top. This will show your device ID. You can drag and drop the device from the tag table onto the LADDR input on the SFC and it will fill in the value for you. I hope that helps clear up any confusion.
dsout Posts: 66 Rating: (5)	Last edited by: dsout at: 1/11/2012 8:01 PM
Suggestion To thank Quote Answer
This contribution was helpful to 3 thankful Users Gabriel de Oliveira ZNOAHR AutoGen_512436

1/11/2012 10:12 PM	Rate (0)
Gabriel de Oliveira Bronze Member Joined: 2/16/2011 Last visit: 1/13/2025 Posts: 229 Rating: (28)	Hello! I upload some pictures to explain the confusion. I was trying with address 256, see "Device.jpg" but other address apear in "SystemConstants.jpg".I will try with the costant and as soon as possible I will return. Thanks Dsout. Attachment SystemConstants.jpg (1703 Downloads)
	Gabriel de Oliveira It Works? Rate It.
Suggestion To thank Quote Answer

1/11/2012 10:15 PM	Rate (1)
Gabriel de Oliveira Bronze Member Joined: 2/16/2011 Last visit: 1/13/2025 Posts: 229 Rating: (28)	Other Picture. Attachment Device.jpg (1373 Downloads)
	Gabriel de Oliveira It Works? Rate It.
Suggestion To thank Quote Answer

1/25/2012 2:42 PM	Rate (1)
Gabriel de Oliveira Bronze Member Joined: 2/16/2011 Last visit: 1/13/2025 Posts: 229 Rating: (28)	Hello; Still not working with DPRD_DAT and DPWR_DAT. I'm reading da IW data end moving to DB and moving DB data to QW..and working. But I'm not happy with this solution... It's not totaly Integrated
	Last edited by: Gabriel de Oliveira at: 1/25/2012 2:42 PM Gabriel de Oliveira It Works? Rate It.
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on