Skip to content

Real-Time Device Readout Panel #381

Open

Description

@Relm-Arrowny

Part of #373 Device Readouts:

Build a dedicated telemetry UI component displaying motor positions, setpoints, and live traces. This resolves the current limitation where users have to use external EPICS screens to track positions

Goals

Acceptance criteria : What journeys should the user be able to complete to consider your feature done
Be as specific as you can, check them off once they work. Add more if you find more requirements during development. Issue should only be considered done after all of them are checked

  • [ ]. Device readout could go through csweblib for
    PV access (unknown); VISR uses PVWS for its UI.
  • Continuous Telemetry during Scans: Telemetry coordinates and readbacks must update continuously even during active scan plans when BlueSky is busy.

Tasks

base on the goals, deduce the tasks required. check them off once they're done

  • PV Polling/Subscription: Set up subscription streams to listen to PVs independent of the BlueSky control loop using pvws.
  • UI Readout Panel: Design and layout a telemetry widget for selected devices based on Neeli's proposed design refinements.
  • Traces & Limits Display: Render live positional traces and soft/hard limits for active devices.

Screen Shoot

Image

Activity

  1. changed the title [-]Real-Time Device Readout Pane[/-] [+]Real-Time Device Readout Panel[/+] on Sep 9, 2026
  2. DanPorter commented on Sep 16, 2026

    @DanPorter
    Collaborator

    example screenshot looks great!
    In the last data flow diagram I saw at the TDSG in August, it said this data would be acquired directly from EPICs via websockets over PVWs.

  3. NKatti2011 commented on Sep 16, 2026

    @NKatti2011
    Collaborator

    Include notes from @EmsArnold

    Correction

    There is no EPICS API. The acceptance criterion in #373 that refers to reading device
    positions "via EPICS API" should be reworded.

    What to use instead

    • csweblib can be used to get information from PVs (perhaps?).
    • VISR uses PVWS for its UI readbacks and is recommended

    Why not read back through Bluesky

    1. There is a single RunEngine, so simultaneous/parallel calls are not possible at present.
    2. A PV read would have to be expressed as a plan, and we would need to run that readback
      plan continuously through the websocket.
  4. added and removed
    core dependencyMore needed to know before we can fully scope this work.
    on Sep 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions