Skip to the content
2 layers30 × 21 mmObservation reva, the printed circuit board in 3D

REST API and local touch UI for invasive control of Samsung CJ791 monitors by electrically emulating the front-panel JOG button. Uses an inline hardware mod on the JOG harness and DDC/CI for feedback, status, and supported monitor functions like input detection and power control.

Size
30 × 21 mm
Copper layers
2
Thickness
1.6 mm
Parts
24
Nets
23
Pads
79
Tracks, vias
122, 0
Pours
1
Routed
Yes
KiCad
KiCad 10.0 (file 20260206)
Created
21 Mar 2026
Updated
7 Nov 2026

Overview

Observation reva is an open-source printed circuit board by raffcorreia, from the raffcorreia/samsung-jog-api repository on GitHub, published under the MIT licence. It is a 2-layer board of 30 × 21 mm with 24 parts on 23 nets, routed with 122 tracks and 0 vias.

It is built around the 74LVC1G17GW, ADS1115IDGSR and TLV9064IDR-MS. Its parts include 8 capacitors, 7 resistors, 4 ICs and 3 connectors.

Main components

3

README

README.md

samsung-jog-api

samsung-jog-api is a hardware-and-software project to make a Samsung CJ791 monitor locally programmable by electrically emulating its front-panel JOG control, exposing that behavior through a local REST API, and hosting a touch-first local control interface on a Raspberry Pi-based control deck.

This repository is organized around the Samsung LC34J791WTNXZA / CJ791 hardware in my setup. Related Samsung monitors with a similar multi-jog front-panel board may be adaptable, but the measurements and assumptions here are specific to this unit unless noted otherwise.

Monitor photo

Samsung CJ791 front view Samsung CJ791 rear view

Status

