HSC2011/Software: Unterschied zwischen den Versionen

aus Metalab, dem offenen Zentrum für meta-disziplinäre Magier und technisch-kreative Enthusiasten.
Wechseln zu: Navigation, Suche
(current state)
(firmware: open issues)
Zeile 19: Zeile 19:
  
 
During firmware development, a serial protocol was developed, which is documented [http://github.com/Metalab/hsc2011/blob/master/firmware/README.serialprotocol alongside the firmware].
 
During firmware development, a serial protocol was developed, which is documented [http://github.com/Metalab/hsc2011/blob/master/firmware/README.serialprotocol alongside the firmware].
 +
 +
Open issues are in descending priority:
 +
 +
* redirect messages for controlling the base station itself
 +
* fine-tuning timing for re-sends and responses (may only need validation)
 +
* virtual machine, including read/write commands
 +
** compiler
 +
* reading battery status (might require some hardware modification)
 +
* reading RSSI state
 +
* multicasts
 +
* <del>removing arduino specific stuff to reduce resource usage</del> (not a priority unless resources become a real problem)
  
 
== PC server ==
 
== PC server ==

Version vom 1. April 2011, 22:46 Uhr

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/laptop

this webserver will provide a webinterface to the javascript application

there are positions open for

  • the webserver/serialcom (python) amir implements this job with java
  • the webfrontend application logic (javascript)
  • the webfrontent design (CSS)
  • firmware and protocoldesign (AVR)

firmware

The current firmware is written by clifford and chrysn and is currently capable of both being a buzzer and being a base station; the base station can control all the hardware in the buzzers and receive events. It can be checked out from the firmware part of the project repository.

During firmware development, a serial protocol was developed, which is documented alongside the firmware.

Open issues are in descending priority:

  • redirect messages for controlling the base station itself
  • fine-tuning timing for re-sends and responses (may only need validation)
  • virtual machine, including read/write commands
    • compiler
  • reading battery status (might require some hardware modification)
  • reading RSSI state
  • multicasts
  • removing arduino specific stuff to reduce resource usage (not a priority unless resources become a real problem)

PC server

There is a proof-of-concept implementation of a serial controller and a simple voting game for debugging purposes in the repository. It demonstrates that the firmware can also do logins, handle disconnected clients and respond to events.