task:beamloss_tool
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| task:beamloss_tool [2024/10/02 03:55] – added note about re-established thresholds. powersa | task:beamloss_tool [2025/08/21 12:34] (current) – ryans | ||
|---|---|---|---|
| Line 4: | Line 4: | ||
| == Tanner' | == Tanner' | ||
| - | The tool configures BCM D5789 instead of D5521. Unfortunately, | + | The tool configures BCM D5789 instead of D5521. Unfortunately, |
| The tool automatically sets BCM thresholds. The calculation need the information on AP config tab to be accurate. The MEBT threshold sets it to a value that includes some noise overhead, so instead of 25 W exactly is corresponds with ~32 W for example. | The tool automatically sets BCM thresholds. The calculation need the information on AP config tab to be accurate. The MEBT threshold sets it to a value that includes some noise overhead, so instead of 25 W exactly is corresponds with ~32 W for example. | ||
| Line 11: | Line 11: | ||
| - | It seems that any time a TCT Parameter is changed (see ‘TCT Recent Parameter Changes’ box) threshold selections are re-established. This can be an issue if you manually stop watching a dBCM while running a lower powered beam. | + | It seems that any time a TCT Parameter is changed (see ‘TCT Recent Parameter Changes’ box) threshold selections are re-established. This can be an issue if you manually stop watching a dBCM while running a lower powered beam. -ALP |
| + | ====Shane note==== | ||
| + | * Good info but not noob friendly | ||
| ===== Links ===== | ===== Links ===== | ||
| - | /* add links to any documents we get here */ | + | |
task/beamloss_tool.1727855727.txt.gz · Last modified: 2024/10/02 03:55 by powersa
