开云体育

The question of CW offset comes up a LOT more frequently than it really should. Here's some reading material for everybody:
/g/BITX20/topic/71305167
/g/BITX20/topic/71240646
/g/BITX20/topic/69640840
/g/BITX20/topic/68539883
/g/BITX20/topic/30247137

My opinion is that the frequency displayed should be the carrier (suppressed carrier if in SSB, and actual carrier in CW). This is how my R1.5.0 software version operates, how TSW's Teensy software displays, and how off-the-shelf radios like ICOM rigs work. There are lots of good reasons to have the TX carrier be the value shown on screen, and if you read through the above linked threads, many of them are explicitly listed.

However, it is NOT how the stock v6 software operates. The stock v6 software transmits CW at the listening frequency. So if your stock v6 shows 7.025.000 on the dial and you have a 800Hz tone set, then you actually transmit at 7.024.200, NOT the frequency shown on the screen! This is the root of Jerry's problem. His reference rig is correctly displaying the desired TX frequency, and if he were to key up with his reference rig, he'd need to tune his uBiTX screen to display 800Hz ABOVE that frequency to get the right tone, not the 800Hz tone offset frequency that the stock v6 uBiTX is transmitting on.

The fix isn't RIT - this isn't an issue of the receivers disagreeing with the transmitters. The fix is to change the frequency displayed on the uBiTX screen to show the actual transmitted carrier frequency.


Reed