Presentation
- For each project, 8-10 minutes are allocated for the presentation (group of two) or 12-15 minutes (group of three).
- It would be good to include the following content:
- Brief introduction of the project
- Division of functions at the system level (e.g. IPO principle)
- Brief overview of the electronics (= circuit in Simulide)
- Software concept (please use code lines sparingly in the presentation; an overview such as a flowchart is better)
- Results (if there were technical difficulties, these can also be shown from a technical perspective)
- What did you learn that other groups should know? (but not: developing good software takes longer than you think - everyone should have noticed that by now
)
- Please note that
- for a 10-minute presentation, 20 slides are definitely too many – 5 to 10 slides should be sufficient.
- lines of code and circuits are usually too small/complex to be readable on a slide.
Please show simplified overviews instead. A board layout (if relevant) is often not a problem as long as it does not contain elements that are too small and detailed.
- It would be great to include a little joke or fun element. This loosens up the presentation and is especially suitable at the beginning or the end, for example as a hook for the project.
- Your electronic system should also be shown “live” - ideally in operation or in a way that illustrates the function (e.g. measurement with an oscilloscope, input with a function generator, substitution of boards). In most cases, this presentation fits well after the results.
- Keep an eye on the time!
Possible Software for Creating a Video
If you would like to include short video clips, the following tips may help you:
- For screen capturing, the built-in Windows 10 tool Windows Game Bar can be used (<Win> + G --> “Capture” window --> start recording).
Recording can also be started directly with <Alt> + <Win> + R. - For editing, you can use, for example, the Microsoft Expression Encoder or OBS Studio.
Submission
Please note the following instructions for submitting the final software.
- Please submit the following components:
- Project folder from Microchip Studio
- Developed simulation (*.simu)
- Short text explaining how to use the software in the simulation.
- For complex state machines in the code, a flowchart may be useful (if the description in the code is too cumbersome)
- Please remove files that are not necessary, i.e. leave out old, unused files and old versions if you created any.
- Submission is via https://git.mexle.org/
Place all files from the Microchip Studio folder in GitLab in your project under the folder “91. Code Submission”. - Check whether these files can be used to build runnable code in a new project.
- If anything special has to be considered (e.g. defining new compiler symbols such as F_CPU), this should be included in the program description (comment in the code) or in a separate text file.
Please note the Requirements for Software Development, especially the evaluation XLS file.