Repository navigation
ED 2 Worksheet
To engineer a robust mechatronic system, it is necessary to distinctly separate the functional expectations of the end-user from the complex technical actuations required by the design engineer. The following matrix systematically identifies the nineteen core functions of the perpetual calendar, directly contrasting the simple user interface requirements against the corresponding mechatronic processing, sensor calibration, and mechanical actuation tasks that must occur within the internal chassis.
| Serial No. | Functions from User Perspective | Functions from Designer Perspective |
|---|---|---|
| 1 | display the current date | actuate stepper motors to position physical dials correctly |
| 2 | display the day of the week | process Zeller's congruence algorithm to drive the day indicator |
| 3 | month selection | process physical rotary encoder signals to navigate month arrays |
| 4 | year selection | process tactile push-button inputs to increment or decrement the active year |
| 5 | determines the correct date for the selected month and year | restrict motor actuation beyond valid date ranges to prevent mechanical jamming |
| 6 | leap year adjustment | execute logic algorithms to automatically alter February's physical step count |
| 7 | month end detection | implement closed-loop sensor feedback to safely reset motor positions |
| 8 | day and date matching | utilise Hall effect sensors for absolute zero-position calibration upon startup |
| 9 | previous month navigation | reverse motor polarity to physically rotate mechanical dials backwards |
| 10 | next month navigation | initiate forward motor actuation for advancing the mechanical display |
| 11 | previous year navigation | process decrement signals safely within the microcontroller memory limits |
| 12 | next year navigation | maintain temporal data accuracy using a battery-backed real-time clock module |
| 13 | compact design which occupies less space | arrange concentric mechanical dials to minimise the overall physical footprint |
| 14 | portable use | select lightweight acrylic or foam board materials to reduce overall mass |
| 15 | low maintenance operation | regulate DC power supply to ensure sufficient torque and prevent motor stall |
| 16 | easy to read display | illuminate the mechanical viewing window using internal light emitting diodes |
| 17 | error free date display | implement optical sensors to perfectly align display elements with the outer casing |
| 18 | long term usability | mount all electronic and mechanical components securely on a rigid internal chassis |
| 19 | easy date adjustment | ensure smooth mechanical power transmission through carefully calculated gear ratios |
The morphological matrix allows the design team to visualise the multiple physical and electronic pathways available to solve each isolated engineering sub-function.
## 3. Concept Design
By combining the different physical means established in the morphological chart, four distinct conceptual architectures have been synthesised. The matrix below details how each concept mathematically and mechanically addresses the primary sub-functions of the perpetual calendar, ranging from tactile incrementation loops to advanced network synchronisation protocols.
| Serial No. | Subfunctions | Concept 1 | Concept 2 | Concept 3 | Concept 4 |
|---|---|---|---|---|---|
| 1 | adjust the day | Tactile push button increment | Rotary encoder scroll selection | Capacitive touch interface | Matrix keypad direct entry |
| 2 | adjust the date | Microcontroller variable update | RTC internal register overwrite | Auto-sync via Wi-Fi module | Potentiometer analog mapping |
| 3 | adjust the month without error | Software array boundary logic | RTC integrated month tracking | Network time server extraction | Pre-programmed EEPROM lookup |
| 4 | account for leap year | Modulo 4 software algorithm | DS3231 hardware compensation | Cloud server automatic adjustment | Standard C time library logic |
| 5 | determine correct date for selected month and year | Zeller's congruence calculation | I2C bus data retrieval | Network time protocol decoding | Algorithm subroutine processing |
| 6 | repeat the calender cycle | Infinite software while loop | Continuous RTC battery backup | Periodic internet synchronisation | Hardware timer interrupt |
| 7 | provide easy resetting | Hardware reset pin switch | Software default state subroutine | Remote web interface button | Power supply cycle toggle |
The internal functional logic of the mechatronic calendar relies on a structured hierarchy to effectively partition the complex processing load. The primary node of the mechatronic perpetual calendar branches into three vital operational arms. The first arm handles taking user inputs, which further divides into the sub-tasks of adjusting the day, adjusting the date, and adjusting the month cleanly. The central processing arm is responsible for doing the brain work, specifically configured to account for leap year algorithms and to determine the correct date. Finally, the physical actuation arm is assigned to output and maintenance, which encompasses repeating the calendar cycle, providing easy resetting capabilities, and running the physical display mechanism for the end-user.