FAQ¶
Q: How do I get the installation files for EnOS Edge?
A: You can refer to the deployment manual and download it via an FTP connection. If you cannot download it, contact Edge team for the file.
Q: What is the communication mechanism between EnOS Edge and the cloud?
A: EnOS Edge can upload data to the EnOS Cloud unsing encrypted/unencrypted MQTT communication (port 18883/11883). It can also connect to a resource server via dynamic HTTPS (port 443) or HTTP (port 80): through these sessions, EnOS Edge will download the necessary resource packages from the cloud and execute remote upgrades.
Q: There are many types of communication protocols supported by EnOS Edge. How do I choose the proper one?
A: EnOS Edge offers both standard and private custom protocols, which are categorized according to the Edge product type, hardware model, and scenario (access or forwarding). If the users utilize standard communication protocols, they only need to select the most recent version available. If they use private custom protocols, ensure that the custom protocols have been uploaded by the Edge team under the specified OU before selecting them.
Q: How can you add EnOS Edge sub-devices repeatedly into different connections?
A: Turn on the multi-channel setting when adding devices, then you can add sub-devices to different connections repeatedly.
Q: How do you set the EnOS Edge data acquisition frequency?
A: First of all, you need to distinguish between the data collecting frequency and the data upload interval of EnOS Edge. Based on different protocols, EnOS Edge supports the setting of collecting frequency by device point grouping, single point grouping, and channel grouping. For specific configuration methods, refer to the protocol configuration manual. The data upload interval can be configured for a single point in the data collection.
Q: Can the EnOS Edge templates be transferred between environments?
A: Yes. EnOS Edge offers template import and export functions. You can export the templates in bulk, then import them into the new environment. Note that the templates imported in the new environment require the same associated model.
Q: What is the difference between an EnOS Edge asset tree and an EnOS asset tree?
A: Users can create an asset tree in EnOS for the OU they’re in, showing business relationships among all devices in the OU. On the other hand the EnOS Edge crops the EnOS asset tree based on the device it is connected to, allowing the user to focus on the relationships between the devices in a single EnOS Edge.
Q: How can I view the TSDB data in the EnOS Edge?
A: The EnOS Edge provides APIs that allow users to view TSDB data with third-party tools.
Q: What are the edge computing options for the EnOS Edge?
A: Currently, the EnOS Edge supports the following two edge computing options:
Edge stream computing: Designed for developers to enable them to easily build edge computing logic with streaming operators, such as the wind turbine state computing logic.
Rule engine: Designed for engineers to enable them to build simple, easy, and customizable edge computing/control logics.
At the same time, it supports the deployment of AI algorithms on edge computing platforms, which can be upgraded on demand.
Q: Is there a containerized deployment system for the EnOS Edge?
A: The EnOS Edge containerized system is based on the K8S and KubeEdge technology stacks. It supports the deployment and upgrade of massive amounts of edge nodes via batch management, and allows cloud-to-edge collaboration as well as autonomous node operations. The user experience is similar to the cloud ECP system, which reduces the learning efforts.
Q: In a disconnected network or air-gap scenario, how could we provide local operation and maintainance capabilities to the on-site teams, without asking them to operate command-line tools?
A: All Edge product series provide local visual operation and maintenance tools to meet the requirements of on-site O&M teams, including visual upgrades, device monitoring, log viewing/download, version check, configuration changes, etc.