PRE2018 3 Group3

From Control Systems Technology Group
Jump to navigation Jump to search

Preface

Group Members

Name Study ID Number
Max Hanssen Industrial Design 1257269
Jorick van Hekke Electrical Engineering 1225185
Suryanto Horlez Computer Science 1286714
Joeri Schults Mechanical Engineering 1266330
Jules Vaes Mechanical Engineering 1263196

Problem statement

The railways in the Netherlands are very vulnerable for all kinds of things. Think for example of fallen leaves, snow, weeds, dead animals, etc. These factors lead to unwanted delays. This autonomous robot is designed to tackle this problem and prevent delays from happening.

Subject

Autonomous railway cleaning robot

Objectives

  • The system must be able to navigate through the Dutch railway system autonomously
  • The system must be able to recognize the different obstacles on the railway
  • The system must be able to clean the railway from obstacles autonomously.
    • For special occasions the system must alert the involved companies
  • The system must provide a short-term solution for certain problems
  • The system must avoid colliding with obstacles
  • The system must be deployable at any time
  • The system must not hinder the human operated train traffic

Users

The NS and ProRail. Indirect users are the train-users.

State of the Art

The past project of PRE2016 3 Group 3 was conducted in a similar design case. Hence, the wiki of this project was analysed and along with the 63 references of their wiki page (numbered 1 - 63).

  1. Smith, O. (2016). No more commuter misery? Trains fight leaves with lasers. Retrieved from http://www.thememo.com/2016/09/12/train-leaves-leaf-zapping-trains-rail-safety-and-standards-board-are-arming-up-with-microwaves-and-lasers/ : asdfgfh
  2. 2
  3. 3
  4. 4
  5. 5
  6. 6
  7. 7
  8. 8
  9. 9
  10. 10
  11. 11
  12. 12
  13. 13
  14. 14
  15. 15
  16. 16
  17. 17
  18. 18
  19. 19
  20. 20

Approach

We will conduct a study and analysis and will come up with a design. If time allows it, we will make a shitty prototype as well.

Planning

Planning Monday Thursday Remarks
Week 1 Introduction + groups The plan Plan finished before Monday
Week 2 Feedback session + research problem approach Research + contact NS Complete questions for NS
Week 3 Feedback session + research solution Research solutions Complete possible solutions for the system
Week 4 Feedback session + research components Components list Complete possible components for the system
Week 5 Feedback session + integrating integrating Integrate the components in one coherent system
Week 6 Feedback session + budget calculation Extra time to complete the above Gather feedback
Week 7 Feedback session + finalize Finalize + presentation preparation Finish remaining tasks
Week 8 Feedback session + finalize + presentation preparation Finalize + presentation preparation Make sure everything is according to the assignment

Milestones

  • First group meeting with everyone
  • Solutions ready
  • Integrating solution
  • Final report
  • Final design
  • Presentation
  • A program that differentiates glass, plants, snow from the other trash

Deliverables

  • Wiki (report)
  • Final presentation
  • (shitty prototype)

Who will do what

  • Sunny (Computer Science): the software of the design
  • Jorick (Electrical Engineering): the electronic components of the design.
  • Max (Industrial Design): the look and feel of the design.
  • Jules (Mechanical Engineering): the 3D model of the design and the general functioning of the design.
  • Joeri (Mechanical Engineering): the 3D model of the design and the general functioning of the design.
  • Everyone:comment/help on other peoples work

Brainstorm (extra)

Move to logbook

Image: 250 pixels