-
Notifications
You must be signed in to change notification settings - Fork 376
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
SQL #11
Comments
Sensitiviti seems ok for me, local 2M repeater in fact is constantly opening on SQL 1 had to switch to 2. |
The sensitivity is okay, but the response threshold is 12dB different from the stock one, and when working in the direct channel or when moving, this is not comfortable. What is still well understood by ear is cut off by a noise suppressor. |
This is not just my opinion. |
People do different things, some FWs do it in code. I think the correct way is adjusting eeprom calibration entries. There is a python tool for that. and a good manual (google translate is your friend): |
The squelch table that Matoz spm81 uses improved one where SATCOM and weaker airband opens normally. And SQL has 9 steps, no point of using it on 1. Could be even higher for low noise areas? |
I have some problems to translate "Fine del pippone" ... :-D |
Me too :)
Good job sir :) By the way, the firmware now includes 1o11's enhencements in SQL sensitivity in the code. I switched to sql 4 and it is still more sensitive than old 1. |
Yes, I noticed that: with this new firmwares there is no need to adjust eprom entries. |
I read that he had some oopsy with his recent updates, he pushed some code that erases calibration data from radio. Should be back soon. |
main to dev
The SQL threshold is too high even by 1.
The text was updated successfully, but these errors were encountered: