IoT Gateway

产品概览

IoT Gateway 是扩展 KEPServerEX 连接平台功能的一个高级插件。它呈现 RESTful Web 服务器以便与 MES 和其他系统中的 Web 服务集成,并将实时工业数据直接无缝地流式传输到整个企业的设备云和大数据分析平台。

IoT Gateway 将运营技术与 IT 联系起来,以支持工业物联网 (IIoT)。这使得决策者能够搜索、监控、分析和呈现数据,以便实时洞察车间运营情况,从而提高系统安全性、改善客户服务、精简自动化过程并提高整个企业的决策质量。

借助企业解决方案和基于云的解决方案,组织能够搜索、监控、分析和呈现来自 PAC、PLC、RTU、流量计算机、OPC 服务器及其他工业硬件和软件的 KEPServerEX 生成的数据。Kepware 已经与大数据和分析提供商合作,以洞察工业设备与系统的运营和状况。

测量、验证和持续调试:确保现场设备如期运行。

容量计划:监控设备或系统计划外停机风险的数据。

根本原因分析和远程故障排除:更好地了解特定设备上出现特定故障的原因并提高效率。

异常和异常值检测:识别可能标志着早期设备生产或部署问题的异常值。

安全和合规:了解可能让机器或人员陷入风险的系统性能或设置点,并快速制定和访问用于合规的报告。

网络安全:改善工业体系中的安全态势,以缓解出现的网络安全威胁。


资源

  • 性能
  • 协议
  • 相关产品
  • 应用案例
  • 可用语言
  • 文档
  • 发行说明
  • 更多技术信息

性能

  • 将 KEPServerEX 的实时数据流式传输到移动、大数据、企业资产管理、分析软件和 IoT 平台
  • 利用 KEPServerEX 内的 150 多个驱动从数千个工业传感器和机器(包括 PLC、RTU、PAC、DAQ、控制器等)收集数据
  • 提供三个代理,以便通过 MQTT和HTTP/REST 协议流式传输数据
  • 为客户端代理提供高级消息格式,以支持多种数据建模要求,例如 JSON、XML、CSV 和自定义模式
  • 包括很多增强功能,例如死区、支持读写数据阵列、多个同时的代理和应用程序连接、跨来源资源共享 (CORS) 限制及 CSV 标签导入和导出。
  • 通过 KEPServerEX 配置 API 为所有代理类型提供第三方和远程配置
  • 支持可基于数据变化或者周期来发布消息

协议

  • MQTT Client
  • RESTful Web Services Client
  • RESTful Web Services Server

相关产品

可用语言

  • 英语

发行说明

6.14.263

2023/7/26

  • 增加了可配置选项,可基于数据变化或者周期发布消息。
  • 增加了CHANNEL和DEVICE作为变量加入到高级消息模板中。

6.12.325

2022/6/23

  • 修复了通过配置 API 创建后无法写入数组标签的问题。
  • 修复了尽管设置为"Send Every Scan"但未发送标签更新的问题。
  • 添加了新选项,用于在与 Rest Client IoT 网关代理失去连接时切换缓冲更新。
  • 添加了一个新选项来跳过 MQTT 和 REST 客户端代理的初始更新。

6.11.764.0

2022/5/16

  • 修复了 IoT 网关代理阵列标签在通过配置 API 创建后无法写入的问题。
  • 修复了设置为“Send Every Scan”时未发送标签更新的问题。

6.11.718.0

2021/12/21

  • Fixed an issue where very small deadband values would be truncated when exporting tags as CSV.
  • Fixed an issue where '$' would incorrectly be removed if it was the first character of an MQTT topic name.
  • Fixed an issue in the where the _PublishesSent and _DroppedEvents system tags were not updating.
  • Fixed an issue where the Scan Rate specified in the tags was not respected.
  • Fixed instability issues that could occur on server startup.
  • Added the ability to specify different ISO timestamp formats in the payload.
  • Added the ability to publish additional tag attributes and a linefeed in the message templates. Refer to help for the full list.

6.10.659.0

2021/8/10

  • Fixed an issue where some system tags were not being updated
  • Fixed an issue where the IoT Gateway service would sometimes not start up correctly and need to be restarted.

6.10.623.0

2021/2/23

  • Fixed an issue where REST Client Agent expansion message error messages could be empty.
  • Fixed an issue in which caused failed authentication could cause the IoT Gateway service to lock up.
  • Clarified event log message posted when the event buffer is full for REST Clients and MQTT Client Agents.

6.9.636.0

2021/8/10

  • Resolved issue with failed authentication through the IoT Gateway that could cause the service to lock up.

6.9.572.0

2020/6/2

  • Updated Java third-party libraries to address security vulnerabilities.
  • Fixed an issue where license status was incorrectly reported as “unlicensed” in the Agent properties.
  • Fixed an issue where Boolean values reported to the server with underlying non-zero values except '-1' were reported as ‘false’ by agents.
  • Resolved issue with the Rest Client Agent “Publish as Media Type” didn't match the option set in the Configuration.
  • Fixed an issue where a deadlock could occur during explicit reads.

6.8.796.0

2019/12/17

  • Agents can be configured to only send updates in which the value has changed, ignoring quality-only changes.

6.7.1046.0

2019/6/18

  • Enhanced the MQTT Agent to allow the use of ‘$’ in the first character of the Topic.

6.3.273.0

2017/9/27

  • 解决了 MQTT 代理在通信中断后不重新连接的问题。

6.2

2017/6/8

  • Added a UI element to modify Rest client connection timeout.

6.1.601.0

2017/4/4

  • The IoT Gateway is now accessible via the Configuration API.
  • Fixed an issue where the MQTT client agent was not shutting down correctly, causing the service to fail on attempts to reconnect or reinitialize from the Configuration.
  • Added generic support for client-side SSL/TLS certificates. Support has been verified with the following MQTT brokers:
    • AWS IoT SSL/TLS
    • Azure IoT Hub SSL/TLS
  • Enhanced input validation and error handling for MQTT broker URLs. Prior to this update, a trailing "/" added to an MQTT URL in the IoT Gateway MQTT agent would not connect or produce a relevant event log message.
  • Added support for explicit device reads to the Rest Server agent. This can be useful when the client is aware of when a data change should have occurred, as an alternative to polling for updates.

5.20.396.0

2016/5/3

  • Added new agent type for publishing data to the ThingWorx platform. The ThingWorx binary protocol enhances configuration, performance, and secure communications.
  • Updated the minimum JRE version to Java 7 (JRE 1.7 32 bit) to support new gateway functionality.
  • Corrected an issue where the MQTT Agent could block all other agents if it did not connect on the initial attempt.
  • Corrected an issue where “Bad” quality updates were repeatedly sent to endpoints due to being interpreted as data changes.
  • Fixed a defect where write requests would timeout if the device's Scan Mode was set to "Demand Poll Only."
  • Fixed an issue where tag scan rate would revert to a default of 10ms if set higher than 32767.
  • Fixed an issue where the REST Client Agent was sending an invalid Accept header, causing the connection to be rejected with an HTTP error 406.
  • Expanded and corrected error handling on the MQTT engine to provide improved feedback.
  • Added support for an advanced template to format data for improved control over the payload being sent from the REST Client and MQTT agents. In addition to JSON, XML and CSV can be generated using this template.
  • Added support for writing to Array data types (with the exception of String Arrays).
  • Added support for writes via MQTT agents. The MQTT agent can be configured to subscribe to a topic on the MQTT broker to allow other publishers to write to tags under that agent.
  • Added support for users to enable or disable connections from Cross-Origin Resource Sharing (CORS) sources. This setting can be used when accessing the IoT Gateway REST Server agent from a custom web page.

5.19.467.0

2015/10/20

  • New product that converts industrial data to IoT protocols including REST and MQTT.

常见功能

  • 提供可自定义的 JSON 数据格式,以支持大多数的 MQTT 和 REST 应用程序
  • 支持死区以限制数据吞吐量
  • 支持标签导入和导出,以便快速配置和部署项目
  • 发布速率可配置
  • 单个事务的数据包大小可配置

MQTT 客户端代理功能

  • 支持 MQTT 3.1.1 版本,包括发布和订阅方法
  • 支持多种数据模式的高级格式(JSON、XML、CSV 和自定义)
  • 支持 MQTT 安全性和数据完整性功能,包括传输层安全性 (TLS)、基于证书的身份验证、用户名/密码身份验证、临终遗嘱和服务质量消息分发
  • 支持来自 AWS IoT 的自签名证书,可实现直接连接,无需第三方中介

REST 客户端代理功能

  • 提供 HTTP PUT 或 POST 方法将数据发布到 Web 服务器
  • 支持多种数据模式的高级格式(JSON、XML、CSV 和自定义)
  • 支持 HTTP 安全性和数据完整性功能,包括 Secure Socket Layer (SSL)、可自定义的 HTTP 标头、服务器测数据接收确认和通过用户名/密码进行的基本身份验证

REST 服务器代理功能

  • 提供直观的拖放配置,自动创建标签 URL
  • 支持 HTTP GET 和 POST 方法,让 Web 客户端可以浏览、读取和写入 KEPServerEX 内的任何可用标签
  • 支持 HTTP 安全性和数据完整性功能,包括跨来源资源共享 (CORS) 限制、Secure Socket Layer (SSL) 和通过用户名与密码进行的基本身份验证

什么是高级插件?

KEPServerEX 不仅是 OPC 服务器,它还是一种适用于工业自动化和 IoT 的连接平台。只需下载 KEPServerEX,然后从包含 150 多种设备驱动、客户端驱动和高级插件的 Kepware 库中选择,以便适合您工业控制系统的独特通信要求。

高级插件可扩展 KEPServerEX 连接平台的功能。通过将设备中的原始数据转换为其他形式,来提高数据实用性,并增强 KEPServerEX 的功能。

高级插件可以单独进行许可或作为套件的组成部分进行许可,还可以随着连接需求的发展按需进行许可。

  • 订货号:KWS-IOTGW1-SUB (1-500 tags) KWS-IOTGW2-SUB (501-5,000 tags) KWS-IOTGW0-SUB (5,001+ tags)

重要通知

自2023年8月14日起已停售永久授权。
IoT Gateway订阅授权可以正常订购。

请联系销售人员获取临时授权

  • 电话:400 613 9938
  • 电子邮件:

KEPServerEX 产品搜索