Bug #4495

Force scan not working

Added by Nicolas C about 1 year ago.

Status:NewStart date:2017-07-22
Priority:NormalDue date:
Assignee:-% Done:


Target version:-
Found in version:4.3-295~ga9dffb7 Affected Versions:


I've a rotor configured with 3 orbital positions.
The workflow is as follows:
- I've added a new network
- I've added an extra orbital position
- Went back to the Network and clicked on Force Scan

The intended result is that the rotor would go to that orbital position and start scanning. The actual result is that nothing happens.

The network is configured correctly and the tuner is IDLE when performing the steps.

Also available in: Atom PDF