Does someone got the Siemens driver working with a PLC on firmware V4 and Tia V20?
Before upgrading firmware from V3 to V4 and from Tia V18 to V20 was the communication working.
How i get in the log that a password i required
DEBUG
SymbolicAddressSpace
08Jan2026 10:07:36
Failed to load symbols
DEBUG
SymbolicAddressSpace
08Jan2026 10:07:36
Failed to load symbols. Error: 'AGL40_SYMBOLIC_PASSWORD_REQUIRED', '0xFFFA010C' SError: 'AGL40_SUCCESS','0x0'
DEBUG
SymbolFsm
08Jan2026 10:07:36
S(LOADING) x E(LoadSymbolsFailure[cause=de.deltalogic.accon.aglink4.AglIOException: Method: 'symbolic_LoadAGLinkSymbolsFromPLC', Error Code: 'AGL40_SYMBOLIC_PASSWORD_REQUIRED', Error Nr: '0xFFFA010C', Error Message: 'AGL40_SYMBOLIC_PASSWORD_REQUIRED',]) = S'(LOADING_WAIT)
DEBUG
SiemensS7Client
08Jan2026 10:07:36
This connection requires a password for symbolic access.
DEBUG
SiemensS7Client
08Jan2026 10:07:36
Error occurred while setting password for the PLC connection.
From what i see in Tia Portal configuration the password is the same as previously.
Here the setting in Ignition
Given the issues, I would suggest v4.0.4 and see if that helps. If anything, it might get you away from other bugs that have popped up in that firmware.
I just did a test with a fresh PLC and start we a blank TIA project and that one was working. So i assume there is a configuration in our standard project that need to be done.
I think i found the issue,
During the upgrade from V18 to V20 the access level management in Tia portal has been changed by Siemens.
By rerun the security wizard and select the following option.
I think the library IA is using doesn’t maybe support the new user management method.
Anyway this solved our issue.
Quick other question, is it logical that everytime a add and extra tag in the PLC i need to do a rebrowse in the gateway ? I though this was only needed if you want to see your tag in the device browser. But i create a tag and manually enter the opcPath and the tag stays in Error until i did the rebrowse.
I think the library IA is using doesn’t maybe support the new user management method.
You're right, good find.
Quick other question, is it logical that everytime a add and extra tag in the PLC i need to do a rebrowse in the gateway ? I though this was only needed if you want to see your tag in the device browser. But i create a tag and manually enter the opcPath and the tag stays in Error until i did the rebrowse.
Yes, unfortunately it is necessary to refresh the browse cache even if you know the OPC item path. The driver doesn't make a request to the PLC using the item path. The driver retrieves symbol information from the PLC and uses that information to look up the tag's ID using the item path. If that item path doesn't exist within that symbol information, the driver is unable to find the ID needed to make a request to the PLC. Refreshing the browse cache on the gateway is the only way to tell the driver to update the symbol information from the PLC.
PS:
I can enter a password for the Full access level and this is the password needed for Ignition
FYI, I think you can get by with a password that only allows read access, if you only need to read from the PLC.