Current state of the repository:

  • completed: Phase 0: Documentation and Evidence Capture
  • completed: Phase 1: Host Preparation and Conservative OS Cleanup
  • completed: Phase 2: Hardware Validation
  • completed: Phase 3: Bus Observation Circuit Design
  • completed: Phase 4: Analog Drive Circuit Design (design docs, KiCad schematic/PCB, BOM, and concept schematic)
  • completed: Phase 5: HDMI and DDC Communication Design
  • completed: Phase 6: Discrete-Component Protoboard Validation
  • completed: Phase 8: GPIO Assignment and Low-Level Control Prototype — execution record
  • completed: Phase 9: Local Platform Bring-Up — execution record, runbook (systemd unit config/systemd/pi-deck.service, kiosk scripts under scripts/kiosk/)
  • completed: Phase 10: Local API — execution record (REST /api/v1, WebSocket /ws/events)
  • completed: Phase 11: Low-Level JOG Console UI — execution record (React JOG console in frontend/; live GPIO on the deck host verified — UI drives real JOG on the appliance)
  • completed: Phase 12: Deployment and Version Tracking — execution record (scripts/deploy.sh, deploy counter/version badge, kiosk reload workflow)
  • completed: Phase 13: Full-Screen UI Layout with Placeholders — execution record (1280×800 deck shell, real JOG/log, calendar and notes placeholders, settings route, popup template, seven-segment clock, LED/record stubs)
  • completed: Phase 14: Log Architecture Refactor — execution record (backend-owned live log buffer, WebSocket replay on connect, synced multi-client log stream)
  • completed: Phase 15: Observation Bus and Hardware Interface — execution record (interrupt-driven ADS1115 + GPIO observation bus, single websocket authority for holds/releases/LED)
  • parked, hardware access pending: Phase 16: Recording and Replay Subsystem — recording workspace, sequence runner, upload/download/edit/replay UI complete; on-device validation is blocked until hardware access is available
  • completed: Phase 17: Development Fixture — execution record (crude open support to hold monitor/control-deck hardware together for development)
  • completed: Phase 18: Display and Touch Validation — execution record (Waveshare DSI display/touch working; HDMI disabled as a display and retained for DDC/CI only; safe brightness ceiling 170/255)
  • completed: Phase 19: Display Usability and Power Hardening — execution record (display/Pi power menu, brightness API/UI cap, color/edge validation page, Xwayland/font readability pass, power measurements)
  • completed: Phase 20: Raspberry Pi 5 Rebuild and Display Performance Validation — execution record, GPIO schema (Pi 5 performance accepted; healthy-panel validation continues in Phase 26)
  • completed: Phase 21: Display Power Control Circuit — execution record (high-side 5V switch + RC soft-start to prevent Pi 5 shutdown on display reconnect; hardware design complete)
  • completed: Phase 22: Physical Display and Pi Power Button — execution record (physical display/Pi power button behavior, PowerMenu updates, and status LED path)
  • completed: Phase 23: Documentation Reorganization, Versioning, and Deploy Harness — execution record (artifact-based naming for all docs and KiCad projects, git-tag versioning, auto-tag on deploy, version panel in settings UI, deploy runbook)
  • completed: Phase 24: DDC Capability Investigation — execution record (validated usable DDC reads, documented unsupported state inference, and established the HDMI-disabled/DDC-active operating model; production write support remains deferred)
  • completed: Phase 25: Bidirectional Custom Monitor Communication and Control UI — execution record (hardware-confirmed KEY_LED receive and KEY_ADC1 command paths, typed responses and unsolicited messages, capture/replay/session tooling, state-aware deck controls, event-driven status recovery, and the large communication monitor)
  • blocked: Phase 26: Replacement Display and Final Pi 5 Host Cutover — execution record (work has started; replacement panel image works, but its touch cable is physically damaged, so touch validation awaits repair or replacement)
  • deferred: Phase 27: Monitor Power-State Characterization (the custom communication STATE model supersedes the planned LED-feedback characterization; remaining ON/IDLE/OFF/POWERED-OFF work is intentionally deferred)
  • deferred: Phases 28–31 retain sequence cleanup, recording settings/editor, advanced productized features, and dashboard data-source planning for future reconsideration
  • planned: Phase 50: Security, Authentication, and Presence-Aware Locking covers login/lock flows, authorization for sensitive capabilities, fingerprint-scanner preparation, and Shortwave/short-range presence-triggered locking
  • deferred: Phase 60: OSD Navigation Model and Monitor-Control Emulator is retained for future reconsideration, but accurate focus tracking requires a new firmware protocol response/pushed message and another firmware validation cycle because Menu reopens at its remembered last selection
  • in parallel: Phase 7: Integrated Controller Board Design (KiCad / layout in progress)
  • repository now includes Phase 1 runbooks and host-preparation scripts
  • repository now includes a Phase 2 execution record for hardware validation
  • repository now includes a Phase 3 execution record for bus-observation hardware design
  • repository now includes a Phase 4 execution record, KiCad design files, and analog-drive BOM artifacts
  • repository now includes completed Phase 5 transport design documentation and execution record
  • repository now includes completed Phase 6 protoboard validation documentation, schematic, BOM, and execution record
  • hardware findings for the JOG board and DDC behavior
  • requirements, design, test strategy, and implementation planning for a Raspberry Pi kiosk-style control deck
  • Application code layout: backend/ (Python package pi_deck: api, services, hardware, … per Architecture), frontend/ (React/TypeScript UI; npm run build copies assets into backend/src/pi_deck/static/; npm run test:e2e in frontend/ builds the UI, runs Playwright against mock pi-deck on 8756, or set E2E_BASE_URL for a live Pi); protoboard GPIO helpers live under backend/src/pi_deck/hardware/. Bring-up script: scripts/pi-deck-gpio-probe (see runbook) — see Phase 8 Execution Record. Host metrics / Pi baseline: scripts/pi-deck-host-health.py (see Phase 9 execution and Host health gate).

Why this project exists

