The number of sensors has surged across the surface of the Earth and around people's lives, providing a variety of data messages around the world. These price-friendly sensors are the driving force behind the development of the Internet of Things (IoT) and our society is facing a digital revolution.
However, connecting and acquiring data from sensors is not always straightforward or so easy. Here are five tips to help ease the first war between the engineer and the transmission interface to the sensor.
Tip 1 - Start with the bus toolIn the first step, the engineer should take the first time to connect to the sensor by means of a bus tool to limit the unknown. A bus tool connects a personal computer (PC) to the sensor's I2C, SPI or other protocol that allows the sensor to "talk". A PC application associated with the bus tool provides an embedded microcontroller (MCU) driver that is known to work with the source to send and receive data and is not unknown or certified. In the working environment of the bus tool, the developer can send and receive messages to get an understanding of how the part works, before attempting to operate at the embedded level.
Tip 2 - Write the transport interface code in PythonOnce the developer has tried to use the sensor of the bus tool, the next step is to write the application code for the sensor. Instead of jumping directly to the microcontroller's code, write the application code in Python. Many bus tools configure plug-ins and sample code in writing scripts, and Python is usually one of the languages ​​available in .NET. Writing an application in Python is quick and easy, and it provides a way to test the sensor in the application, which is not as complex as testing in an embedded environment. Having high-level code will make it easy for non-embedded engineers to mine sensor scripts and tests without the need for an embedded software engineer.
Tip 3 - Test the sensor with Micro PythonOne of the advantages of writing the first piece of application code in Python is that by calling Micro Python, the application calls to the bus tool application programming interface (API) for easy replacement. Micro Python runs in real-time embedded software, with many sensors for engineers to understand its value. Micro Python runs on a Cortex-M4 processor and it's a great environment to debug application code from it. . Not only is it simple, there is no need to write I2C or SPI drivers here, as they are already covered in the Micro Python library.
Tip 4 - Using Sensor Vendor CodeAny sample code that can be "searched" from the sensor manufacturer, the engineer needs to go a long way to understand how the sensor works. Unfortunately, many sensor vendors are not experts in embedded software design, so don't expect to find a beautiful architecture and elegant example that can be put into production. Just use the vendor code to learn how this part works, and then the frustration of refactoring will emerge until it can be cleanly integrated into the embedded software. It may start like “spaghetti,†but using the manufacturer's understanding of how its sensors work will help reduce many of the weekends that have been destroyed before the product launch.
Tip 5 - Use a sensor fusion libraryThe chance is that the sensor's transmission interface is not too new, and no one has done this before. All libraries known, such as the "sensor fusion library" provided by many chip manufacturers, help developers quickly master, and even better, avoiding the reincarnation of their re-development or drastic modification of the product architecture. Many sensors can be integrated into a common type or category, and these types or categories will allow the driver to be developed smoothly and, if handled properly, are almost universal or less reusable. Look for these sensor fusion libraries and learn about their strengths and weaknesses.
Final thoughtWhen sensors are integrated into embedded systems, there are many ways to help improve design timeliness and ease of use. When developers start designing, through a high-level abstraction and learning how sensors work before integrating sensors into a lower-level system, they will never “walk the wrong wayâ€. The many resources that exist today will help developers “winâ€, without having to start from scratch.
Specific features of Grille Curtain LED Display
What is grille curtain LED Display Screen? grille curtain LED Display screen is made up of several pieces single led strip. It is a LED screen which looks like a grille and now become more and more popular among the LED industry. It can be called like strip Led screen. Since it shows us a hollowed-out , meshy visual effect, so LED display experts also call it mesh LED screen. This type of outdoor led screen mainly apply for wall of outdoor, glass wall, top of buildings, Column ads and led Curtain and so on.
Cross-time design of grille curtain LED breaks the limitation of traditional LED display for buildings and walls, makes the assembly project easier and selective. Maybe that is the reason why it can be used widely among all the field. Now let`s CATA editor introduce some technical advantage and how it makes the led screen project easier.
Grille curtain LED Screen technical featureⶠLight weight and anti-wind
Grille curtain LED Screen technical featureâ· High energy efficiency and low consumption
Grille curtain LED Screen technical feature⸠High integrate design
Grille curtain LED Screen technical featureâ¹ IP67 protection level
Grille curtain LED Screen technical feature⺠easy assembly and maintenance
Led Video Curtain,Large Led Curtain Screen,Media Led Grid Display,Custom Curtain Led Display
Shenzhen Priva Tech Co., Ltd. , https://www.privaled.com