- Kepware opc server manual how to#
- Kepware opc server manual password#
The message format required from IBM are: Once connected, you can validate that the data is sent to the broker and can be used for dashboarding or other services. In this example, we are going to select the _time_second tag and add it to the agent: For example: Ĭlick Finish to complete the Agent Configuration Add a Tag from Kepware by clicking Add IoT Item
Kepware opc server manual password#
Password: The password is the authentication token specified in the device information. Username: The fixed string “use-token-auth” is used as username to indicate that a token is being used. The MQTT client ID is in the format d:orgId:deviceType:deviceId. Click Next to reach the next configuration page The value can be any string that is valid in MQTT.Īs such, the format we will use is iot-2/evt/ event/fmt/ jsonģ. Common content type values include but are not limited to “json”, “xml”, “txt”, and “csv”.
Kepware opc server manual how to#
format_string is a string that defines the content type of the message payload so that the receiver of the message can determine how to parse the content. When receiving these event messages, the subscribing application can either use a wildcard to receive events with any ID or subscribe with an event_id that matches the event_id that the publisher used. The event ID can be any string that is valid in MQTT. event_id is the ID of the event, for example status. The required topic format is: iot-2/evt/ event_id/fmt/ format_string Therefore our final URL will be: ssl://.com:8883 The connection to IBM is using the SSL version at port 8883. Select MQTT Client from the drop down Configuration for the MQTT Agent are as follow:Īppend the organization id to “.” for the hostname. The complete documentation can be found here: 
The protocol used to connect to Watson is via MQTT. Step 2: Configuration of the KEPServer EX IoT Gateway Under Security, you may leave the Auth Token blank to auto generateīy now, you will have the required connection parameters for the connection:
Enter Device Type and Device ID as required for your data modeling and click Next and follow the wizard to reach the summary page. Select Add Device at the right corner of the UI. Once Logged in, your organization ID are displayed at the top right:. Launch the IBM Watson IoT Platform by clicking Launch Select the appropriate plans and click Createģ. Create the IoT Platform by searching for it in the search box. Step 1 : Configuration of IBM Watson’s IOT Platform This guide assumes:įamiliarity with KEPServerEX’s OPC UA Server Configuration as well as the concepts in operating KEPServerEX. I did an export of the OPC UA and as the default config publishes all variables on OPC UA we are way over the 30000 limit of OPC UA Nodes.In this post, I will documenting on the process for sending data to IBM Watson Cloud Platform. *Did the same configuration on another 1518 CPU and it worked directly but we need the other one running as well.Īnyone has an idea why the PLC dont listens on the OPC UA port when we activate the functionality in the TIA? The PLC never starts to listen on the port specificed in TIA, tried also to scan all ports but no luck.Įdit: Found that there are limitations of how much data that can be configured, could it be that we hit the limit? Attaching the limit table i found in the communication function manual. * Used Wireshark too trace the network traffic, the first packet is directly rejected with packet like it does when there is no listener on the port. 
* Used the portscanning tool in OPC Expert and scanned the PLC for open ports, only port 102 that the PLC listens on so no listener on the OPC UA port. * Deactivated OPC UA, downloaded hardware configuration, activated OPC UA and downloaded again * Tested different OPC clients, Kepware, Ignition OPC Expert, Prosys, same results on all that they get connection error directly. Last week we should use this OPC UA server again but were not able to connect to it anymore. We have a Siemens 1518 CPU that we activated OPC UA on in TIA v14 for a month ago and it worked fine.
0 kommentar(er)
