Current situation
Let me talk about the current situation first. Everyone knows that the Internet of Things is characterized by fragmentation, with a very wide variety of equipment and various equipment protocols, which adds a lot of work to enterprises and developers. It is often adapted to this company, and it must be adapted to the equipment of that company. It is obviously the same type of equipment, but it still takes a lot of time to adapt to different manufacturers. . .
The following are examples of these manufacturers
Module
We know that NB-IoT has now been included in the 5G standard, and there will be more and more development and applications in the field of low-speed IoT. At present, there are many NB-IoT module manufacturers, including Quectel, Gosuncn, China Mobile Internet of Things, Lierda, Changhong Ailian, etc., mainly based on the HiSilicon Boudica150 and MediaTek MTK2625 solutions. Based on these two chip solutions, module manufacturers have integrated and exited their own modules, and it is precisely in this that there are many things that are not friendly to developers.
Take Quectel and CMEC as examples. Both of them have NB modules based on the Hisilicon Boudica solution. Quectel has BC35/BC28 and CMEC has M5310-A, but these two modules are not only different in package, but also in AT commands. different, such as:
shift away there AT+QSECSWT, AT+QLWULDATAwhile in the corresponding instructions for the shift AT+NSECSWT, AT+MLWULDATAand so these can be confusing, obviously the same program, but why not make the same, which is to highlight the personality it? Manufacturers are for their own interests, but under the current trend of vigorous development of the Internet of Things, this pattern is too small. No module manufacturer can occupy the entire market, but it is very inconvenient for manufacturers and developers to use modules. After changing the module, not only the hardware but also the software must be changed. Why not unified at the module level Up? Call for the establishment of module standards and unify the Internet of Things! ! !
Even if they are all modules of Moveaway, the module commands of different chip solutions (HiSilicon and MTK) are different. I wonder, the firmware of the AT command is written by the module manufacturer. If you write it, it will kill you. Why do you have two sets, using your module to change the code every day, it is meaningless and a waste of developer time! ! !
Sensing equipment
There are too many types of sensor equipment than modules, so the agreement is even more speechless. It is impossible to say that all of them are unified. After all, the equipment is different, let alone the agreement. But at least for the same type of equipment, we can unify the following agreements.
Take electricity meters as an example. The first type of electricity meters installed by residential users are all based on the State Grid DLT645 protocol. The meter manufacturers are different, but the protocol is the same, so the collection systems are all unified. This is because the State Grid is setting standards.
However, in addition to these types of meters, the market is flooded with a large number of Type II meters, most of which are installed in shops, office buildings, and apartments. Most of these meters support the Modbus protocol, and different registers store different power data. There are many problems in this. The same is the voltage. Manufacturer A may use register No. 1, while manufacturer B may use register No. 300. There are many differences, which is very painful. In a project, there may be 7/8 kinds of such meters, each of which is different. Your collection program adapts to a large workload. Obviously it is very simple, but it is so troublesome to do it, which is against humanity. To borrow the words of a certain leader, this is not serving the people.
Imagine that everyone regulates the register address and uses the same register to represent the same physical quantity. For the manufacturer, there is almost no workload. They only modify a few addresses of their own programs. However, no one does this kind of thing. . .
to sum up
Here is just a brief description of these issues with modules and electric meters as examples. It is hoped that on the development path of the Internet of Things, more manufacturers can unite to formulate industry standards and simplify the difficulty of implementing the Internet of Things.