[aprssig] How to deal with DTMF keypad differences between manufacturers
F5SMZ Jean-Philippe f5smz at wanadoo.frTue Sep 30 07:11:21 UTC 2008
- Previous message: [aprssig] OpenAPRS Direct Client Connection Interface (gogo gadgetsmart phones)
- Next message: [aprssig] How to deal with DTMF keypad differences betweenmanufacturers
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi all, prototyping the APRStt engine with a soundcard on Windows XX lead me to this situation during the various tests. Entering the callsign with the Kenwood DTMF keypad is OK, following the APRStt spec with my TH-D7. But when I want to use my "old" FT-470 from Yaesu, my "1" is "empty", QZ are elsewhere (identical as my GSM), e.g "7" and "9" keys are hosting 4 different letters!; so I'm currently wandering how to deal with that, as tones doesn't reflect kenwood's ones. Another issue, was the testing of "long" callsign DTMF strings, where we can easily goes up to 18 DTMF digits in normal mode, obviously not in hashing mode; but various tested TRX have only 15 to 16 DTMF digits memories. 73, Jean-philippe, F5SMZ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.tapr.org/pipermail/aprssig/attachments/20080930/faf68081/attachment.htm
- Previous message: [aprssig] OpenAPRS Direct Client Connection Interface (gogo gadgetsmart phones)
- Next message: [aprssig] How to deal with DTMF keypad differences betweenmanufacturers
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the aprssig mailing list
