plans(optical): the PON budget is called whole-path and prices one cable #2442
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge!2442
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "plan/1121-1537"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Plans only. One page,
docs/plans/pon-path-budget.md.The engine's
ponBudget()is designed for a path (lengthM+splitters[]) and is called once per cable fromvalidateLink(), whilevalidation.js:139calls the result "a whole-path verdict". Measured today: two 24 km legs of one PON through a 1:8 splitter each validate clean at 8.2 dB spare; the 48 km path is 28.2 dB against a 28 dB B+ budget and nothing says so.Also found: 6 of 21
category: splitterspecs carry nosplitRatio, so they are priced at 0 dB (FBT 1x2 at 66 km: validates at 23.7 dB / 4.3 dB spare; with the part's real 4.1 dB it is 27.8 dB / 0.2 dB, and the <3 dB warning never fires); 0 of 2,352 specs declareponClass, so every PON is priced as GPON B+; the spare is computed and thrown away; andshow interfaces <port>prints no cage or media even thoughcli.js:803says it does.Steps: (1) price the path, reusing
E_OPTICAL_BUDGET; (2) refuse a splitter whose ratio cannot be resolved instead of charging 0 dB; (3)ponClasson 5 sourced OLT specs + schema + audit; (4) store the verdict on the link; (5) print the media inshow interfaces <port>; (6) optionalshow pon— needs Jay's approval.Closes no open issue: the queue holds only #130.