Siemens Enhanced Driver Symbolic address not working with S7-1211C

Hi All,

I am facing an issue with the Siemens Enhanced Driver connection to a Siemens S7-1200 PLC. When I create the device connection using absolute addressing, it connects successfully. However, when I try to connect using symbolic addressing, the device goes into a “Reconnect Wait” state.

Here is Details of Setup -
TIA Portal: V16 V6
CPU: 1211C
Firmware Version: V4.3
Ignition Edge: 8.3.4

Here is Logs from Ignition.

Below things are already checked .
1- PLC is reachable (ping OK)
2-PUT/GET communication enabled in PLC protection settings
3- Access level set to Full Access

Any guidance or recommended configuration for stable symbolic communication with S7-1200 would be greatly appreciated.

Thanks in advance :slightly_smiling_face:

Can you share full logs? There should be a message about why the connection attempt failed that we're not seeing in your screenshot.

Just a note: PUT/GET access is not required for symbolic access.

1 Like

Here is screenshot of logs



Do you have secure connection disabled in the device connection config? If so, set it to Preferred instead.

EDIT: Alternatively, change the PLC config to allow unsecure connections. The error message you're seeing is logged when we try to connect unsecure (without TLS) but the PLC requires secure connections.

@Cody_Morgan I have tried both option Preferred & Disable but no success

In that case, I need the logs from when you tried with "Preferred" to be able to help. The PLC requires a secure connection, but the screenshot of your logs indicates that secure connections were disabled. The driver needs to attempt a secure connection, and I need to see what the error message is when the secure connection fails.

EDIT: If you don't want to upload your logs to the forum, but are willing to share the full upload via dropbox, you can do so here: Dropbox

Here are logs, as you can see First it tried to create Secure Connection & After its failover tried to create unsecure that also failed .



I think the logs are misleading you here. The log says "Error creating secure connection" but the inner exception message "AGL40_ONLY_SECURE_COMMUNICATION" indicates that the driver did not actually attempt to create a secure connection. This is an error that should only be returned when the PLC rejects an unsecure connection due to the PLC configuration requiring secure connections.

The log message is bad. Something more accurate would be "Error during first connection attempt...". The message is a holdover from when the driver always attempted a secure connection before falling back to an unsecure connection. Now that the user can disable secure connections, the log message is misleading.

That being said, if you really are confident that the logs you are showing me are from an attempt when the device connection was configured with secure connections set to "Preferred", then you should open a support case. This might indicate a bug in the underlying protocol library we use. But, even via support, you'll need to provide the full log file.

Alternatively, you can change the PLC config to not require secure connections. Or, try setting secure connections to Required in the device connection settings.