Ignition Connect to Siemens OPC-UA

I have 1 siemens PLC, 1500 brand, it have the opc-ua inside, it is in the same IP with Server , as the upside picture i have success connect to it .

but in the real production line, the PLC IP is 172.16.127.2, i need use a NATR to switch it to the same ip as the ignition server,

this is when i configure the

most of the case it will shows

but sometimes the step4 can show as the following picture

it will failed at step6

but i use kepware to read

it can browse the tags by means of OPC-UA

TAG READ IS OK

My question is , if the kepware is ok , that means the plc and network should be ok , but why ignition failed, how to set ignition successfully read the opc-ua tags?

Make sure you're entering the URL and not just the IP and port number. In your screenshot you only entered the IP and port without the opc.tcp:// prefix. That's required if I recall.

i have set as you mentioned,

it still report fault

if i skip the advanced configure and go to the following steps

it shows fault

Try making your discovery URL: opc.tcp://10.84.50.3:4840/discovery

i have tried, but still now works

At this point, I'd check your logs and possibly even turn on debugging on whichever logger is generating the error to see if you can get any more detail on what the problem could be.

You are routing through a network address translation device. Use the "Endpoint Host Override" setting. Try this:

Discovery URL: opc:tcp://172.16.127.2:4840

Endpoint URL: opc:tcp://172.16.127.2:4840

Endpoint Host Override: 10.84.50.3

(Might need Discovery to be opc:tcp://10.84.50.3:4840. I avoid Siemens like the plague....)

I have tried the upside three choice, all of them are failed

When testing Kepware, are you doing it from the Ignition server or another PC?

Your IP addresses suggest you have an oversized subnet unless you have a router or firewall between Ignition and your NATR device. 10.84.x.x and 10.90.x.x are at a minimum a /12 (255.240.0.0 subnet) with over 1 million usable IPs. If you are using a firewall or router between these and you're not testing Kepware from the Ignition server, I suspect you have a network issue. It could be routing (are all default gateways configured properly?) or a firewall blocking it.

On a separate note, if your subnet really is that large, I highly suggest rethinking your network architecture. That large of a subnet means you have a huge broadcast domain and if you're not having problems yet, you will eventually.

Ignition and Kepware Server are in the same server, if the network setting or PLC have issue, how can kepware read success without issue and ignition not able to read

Were you able to look at the ignition logs or enable debugging on them to get additional error information?

	{
		"name": "drivers-request-cycle-10.84.50.3",
		"id": 25028,
		"state": "WAITING",
		"daemon": true,
		"system": "OPC",
		"scope": "Gateway",
		"cpuUsage": 0,
		"waitingFor": {
			"lock": "java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@2c37ae6e"
		},
		"stacktrace": [
			"java.base@17.0.18/jdk.internal.misc.Unsafe.park(Native Method)",
			"java.base@17.0.18/java.util.concurrent.locks.LockSupport.park(Unknown Source)",
			"java.base@17.0.18/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionNode.block(Unknown Source)",
			"java.base@17.0.18/java.util.concurrent.ForkJoinPool.unmanagedBlock(Unknown Source)",
			"java.base@17.0.18/java.util.concurrent.ForkJoinPool.managedBlock(Unknown Source)",
			"java.base@17.0.18/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(Unknown Source)",
			"com.inductiveautomation.xopc.driver.api.BlockingRequestQueue.waitForNext(BlockingRequestQueue.java:123)",
			"com.inductiveautomation.xopc.driver.api.BlockingRequestQueue.take(BlockingRequestQueue.java:111)",
			"com.inductiveautomation.xopc.driver.api.BasicRequestCycle.run(BasicRequestCycle.java:127)",
			"java.base@17.0.18/java.lang.Thread.run(Unknown Source)"
		]
	}
here is the log in the thread

That's the thread, not the log. Look in your live diagnostic logs, not the thread dump. If you're using the diagnostics bundle it will be in the wrapper.log file.

If you're not required to use v8.3.7 I'd suggest updating to v8.3.10 as there have been several updates regarding OPC-UA in the last several versions and it's possible they could fix things for you. Even if they don't you'll know you're on the latest version so if you reach out to support that is something they won't have to have you do as a troubleshooting step for them.

still not works when update to the latest version , i will reach out to support, thanks a lot

when have NATR, setting like this, it works

image

So, what I suggested in comment #7 above. Why did you mark your own comment as the solution?

You can see my setting is a little different from your suggestion.

the first IP should NATR IP, then it works, connection can be connected and tag can be browse.

Last time your suggestion almost is correct, appreciate your and team support, so when I have the answer, i share to others

If you read Phil's suggestion he did suggest what you said in the last sentence to try those settings also.