Technical Roadmap for C # Industrial IoT and Integrated system solutions (data source, DAQ, data upload and receive, ActiveMQ, Mongodb, WEBAPI, mobile app)

Directory

Technical roadmap for industrial IoT and integrated system solutions ... 1

Objective... 1

Chapter I. System architecture ... 3

1.1 Hardware architecture Diagram ... 3

1.2 Component Architecture Diagram ... 4

Chapter II Technology Selection and introduction ... 5

2.1 Development environment ... 5

2.2 Data Sources ... 5

2.3 Data Acquisition ... 5

2.4 Data Upload service ... 6

2.5 Message Middleware ... 6

2.6 Data Reception Services ... 6

2.7 Data Storage ... 6

2.8 Data Interface ... 7

2.9 Web Business System ... 7

2.10 Mobile mobile app. 7

Chapter III Introduction of the demo ... 8

3.1 Directory Introduction ... 8

3.2 Demo Debug ... 8

Objective

After 2000, the Internet in China's land in full swing development, in this industry competition is more than the acceleration. I remember clearly that there is a passage in the world is flat: in Africa, when the antelope wakes up in the morning, it knows that he must run faster than the fastest lion, or else it will be eaten; when the lion wakes up in the morning, he knows that he must catch up with the slowest antelope, or starve to death, whether you are a lion or an antelope When the sun rises, you'd better start running! We run this more than 10 years of time, the Internet technology has led the development of the various lines, but also swept through the various lines.

In the 2006, the industry was also using telephone lines for data transmission and Remote Assistance. Network technology slowly in all walks of life conduction, industrial industry is also in development, LAN, optical fiber Ethernet, WIFI\3G\4G, etc. has been widely used. While promoting the development of the manufacturing industry, the Internet technology has also driven many companies to advance with the times, upgrade technology and provide better service.

We are thinking, how will the post-Internet era evolve? will be the process of deep integration of the Internet with all walks of life, such as the now often mentioned IoT, I think it is essentially industrial Internet, is the manufacturing technology and Internet technology seamless docking. Whether it is the internet of things or the industrial web, the future of the interaction between things and things, things and human interaction will not be avoided. With the development of hardware and software, the development of the intelligent chip, the development of embedded operating system and the development of intelligent sensor have been accelerated.

Big data, distributed, cloud computing are also developing at an alarming rate, and some people may think that these things are far from our lives. But this is not the case, the distance from 2006 is only about 10 years, now the development is not previously you can imagine, and this acceleration of development, 2 years of development may be your last 10 years of development. Regardless of whether these technologies can now be landed, this trend cannot be changed.

The flow of data can be cashed in, and the flow of cash can increase GDP. The progress of technology is the improvement of productivity, and the future organizational structure and relationship will inevitably change. Whether you know the technical technology, whether you understand the management, the way of thinking will certainly be eliminated.

The following is an introduction to the technical roadmap of solutions for the IoT and integrated systems, only for technology selection and system flow, and for the evolution of the architecture and the technology which is better not to be specified. For reference only!!!

Chapter I. System architecture

Architecture diagram The main expression of an approximate structure of the meaning, can be less accurate, I hope you can understand. As a system also includes the network Deployment framework diagram, depending on the scenario and the network environment is not the same as the network framework diagram, so it is not covered in this article.

1.1 Hardware architecture Diagram

1.2 Component Architecture Diagram

Chapter II Technology Selection and introduction

The article does not introduce the Code section, in the demo case there is a complete code and comments, you can download debugging.

2.1 Development environment

Development language: All use C #, with a small number of JS code.

Development tools: In addition to the app section, all components are developed using VS2012, the app is developed with VS2015, and VS2015 is a super development tool factory that develops IoT embedded programs on the WIN10 operating system, no problem.

Operating system: Windows 8.1, used to be good, I heard to stop the service, but there are people using XP, do not worry.

2.2 Data sources

The data source is the thing that produces the data, also some people refer to this piece collectively as the sensor, but I think this term is not very accurate, so I generally refer to this piece as the data source.

Data sources include a lot of content, such as: all kinds of sensors, large and medium-sized devices, hardware circuits, software components and so on. The communication protocols of various data sources are different, the communication links are different, the communication mechanism is different, in the absence of uniform standards, this part of the work is more important. With the data, your business system has the value of being applied.

Data source I was writing a module of small programs, including serial communication and network port communication. For communication protocols, see the design and implementation of the C # communication (Serial and network) framework (Superio)-12. Two development and application.

2.3 Data acquisition

The Data Acquisition section uses the Superio framework because it supports a unified plug-in device driver development for serial and network ports, which means developing a driver that supports serial and network port communication. In addition, scalability is relatively strong, can greatly reduce the workload.

A driver was developed to add two drive instances under the Superio platform, which is responsible for serial and network communication with the data source program.

2.4 Data Upload Service

Data upload service is developed under the Superio platform, can inherit the Iappservice interface to develop plug-in service, and mount to the Superio platform to run, after the device driver collects data, can pass through the interface to the service plug-in, through the memory interaction data. If data interaction is involved, data can be interacted via media such as database, text file, etc.

The data upload service interacts directly with the message middleware (ActiveMQ) and is then forwarded by the ACITVEMQ message. The data upload service is actually the message producer's role.

2.5 Message Middleware

Message middleware uses ACTIVEMQ and needs to deploy the Java Runtime environment. The available message middleware is more, for example: RabbitMQ, ZEROMQ, etc.

Depending on the application scenario, the technical options and technical routes that you can choose are different. This piece of message middleware can also be replaced with communication components, such as Netty and SuperSocket.

2.6 Data Reception Services

The data receive service is developed under the Superio platform and can inherit the Iappservice interface to develop plug-in services and mount to the Superio platform.

The data receiving service interacts directly with ACTIVEMQ and receives messages forwarded by ACTIVEMQ, which is actually the role of the message consumer.

2.7 Data storage

Data storage uses MongoDB, does not like big and bloated things, and does not need ORM, deployment is simple, you can use the Mongovue tool to manage the database. If it is danale, it can be directly cmd.

2.8 Data Interface

The data interface adopts the Web Api, which conforms to the restful HTTP protocol, and the operation invocation is simple and convenient. The WebService SOAP protocol was discarded, and the WCF framework was not selected.

This block does not implement permissions, security management.

2.9 Web Business System

The business system uses the MVC framework, but the front end does not interact with the controller in the background, but rather interacts with the webapi of the data interface. The front and rear ends are completely detached.

2.10 Mobile mobile App

Mobile phones are developed using VS2015 and are developed using the Xamarin framework, which supports cross-platform. Xamarin is a very good thing, the only drawback is the need to pay, for Chinese IT staff, this should not be an obstacle.

Chapter III Introduction of the Demo 3.1 catalogue

The project directory is described below:

ClientService: Upload data and interactive components.

Devicedemo: Device driver, responsible for collecting data.

Deviceexport: Data output component, not used in demo.

Deviceshowui: The data display view component, which is responsible for displaying the collected data information.

Formtest: Test the main project of each part.

Protocolpackage: Public protocol package.

Serverservice: Data receives data and interaction components.

Superio_app: Mobile App side, need to VS2015 open.

SUPEROPCCLIENT:OPC client components.

SUPEROPCSERVER:OPC Service-side components.

Testdevice: Simulates the client test program.

Webapi:webapi and web business side data display.

3.2 Demo Commissioning

: http://pan.baidu.com/s/1pJ7lZWf

(1) Download demo and tools

Download Superio v2.2.7\superio_demo v2.rar; download MongoDB database; Download ACTIVEMQ message middleware.

(2) Start up services and procedures

Start Mongodb,mongodb-win32-x86_64-2008plus-3.0.3-1\start.bat, the default listening port is: 2222.

Starting the ACTIVEMQ service, Apache-activemq-5.12.0\bin\win64\activemq.bat, requires a Java runtime environment.

To start the Superio_demo.sln solution, you need to VS2012 develop the IDE, or you can turn it into a VS2015 project and recompile.

To start the Superio_app.sln solution, you need to VS2015 develop the IDE, and if you use the VS-bring simulator, you need to execute the ip> of the <ADB Connect simulator to successfully deploy the program to the emulator and debug it. Otherwise, the VS tool is in the deployment phase.

(3) operation

(4) Debug video

Youku video is not too clear, please download HD debug video, Address: Http://pan.baidu.com/s/1pJ7lZWf in the "video demo".

Only laugh at

Email:[email protected]

qq:504547114

. NET Development Technology Alliance: 54256083

Document Download: Http://pan.baidu.com/s/1pJ7lZWf

Official website: http://www.bmpj.net

Technical Roadmap for C # Industrial IoT and Integrated system solutions (data source, DAQ, data upload and receive, ActiveMQ, Mongodb, WEBAPI, mobile app)