# Wi-Fi Devboard lab record

Use training aliases. Keep actual captures and configuration backups private.

## Inventory

- Date and operator:
- Board model, chip and revision:
- Flipper firmware project / version / API:
- Companion app version / source:
- Board firmware version / target / release URL:
- Download checksum and published comparison, if available:
- Backup location and intended recovery image:

## Scope and setup

- Authorized AP / client aliases and participants:
- Lab purpose and allowed actions:
- Band, channel, radio conditions checked and source/date:
- AP security mode / PMF setting:
- WAN disconnected? Radio environment and boundary:
- Scan method: active, passive or not yet verified:

## Prediction and observations

- Prediction:
- Variable changed:
- Factors held fixed:

| Trial | Position / orientation | AP alias | Channel | RSSI (dBm) | Observation |
| --- | --- | --- | --- | --- | --- |
| 1 | A | | | | |
| 2 | A | | | | |
| 3 | A | | | | |
| 4 | B | | | | |
| 5 | B | | | | |
| 6 | B | | | | |
| Control | AP off, fresh scan | | | | |

## Recovery and explanation

- Flash result and board version after reset:
- Known log event or version response after recovery:
- What the result establishes:
- Alternative explanation / uncertainty:
- Mechanism and corresponding defense:
- Practical steps not tested:
- Next review date: