hello, I participated in the horizontal project of RFID in the internet of things. Let me give you a general introduction to the structure of the Internet of Things engineering team, which can be regarded as attracting jade. If you say something wrong, please forgive me.

Look at your answer above. You are only a sophomore, and you are aiming to establish a team model. Your spirit is really commendable, and you will be awesome in the future.

first, for college students, especially in the undergraduate stage, I think it is enough to set up a team, and you don't need to go down to the department. The starting point of your project is to master the whole process. As for in-depth research, that will be later. Without an overall grasp of the project, how can we talk about project integration and in-depth research? In view of this, it is suggested to divide the whole team into two directions-hardware and software. Of course, it does not mean that it is purely hard and soft. But roughly grouped according to personal characteristics and proficiency.

Second, college students are definitely short of funds. Make good use of the resources at hand and see if the college has established a joint laboratory with large enterprises. In the past, our school cooperated with TI, so there was a joint laboratory. After the establishment of the joint laboratory, enterprises will regularly give away boards. If they can, they can borrow boards. It's not that they care about the number of functions of boards. It's true that the boards of big factories have excellent stability. I have tried to burn different boards in the same program, and the stability is very different. Therefore, if conditions permit, it is strongly recommended to use the board of a large factory. If there are no conditions, it's okay. Now taobao is so developed, go up and search for a single chip microcomputer. The simplest one will do. The price will be around 21, and the function will be good as long as it is practical. Generally speaking, if you just start, it is enough to have a USB+ serial port for transmission, which is not too complicated. 2.4ghz is fine for wireless transmission.

thirdly, all the above are preparation for application. The internet of things is a technology that has only been developed in recent years. In fact, it is not a new technology when it is split up. It is composed of sensor, transmission (wired and wireless), single chip microcomputer and terminal (with an oracle database for complex points). Take a simple project for example, it can be more vivid. Let's say, wireless ranging system. First of all, sensors, usually ultrasonic distance sensors (of course, you can also use lasers, but the price. . . ) The specifications, accuracy, temperature influence factors and so on all need to be considered before you choose them. Secondly, what needs to be considered is the transmission mode between it and middleware (which can be single-chip microcomputer, FPGA, etc.). If wireless is used, it is necessary to study the RF frequency and the knowledge of channel transmission. Generally, the appropriate frequency is selected according to the transmission distance. In the past, infrared ray was useful, but that was too bad, and it could not be transmitted if the window was not aligned. It was too demanding for the environment and was eliminated. At present, the frequency band of the mainstream wireless mouse is 2.4ghz, and the transmission distance is about 11 meters, which is suitable for general communication. The only drawback is that the bandwidth is a little narrow and the transmission speed is somewhat affected. Of course, you can use satellite channels if you have money ~ hehe. Of course, there are many things in transmission. If you go deeper, you can study protocols and headers. If you think TCP/IP is too popular, you can design your own headers and invent new protocols. If you are a middleware, you can choose it at will, and the dominant idea is still enough, so don't waste it. Next, it's the same old story. The transmission between the middleware and the terminal (usually a pc) is over. If it's wired, it's ok (I skipped the driver design of the single chip microcomputer here, but it's too in-depth, so there's no need to talk about it for the time being, and generally the single chip microcomputer you bought will come with it and will teach you to tune it up, so don't worry). If wireless connection is still adopted, the interference problem should be considered. It is suggested to adopt the wireless transmission mode of computer 812.11a/b/g/n.. . . What generation has it developed to now? Looks like I? I don't know. Look it up for yourself. This can effectively avoid interference. At this point, the computer can communicate with the single chip microcomputer, which is the legendary communication. As for how to record the data you receive and how to deal with it, that is another story. If you have spare capacity, it is absolutely powerful to learn oracle database and SQL language. JAVA is the best choice if considering the transplantation of the later platform (easy to use and easy to learn, we have been using it! Haha) Of course, there is also a need to burn programs in the front MCU. The language is definitely not an assembly. C# and C++ are enough, but generally there are more C. Didn't we say that we should group? That's the purpose.

fourth, the front is almost over, why is there a fourth? The main reason is that I forgot to say that you have to study the algorithms, including anti-collision algorithm, channel optimization algorithm, routing algorithm, etc. In case of anti-collision, that is to say, if there are multiple wireless sensors that need to transmit information to the microcontroller within the frequency range of the microcontroller, which is the first? Modern communication already has TDD, FDD, OFDM, CDMA and other modes. . . If optimization is considered, it is necessary to introduce new knowledge such as cost function and game theory. Routing algorithm, you should consider the reliability of routing nodes, channel attenuation, relay and other issues.

having said so much, it's a good idea. It's all personal shallow understanding of the Internet of Things. It's not a guide for you, but a communication. It's getting late, go to bed, good night!