-
Notifications
You must be signed in to change notification settings - Fork 69
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
MaxAFCStep may be used uninitialised #56
Comments
If you don't set a value, it will be zero, which disables its action. So AFC works but isn't bounded. |
Thanks, I should have been paying more attention to the code. You could set a sensible default value, but it is not a problem. |
Yeah, that's reasonable. I'll add to the list.
Dave
…On 10 July 2018 at 22:24, ED6E0F17 ***@***.***> wrote:
Thanks, I should have been paying more attention to the code. You could
set a sensible default value, but it is not a problem.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#56 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABBodJGmznnDvKvXNcvYuKmvdAXVDIZ8ks5uFRuLgaJpZM4VJpHp>
.
|
My actual problem was a typo in gateway.txt: "AFC0=Y", so if you could make AFC default to on, that would be good too....... |
AFC is only needed at the narrower bandwidth settings so it doesn't necessarily make sense to default to on. Also you can easily toggle the setting using the f or F key. |
I may be missing something, but If I don`t set MaxAFCstep in config, I am not going to be able to use calling mode to correct drifty payloads.
The text was updated successfully, but these errors were encountered: