Geschwindigkeitsmessstrecke mit Arduino: Unterschied zwischen den Versionen
| Zeile 30: | Zeile 30: | ||
==== LED Based 8 segment display ==== | ==== LED Based 8 segment display ==== | ||
A simple LED based 8 segment display was implemented for the project last time. For reference, the [https://www.mikrocontroller.net/articles/LED LED tutorial] guide for Micro-controller was used. But it had limitation. | A simple LED based 8 segment display was implemented for the project last time. For reference, the [https://www.mikrocontroller.net/articles/LED LED tutorial] guide for Micro-controller was used. But it had limitation. | ||
So we are now upgrading the display with [https:// | So we are now upgrading the display with [https://datasheetgo.com/c547b-datasheet-npn-transistor/ C547B transistor]. | ||
==== Future development ==== | ==== Future development ==== | ||
Instead of using a led based display we can implement MQTT protocol to get the end result from the sensor in our smartphone with help of raspberry pi. That will allow to record the result more conveniently. During the implementation of MQTT protocol, the raspberry pi module will work as MQTT broker and both Arduino and Smartphone will be MQTT client. The broker will receive sensory data from the Arduino (1st client) and then it will forward the message to the smartphone (2nd client). As the system will only be used to receive the data collected by the sensor and processed by the arduino and not to control the sensor, it will be uni-directional; that means we will opt out the part to control any sensor from the smartphone application. | Instead of using a led based display we can implement MQTT protocol to get the end result from the sensor in our smartphone with help of raspberry pi. That will allow to record the result more conveniently. During the implementation of MQTT protocol, the raspberry pi module will work as MQTT broker and both Arduino and Smartphone will be MQTT client. The broker will receive sensory data from the Arduino (1st client) and then it will forward the message to the smartphone (2nd client). As the system will only be used to receive the data collected by the sensor and processed by the arduino and not to control the sensor, it will be uni-directional; that means we will opt out the part to control any sensor from the smartphone application. | ||
Version vom 16. Mai 2023, 14:56 Uhr
Author: Syed Rafsan Ishtiaque
Category: Part of Main Internship
Duration: 02.05.2023 - 00:00:0000
Supervisor: Prof. Dr.-Ing Ulrich Schneider
Objective
Developing the speed measuring unit for any car project
Hardware
Sensor
1. Sharp 2D120X F 09
The Sharp distance measuring sensor is used to determine the speed/ velocity of the car unit. In this case, two identical sensors were used. According to the manufacturer SHARP, the range of the sensor is 4 cm to 30 cm, typical response time apprx. 39 ms, typical start up delay apprx. 44 ms, Average Current Consumption: 33 mA. The operating temperature is -10°C to 60°C, so that is ideal for this project as it is initially an indoor project. according to the stamp on the sensor, the manufacturing date was September 2016. According to the data sheet, the sensor should be mounted on any frame in such way that it gives the optimum result. For that the general instructions are available on the Data Sheet.
Current status of the Speed Tracker
The sensor parts are fully functional. The display board of the measured speed is under development
Display
LED Based 8 segment display
A simple LED based 8 segment display was implemented for the project last time. For reference, the LED tutorial guide for Micro-controller was used. But it had limitation. So we are now upgrading the display with C547B transistor.
Future development
Instead of using a led based display we can implement MQTT protocol to get the end result from the sensor in our smartphone with help of raspberry pi. That will allow to record the result more conveniently. During the implementation of MQTT protocol, the raspberry pi module will work as MQTT broker and both Arduino and Smartphone will be MQTT client. The broker will receive sensory data from the Arduino (1st client) and then it will forward the message to the smartphone (2nd client). As the system will only be used to receive the data collected by the sensor and processed by the arduino and not to control the sensor, it will be uni-directional; that means we will opt out the part to control any sensor from the smartphone application.