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 springen
(Die Seite wurde neu angelegt: „there will be different software components involved there is a '''firmware''' on each device there will be a '''hostsoftware (webserver)''' that runs on the pc…“)
 
(cleaned up)
 
(15 dazwischenliegende Versionen von 3 Benutzern werden nicht angezeigt)
Zeile 1: Zeile 1:
there will be different software components involved
<small>< [[HSC2011]]</small>


there is a '''firmware''' on each device
The EduBuzzer has software run in three parts:


there will be a '''hostsoftware (webserver)''' that runs on the pc/laptop
* [[HSC2011/Software/Firmware|Firmware]] running on the ATMega controllers (for hardware control and radio communication)
** 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/Software/ygor|Middleware]] running natively on the computer (for serving the firmware, managing communication and for persistence)
* A [[HSC2011/Software/Frontend|Frontend]] running in a web browser (containing the game logic itself)


this webserver will provide a webinterface to the '''javascript application'''
The communication through the whole software is described in the [[HSC2011/Communication|communication documentation]].


 
[[Kategorie:HSC2011]]
the firmware prototype is written by clifford and development will soon be taken over by someone else willing to contribute to the project
[[Kategorie:English]]
 
there are ''positions open'' for
- the webserver/serialcom (python)
- the webfrontend application logic (javascript)
- the webfrontent design (CSS)
- firmware and protocoldesign (AVR)

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.