Limits Table (Bluetooth)

The Limits Table trace shows, for each result in the Results Table, the limit that applies and the resulting pass/fail status. The results run down the rows — the same results in the same order as the Results Table — and the Limit and Status columns run across.

The limits are resolved automatically from the Bluetooth Core Specification for the active PHY Physical Layer rate and packet type — there is no user limit editor.

Limit Column

The limit is shown in whichever form the specification defines for that result:

A range, when the result is bounded on both sides — for example 225.0k to 275.0k for Δf1avg on the LE 1M PHY.
>= followed by a value, when only a lower bound applies.
<= followed by a value, when only an upper bound applies — for example <= 20.00 for the mean output power of an LE packet.
Blank, when no limit applies to that result in the current configuration.

The Df2 Rate limit carries additional context, because its bound is a percentage while the deviation floor those percentages are measured against depends on the PHY. It reads >= 99.90 % @ 185.0k on LE 1M and >= 99.90 % @ 370.0k on LE 2M, so the criterion that actually moved with the PHY stays visible.

Status Column

PASS — the result was measured and meets its limit.
FAIL — the result was measured and does not meet its limit.
*** — no verdict, because a verdict requires both a measured value and a limit to compare it against.

Two different situations produce ***, and the Results Table distinguishes them. Read across to that result's Value cell:

If the Value cell also shows ***, the result was not measured on this acquisition — there is nothing to judge.
If the Value cell shows a number, the result was measured but is not constrained — the specification defines no limit for it in the current configuration. The Limit cell beside it is blank.

A result that has no limit is never reported as PASS; it reads *** instead.

Results With No Limit

Which results show a blank Limit cell depends on the active PHY rate and packet type; it is not a fixed list. For example:

Df1 Max is unbounded on LE 1M and LE 2M — the specification bounds the Δf1 family through Δf1avg — but carries a lower bound on LE Coded S=8.
Df2 Avg has no limit of its own on any rate; the Δf2 family is constrained through Df2 Rate and the Df2/Df1 Ratio.
Df2/Df1 Ratio carries a lower bound of 0.8 on the uncoded rates and none on LE Coded. Because Δf1avg and Δf2avg are measured with different test payloads, its cells also stay blank until both Δf families have been measured.
Min Df1 Max and Min Df2 Max are unbounded on every rate — the specification defines no limit for them.