did one of you ever get the OPC link up and running? Currently my small demo consists of a EFM 1.5 installed locally on Windows and a simulated OPC-UA server running on a separate Windows machine.
The documentation on github describes the following:
For the "add connection" action:
name: any name
host: the network name of the PC which is running the OPC server(s)
domain: in most cases, this should be localhost
user: name of the windows account (on the host PC) which is running the server(s)
password: password of this windows account
Note that if you only need your connection for connecting to XML-DA servers, you only need the "name" parameter. XML-DA servers are not tied to a specific PC, so they may be accessed from any connection
For the "add server" action:
name: any name
server prog id: this should be something like "Kepware.KEPServerEX.V5" or "Matrikon.OPC.Simulation.1", however, the dslink will usually automatically discover the OPC servers running on the host PC and give you a drop-down list of server ids to choose from.
Unfortunately with the syntax so far no successful connection came off
The open source OPC link to which you refer is for connecting to OPC-DA servers only, not OPC-UA. To connect to an OPC-UA server, you will need an OPC-UA link. Cisco has created an OPC-UA link that is currently in beta. Please contact your Cisco account rep to arrange for download of that link.
Industrial customers are increasingly realizing the importance of digitization to compete and stay relevant in today's business environment. Any digitization efforts involve connecting thousands of sensors and devices to the network, extracting and proces...
This example shows ICPAM integration to VSM 7.12
Principal of operation:
SENSOR_CONNECTOR will connect to ICPAM & register the callback endpoint. Currently SENSOR_CONNECTOR is registering endpoint for all types of events available in ICPAM.
You have confirmed that EFM is running, and you can open a broker connection using port 8080 or 8443 from the EFM server. However, from an external broker, not hosted on the same machine, the connection is refused.
Is this is your fi...
EFM broker connection to upstream EFM server is failing. You have confirmed that the IP connectivity to the destination port number (tcp/443 by default) is open, yet the connection does not establish from the EFM broker to the EFM server.
EFM v1.6.1 IOx application now supports passing parameters via GMM.
This capability now enables configuring an upstream broker for that EFM node via GMM UI.
Step 1: Install EFM 1.6.1 IOx app within GMM
Step 2: Deploy this app on a gateway (The upst...