HSC2011/Communication: Unterschied zwischen den Versionen

(3 dazwischenliegende Versionen von 2 Benutzern werden nicht angezeigt)

Zeile 1:

Most pieces of information (events, commands, etc.) travel through the whole [[HSC2011/Software|software stack]]. The steps there and interfaces are:

{|border="1"

{| border="1" cellspacing="0" cellpadding="2" width="100%" style="border-collapse:collapse;"

! File || Implementation || Interface || Description

!style="background:#D3D3D3"| File

!style="background:#D3D3D3"| Implementation

!style="background:#D3D3D3"| Interface

!style="background:#D3D3D3"| Description

|-

Zeile 35:

Zeile 40:

|rowspan=2| <tt>software/ …/ base.js</tt> || JavaScript application || || library for developing games

|-

| || <tt>Edubuzzer.event_occurred</tt>, … || game development API

| || <tt>Edubuzzer.event_occurred</tt>, <tt>Edubuzzer.send_set()</tt>… || game development API

|-

| '''your application''' ||colspan=2| whatever you like ||

|}

== Serial format ==

The serial serialization format is important as it is passed through the whole software stack (from C to JavaScript, although both also use processed forms of it). Even if it not directly used in the "wire" format strucs and the JavaScript object representation, it can be used to understand the other representations.

The serial format documentation also explains lots of details of how the devices can be controlled, so it is recommended reading for game developers env everyone else.

Read it in full length at [[HSC2011/Communication/Serial protocol]].

If you want to test the devices manually on the serial console, use a baudt rate of 57600.

[[Category:HSC2011]]

[[Category:English]]