TRENDnet TPE-TG PoE+: five unmanaged PoE+ switches (31/246/440/380/70 W) #1647
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!1647
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1116-1025"
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?
TRENDnet carried two switches and a powerline adapter before this; the vendor's unmanaged PoE+ range - the one people actually cable IP cameras and APs to - was absent. This adds five members, one per distinct port/PoE shape, all from the vendor's own product pages.
What was added
All five are unmanaged:
l2-forwardpluspoe-pse, nocli, nohttp-server. The802.3af/802.3attokens are kept as declared and reported by the importer as hardware facts with no engine behaviour, exactly as docs/DEVICE_SCHEMA.md describes.Evidence
Per-device sources are recorded in each spec's
sourceUrland inpoe.sourceUrl:Fabric figures are self-consistent with the port counts in every spec (18 physical positions x 2 Gbps = the stated 36 Gbps on the combo box, 26 x 2 = 52 Gbps, 7 total Gbps-equivalents = 20 Gbps on the multi-gig box), which is the cross-check that caught nothing this time but is the reason the numbers were trusted.
Discrepancies and the one modelled choice
poe.notesays how many devices of each class actually fit, because "16 PoE+ ports" reads as 480 W and is not.-sfpsiblings; the assumption is stated in the spec'snotesso the next pass can correct it from a photo rather than guess again.Gates
node scripts/syntax-check.js- 348 files, all OKnode scripts/audit-port-types.js- 2201 models, 24835 ports, 0 offending devices, 0 offending ports (no trendnet findings)catalogue-hygiene,capability-vocabulary,combo,poe,poe-agreement,import-devices-capabilities,doc-catalog-counts,faceplate-catalogue,link-parts,duplicate-models- all passcheck-control-bytes,check-canonical-urls- cleanE_COMBO_OCCUPIEDnaming the occupied sibling, while port17-sfp to a TPE-TG262 SFP slot validatesdocs/DEVICE_REGISTRY.mdregenerated (2,196 -> 2,201 models, switch 370 -> 375), not hand-editedmain is red from this merge —
test/property-validator.test.js, deterministicorigin/main@677cfb0e(this PR) and @1efbafd5:Test (Node 18/20/22)all fail in run 3637. Reproduced locally on a clean checkout of both commits:30049dc6(the commit before this one) is green, 19/19. So the red starts here — not because this PR changed behaviour, but because five new specs change the fixture the fixed seed draws from:specs[Math.floor(rand() * specs.length)]now lands on an SFP56 port, and connecting it with aconsole-rs232media override returnsE_BIDI_MISMATCHfromengine/optical.js:225/engine/media.js:1339.The assertion at
test/property-validator.test.js:125is:RULE_CODESisvalidation.RULES— 24 entries — but the engine declares 75 distinctcode: 'E_…'values. 59 of them are outside the rules table, includingE_BIDI_MISMATCH,E_BAUD_MISMATCH,E_OPTICAL_BUDGET,E_LINK_*. Any draw that reaches one of those codes fails identically; seed 65 just stopped avoiding them first.Deleting any one of the five new specs makes the suite pass again (verified for all five) — that is the fixture draw moving, not a fix.
Needs a decision, not a guess — two candidates, both outside catalogue work:
test/: check the code against the union of every code the engine declares, not justvalidation.RULES(thenE_PORT_IN_USEspecial-casing goes away too).engine/validation.js: publish the media/optical/link code family intoRULES.I have not touched either —
engine/andtest/are not mine to edit. Until it is fixed every merge to main inherits a red tip and each new device spec re-rolls the draw.