Connection to Ignition with a ProFace HMI

Ignition
1

Hi,

We will implement Ignition in the factory in the next months. We already have determined what equipment will be connected to it. We will have Siemens PLC (S7 1500 type) and ProFace HMI (GP3500 and GP4000 for example, no PLC). So I have two questions for each one:
1- I have choice between the S7 driver and the OPC UA driver to communicate between the Siemens PLC and Ignition. What are the things I need to take in consideration if I want one more than the other ? OPC UA driver seems easier to put in place and to read/write PLC tags directly, but it has a number limit. And the S7 driver doesn't have the limit, but DBs in the PLC, and some other parameters have to be modified to let the connection works. What are your though about this ?
2- For the ProFace, it seems that it can't be connected to Ignition because the HMI acts only as OPC UA client, and it should be as a server (like a PLC). So drivers provided by Ignition can't work. Is it true ? If yes, do you have any tips to this problem ? (without buying a PLC just to make the connection).

Thank you.

2

  1. I'd use the built-in S7 OPC Server so far as possible. Only go the native driver route if you need the point quantity. (Do try to forecast that and do up front, though.)

  2. Yes, the Ignition OPC server can be exposed to external clients. But by default, it only listens to localhost. You will need to configure it to listen widely, and set up authentication.

1 Like
3

Thank you @pturmel for your answer.

What do you mean by "configure it to listen widely" ? I did a lot of research but nothing was useful...

4

Two approaches:

  • Configure the listening address to 0.0.0.0, the wildcard address. Ignition will then allow connections from any computer that can reach any of its IP addresses. This is what I mean by "listening widely".

  • Configure the listening address to an IP address of one of your computer's network interface. Do this if you cannot safely allow connections on all interfaces. You will then need to fix Ignition's own loopback connection to use the one address, too, as it won't be listening on localhost any more.