The CJ791 is a capable monitor, but it is frustrating to automate cleanly.

  • It has multiple useful inputs: HDMI, DisplayPort, and Thunderbolt / USB-C
  • It has a rear-mounted JOG control that can navigate the on-screen display and trigger functions the normal software control path cannot, but it is inconvenient to use repeatedly
  • It exposes DDC/CI, which is enough to read some state and control some functions
  • It does not reliably expose the full monitor control surface over DDC alone on this unit

In practice, this project uses a hybrid model:

  • JOG emulation for actions that need true front-panel behavior
  • DDC/CI for machine-readable feedback and the functions that already work reliably
  • front-panel LED observation for local feedback cues such as input-change blink patterns, idle state, and possible OSD boundary signals
  • a local Raspberry Pi touch device as the always-on operator-facing control surface

This matters especially for input switching. On this monitor, source selection is effectively a cycle through available inputs rather than a reliable direct jump to a named source, so current-state feedback is what tells the controller when to stop cycling.

System overview

High-level system shape:

  • custom inline controller sits between the original JOG board and the monitor main board
  • controller reproduces the same resistance-to-ground states the monitor expects on KEY_ADC1 and KEY_ADC2
  • controller observes the front-panel LED state as an additional feedback signal
  • local backend software exposes high-level actions through a REST API
  • a local touch UI runs in kiosk mode on a Raspberry Pi and calls the same API
  • DDC/CI provides state readback and supported direct controls such as brightness and power

The system is expected to support three operating modes:

  • JOG mode for raw low-level control, investigation, and recovery
  • DDC mode, where the controller can read the current input and stop source-cycling or PIP navigation at the correct state
  • Blind mode, where the UI asks the user for current and desired input so the controller can perform blind source cycling from a known starting point

Documentation index

Use these section indexes to navigate the repository documentation:

  • Hardware Reference — GPIO wiring, Raspberry Pi pinout, monitor connections, schematics, and bills of materials
  • Implementation Plan — planned phases and links to phase execution records
  • Investigation Data — register captures, I2C/DDC scans, and hardware-analysis notes
  • Runbooks — Raspberry Pi preparation, deployment, and hardware bring-up procedures

Core project documents:

Hardware and reverse-engineering entry points:

Operational docs:

Start here

Recommended reading order:

  1. README.md
  2. Requirements
  3. Solution Overview
  4. Hardware Reference
  5. CJ791 JOG Board Notes
  6. CJ791 DDC and VCP Behavior
  7. Implementation Plan

Safety and scope

This project intentionally modifies monitor hardware and is not warranty-safe.

  • opening the monitor can damage clips, cables, or boards
  • cutting or extending the JOG harness can permanently alter the monitor
  • mistakes on the key lines can damage the monitor input circuitry
  • nothing here should be treated as stock-safe or supportable by the manufacturer

The goal is not to preserve stock condition. The goal is to create a practical, local, programmable control interface for a monitor whose original user interface is difficult to automate cleanly.

Parts

24
QtyValueFootprintReferences
4100nCapacitor_SMD:C_0402_1005MetricC1, C2, C3, C4
310k 1%Resistor_SMD:R_0402_1005MetricR1, R2, R3
31nCapacitor_SMD:C_0402_1005MetricC6, C7, C8
20Resistor_SMD:R_0402_1005MetricR6, R7
24.7k 1%Resistor_SMD:R_0402_1005MetricR4, R5
274LVC1G17GWPackage_TO_SOT_SMD:SOT-353_SC-70-5U3, U4
11uCapacitor_SMD:C_0402_1005MetricC5
1ADS1115IDGSRPackage_SO:MSOP-10_3x3mm_P0.5mmU2
1HOST_IFConnector_PinHeader_2.54mm:PinHeader_1x07_P2.54mm_VerticalJ2
1MONITOR_INPUTConnector_PinHeader_2.54mm:PinHeader_1x04_P2.54mm_VerticalJ1
1SPARE_IFConnector_PinHeader_2.54mm:PinHeader_1x02_P2.54mm_VerticalJ3
1TLV9064IDRPackage_SO:SOIC-14_3.9x8.7mm_P1.27mmU1
1U1D_INTestPoint:TestPoint_Pad_D1.0mmTP8
1U1D_OUTTestPoint:TestPoint_Pad_D1.0mmTP9

