I have two beacons set up: default and HF. For some reason, whenever I send a capitol "C" on the HF beacon, it comes out as "ÛC". Example: "ÛColorado" vs "colorado". This happens on two seperate computers and does not happen with a lower case "c" or when using the default beacon.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That's very weird. Could you export your configuration (File->Configure->Export to XML) and send that and transmit log (log directory, file AX25xmit* just for the date where you saw the problem? I think I'm going to need to see how you're set up for this.
Also, what are you using for an HF TNC, and what are you receiving the garbled packets with?
Incidentally, does it happen with any other upper case letters besides "C"?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Using a SignaLink and UZ7HO's SoundModem. I have only seen it happen with the C. I have seen it constantly since you added the multiple beacon option. I should correct that I do see it on the default beacon IF I use a soundcard instead of a TNC, so maybe it is a soundcard issue.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have two beacons set up: default and HF. For some reason, whenever I send a capitol "C" on the HF beacon, it comes out as "ÛC". Example: "ÛColorado" vs "colorado". This happens on two seperate computers and does not happen with a lower case "c" or when using the default beacon.
That's very weird. Could you export your configuration (File->Configure->Export to XML) and send that and transmit log (log directory, file AX25xmit* just for the date where you saw the problem? I think I'm going to need to see how you're set up for this.
Also, what are you using for an HF TNC, and what are you receiving the garbled packets with?
Incidentally, does it happen with any other upper case letters besides "C"?
Using a SignaLink and UZ7HO's SoundModem. I have only seen it happen with the C. I have seen it constantly since you added the multiple beacon option. I should correct that I do see it on the default beacon IF I use a soundcard instead of a TNC, so maybe it is a soundcard issue.
Here is a typical transmit log. The HF beacon is from KD0SFY-2 and does not appear to contain the strange character, but it does get added somehow.
Here is the xml.
And here are two beacons:
1:Fm KD0SFY-2 To APJYC1 <UI C="" Pid="F0" Len="59"> [13:32:57T]
@203257h3853.25N/10447.54W&/A=6398 ÛColorado Springs IGate
1:Fm KD0SFY-2 To APJYC1 <UI C="" Pid="F0" Len="58"> [13:33:57T]
@203357h3853.25N/10447.54W&/A=6398 colorado Springs IGate