[aprssig] DTMF encoding
F5SMZ Jean-Philippe f5smz at wanadoo.frTue Sep 30 21:38:27 UTC 2008
- Previous message: [aprssig] HT/mic DTMF standards
- Next message: [aprssig] DTMF encoding
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi all, following the various posts today, here is the my proposal/conclusion: 1) First, it appears that we need to stay below 17 digits (e.g most of TRX have a 16 digits memory bank limit) 2) We need a standard DTMF keyboard layout (GSM/Yaesu keyboard is fine; or at least more "standard") Here we go: Let's assume we use an encoding system "a la " Echolink; it will lead us to a maximum of 12 digits for a 6 character callsign. Example: F5SMZ = 3350746194 We need a checksum after that: 3350746194K and a "D" to terminate the sequence: 3350746194KD Now suppose we skip the ## preamble and just include the leading A: A3350746194KD We have now a 13 digits sequence; in case we have a 6 characters callsign, we reach 15 digits, which is still below the 16 digits memero bank limit of most TRX. This let us also run the B, C and Q APRStt sequences in the future. Hope it's help. jean-philippe F5SMZ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.tapr.org/pipermail/aprssig/attachments/20080930/89b64757/attachment.htm
- Previous message: [aprssig] HT/mic DTMF standards
- Next message: [aprssig] DTMF encoding
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the aprssig mailing list
