Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
didattica:magistrale:esa:ay_1718:main [2018/03/06 15:37]
pezzuoli 		didattica:magistrale:esa:ay_1718:main [2020/09/17 16:55] (current)
Line 21: Line 21:
  
 **Objective of the course** **Objective of the course**
-  * Provide a minimum approach to electronccis concept ​and components, ​to develop an architecture for an embedded system. +  * Provide a minimum approach to electronic concepts ​and components, develop an architecture for an embedded system. 
-  *Provide also needed skills in the embedded system enviorement regarding:+  * Project and development of an embedded system using fast prototyping instruments. 
 +  * Provide also needed skills in the embedded system enviorement regarding:
     * Business - budgeting and time management     * Business - budgeting and time management
     * Software engineering/​reengineering     * Software engineering/​reengineering
Line 59: Line 60:
      * BOM      * BOM
      * PCB, schematics, cricuits      * PCB, schematics, cricuits
 +
  
 **Peripherals ​ and Communication** **Peripherals ​ and Communication**
Line 72: Line 74:
      * Signal Analysis ​      * Signal Analysis ​
      * Type of sensors ​      * Type of sensors ​
-     ​* ​Temperature, light, accelerometer,​ pressure, IMUs, +     ​* ​Sensors Overview  
 +     * Actuactors Overview 
 +     * IMUs, Accelerometers, Gyroscopes and Magnetometers
         ​         ​
- 
 </​WRAP>​ </​WRAP>​
 ---- ----
 ===== Study material ===== ===== Study material =====
 <WRAP box round center 95%> <WRAP box round center 95%>
 +Books: 
 +  * Making Embedded Systems 
 +    * https://​books.google.it/​books/​about/​Making_Embedded_Systems.html?​id=VCOTy1xWZmQC&​source=kp_cover&​redir_esc=y
 ===== Exams ===== ===== Exams =====
 <WRAP box round center 95%> <WRAP box round center 95%>
 **Practice** **Practice**
-  * Projects ​(to be defined)+  * Projects ​
 **Theory** **Theory**
   * Theorical Questions   * Theorical Questions
 +**Exam Rules**
 +You have to notify at least 5 working days before oral exam that you're almost done with your documentation and i can take a look at it. 
 +If documentation 5 days before oral exam is not enough clear and detailed, you will receive an e-mail.
 +Three different scenarios will be available:
 +
 +  * Scenario 1: I tell you that you're not ready for the exam and you have to improve your documentation, ​ you will not have enogh time to   
 +  * Scenario 2: You are almost done, I leave comments about your documentation and you have to be done documentation in the right way 2 working day before exam (I'll check it again). ​
 +  * Scenario 3: You are ready and I will accept you at the oral exam.
 +
 +e.g. For exam on 11th June you should provide documentation on June 4th (5 working days before) but you can keep working on project development.
 +=================================================================================================
 +Prepare yourselves also for questions about what we did during lectures. ​
 +Communication protocols, busses, IMUs and so on. Expecially about something you used in your project.
 +=================================================================================================
 +Choices about accepting/​not accepting you at exams are not opinable, same for votes. ​
 +
 </​WRAP>​ </​WRAP>​