Kevin,
The flexy is acting as the OPCUA Server. We don’t have an OPCUA Client.
I don’t understand what the IP addresses you mentioned have to do with anything? Those are the addresses for the ABLogix, which are working correctly now. Even when they are turned off we still have the issue with the OPCUA errors.
The connection between the Flexy(OPCUA Server) and the PC is a direct connection, there is no firewall so yes, the 4840 port is open.
I’m not sure what you are asking for with the settings and certificates. That information was in the backup we supplied was it not?
What error are you talking about suggests that the endpoint is inactive?
Let me restate the issue at hand to try to gain some clarity and see if we can’t get focused on the problem at hand, because it feels a bit like we are just stabbing in the dark right now.
When the OPCUA Server is enabled we get records in the Real Time Logs like the following every 10-15 seconds:
Every 3-4 minutes when the OPCUA server is enabled, the flexy restarts on its own and when it comes back up we get this message in the event logs:
We are connecting to 2 different ABLogix PLCs and we are seeing the Tag values change now. We were getting errors associated with that previously, but that was because we mistakenly had the wrong IP addresses in the topic setup. That is fixed now though and we don’t seem to be having any trouble with that.
We have tried reducing the problem down to find what part is causing the “UA ServerMain stopped due to error” issue. We tried disabling the ABLogix topics, removing all Tags, deleting all certificates, and none of that stopped the “UA ServerMain stopped due to error” issue from occuring. It seems to me like the issue is that the UA Server is getting some kind of error which eventually causes the flexy to reboot itself. I just can’t figure out what that error is. It seems to happen irrespective to any of the IOServer configurations or Tag configurations, or Certificate configurations.
We have a project that is totally held up by this issue and we don’t seem to be making a lot of progress with the back and forth emails. I would like to request either getting this issue escalated to someone who can help us understand what the 0x80050000 means or at the very least get someone on the phone who can walk us through the troubleshooting live. Right now it seems like you are asking us to do a bunch of things that don’t seem directly related to the issue at hand or that we have already illiminated and the time lapse between email communication is dragging things down. Please let me know what we can do to accellerate a resolution.
Thanks,
Justin