[Technical Classroom] UniMAT Internet of Things Application Course (11) - Advanced Course of Cloud Configuration

In order to help UniMAT customers use IoT products more conveniently, a series of articles on Internet of Things application courses are launched. The articles will comprehensively introduce the software and hardware, operation methods, related configurations, typical applications, common problems and other knowledge of UniMAT IoT. After reading the full text, you can have a comprehensive understanding of the Internet of Things, and achieve more with less for the application of the Internet of Things.

In this issue, we will bring you the advanced tutorial of Edimensional IoT cloud configuration .

 

 

1. Description

 

This article belongs to the advanced course of the Internet of Things. It is assumed that the user has initially possessed the skills of using the Internet of Things, and can bind the Internet of Things devices and add data.

With the in-depth use of the Internet of Things, various application scenarios are gradually developed. Flexible use of IoT is essential.

In order to meet various application scenarios, the cloud platform adopts the method of virtual device + standard/non-standard template. Implement one-to-one standard mode, many-to-one and one-to-many non-standard mode. It needs to be explained that the "right" refers to the actual IoT screen or Ubox. "Yes" is followed by the entire equipment on site, which may be a single control cabinet or a piece of equipment divided into multiple processes.

①One -to-one: Standard application scenarios One device corresponds to one cloud configuration and data classification.   

②Many to one: Multiple entity SN numbers correspond to one device. For example: the entire production line uses multiple physical devices due to the long distance, but the display should be presented as one device.   

③ One-to-many: One entity SN corresponds to multiple devices. For example: after multiple small devices are connected to a local area network, data is uploaded through a physical device, but the display needs to show each small device.   

 

 

2. Application Implementation

 

Now the three uses of the device are introduced in turn, and the implementation steps are given.

 

01 One on one

 

One-to-one standard templates are highly reproducible. On a complete set of standard devices, there is no need to write variables for each device, and it is not necessary to write a cloud configuration for each device. Standing in a scenario where a device corresponds to an Internet of Things, it is possible to use the binding of anyceess' device replication and cloud configuration to realize one-time writing and reuse.

Note: One of them refers to a SN device, not a virtual device (one SN can generate multiple virtual devices)

 

 

Templates, Devices and Data

 

First, you can make a model (that is, the first project in the project), and use it in batches later.

a. Add SN devices and data in Anyaccess (for details, please refer to the Anyaccess help documentation).

b. Add a virtual device. Click ①Device Center->②Virtual Device->③Add Device->④Query. Then fill in the device information according to your actual situation. Special attention should be paid to the one-to-one standard equipment that the standard template in the blue box must be checked.

c. Create a standard template. Click ①Configuration Management->②Template Management->③Add Template. To create a template, you need to pay attention to the template type in the blue box, and choose a standard template for one-to-one standards.

d. Template data. Cloud configuration directly clicks components in the template to add data items. Cloud configuration reads the data of the name of the device bound to it. If the device does not have data of this data name, a red exclamation mark will be displayed.

Use of standard equipment

 

After the template project is completed. Batch copy projects by copying data and binding the prepared cloud configuration.

data. In anyaccess, select the template project and click the device copy to transfer all the data in the template project, including real-time data, alarm data, historical data, scripts and data forwarding.

Cloud configuration. On the cloud platform, a cloud configuration can be bound with multiple devices. The same device is bound with the same template, and the data in the cloud configuration will automatically read the corresponding data. Connect data items.

The following figure is an example. Equipment: Test A and Test B are the same project. They have the same data and the same screen, so they use the same template. Templates are bound directly without any changes.

02 One-to-many

One-to-many is to separate an actual device (an SN number) into multiple virtual devices.

 

Usage scenario: Multiple small devices are uploaded to the platform through one IoT device in order to save, and used separately on the platform. It is also a renovation of an old project, which was originally in a host computer, and the device needs to be uploaded to the cloud, and then displayed separately.

 

Templates and Virtual Appliances

 

a. Add SN devices and data in Anyaccess (for details, please refer to the Anyaccess help documentation).

b. Virtual device creation is similar to standard one-to-one. It should be noted that one-to-many can be standard or non-standard (the standard template in the blue box is checked to create a standard device, and it is not checked to create a non-standard device). Personally, it is recommended to choose a standard template so that it will be easier to understand intuitively. (For use of non-standard equipment, please refer to 2.3.2 to create data) 

Standard: Requires adding data to components in each cloud configuration template.

Non-standard: The need to add data sources is cumbersome to use, and it is somewhat flexible.

c . Use the standard template on the template (the template must be the same as the device corresponding to the standard), the standard template only needs to connect the data items in the template when making the template, and there is no need to add data sources like non-standard templates. In use the same as one-to-one, the connection variable is then bound to the device.

Note: The standard template cannot use the one-to-one usage in the virtual device generated by the same SN number.

d. Multiple virtual devices can be used to make templates respectively.

03 Many to one

Many-to-one is to integrate multiple actual devices (multiple SN numbers) into a virtual device.

Application scenario: For the production line and other environments, multiple devices are matched with each other to form the entire system. There is an IoT device in the control cabinet, but it must be identified as a device on the cloud.

To use this function, be sure to read the chapter on cloud configuration data for non-standard devices.

 

Non-standard equipment cloud configuration data

 

There is a big difference between the non-standard equipment and the template and the original usage. Especially regarding cloud configuration data usage.

a. Since the data comes from multiple SN devices, in order to facilitate unified management and avoid the occurrence of data with the same name, it is necessary to reproduce the template data source in the template to ensure that its data name is unique.

b. After the template data source is established, you need to enter the virtual device to correspond the data source with the device data.

03 Ending

The flexibility of cloud devices can be brought into play through combined or decentralized use. Meet various application scenarios.