HSC2011/Software: Unterschied zwischen den Versionen
aus Metalab Wiki, dem offenen Zentrum für meta-disziplinäre Magier und technisch-kreative Enthusiasten.
Zur Navigation springenZur Suche springenChrysn (Diskussion | Beiträge) (→firmware: remove section, moved to firmware) |
Chrysn (Diskussion | Beiträge) (cleaned up) |
||
| (3 dazwischenliegende Versionen von einem anderen Benutzer werden nicht angezeigt) | |||
| Zeile 3: | Zeile 3: | ||
The EduBuzzer has software run in three parts: | The EduBuzzer has software run in three parts: | ||
| − | * [[HSC2011/Firmware|Firmware]] | + | * [[HSC2011/Software/Firmware|Firmware]] running on the ATMega controllers (for hardware control and radio communication) |
| − | ** The firmware can run additional code inside a [[HSC2011/ | + | ** The firmware can run additional code inside a [[HSC2011/Software/embedVM|virtual machine]] for tasks like LED fading, meldoy beeping or even autonomous games. |
| − | * [[HSC2011/ | + | * [[HSC2011/Software/ygor|Middleware]] running natively on the computer (for serving the firmware, managing communication and for persistence) |
| − | * A [[HSC2011/Frontend|Frontend]] running in a web browser (containing the game logic itself) | + | * A [[HSC2011/Software/Frontend|Frontend]] running in a web browser (containing the game logic itself) |
The communication through the whole software is described in the [[HSC2011/Communication|communication documentation]]. | The communication through the whole software is described in the [[HSC2011/Communication|communication documentation]]. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
[[Kategorie:HSC2011]] | [[Kategorie:HSC2011]] | ||
| + | [[Kategorie:English]] | ||
Aktuelle Version vom 2. Mai 2011, 19:54 Uhr
< HSC2011
The EduBuzzer has software run in three parts:
- Firmware running on the ATMega controllers (for hardware control and radio communication)
- The firmware can run additional code inside a virtual machine for tasks like LED fading, meldoy beeping or even autonomous games.
- Middleware running natively on the computer (for serving the firmware, managing communication and for persistence)
- A Frontend running in a web browser (containing the game logic itself)
The communication through the whole software is described in the communication documentation.
