Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scanning ends up in monitoring more than one cell #15

Open
sv1 opened this issue Feb 4, 2017 · 2 comments
Open

Scanning ends up in monitoring more than one cell #15

sv1 opened this issue Feb 4, 2017 · 2 comments

Comments

@sv1
Copy link

sv1 commented Feb 4, 2017

I am using the 6-channel configuration, to monitor a cell with 1 control channel and 4 traffic channels.

If I start "scanning until first network is found", telive is muting receivers 2-6 until next channel is found.

And then immediately un-mutes all receivers.

If the next channel found is assigned in another cell you end up in "too many changes...... etc"

I think that either all receivers should be tuned to the newly found channel, or unmuted only after new channels of the new cell are discovered.

thanks

@sq5bpf
Copy link
Owner

sq5bpf commented Feb 22, 2017

it should scan with receiver 1, and when it finds this network it should tune receivers 2-6 from the frequency data in the traffic. maybe there is a problem with this frequency data, or maybe there is another transmitter which uses the same frequency. please verify this from the messages (increasing verbosity will get you more data).

as a workaround disable the automatic tuning. tune the first receiver (either via scanning or just input the frequency manually), and look at the frequency data. using this tune channels 2-6. you will probably find that one of the frequencies sends bad data, so just don't use it.

please report what you've found

@sv1
Copy link
Author

sv1 commented Feb 24, 2017 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants