This guide walks through reading the auto-generated diagram, watching live data flow, and drilling into a specific stream.
1. Connect to a CoreEngine
Launch System Layout and pick the target CoreEngine instance from the SimEng picker — local or reflected, it works the same either way. System Layout reads that project's streams.json and builds the diagram automatically.
2. Read the Diagram
- CoreEngine sits at the center.
- Each Device box is one physical target — streams sharing the same driver and IP address are grouped together automatically.
- Streams with no IP (local/file/serial) each get their own Device box.
- Right-click a Device box for its context menu: Delete removes it, and Move lets you drag its interfaces onto another Device box — use this to merge several interfaces into a single device when you want a different grouping than the automatic one.
3. Watch Data Flow Live
Lines connect CoreEngine to each stream, animating with live traffic:
- Green and moving — data flowing normally, speed reflects the actual message rate.
- Red — that block's error counter just incremented.
- Direction follows the stream's declared block direction:
outflows CoreEngine → device,inflows device → CoreEngine.
4. Drill Into a Stream
Right-click any stream node and choose Show Properties to open its Stream Monitor window:
- Full driver configuration, flattened field by field.
- Every block with live message count and error count — errors highlighted in red.
- A live rate readout (e.g. "50 Hz · 20 ms") in the window title.
5. Check Overall Health
Use the toolbar's Status, Profiler, and State report buttons for the same Core States, Profiler, and States Status views available in DIPanel.
If a device looks idle or shows red arrows, open its Stream Monitor first — the per-block error count and rate readout is usually the fastest way to confirm whether it's a real connectivity problem.