1510SP-1PN OPC-UA server to computer browser

Hi all,

I have a question about connecting to 1510SP-1PN OPC-UA server from computer browser on the same network.
OPC-UA server address is 10.184.64.60:4840, and i can ping this IP from my laptop.
However, when I type 10.184.64.60:4840/browse in Chrome/Iexplorer, i do not get any response from OPC-UA server...
Can you please tell me why it's not working?

I intend to use Invoke-WebRequest command in Windows Powershell to read tags from PLC.
Many thanks!

p.s. i used the same way to connect from the same laptop to KepwareEx IoT gateway, and it worked perfectly. Connection string was xx.xx.xx.xx.port/iotgateway/browse to expose all tag names, and then https://xx.xx.xx.xx:xxxx/iotgateway/read?ids=Channel1.Device1.Tag1

rodmanlt said:

Hi all,

I have a question about connecting to 1510SP-1PN OPC-UA server from computer browser on the same network.
OPC-UA server address is 10.184.64.60:4840, and i can ping this IP from my laptop.
However, when I type 10.184.64.60:4840/browse in Chrome/Iexplorer, i do not get any response from OPC-UA server...
Can you please tell me why it's not working?

I intend to use Invoke-WebRequest command in Windows Powershell to read tags from PLC.
Many thanks!

p.s. i used the same way to connect from the same laptop to KepwareEx IoT gateway, and it worked perfectly. Connection string was xx.xx.xx.xx.port/iotgateway/browse to expose all tag names, and then https://xx.xx.xx.xx:xxxx/iotgateway/read?ids=Channel1.Device1.Tag1

Click to expand...

I've never heard of that being a supported feature of the built in OPC server on a PLC. They do have a web page you can activate, though, and even load custom web pages into.

Thanks for your reply! I struggled to find ANY documentation explaining how to use OPC-UA server in 1500 type plcs.. only brochures with general information, but nothing to the level of detail I need...
You're talking about webserver feature, which is not the same as OPC-UA server, as far as I understand it...
I'm pretty sure that OPC-UA server is activated on the plc, as I managed to connect to it with android app called Prosys OPC UA client, and it allowed me to browse for tags first, and then subscribe for certain tags and see them live on the phone. Connection string(aka Uri) in Prosys was opc.tcp://10.184.64.60:4840
But OPC-UA client on the phone is not exactly what I need...

OPC UA offiicial specifications also support an http:// and https:// protocols, but many OPC UA server implementations do not support it. Even more in industrial automation where the binary protocol opc.tcp:// is used almost exclusively.

Furthermore, connecting to an OPC UA server is a multi-step process:
- Open secure channel
- Get Endpoints list
- Create Session
- Activate Session

... and I doubt that a simple browser will execute that sequence correctly

Ok, that's why opc.tcp:// string worked from the phone and http(s):// string didn't work from the computer....

You helped me to formulate a question to Siemens support... All I need to ask them is if 1500 OPC-UA server supports http(s):// protocols...?

lfe said:

... and I doubt that a simple browser will execute that sequence correctly

Click to expand...

Yes it's not a browser itself.
In Windows Powershell, there is a command InvokeWebRequest, which I used successfully to get tags from KepwareEx OPC server.
You need to know endpoints first. This can be done in browser by typing [http://IP: port/browse] in the address bar.
Or, if you know tag names already, type in address bar [http://IP: port/read?ids=tag name] and it returns tag value.

Again, this works in KepwareEx.
I get data from KepwareEx with Invoke WebRequest command in powershell and push it to live PowerBI stream, and I see live data in PowerBI..Visuals in PowerBI are just amazing...

But I want to bypass KepwareEx at all, thus I can use Invoke WebRequest on 1500 PLC not on Kepware..

I think that I found the best document which explains S7- 1500 OPC-UA server configuration in every detail. However, only opc.tcp:// are used in all examples, not http://
Entry ID: 109737901
https://cache.industry.siemens.com/dl/files/901/109737901/att_898965/v3/109737901_OPC_UA_Client_S7-1500_DOKU_V10_en.pdf


added: quote from Communication Function Manual, 10/2018, A5E03735815-AG
Independence of a specific transport layer
The following transport mechanisms are currently supported by OPC UA:
– The transfer of messages as a binary stream directly via TCP/IP
– The transfer of messages with XML over TCP/IP and HTTP. This transport mechanism allows only a slow transfer and is therefore almost never used. The S7-1500 CPUs do not support this transport mechanism.



Ok, so http:// is not supported, as lfe suggested earlier

Thread can be closed

Connection to the KEPServerEX IOT Gatway was done with REST or MQTT. That is not the same as OPC UA. OPC UA iuses completely different calls and methods. You need an OPC UA CLient to get the data from the OPC UA server in the S7-1500. you could use the OPC UA Client Driver in KEPServerEX to get the data and then connect your web client to the IOT GAteway and get the data.