Siemens Symbolic disconnect after adding certain tags

Ignition
1

Hi everyone,

I’m still running into a similar issue. When I add just a few UDT tags, everything works as expected. But once I add more, the tags become disconnected.

Refreshing the browse or disabling/enabling the connection doesn’t change anything, I keep seeing the same log message.

image

I’m currently on version 8.3.0 LTS.

Has anyone encountered this before or found a solution?

Thanks in advance!

1 Like
2

This looks like a similar issue that we've recently seen, but we have had trouble consistently reproducing it.

Are you attempting to read from a number of String tags? If so, you can try to disable the String tags to see if that alleviates the issue.

If you can provide the following info, it may help us narrow down this issue.

  • An Ignition tag export
  • MLFB for your PLC (You can get this by reading the MLFB diagnostic tag)
  • PLC firmware version (You'll have to retrieve this from the TIA Portal, but make sure you are "Online" so that you see the version on the PLC and not just the version stored in the project)
  • TIA Portal Version, including the update number, if any. (E.g.- TIA Portal V20 Update 3) You can get this by going to Help > Installed software ... in the TIA Portal.

If any of this info you would prefer not to share via the forum, you are welcome to upload to this dropbox folder. Dropbox

3

Hi Cody,

Thanks for the response!

Removing the string parts did indeed do something with performance. We were able to create the largest amount of tags so far.

I will provide you the tag export in the Dropbox link.

Here is the other information:

image
image994×432 22.6 KB

image
image416×293 4.27 KB

Thanks in advance!

Best regards,
Ben

1 Like
4

This is starting to look like a bug in the Siemens PLC firmware v4.0.0.

A hotfix (Hotfix 1) for PLCSim Advanced V7 Update 1 was released 2 days ago. I am not sure which version of the firmware PLCSim Advanced used before the hotfix, but the KB says that Update 1 now uses firmware v4.0.4. After applying the hotfix, I can no longer reproduce this issue.

Another user has reported to us that updating their PLC to firmware v4.0.4 has also resolved the issue for them.

I'm still trying to confirm 100% that this is a bug in the firmware that is resolved in 4.0.4, but I am confident enough at this point to recommend updating. If you do update, please let us know how it goes for you.

Thanks!

1 Like