10/21/2019 12:53 PM | |
Joined: 8/3/2009 Last visit: 9/23/2024 Posts: 13759 Rating: (1738) |
Hello here are examples for both: https://support.industry.siemens.com/cs/ww/en/view/109768964 https://support.industry.siemens.com/cs/de/en/view/109478798 Bye Murof |
If this Information really helps, you could use the Rate function |
|
4/23/2023 1:55 PM | |
Joined: 2/25/2019 Last visit: 9/15/2024 Posts: 6 Rating: (1) |
F-Link is awesome but can be confusing to work with at first. This tool relies on a mechanism the binds the data to a pre-process and post-process with the safety code in between. This means whatever communication method you use for F-Link you are at the mercy of. So if you choose TCP/IP to route safety then you are choosing a non-deterministic communication method. I-Device is deterministic meaning it bound to a known timing bus in Profinet. TCP/IP doesn't afford these luxuries, however, Profinet does not provide routing. So, if you can afford a high enough failsafe-monitoring time then go with F-Link it is easy and you can send alot of safety data quickly. If you are expecting this to be high speed failsafety reactions, then maybe reconsider. Alternatively, Idevice is used on a single network but does give you faster speeds. One more reason F-Link was created was to send more safety data. If you check the Safety I-device method it only provides two words worth of transmission possibilities. So you end up using alot of block for this. With F-link and TCP/IP, you can extend the possibility with larger data volumes than can be sent in one instruction. Technically you could use F-Link with iDevice, or OPC UA, UDP, or Modbus TCP. It is dependent on what you put in the Pre-Post Processing as the mechanism. The example shows TCP/IP using the Open user communication blocks. The catch here is to know what your cycle time is set up for on safety. This is going to limit how fast you can send and receive on F-Link. Also control when the OUC blocks are called by using a Cyclic Interrupt. Rule of thumb, whatever your F-Monitoring time is, you ideally want to be able to send and receive data twice as fast as the monitoring time. This is because you must process the data on the send and the other PLC must now receive it and process it. If you create a cyclic, and decrease the cycle time on the safety code also keep a close watch on the overall PLC cycle time. It can become a balancing act if you have a small F-monitoring time. In this sense, hopefully, you can see how I-Device solves a lot of the non-deterministic issues TCP/IP creates. See Pg. 18 for the comparison: F-Link Example Hope this can help anyone else out in the future. Attachment109768964_Flexible_F-Link_DOC_V10_en.pdf (258 Downloads) |
Last edited by: AutoGen_9215938 at: 04/23/2023 14:01:09Last edited by: AutoGen_9215938 at: 04/23/2023 14:03:42Last edited by: Jen_Moderator at: 04/24/2023 09:33:12PDF attached from link. |
|
Follow us on