Wiki » History » Version 2
Girish Kumar, 14 Jul 2025 10:22 AM
1 | 2 | Girish Kumar | |
---|---|---|---|
2 | 1 | Girish Kumar | # OutPlay architecture |
3 | --- |
||
4 | 2 | Girish Kumar | ## Feature checklist |
5 | |||
6 | ### Sensor module feature |
||
7 | 1 | Girish Kumar | ``` |
8 | 2 | Girish Kumar | Feature checklist: |
9 | 1. Should be able to join and rejoin a given Wi-Fi SSID |
||
10 | 2. able to register itself with the cluster |
||
11 | 3. Always listen to MQTT for any incoming command |
||
12 | 4. Listen to the proximity sensor in the specified time window |
||
13 | 5. Play a sound first, and start the countdown LED |
||
14 | 6. Record valid play if input (proximity sensor) is within the valid play window. |
||
15 | 7. sends hit/miss to MQTT |
||
16 | 8. able to respond to a ping message if asked. |
||
17 | ``` |
||
18 | |||
19 | ### App module feature: |
||
20 | 1 | Girish Kumar | ``` |
21 | 2 | Girish Kumar | Feature checklist: |
22 | 1. Able to register and deregister the sensor module to the spatial court location. |
||
23 | 2. able to send a play command to the sensor module and wait for the reply. |
||
24 | 3. if failed to receive a reply, then go to the next sensor module. |
||
25 | 4. able to record the hits and misses with time. |
||
26 | 5. able to define game profiles. |
||
27 | 6. able to ping/pong sensor module. |
||
28 | 7. able to log the events for game analysis. |
||
29 | 1 | Girish Kumar | |
30 | 2 | Girish Kumar | ``` |
31 | |||
32 | 1 | Girish Kumar | # Hardware requirements |
33 | --- |
||
34 | 2 | Girish Kumar | ``` |
35 | ``` |
||
36 | |||
37 | 1 | Girish Kumar | |
38 | # Firmware requirements |
||
39 | --- |
||
40 | |||
41 | # communication methods |
||
42 | --- |
||
43 | |||
44 | # Master node requirements |
||
45 | --- |
||
46 | |||
47 | # App design |
||
48 | --- |
||
49 | |||
50 | # log, events, diagnose |
||
51 | --- |
||
52 | |||
53 | # game play profiles ( i.e. play_mode, time_played, success rate), |
||
54 | --- |