The uTracer11-GUI has not only access to the PDP-11 CPU, but also total UNIBUS-Signals.
M93X2-probe reads all 56 signals, and can write also a sub set of signals to perform PoweOn-Reset, DATI and DATO cycles as well as block the CPU from UNIBUS access.
(So simulators must implement an UNIBUS simulation too ... the bar is set high).
All panels here are only active when the CPU is micro-single-stepped.
Raw UNIBUS signals
All 56 UNIBUS signals are show in this panel:
This panel show the same information as UniProbe,, but not in real time and without "Blinkenlight-sex appeal"
If the M93X2 probe plus into a MUD slot, the Interrupt BG* and DMA Grant NPG signals are invalid.
Active Memory access
Another panel shows the latest memory and I/O page accesses via DATI/DATO cycles.
This is in fact a tabular display of the 256k address range, but reduced to addresses actually accessed by the CPU.
So you see only the "hot" part of memory and devices in use, while single stepping the CPU-under-test.
The most recent address is marked in "red".
UNIBUS activity is also seen in the CPU Trace panel.
EXAM, DEPOSIT, upload, download
As the M93X2 probe can also execute active DATI and DATO cycles, we have a tool to change and inspect memory (and devices registers).
These functions are found on all PDP-11 console monitors, be them "Blinkenlights", 11/34 style "programmer consoles", or 11/44-like front end processors.
There are a few controls to execute single DATI (read=EXAM) and DATO (write=DEPOSIT) cycles.
Also upload and downloaf of whole code blocks are possible.