Five Techniques To Make Sensors Simpler


        Tip 1-start with the bus tool

        As a first step, engineers should take the form of a bus tool to limit the unknown when they first connect to the sensor. A bus tool is connected to a PC / PC and then to the sensor's I2C. SPI or other protocols that allow sensors to "talk". PC applications associated with bus tools provide a known and working source for sending and receiving data, not unknown. An unauthenticated embedded microcontroller / MCU) driver. In the working environment of a bus tool, developers can send and receive messages to get an understanding of how this part works. Before attempting to operate at an embedded level.

        Tip 2-write transport interface code in Python

        Once the developer has tried to use the sensor with the bus tool, the next step is to write application code for the sensor. Instead, write application code in Python. Many bus tools configure plug-in plug-ins and sample codes in writing scripts. Python is usually one of the languages available in .NET. Writing applications in Python is fast and easy, and provides a way to test sensors in your application. This approach 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 test tests. Without the care of an embedded software engineer.

         Tip 3-testing sensors with Micro Python

         One of the advantages of writing the first piece of application code in Python is by calling Micro Python. Application program call to bus tool application programming interface (API) can be easily replaced. Micro Python operation in real-time embedded software. Many of these sensors are available to engineers to understand its value Micro Python operates in a Cortex-M4 processor and is a good environment. Not only is it simple, but there is no need to write I2C or SPI drivers here, because they are already covered in Micro Python's functional libraries.

          Tip 4-using sensor vendor code

          Tip 5-using a sensor fusion function library