-
Notifications
You must be signed in to change notification settings - Fork 45
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
D878UV: Rx Tone not supported #111
Comments
I cannot reproduce it here for now. To which frequency was it set? |
RxTone was 79.9 Hz like this:
Steps to reproduce:
Selecting an RxTone in qdmr and saving it to disk works. Also reloading this codeplug from disk works. Have not tried to flash an RxTone with qdmr yet. |
Ahh, yes. This way I can reproduce it. However, it is actually intentional: Have you set the Squelch mode to CTCSS/DCS? In my opinion, the RX CTCSS/DCS makes no sense if it does not control the squelch. As the internal codeplug representation in qdmr has no field to hold the squelch control separately from the RX CTCSS/DCS, I interpret a carrier based squelch as a disabled RX CTCSS/DCS. |
There is, however, a situation where a proper CTCSS tone may be read a disabled: The D878UV supports non-standard CTCSS frequencies, I do not support in qdmr. In these cases, the CTCSS setting is cleared for both RX and TX. |
Yes, squelch mode was carrier.
But found another issue: qdmr shows 79.9 Hz, but in AT CPS "77 Hz" was selected. Shall I open another issue? |
Ok, this appears to be another issue with the decoding of the codeplut. We can keep this bug issue for it. |
Found it. There was an entry missing, so all frequency indices were off by one. |
When reading a codeplug from D878UV the RxTone setting is lost (always "-"). TxTone works.
The text was updated successfully, but these errors were encountered: