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

SQL #11

Closed
Electronicpilot opened this issue Oct 5, 2023 · 9 comments
Closed

SQL #11

Electronicpilot opened this issue Oct 5, 2023 · 9 comments

Comments

@Electronicpilot
Copy link

The SQL threshold is too high even by 1.

@subsubl
Copy link

subsubl commented Oct 5, 2023

Sensitiviti seems ok for me, local 2M repeater in fact is constantly opening on SQL 1 had to switch to 2.

@Electronicpilot
Copy link
Author

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.

@Electronicpilot
Copy link
Author

This is not just my opinion.

@egzumer
Copy link
Owner

egzumer commented Oct 5, 2023

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.
https://github.com/amnemonic/Quansheng_UV-K5_Firmware/tree/main/python-utils
squelch_table_read.py
squelch_table_write.py

and a good manual (google translate is your friend):
Guida Firmware Squelch V_batt.pdf

@egzumer egzumer mentioned this issue Oct 5, 2023
@subsubl
Copy link

subsubl commented Oct 5, 2023

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?

@ik5wwp
Copy link

ik5wwp commented Oct 10, 2023

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. https://github.com/amnemonic/Quansheng_UV-K5_Firmware/tree/main/python-utils squelch_table_read.py squelch_table_write.py

and a good manual (google translate is your friend): Guida Firmware Squelch V_batt.pdf

I have some problems to translate "Fine del pippone" ... :-D
I'm the autor of the manual! :-D :-D

@egzumer
Copy link
Owner

egzumer commented Oct 10, 2023

I have some problems to translate "Fine del pippone" ... :-D

Me too :)

I'm the autor of the manual! :-D :-D

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.

@ik5wwp
Copy link

ik5wwp commented Oct 10, 2023

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.
By the way, whats happened to 1of11 repository?

@egzumer
Copy link
Owner

egzumer commented Oct 10, 2023

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.

@egzumer egzumer closed this as completed Oct 11, 2023
Prz3ma55 pushed a commit to Prz3ma55/uv-k5-firmware-custom that referenced this issue Mar 11, 2024
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

4 participants