This is an advanced/doctoral project course that gives 7.5 ECTS credits. The course is given during the second study period of the fall semester (HT2), or any time during the year upon agreement between students and a teacher from the Automatic Control department. (Contact Kristian if you are interested in taking the course at another time than HT2.) See the course syllabus for more information. Course evaluations by previous participants are available through the CEQ system (Current course code: FRTN40, old course code: FRT090).
Below is a timeline of the course. Participation is mandatory for all listed activities, except for the pre-meeting (for which it is still highly recommended). Link to course in LTH schedule system.
- Mon Oct 22, 15:15-17:00 in M:B. Course introduction lecture (slides). Apart from a general introduction and presentation of project proposals (book of abstracts), an introduction to git version management and the gitlab issue tracking system will be given.
- Tue Oct 23. E-mail a wish list of three (3) projects in prio order (see book of abstracts), most desirable first (and possibly list of group members) to email@example.com. Decisions on groups will be communicated as soon as possible via web page and e-mail.
- Mon Nov 5, 10:15-12:00 in MA 6. Tutorial lecture on report writing in LaTeX, and good opportunity to meet group members and work on project plan.
- Fri Nov 9. Project plan should be pushed to git (instructions here). Each group should have completed component order spread sheet (link circulated via course mail list) with all components needed for the project.
- Mon Nov 19, 13:15-15:00 in M:2112B. Feedback seminar 1 on modeling and design.
- Wed Dec 5. The report for feedback seminar 2 should be pushed to git (instructions here) to allow peer review prior to the seminar.
- Mon Dec 10, 13:15-15:00 in M:2112B. Feedback seminar 2 on control and implementation. Each group presents and provides feedback on another groups' report (instructions here).
- Thu Dec 20. A complete final report should be pushed to git (instructions here) and project advisor notified.
- Mon Jan 7. All groups should leave review feedback on another group's final report (instructions here).
- Thu Jan 10 13:15-17:00 in Lab A+B. Project demonstrations. Half day, either Thu Jan 10 or Fri Jan 11. Decided by vote on intro meeting Oct 22.
- Fri Jan 18. Revised (print ready!) final report should be pushed to git (instructions here) and project advisor notified.
- Fri Jan 25. Day for LADOK registration of course results. See below for credit requirements.
For course credits, it is required to
- participate in the project work and all mandatory activities (see above).
- clean up after your group in the lab.
- return all borrowed items, such as tools, components, etc. and make sure to have your group's project advisor e-mail Kristian, with cc to Pontus and group members, that your group has returned everything and cleaned up.
- do the above within stipulated deadlines, and make sure to have each item approved by your group's project advisor.
Apart from the scheduled events, we will mainly use the course web (this) and the e-mail list FRTN40@list.control.lth.se (to which your e-mail address registered in LUCAT has been added. Important: if you have not received a welcome e-mail by the course start date, notify one of the teachers. The issue/milestone handling system tied to your repo in gitlab (instructions here) will also be a good way for communicating progress and issues, both within the project group and with your project advisor.
You decide with your project advisor on when, and how frequently, to schedule supvervision meetings. However, you must schedule at least one meeting per course week. A good idea is to meet up with the group before meeting the project advisor, to get on the same page, assemble a status summary, and identify the issues that are the most burning.
We hope that you are enjoying the course. Whether or not, we appreciate feedback and suggestions on how to improve. You can give it directly to course staff, anonymously via the student representatives, or via an anonymous online form.
Anton Cervin (firstname.lastname@example.org)
Charlotta (Lotta) Johnsson (email@example.com)
Martina Maggio (firstname.lastname@example.org)
Kristian Soltesz (email@example.com, course responsible)
The role of the student representative is described here (unfortunately only in Swedish).
- Git / Git@wikipedia
- How to upload a Modelica model to the NXT (pdf)
- nxtOSEK for Lego Mindstorms NXT
- C Tutorial
- Lego Mindstorms NXT
- NXC for Lego Mindstorms NXT.
- NXT motor characteristics 1.
- NXT motor characteristics 2.
- T2N communication with Lego NXT.
- HiTechnic Lego NXT sensors
- RWTH Mindstorms NXT Toolbox for Matlab