Welcome to your wiki!
This is the default page, edit it as you see fit. To add a new page simply reference it within brackets, e.g.: [SamplePage].
The wiki uses Markdown syntax.
Introduction
Today, road safety and technology are closely linked. The driver is increasingly seen in his conduct, and for the safety of all. New technologies are continually being developed in offices and major research in the automotive industry.
We have dedicated this multidisciplinary project team to the improvement in road safety. Therefore we will base our work on visibility problems inherent in vehicles, and in based on two technologies. We will focus our study on two issues of visibility within the vehicle.
Visibility is a key point for the safety of all road used. Requires that the driver can see and be seen. We decided to name our project "Lynx". This project is divided into two parts:
The first point on which the team is working with the guidance in the event of inclement weather such as dense fog. When very severe weather have places, or fog is present on the road, it becomes very difficult for the driver to see his environment and judge distances and speeds of other users. The aim is to address this problem in innovative ways. The idea is to communicate these vehicles to obtain information directly from surrounding vehicles. The focus will warn the driver clearly, the distance separating the user directly in front, as well as the awareness to adopt a safe distance correct.
The second point on which we want to develop a solution is for the problems vehicle headlights. A car with a faulty headlight is a dangerous vehicle for himself and for others. The headlights are elements providing the driver that his movements are visible to all. Today, the moment you realize that a light fails, it is already too late and it is necessary to replace quickly. We want to act in the sense of anticipation at this level: the driver must be notified before a problem will occur on one of the lights. In solving this problem, the driver will not risk more than circulate with a fire beacon missing.
All our project will focus around the issue of visibility using the CAN protocol of the vehicle and inter-vehicle communication technologies.
1. Architecture project
Our system as a solution could be clearly identified as improved road visibility, at all levels. As we stated in the introduction, this project has two distinct axes. That is why we discern two systems:
The aid guide is the system that will:
- Simulate two vehicles and CAN protocol using the software Vector CANoe
- Create a wireless connection between the two simulations (802.11 g)
- Send and receive information from another vehicle simulator (Antenna Wifi, ADC / Wifi)
- Process and perform calculations on the data received (Easypic 5)
2. Architecture system 1
The first system of this project is that making aid guide. This system represents a situation of "real" life, which will be simulated using various intermediaries (hardware and software) of the school. It will consist of two subsystems, symbolizing the vehicles that communicate together.
The test of the electrical shall:
- Compare the time running lights with the estimated life of the bulbs
- Tell the driver when the end of life of the bulb estimate is close
This document aims to clearly define the project's architecture, the means and technologies used to carry it out and explain all its technical and organizational part. It also describes the great utility for you to own this application in order to drive well under heavy fog.
Architecture system
C2C
WIFI (802.11)
=> Mais ici, on va surement d'abord proposer la version éthernet avec le code associé
Informations about WIFI :
For Intelligent Transport System (ITS) researchers have realized that it was very difficult to use the WiFi standard (80211.g) for several reasons:
- Firstly, the main problem of these inter-vehicular communications is time. Two cars crossing in opposite directions, can be connected via WIFI little time. Or authentication in 802.11g takes too long, it will be realized when we connect with his computer. It is therefore deleted in 802.11p.
...
Cf suite avec Ethernet plutôt que Wifi
3. Architecture system 2
Our project is also composed by a a wear detector headlights.
We are going to explain it in this paragraph.
The simulation is carried out thanks to the software Canoe and Development EasyPIC5 electronic card. Canoe simulates the activation of headlamps (dipped beam or cross). At the time of ignition (simulated) fires, the microcontroller card information recovered activation of lights and trigger the stopwatch. Each bulb has an estimated life, for example, halogen lamps may vary from 2000 to 3000 hours of use, depending on the model.
Recall that in a glass ampoule under vacuum, a tungsten filament is heated to incandescence by the passage of an electric current (Joule effect). Some bulbs contain an inert gas (argon, krypton or xenon) to increase their lifespan (maximum 1500 hours). In contrast, in a halogen bulb: a gas of the family halogens (fluorine, bromine or iodine) present in the bulb combines with the tungsten "sprayed" and is deposited on the filament. It is the increase in temperature, which improves its performance life (2 000 to 4 000 hours).
3.1 Subsystem 1
Firstly, the first subsystem is software that simulates the canoe CAN bus. The operation of this software has already been explained in the previous section. The objective in this part of the software is to simulate the headlights.
Canoe on the software you add a node that will manage the light switch with a boolean. Thus, we can enable and disable the headlights from the computer. When the software will return the value 1, ie that the headlights are turned on and when the boolean value will be 0, the headlights are off.
3.2 Subsystem 2
The second subsystem is the development EasyPIC5 card. It has an element that is the PIC18F microcontroller.
3.3 Microcontroller
The programming language of the microcontroller will be C.
We will create functions that will allow to calculate the wear headlamps. A value of "time" corresponding to the life of the lamp in hours will be seized. This data will be stored in the microcontroller.
We will test for a halogen bulb and we consider that the model chosen has a lifespan of 2500 hours (manufacturer's data). This variable will be named "time" in the following explanations.
3.4 Timers
When the user activates the headlights via CANoe simulation software, the microcontroller activates a timer (stopwatch).
Internally, the microcontroller does not count in seconds: he realizes overflows by 32 seconds and then it will take several timers to succeed to count seconds and in minutes then hours. Edge to the timer when the user stops the operation of its beam.
We will define a threshold value for which the operation of the lamp is more certain is that the lamp reaches its end of life and may soon stop working.
Suppose first that this value is 80% of the life of the bulb.
The bulb therefore will return in degraded after 1600 hours of operation.
The program is coded in C on the microcontroller and conduct a control loop operating time of the lamp. The microcontroller will then send the information to the remaining life of the bulb to the CAN bus which then transmit to the display.
In case the user should replace the bulb: failure, accident ... with a new bulb, then it should be a "reset" so that the software starts counting the life of the new bulb and system operation resume.
4 Tests / Simulation realization