[chirp_devel] tmode of "TSQL-R"
The tmode of "TSQL-R" is not documented. It appears to be used in a few drivers to map to the Yaesu internal squelch mode of "REV TN". Is this correct? more generally, is it acceptable to add an obscure mode to the UI? I had originally added "REV TN" as a value for an "extra" memory field on the ft-4. The FT-4 has yet another "extra" sql_type called "PAGER". can I add "PAGER" to the UI tmode list instead? I feel like both "TSQL-R" and "PAGER" should NOT be in the standard UI tmode list, but I will defer to the experts. My reasoning: the UI should remain as generic as possible to maximize the sharing of channel lists. Treating this sutff as "extra" allows the driver implementer to decide how to handle this stuff on a case-by-case basis. I'm als not completely sure that the semantics of "TSQL-R" is the same for non-Yaesu vs. Yaesu, although I think it's the same for all Yaesus.
The tmode of "TSQL-R" is not documented. It appears to be used in a few drivers to map to the Yaesu internal squelch mode of "REV TN".
Many (most?) radios have a reverse tone mode, several call this TSQL-R (or similar) in the radio itself and that's what the convention in chirp is. Many drivers in chirp may not support it, but that's a different thing.
Is this correct? more generally, is it acceptable to add an obscure mode to the UI? I had originally added "REV TN" as a value for an "extra" memory field on the ft-4. The FT-4 has yet another "extra" sql_type called "PAGER". can I add "PAGER" to the UI tmode list instead? I feel like both "TSQL-R" and "PAGER" should NOT be in the standard UI tmode list, but I will defer to the experts. My reasoning: the UI should remain as generic as possible to maximize the sharing of channel lists. Treating this sutff as "extra" allows the driver implementer to decide how to handle this stuff on a case-by-case basis. I'm als not completely sure that the semantics of "TSQL-R" is the same for non-Yaesu vs. Yaesu, although I think it's the same for all Yaesus.
TSQL-R _is_ part of the core and should be exposed as such if you're going to add it in your driver. Same for DTCS-R.
Many drivers have a "Pager" or "Bell" setting too, but very few drivers in chirp support it and it's not modeled in the core. So, I'd prefer you model your pager setting as a mem.extra, and support TSQL-R for the reverse tone function.
--Dan
Thanks! As I said earlier, I'm a very new Ham, so this is exactly the sort of stuff I don't know. I''ll modify the driver to handle TSQL-R from the tmode field and handle PAGER as an extra.
The ft-4 does not appear to have a DTCS-R function, by that or any other name, so implementing non-support should be easy :-)
If you wish to add me as a wiki editor, I can update the Tonemodes page.
On Thu, Feb 21, 2019, 15:42 Dan Smith via chirp_devel < chirp_devel@intrepid.danplanet.com> wrote:
The tmode of "TSQL-R" is not documented. It appears to be used in a few
drivers
to map to the Yaesu internal squelch mode of "REV TN".
Many (most?) radios have a reverse tone mode, several call this TSQL-R (or similar) in the radio itself and that's what the convention in chirp is. Many drivers in chirp may not support it, but that's a different thing.
Is this correct? more generally, is it acceptable to add an obscure mode
to the UI? I had originally added "REV TN" as a value for an "extra" memory field on the ft-4. The FT-4 has yet another "extra" sql_type called "PAGER". can I add "PAGER" to the UI tmode list instead?
I feel like both "TSQL-R" and "PAGER" should NOT be in the standard UI
tmode list, but I will defer to the experts. My reasoning: the UI should remain as generic as possible to maximize the sharing of channel lists. Treating this sutff as "extra" allows the driver implementer to decide how to handle this stuff on a case-by-case basis. I'm als not completely sure that the semantics of "TSQL-R" is the same for non-Yaesu vs. Yaesu, although I think it's the same for all Yaesus.
TSQL-R _is_ part of the core and should be exposed as such if you're going to add it in your driver. Same for DTCS-R.
Many drivers have a "Pager" or "Bell" setting too, but very few drivers in chirp support it and it's not modeled in the core. So, I'd prefer you model your pager setting as a mem.extra, and support TSQL-R for the reverse tone function.
--Dan _______________________________________________ chirp_devel mailing list chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers
Thanks! As I said earlier, I'm a very new Ham, so this is exactly the sort of stuff I don't know. I''ll modify the driver to handle TSQL-R from the tmode field and handle PAGER as an extra.
Sounds good.
The ft-4 does not appear to have a DTCS-R function, by that or any other name, so implementing non-support should be easy :-)
Yeah, not surprising.
If you wish to add me as a wiki editor, I can update the Tonemodes page.
Done.
--Dan
participants (2)
-
Dan Clemmensen -
Dan Smith