Q: Why do we need to update resource packages? What are the requirements and process?

A: Resource packages include device asset information (including site and device information), model information (basic models and inherited models), protocol JAR files, point.csv files, mapping configuration files, and event trigger configuration files. Any modification to these information would require the updating of the resource packages. Usually, these resource packages are updated only during implementation and O&M as they become quite stable in daily use. The update frequency depends on the project requirements.

The resource packages are updated over HTTP(S). Port 80 (for HTTP) or 443 (for HTTPS) needs to be enabled for both EnOS Cloud and gateways.

If the resource packages are hosted on an FTP server, the server can push them to the users. The users can then view the packages and copy them onto the FTP server for the gateway devices.

Q: What are the requirements for remote control commands?

A: Remote control commands are based on TCP. Ports 8043 and 8099 need to be enabled on EnOS Cloud.

Q: What are the requirements for communication testing and dataflow monitoring?

A: Communication testing and dataflow monitoring are based on TCP. Port 8043 and 8099 need to be enabled on EnOS Cloud.

Q: Do MQTT topics support wildcard characters?

A: Yes. MQTT topics support the following wildcard characters:

  • Multi-level (#): A topic like XXX/level1/level2/# helps you subscribe to any topic under level2.
  • Single-level(+):XXX/level1/level2/+ helps you subscribe to all topics immediately under level2.

Q: Can EnOS Cloud subscribe to third-party message brokers?

A: Applications running on top of EnOS can subscribe to third-party brokers. EnOS Cloud does not support subscription to third-party brokers currently but can be customized to do so.

Q: What should I do if the device certificate expires? Can I use OTA to renew the certificate?

A: You need to renew the certificate if it has expired. The owner of the expired certificate needs to apply for a certificate with a renewed validity period. Before the original certificate expires, the device can still use it to get connected to EnOS. The device should use the renewed certificate to connect to EnOS after it has obtained it. OTA is not suitable for renewing certificate as it is designed for large-scale firmware upgrade.

Q: Can logic assets be converted into device assets?

A: Logic assets cannot be converted into device assets. You can create a new device asset to replace the logic asset and then delete the logic asset.

Q: Should an OPC-UA server be registered as a device asset or logic asset?

A: It depends. A device asset has an authentication triple (device key, product key, and device secret) and can be connected to an MQTT broker to upload data, while a logic asset does not have the authentication triple and cannot connect to a broker. If you have registered the OPC-UA as a logic asset but need to upload some measurement point data, you can use the EnOS APIs to do so.

Q: If a device is registered in OU 1, can I use the device in OU 2?

A: You can subscribe to its data across OUs. For OU 2, devices registered on OU 1 is not visible.

Q: Which is updated by EnOS OTA, the firmware or the runtime engine of the gateway device?

A: A device can download OTA files through EnOS OTA and it can determine what this OTA file is used for. Therefore, EnOS Edge can use the downloaded OTA file to either update the runtime engine or firmware.

Q: Can EnOS Edge subscribe to EnOS Cloud for data? How to configure EnOS Edge?

A: EnOS Edge can subscribe to EnOS Cloud data over MQTT, which does not require any configuration as EnOS Edge subscribes to data using its own runtime engine. Other gateway devices can subscribe to EnOS Cloud data using EnOS device SDK.

Q: How can a device connect to EnOS if we cannot burn the authentication triples onto it or change its firmware?

A: For programmable devices, authentication triples are stored in the device for static authentication.

Dynamic authentication can be used for authenticating programmable devices on a large scale. The serial number of the devices can be used as the device key. For example, NB-IoT devices can use IMEI as their device keys.

Non-programmable devices can be connected to EnOS Cloud through EnOS Edge, the existing third-party cloud, or SCADA system.

Q: How does the TSDB store measurement point data?

A: The TSDB uses the measurement point ID as the key to store point data. If the data of a measurement point has entered the TSDB, you cannot edit its data type, delete the measurement point, or model.

Q: How to select my device connection scheme?

A: The choice depends on the capability of your devices, your business scenario and requirements. Refer to Selecting the Device Connection Protocol.

Q: Is there any limit on the basic information fields of model, product, asset, and asset tree?

A: The limitation is as follows:

  • Model name, product name, asset name, asset tree name: 1-64 characters.
  • Product key, device key: 1-64 characters. Chinese, English, numbers and em dash (-), underscore (_), or period (.).
  • Model description, product description, asset description, asset tree description: no more than 100 characters.

Q: How do we connect real devices to EnOS and get their reported data?

A: Real devices can be connected to EnOS directly or through a gateway proxy via MQTT/HTPP/CoAP. You need to create a device model, create a product, and register the device on EnOS. IoT Hub provides standard C/Java/Node.js/Python device SDKs for development.

Q: Can third-parties use EnOS apps and APIs?

A: The APIs IoT Hub provides are open APIs, therefore, as long as the third-parties have an SA account and relevant OU authorized permissions, they can.

Q: What is the difference between Edge and device?

A: In IoT Hub, both Edge and device are devices, but Edge represents the gateway, which can mount sub-devices under it, and when real devices are connected, the Edge can report data and receive commands on behalf of the sub-devices.

Q: Is there a limit to the number of devices that can be managed for EnOS products? What are the charges?

A: For a single OU, the limit of 100k devices can be increased. Charges are based on the number of messages, contact the BD for more information.

Q: How can we apply for EnOS storage such as IMBD, TSDB, Archive, etc.? What are the charges?

A: You can apply for file storage services in resource management. Contact the BD for more information regarding the charges.