Week #5

Week #5 #

Team #

Team Members #

Team MemberTelegram AliasEmail AddressTrackResponsibilities
Dmitriy Vizitei (Lead)@otkisaevd.vizitei@innopolis.universityLow level (embedded) + Electric circuit engineer + testingProject coordination, task delegation, programming and testing prototypes
Senea Belykh@SenyaZenyas.belykh@innopolis.universityLow level (embedded) + Electric circuit engineerProgramming and testing prototypes
Dmitry Ryabov@theDioxiderd.ryabov@innopolis.universityLow level (embedded)Programming
Anas Hamrouni@reachnastaa.hamrouni@innopolis.universityDesign engineerDesigning 3D models
Andrew Pavlov@chaleshka_0and.pavlov@innopolis.universityTech writerDocument the work and write reports

Feedback #

Through Alexander Maloletov (Director of the Robotics Development Center in Innopolis), we agreed that upon completion of the order, the project participants will receive a lump sum payment.

Iteration & Refinement #

Performance & Stability #

When the magnet slides post reed switches, there is a chance to get a value equal to 0. This is due to the current solution and design. There is a metric associated with the gaps between switches.
An iteration solution would be to reduce the size of reed switches to such an extent that a negligibly small gap between the switches is reached, which would guarantee a constant and unambiguously set position of the float.

Weekly commitments #

Individual contribution of each participant #

MemberContribution
Dmitriy ViziteiAssembly of a product, communication, testing: photo, video 1, video 2, video 3
Senea BelykhLittel change design of board and design of a microcontroller board
Dmitry RyabovDetermining reed switch based on voltage: photo, commit 1, commit 2
Anas HamrouniPCB design + review of dimensions
Andrew Pavlov5nd week report.

Plan for Next Week #

  • Build the microcontroller board
  • Complete the prototype assembly
  • Сontact the customer to confirm our product solution

Confirmation of the code’s operability #

We confirm that the code in the main branch:

  • In working condition.
  • Run via docker-compose (or another alternative described in the README.md).