S14: Power efficient security door system for light-rail using CAN bus
Contents
Grading Criteria
- How well is Software & Hardware Design described?
- How well can this report be used to reproduce this project?
- Code Quality
- Overall Report Quality:
- Software Block Diagrams
- Hardware Block Diagrams
- Schematic Quality
- Quality of technical challenges and solutions adopted.
Power efficient security door system for light-rail using CAN bus
Abstract
This project is about controlling the operations of doors and sensors in a light rail train, such that they are operated only when required, thus reducing power consumption. Currently, when a light rail halts at a station the driver opens all the doors of all the coaches. However, except for peak hours and especially during weekends and holidays, the number of people entering and exiting a train at a particular station is comparatively very low. Sometimes, only 2-3 people enter or exit a train and that too they use only 1 or 2 doors of the train. In such cases, operating all the doors is simply a waste of power. Our project provides a solution to this problem by allowing the driver to operate only selected doors as per the requirement. It senses from which coach the stop request was pressed or in front of which door the passengers are standing on a station to enter the train. Accordingly to these inputs it selectively operates only those particular doors. The rest are not operated and thus we not only save power but the reduced wear and tear of moving parts of doors enhances their lifetime. This project is based on the concept of CAN bus which is used for communication between sensors, switches and lights of different coaches of the train.
Objectives & Introduction
The primary objective is to understand and implement CAN bus communication between two or more SJOne boards, such that any node can send message to any node and upon receiving a CAN message take a desired action immediately. Our secondary objective is to use CAN protocol in real time application such as to control doors, sensors and switches of different coaches of a light-rail train. This application aims at operating the doors of a train selectively as per the requirement, rather than operating all the doors. This will reduce the power consumption and increase the lifetime of the doors.
Team Members & Responsibilities
- Ashish
- Concept and logic development, developing algorithm and hardware interface
- Anitha
- FreeRTOS software design, code development, verifying test cases
- Hasan
- Sensor, peripheral interface and testing of software code
Schedule
Show a simple table or figures that show your scheduled as planned before you started working on the project. Then in another table column, write down the actual schedule so that readers can see the planned vs. actual goals. The point of the schedule is for readers to assess how to pace themselves if they are doing a similar project.
Week# | Date | Task | Actual |
---|---|---|---|
1 | 02/27/2014 | Finalized scope of the project and ordered CAN transceiver TJA1040 | Completed. Deciding which tranceiver is compatible to SJone board |
2 | 03/06/2014 | Prepare complete block diagram with all components needed and draw the state diagram | Block diagram completed. State diagram finalization pending. Need to think more on different possibilities of event occurance when switching between states |
3 | 03/13/2014 | Complete state diagram and gather BOM of rest of the parts | Completed state diagram on book, but pending to draw in paint and upload on wikipage. BOM parts received. |
4 | 03/20/2014 | Prepare the hardware prototype boards for all three coaches | Task completed except for sensors, relays and motor interface (to be decided at the end after testing CAN functionality successfully) |
5 | 03/27/2014 | Read on CAN bus protocol and transceiver from datasheet | Task completed |
6 | 04/03/2014 | Check the transceiver along with SJone board and build basic driver to run CAN bus | Testing could not be completed successfully, understanding and testing of CAN code is in progress. |
7 | 04/10/2014 | Perform testing of CAN driver. Develop logic for the project and implement it on CAN bus. | Self test loop for CAN driver failed. Debugging it is in progress. (Running behind the schedule by 1 week, Need to work hard to cope-up and complete the project on time.) |
8 | 04/17/2014 | Testing the CAN protocol and verifying the logic. | Self test for CAN was successful, Tx and Rx between two CAN controllers was tested successfully. |
9 | 04/24/2014 | Interface sensors, motors and test with CAN bus protocol. | Interface of fire sensor, stepper motor was tested successfully, however DC motor is pending. CAN test for hardware level address filtering is still failing and its diagnosis is in progress |
10 | 05/01/2014 | Testing and debug of the prototype board and code. Final touch-up on the design, code and wikipage | |
11 | 05/08/2014 | Final demonstration |
Parts List & Cost
Give a simple list of the cost of your project broken down by components. Do not write long stories here.
Design & Implementation
The design section can go over your hardware and software design. Organize this section using sub-sections that go over your design and implementation.
Hardware Design
Discuss your hardware design here. Show detailed schematics, and the interface here.
Hardware Interface
In this section, you can describe how your hardware communicates, such as which BUSes used. You can discuss your driver implementation here, such that the Software Design section is isolated to talk about high level workings rather than inner working of your project.
Software Design
Show your software design. For example, if you are designing an MP3 Player, show the tasks that you are using, and what they are doing at a high level. Do not show the details of the code. For example, do not show exact code, but you may show psuedocode and fragments of code. Keep in mind that you are showing DESIGN of your software, not the inner workings of it.
Implementation
This section includes implementation, but again, not the details, just the high level. For example, you can list the steps it takes to communicate over a sensor, or the steps needed to write a page of memory onto SPI Flash. You can include sub-sections for each of your component implementation.
Testing & Technical Challenges
Describe the challenges of your project. What advise would you give yourself or someone else if your project can be started from scratch again? Make a smooth transition to testing section and described what it took to test your project.
Include sub-sections that list out a problem and solution, such as:
My Issue #1
Discuss the issue and resolution.
Conclusion
Conclude your project here. You can recap your testing and problems. You should address the "so what" part here to indicate what you ultimately learnt from this project. How has this project increased your knowledge?
Project Video
Upload a video of your project and post the link here.
Project Source Code
Send me your zipped source code and I will upload this to SourceForge and link it for you.
References
Acknowledgement
Any acknowledgement that you may wish to provide can be included here.
References Used
List any references used in project.
Appendix
You can list the references you used.