How to connect the OPC Client with Matrikon OPC DA Simulator?

Hi Pablo!

I Agree with Rickard, Using OIGateway to talk to a OPC Server is introducing an unnecessary step in your system.
But there are indeed reasons for doing so, If you want to avoid OPC over network you could have OI Gateway on the same node as the OPC Server and then use Suitelink to communicate remotely with OI Gateway, thus removing the OPC over network communication.

But looking at your setup, the correct syntax for addressing on a remote object would be 

OPCMatrikon_001.Random.OPC.DeviceGroup.Random.Int1

Best way to verify is using object viewer.
The use of Item references can be applied as a step 2, once you have verified connection, if needed.

I note that you have checked the Use scan group as access path, this would break the above address, since it will insert the scangroup name in your final address, on a incorrect position, this selection could be applied on other OPC servers, not OI Gateway, since OIGateway has the "OPC.DeviceGroup" in the access path.

I would omit this selection for simplicity in your testing.

If you would set up the OPC object against the Matrikon OPC server, without the OIGateway involved, the config would be simpler.

Please note that I'm avoiding naming my scangroup to Random to make the following example more clear.

Then your syntax would look the following: OPCMatrikon_002.Fast.Random.Int1

<DeviceIntegrationObject>.<ScanGroup>.<Path.Item>

In this case you could apply the Use scan group as access path method.

Naming your Access name "Random" and removing one part of your address.

Result would then be: OPCMatrikon_002.Random.Int1

<DeviceIntegrationObject>.<ScanGroup/Path>.<Item>

I hope this clears things out.

If you at this point still have issues connecting, it must be some security or network related issues, but since this is such a late reply to your post, you might have resolved all of your issues already 

Hi Pablo!

I Agree with Rickard, Using OIGateway to talk to a OPC Server is introducing an unnecessary step in your system.
But there are indeed reasons for doing so, If you want to avoid OPC over network you could have OI Gateway on the same node as the OPC Server and then use Suitelink to communicate remotely with OI Gateway, thus removing the OPC over network communication.

But looking at your setup, the correct syntax for addressing on a remote object would be 

OPCMatrikon_001.Random.OPC.DeviceGroup.Random.Int1

Best way to verify is using object viewer.
The use of Item references can be applied as a step 2, once you have verified connection, if needed.

I note that you have checked the Use scan group as access path, this would break the above address, since it will insert the scangroup name in your final address, on a incorrect position, this selection could be applied on other OPC servers, not OI Gateway, since OIGateway has the "OPC.DeviceGroup" in the access path.

I would omit this selection for simplicity in your testing.

If you would set up the OPC object against the Matrikon OPC server, without the OIGateway involved, the config would be simpler.

Please note that I'm avoiding naming my scangroup to Random to make the following example more clear.

Then your syntax would look the following: OPCMatrikon_002.Fast.Random.Int1

<DeviceIntegrationObject>.<ScanGroup>.<Path.Item>

In this case you could apply the Use scan group as access path method.

Naming your Access name "Random" and removing one part of your address.

Result would then be: OPCMatrikon_002.Random.Int1

<DeviceIntegrationObject>.<ScanGroup/Path>.<Item>

I hope this clears things out.

If you at this point still have issues connecting, it must be some security or network related issues, but since this is such a late reply to your post, you might have resolved all of your issues already 

Thank you for your answer! I finally fixed this using AVEVA EDGE as an OPC DA Server though and it worked just fine, it didn't work before probably because the version I used of matrikon was the free one.

I'll keep in mind hough your comments!

Thank you very much again!