Disabling F-link connections

We are using multiple F-link connections, but depending on the environment / project not all of the F-link connections are used. When F-link receive is not active, I have activated the PASS_ON input of the system datablock, to request passivation for that F-link connection.

At software level everything is fine.

But when visiting the PLC, the PLC display indicates that there is an error and the error is that the F-link connection has been passivated. Maintenance is required. Also HW configuration online view shows that the PLC has an active error. And diagnostic buffer shows that the unused (but passivated) F-link connections have raised an error that has not been cleared.

Is there any method to configure the F-link so that this error / maintenance request is not activated? I have intentionally disabled the F-link connection: I don't want to get an error from it.

The only way I can figure out is to add some dummy connections: When I know that this specific project does not use F-link connection ABC, I will create a dummy communication so that the PLC will talk to itself using the F-link connection ABC. But this feels like a lot of extra work. And it will require me to add even more F-link connections for those projects that do not use all of the F-link connections. (The senders.)

Perhaps you can remove unused F-links?

Or, change the address to the same IP as the PLC and loopback unused F-Links (if that is even possible).

However, the best suggestion is to do what the F-Link documentation states, for support, submit a "Support Request" (using gray bar link above these online forums) and create a new request.

This software, so it is not like optional hardware where options handling is a possible solution.

However, you might put each F-Link call inside an FB that requires a bool (bit) input, like "F-Link_DB".PLC[plcConstant1] where "PLC" is an array of bool and plcConstant1...plcConstant"Max" are either true or false, "depending on the environment / project".  Set the constants and if FALSE, the associated F-Link call gets disabled before it can inject any error or require software passivation.

My best suggestion is ask Siemens.  There may be some internal DB tag available that performs the enable/disable for you.

Elonen

We are using multiple F-link connections, but depending on the environment / project not all of the F-link connections are used. When F-link receive is not active, I have activated the PASS_ON input of the system datablock, to request passivation for that F-link connection.

At software level everything is fine.

But when visiting the PLC, the PLC display indicates that there is an error and the error is that the F-link connection has been passivated. Maintenance is required. Also HW configuration online view shows that the PLC has an active error. And diagnostic buffer shows that the unused (but passivated) F-link connections have raised an error that has not been cleared.

Is there any method to configure the F-link so that this error / maintenance request is not activated? I have intentionally disabled the F-link connection: I don't want to get an error from it.

The only way I can figure out is to add some dummy connections: When I know that this specific project does not use F-link connection ABC, I will create a dummy communication so that the PLC will talk to itself using the F-link connection ABC. But this feels like a lot of extra work. And it will require me to add even more F-link connections for those projects that do not use all of the F-link connections. (The senders.)

I created a support ticket to Siemens and got this reply:

Siemens

"Unfortunately, this is not possible. If the two controllers are started at different times, the Flexible F-Link communication must be acknowledged once. When communication is running, an interruption of the connection is detected at the latest after expiry of the configured timeout. The Flexible F-Link communication is then passivated, and the set replacement values are output. And you will receive the timeout error message, this can’t be deactivated.

What we would recommend, if possible, with the costumer configuration, the failsafe communication via SENDDP and RCVDP since the new version a variable DP_DP_ID can be used and set 0. As of version V3.0 of the SENDDP and RCVDP instructions, no connection is established at the DP_DP_ID input for a F-communication ID "0". So, in your case if the partner is not available, the DP_DP_ID for the specific connection must be set 0 and you will not receive an error due to the fact the communication won’t be established.

Information cab found under the following links: SIMATIC Industrial Software SIMATIC Safety - Configuring and Programminghttps://support.industry.siemens.com/cs/ww/en/view/54110126/171181021067Variable assignment F-Communication ID (DP_DP_ID)https://support.industry.siemens.com/cs/ww/en/view/109767139"

 So once a F-link connection has been defined, it must be operational or else it will generate an error that shows up in diagnostics buffer and error led. Workaround would be to use alternative communication method (DP_DP) but it is not suitable for us due to large amounts of data being transferred.

I guess I need to create dummy connections so that the unused F-links will appear to work from PLC point of view.