doc: add packet structure to README
This commit is contained in:
parent
7bc99720ba
commit
34cf67d4b7
1 changed files with 43 additions and 0 deletions
43
README.md
43
README.md
|
@ -13,3 +13,46 @@ Because blinkenwall v3 has `64 * 96 = 6144` pixels, driving it at 100 FPS requir
|
||||||
(typically SPI), so this would require coordinating several microcontrollers in parallel. A
|
(typically SPI), so this would require coordinating several microcontrollers in parallel. A
|
||||||
much more integrated solution is to instantiate as many WS2812 drivers as desired in an FPGA,
|
much more integrated solution is to instantiate as many WS2812 drivers as desired in an FPGA,
|
||||||
then point the entire video firehose at the FPGA.
|
then point the entire video firehose at the FPGA.
|
||||||
|
|
||||||
|
## Ethernet communication
|
||||||
|
|
||||||
|
The controller accepts UDP packets containing image data on port 61437 ("PIXEL"). Each packet
|
||||||
|
contains color data for one strand of LEDs.
|
||||||
|
|
||||||
|
The packet structure is as follows:
|
||||||
|
|
||||||
|
<table>
|
||||||
|
<tr>
|
||||||
|
<th></th>
|
||||||
|
<th>00</th>
|
||||||
|
<th>01</th>
|
||||||
|
<th>02</th>
|
||||||
|
<th>03</th>
|
||||||
|
<th>04</th>
|
||||||
|
<th>05</th>
|
||||||
|
<th>06</th>
|
||||||
|
<th>07</th>
|
||||||
|
<th>08</th>
|
||||||
|
<th>09</th>
|
||||||
|
<th>0a</th>
|
||||||
|
<th>0b</th>
|
||||||
|
<th>0c</th>
|
||||||
|
<th>0d</th>
|
||||||
|
<th>0e</th>
|
||||||
|
<th>0f</th>
|
||||||
|
</tr>
|
||||||
|
<tr>
|
||||||
|
<th>00</th>
|
||||||
|
<td colspan="4">magic</td>
|
||||||
|
<td colspan="4">strand number</td>
|
||||||
|
<td colspan="4">frame number</td>
|
||||||
|
<td colspan="4">pixel 1</td>
|
||||||
|
</tr>
|
||||||
|
<tr>
|
||||||
|
<th>10</th>
|
||||||
|
<td colspan="4">pixel 2</td>
|
||||||
|
<td colspan="4">pixel 3</td>
|
||||||
|
<td colspan="4">pixel 4</td>
|
||||||
|
<td colspan="4">pixel 5</td>
|
||||||
|
</tr>
|
||||||
|
</table>
|
||||||
|
|
Loading…
Reference in a new issue