More from raffcorreia/samsung-jog-api

2
  • 4 layers110 × 65 mmHdmi ddc intermediary, the printed circuit board in 3D

    Hdmi ddc intermediary

    raffcorreia/samsung-jog-api

    REST API and local touch UI for invasive control of Samsung CJ791 monitors by electrically emulating the front-panel JOG button.

    23 partsMIT
  • 2 layers85 × 45 mmAnalog drive, the printed circuit board in 3D

    Analog drive

    raffcorreia/samsung-jog-api

    REST API and local touch UI for invasive control of Samsung CJ791 monitors by electrically emulating the front-panel JOG button.

    17 partsMIT

Similar boards

  • 2 layers235 × 68 mmN2-etoile-0v, the printed circuit board in 3D

    N2-etoile-0v

    essensys-hub/essensys-i2c-etoile-0v

    Carte qui relie le boîtier principal (BP, carte SC944D) aux boîtiers auxiliaires (BA1 SC940D, BA2 SC941C, BA3 SC942C) d'une installation Essensys en étoile autour d'un plan 0 V commun, à la place du chaînage d'origine.

    181 partsMIT
  • 4 layers120 × 100 mmSkywave sdr, the printed circuit board in 3D

    Skywave sdr

    olegantonov/skywave-sdr

    Rádio portátil modular de baixo custo: ESP32-S3, OLED, PTT, HF SDR e expansão VHF/UHF. Em desenvolvimento.

    87 partsMIT
  • 4 layers100 × 100 mmCarrier, the printed circuit board in 3D

    Carrier

    AxelMcKenna/AFX-1000

    RMX-1000-inspired effects processor for macOS, AU and VST3, built on a shared C++20 engine. Standalone Daisy Seed 3 hardware with two main PCBs and a custom housing is in development.

    110 parts1
  • 4 layers62.3 × 188.5 mmOpt 14, the printed circuit board in 3D

    Opt 14

    gustebeast/public-steel-guitar

    A pedal steel guitar you can build yourself, from parts anyone can buy.

    233 partsCERN-OHL-S-2.0
  • 4 layers170 × 100 mmLeviathan V1.3, the printed circuit board in 3D

    Leviathan V1.3

    MotorDynamicsLab/Leviathan

    Leviathan Main Controller for Voron 2 / Trident 3D Printers

    420 parts124GPL-3.0
  • 4 layers57.9 × 59.4 mmGW4302, the printed circuit board in 3D

    GW4302

    garrettsworkshop/GW4302

    Prototype RAM cartridge compatible with Commodore 1700/1750/1764 RAM Expansion Unit (REU)

    100 parts11
  • 2 layers24 × 18 mmUsb2serial autovtg, the printed circuit board in 3D

    Usb2serial autovtg

    znuh/usb2serial-autovtg

    USB to serial converter with automatic target voltage detection, buffered IOs, 1.8V to 5V support and backflow current protection

    38 parts9CC-BY-SA-4.0

Questions

How big is the Observation reva PCB?

It measures 30 × 21 mm and has 2 copper layers, 1.6 mm thick.

What parts does the Observation reva use?

24 parts, built around the 74LVC1G17GW, ADS1115IDGSR and TLV9064IDR-MS. The full list of its parts is on this page, with links to each part's symbol and footprint where PCBKit's library has them.

Where can I download the Observation reva KiCad files?

From the raffcorreia/samsung-jog-api repository on GitHub, at the commit this page was made from: the board is hardware/kicad/observation-reva/observation-reva.kicad_pcb and its schematic hardware/kicad/analog-drive/analog-drive.kicad_sch. PCBKit opens the board in the browser, with nothing to install.

Can I use the Observation reva design in my own project?

Its repository publishes it under the MIT licence: you may reuse it on that licence's terms (keep the author's notice, and for a copyleft licence share your changes alike).