It is the first "Version 1. In this post, I'll detail what the product is, why we built it, and how it is different from other Kepware products. What is ThingWorx Kepware Edge? Why did we build ThingWorx Kepware Edge?
Primarily to connect remote devices directly at the site of the device. Unconnected assets obviously leave value uncaptured—they cannot be monitored, controlled, or analyzed for performance improvements.
Connecting to a centralized OPC Server is also less than optimal. It means that insecure protocols, such as Modbus, are going beyond the local network. The solution is a change in architecture. If compute is added at the device or asset site, data can be translated into secure, efficient protocols before leaving the local network. To date, most have balked at the idea of deploying a Windows-based machine and full OPC Server at each remote site.
That can be expensive and creates IT headaches. Updating hundreds of remote Windows machines could keep an IT team busy full time. ThingWorx Kepware Edge is a more cost-effective and manageable solution. ThingWorx Kepware Edge is also headless and remotely configurable so it can be centrally managed. Additionally, the product has some key differences that users should be aware of. Please review the product pages and user manuals for more details on what features are included in each of the drivers.
We are looking forward to working with you to deploy the solution and improve your connectivity to remote assets.
Register for the Webinar. Learn how Hirotec improved shop floor productivity. Locate a Reseller. Explore Kepware's hands-on OPC and product training. Browse recent posts on the Kepware Blog. Choose your preferred language. All Rights Reserved.When managing Industrial Internet of Things IIoT data, it can be challenging to collect and send this data to the cloud for processing and advanced analytics for example, to predict quality or equipment failure.
There might be many different devices on a manufacturing floor, each with its own protocol. By the end of the post, you should have enough information to create a secure and reliable process for real-time industrial data so everyone from the shop floor to the top floor can make smarter decisions.
Copy the device certificates that you downloaded and extracted earlier. You can use the local file sharing feature of the Microsoft Remote Desktop Connection software. Copy the PemEncodedCertificate value and paste it in a text editor. At least one agent must be configured with one active tag for the gateway service to start. Configure the agents and tags in the IoT Gateway section. We are now able to process the IoT messages from disparate industrial devices in the AWS environment.
By following the steps in this post, you can collect industrial data from programmable logic controllers PLCsSCADA systems, plant historians, and other manufacturing systems and in a few hours get data flowing into AWS securely, efficiently, and cost-effectively.
After the industrial data is ingested in AWS, it can be used for a variety of smart manufacturing use cases, including building ML models for predictive maintenance.
See for yourself. Get started today with connecting industrial assets and applications from the plant floor to AWS. Enables local messaging between devices over a secure network by using a managed subscription scheme through the MQTT protocol. Ensures secure connections between devices and the cloud using device authentication and authorization. Provides secure, over-the-air software updates of user-defined AWS Lambda functions. You can download and install the current JRE from here.
The resources you create in these procedures should be created in the same AWS Region. Make a note of the endpoint address and port. Choose Create New Device. To create a registry entry for this device, in Nameenter KepServerand then choose Next. On the Set up security page, choose Use Defaults to use the 1-Click option. Be aware that this is the only step in the process when you can download keys so make sure you download them here or you will have to create a new AWS IoT device.
Choose Finish. KepServer should now appear in the Devices list of your Greengrass group.AWS IoT Core Secure Authentication with JITR - Getting Started
On the group configuration page, choose Subscriptionsand then choose Add Subscription. Then choose Next. For Optional topic filterenter iotgatewaychoose Nextand then choose Finish. On the group configuration page, from the Actions menu, choose Deploy to deploy the updated group configuration to your Greengrass core device: To confirm a successful deployment, choose Deployments.
You should see Successfully completed in the Status column close to the time you initiated the deployment. Choose the IoT Gateway tab.
If you are prompted for a password, leave it blank, and then choose OK.To verify the connection, we will be using the SQL workbench for this. In order to use the datalogger properly, you will have to launch the 32 bit variant of the DSN.
Now Available: Factory-wide Connectivity for access to the right data, at the right time.
The ODBC driver has to be 32 bit as well. Click test and you should be able to connect sucessfully, Click ok to close all the window Now under the datalogger general tabyou should be able to select the newly created DSN. Key in the username and password: Proceed to Data map and configure the tags you want to add in by clicking Add…. Depending on your preference, you can configure Kepware to log into an existing table or get Kepware to create a table for you.
Simply key in thename of the table you want. Click any of the option in the left panel for example, connectivity and a prompt will appear to ask you to save.
The datalogger plugin will now start logging. You are commenting using your WordPress. You are commenting using your Google account. You are commenting using your Twitter account. You are commenting using your Facebook account. Notify me of new comments via email. Notify me of new posts via email.
Select the db of your preference and proceed. In this tutorial, we will be using the mySQL Db. Click next and customize your db instance. Take note of your Master username and password and click next. Take note of your port number.If you've got a moment, please tell us what we did right so we can do more of it. Thanks for letting us know this page needs work. We're sorry we let you down. If you've got a moment, please tell us how we can make the documentation better. This enables devices to collect and analyze data closer to the source of information, react autonomously to local events, and communicate securely with each other on local networks.
Locally deployed Lambda functions and connectors are triggered by local events, messages from the cloud, or other sources. In AWS IoT Greengrass, devices securely communicate on a local network and exchange messages with each other without having to connect to the cloud. Device security credentials function in a group until they are revoked, even if connectivity to the cloud is disrupted, so that the devices can continue to securely communicate locally.
Deployment and local execution of connectors and Lambda functions. MQTT messaging over the local network between devices, connectors, and Lambda functions using managed subscriptions. Secure connections between devices and the cloud using device authentication and authorization.
Local shadow synchronization of devices.
What Is AWS IoT Greengrass?
Shadows can be configured to sync with the cloud. Automatic IP address detection that enables devices to discover the Greengrass core device. Central deployment of new or updated group configuration. After the configuration data is downloaded, the core device is restarted automatically. Secure, over-the-air OTA software updates of user-defined Lambda functions.
Secure, encrypted storage of local secrets and controlled access by connectors and Lambda functions. A stream manager that processes data streams locally and exports them to the AWS Cloud automatically.
This feature requires Java 8 on the Greengrass core device. A new Greengrass Docker application deployment connector that runs a Docker application on a core device. For more information, see Docker Application Deployment Connector. Lambda functions that run without containerization can access machine learning resources in the Greengrass group. Local MQTT traffic can travel over a port other than the default port Support for Armv6l. Fixes a bug introduced in v1.Connects disparate devices and applications, from plant control systems to enterprise information systems.
The platform design allows users to connect, manage, monitor, and control diverse automation devices and software applications through one intuitive user interface. Watch our two-minute video below to see how KEPServerEX solves common connectivity challenges—providing secure and reliable access to real-time industrial data so everyone from the shop floor to the top floor can make smarter decisions.
KEPServerEX provides the connectivity, usability, and performance required by the modern enterprise—offering competitive benefits that can be experienced from the plant floor to IT to the boardroom.
KEPServerEX provides critical technical features that enable accessibility, aggregation, optimization, connectivity, security, and diagnostics. Expand the topics below to learn more about these features. OPC is the leading standard for industrial automation connectivity. It also provides data access for the ThingWorx platform, enabling you to develop and deploy smart-connected solutions for the IoT. Its customizable data format supports most MQTT and REST applications—enabling users to choose the vendors and communication methodologies right for their system.
Some applications require information to be made available from a file or database. This information is typically exported at a predefined rate and includes both current and historical data. KEPServerEX optimizes communications and reduces network and device load via data conditioning and reduction, customized load balancing, and protocol-specific optimization.
In addition to providing raw values to connected applications, KEPServerEX can perform linear or square root scaling, basic arithmetic expressions, and apply deadbands. These features utilize minimal bandwidth and resources by providing only the most critical updates.
Sending Kepware Data to AWS IoT Hub
KEPServerEX is used in critical applications where highly-reliable systems are required for maximum uptime. It includes the ability to define redundant network paths, primary and secondary data sources, and applicable failover criteria. In large networks that have many devices and applications requiring information, flexible control is necessary to allow for customized load-balancing of data collection and information flow. KEPServerEX provides tools to schedule the frequency of communications and throttle the demand across the network.
KEPServerEX optimizes communications with devices by aggregating identical requests from different applications whenever possible. Multiple demands on data can be batched together into the fewest requests possible. These optimizations are unique to each protocol, and are designed to reduce network overhead and device processing. In a typical industrial automation network, devices and controllers must communicate with one another even if they are not from the same manufacturer or do not support the same protocol.
KEPServerEX provides the ability to establish links between data values in different data sources, allowing Machine-to-Machine M2M communications as close to the device as possible. These changes include adding, editing, reading, and deleting objects such as channels, devices, and tags in the server.
The Configuration API enables programmers to create simple webpages where users can identify the properties that change, and then programmatically create the channels, devices, and tags to the company standard. It also enables the use of templates to standardize creation and naming among different types of devices—ensuring consistency and increasing user efficiency.
KEPServerEX simplifies the configuration of connected applications by providing a single point of entry to all information—eliminating the need to purchase, operate, troubleshoot, and maintain multiple disparate solutions for discrete connectivity.
KEPServerEX can support connections to thousands of data sources and provide information to hundreds of applications. The platform design simplifies the configuration of the connected applications by providing a single point of entry to all information.
KEPServerEX also enables troubleshooting and issue diagnosis, provides control to the access of information based on user roles, and the ability to restrict the frequency of communications over bandwidth-limited telemetry-based environments. Anything can be added, configured, or deleted while the server is on-line and operational.
KEPServerEX can also store information in any ODBC-compliant database using the DataLogger advanced plug-in, which has a store-and-forward capability for when a database is unreachable or unable to process the information fast enough. KEPServerEX supports the broadest range of drivers available, including current and legacy devices across various verticals, a variety of wired and wireless network mediums, and connectivity to databases, custom software applications, and other OPC servers.
KEPServerEX offers the broadest range of drivers available, supporting devices across various verticals within industrial automation.What is an interface? It offers users flexible deployment of valuable Kepware functionality and native connectivity to ThingWorx, the leading Industrial IoT platform. An interface is a software component that enables ThingWorx Kepware Edge to meet the connectivity requirements of a specific client application.
Interfaces handle all supported connectivity to applications that monitor or control devices; drivers handle all proprietary communications to devices.
Learn how Hirotec improved shop floor productivity. Locate a Reseller. Explore Kepware's hands-on OPC and product training. Browse recent posts on the Kepware Blog. Choose your preferred language. Products ThingWorx Kepware Edge. ThingWorx Kepware Edge allows the server to be deployed directly at the edge, meaning MQTT can be used to transport data securely over the network.
MQTT is a highly efficient protocol. Using MQTT can therefore reduce network traffic and associated costs, which can be especially high on cellular or satellite connections. MQTT also utilizes modern security: TLS at the transport layer, and encryption and authentication at the application layer. Users can be assured of message confidentiality and integrity using the MQTT protocol. Available Languages English. Learn More. All Rights Reserved.You do not need to run the quick test.
The next two sections guide you through verifying that the Connector is running properly. Log in to ThingWorx Composer. From the Properties page, add a new remotely bound property. For testing purposes, set its value to read from the edge remote devices on every read. Save the Thing. Your new Thing should appear under the Things category, with the new name. From ThingWorx Composer, set the value of the newly created property. You should see a value for that property under a JSON object called desired.
Edit the shadow so that there is an object called reported at the same level as desired. Within the desired object, add a new value for your property. From ThingWorx Composer, check the value of the property.
It should change to the same value as in the shadow's reported object. For more information, see. You can download a demo of KepserverEX by filling out a form on the kepware. The demo is as functional as the full version, the only difference being a time restriction of two hours before having to shut down and restart KepserverEX before it will connect to devices again. Topics can be anything, and writing to a topic creates that topic.
At the server tag field, click the ellipsis next to the field. Add the PublishesSent Tag and apply it. If it's not already selected, select Subscribe to a topic. In the Subscription topic field, put the topic that the IoT Gateway is publishing to and click subscribe.
Every five seconds, you should see information coming in as a json block from KepserverEX.