Components + Guidesesc
Visualization

Pixel Screen (16x16)

Use the pinless 16×16 monochrome Pixel Screen to visualize a 32-byte framebuffer in workspace RAM. It is a memory-polling display model, not an electrically wired LED matrix.

Overview

The 16 × 16 Pixel Screen is a pinless monochrome framebuffer display backed directly by workspace RAM.

Exact DigiSim.io Implementation

  • The component has 0 inputs and 0 outputs; no wire connection is used.
  • It scans RAM components in the workspace and polls 32 bytes every 100 ms. With multiple RAMs there is no target selector, so use one RAM for deterministic display data.
  • Within each byte, bit 0 is the leftmost pixel and bit 7 is the rightmost pixel (LSB-first). A 1 lights the pixel.
  • Default start address is 0xE0, so the full default framebuffer is 0xE0–0xFF.
  • The address dialog accepts 0x00–0xF0. For a complete 32-byte frame the start must be 0xE0 or lower; bytes beyond 0xFF are skipped.

Inspector Window

  • The window shows the 16 × 16 square grid, framebuffer address range, lit-pixel count, RAM-reading status, and a Clear button.
  • The context menu changes the start address, foreground/background colors, or clears the mapped bytes in RAM.
  • Pixel scale is an internal layout value, not a user-facing setting.

Learning Path

Prerequisites

Next Steps

Frequently Asked Questions

How does the pixel screen work?

The screen has no input or output pins and does not connect to circuit wires. Every 100 ms, it polls 32 bytes from workspace RAM; a 1 bit lights the corresponding pixel. If the workspace contains multiple RAM components, the screen cannot select among them, so use one RAM for deterministic output.

How is pixel data organized?

Each row occupies two consecutive bytes; bit 0 maps to the leftmost pixel within each byte and bit 7 to the rightmost. The default framebuffer is 0xE0–0xFF, and a complete 32-byte frame must start at or below 0xE0.