[wxsig] RE: Chaning T238+ destination callsign
Steve KA5YFC ssbrockw at swbell.netSat Feb 25 05:52:51 UTC 2006
- Previous message: [wxsig] Chaning T238+ destination callsign
- Next message: [wxsig] Changing T238+ destination callsign
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Will, You might check with Bob, WB4APR, and make sure that the APWX.. is not taken by another application before it is set in stone. There is some kind of application registration thing that they keep track of to make sure that each app is recognized. Steve KA5YFC -----Original Message----- From: Will Beals Subject: [wxsig] Chaning T238+ destination callsign Folks: Someone finally explained why the T238 weather data does not show up on Kenwood D7 handhelds and D700 mobile rigs. Those rigs default to only decode data who's destination callsign begins with AP. This seemed a rather strange to me, but in a piece of test code I changed the T238s source callsign from WX1W to APWX1W and sure enough, the data suddenly appeared on my D7! If there are some good reasons for some folk to stick with WX1W, then I can make it a user option to select different destination callsigns. If there aren't any good reasons, then I'd like to just change the hardcoded destination callsign to APWX1W. Any issues? will
- Previous message: [wxsig] Chaning T238+ destination callsign
- Next message: [wxsig] Changing T238+ destination callsign
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the wxsig mailing list
