Re: FT-50 full duplex - was: [amsat-bb] Handheld for Echo and FM Sats?

[Mike Gilchrist <32one@xxxxxxxxxxxxx>]

I have my FT-50 sitting here with me.  I am looking at the frequencies I 
have programmed into the rig for AO-27.  There are five of them, per my 
post from yesterday.  I have an observation that might be a clue as to why 
your rig isn't allowing you to hear your downlink.

When I go through the menus, looking at ALL the settings for AO 1, I find:

SQL     0
TXPO    HI
RPTR    DUP     This may be the key.  The upper right of the screen also 
has a black -+
                 It won't let me change it either!  I think because it 
contains a non-standard split.
SHFT            Not changeable!
VDUP    Off
RPTL    off
RESM    5
SCNL    off
APO     off     Automatic Repeater Offset (may be critical)
WSQL    0       Not changeable!
AMOD    on
RMOD    N-FM


Now all of my repeater entries have very different settings, and my simplex 
entries have other very different settings.  Once I had these working I 
"copied" each entry over and over, changing frequency and name tag for 
several other entries, including a set of five for SO-35.

Try these settings and post back here your results.

73, Mike kf4fdj



At 10:10 AM 7/9/2004, Mike Gilchrist wrote:
>John:
>
>You may have a point.  My serial number is 7F201614.  I have the keyboard 
>addition which adds DVR, and maybe the key is here: I did the mod which 
>opens up the transmit/receive range.
>
>At one time I had a 70 cm repeater on the tower at my job.  The fellow who 
>built the repeater had a 2 M repeater which we used to link to mine.  He 
>would use the 2 M input and listen on my 70 cm output.  I would talk on 
>the 70 cm input and listen on his 2 M output.  I have sat for hours in my 
>living room talking to him *FULL DUPLEX* using my FT-50.  We could key 
>down and *BOTH* of us could interrupt each other at will.  We talked that 
>way regularly.
>
>Now when you are programming those frequencies, make sure you turn off any 
>repeater offset!  You have to make sure you program simplex frequencies 
>into the slot.  If you don't, you might have the receiver, which is still 
>working as you transmit, listening to another frequency other than one 
>which you have set up in your test.  Maybe you still don't have the rig 
>set up properly?
>
>I've done countless demos on the easy sats using my FT-50.  Maybe I DO 
>have a spook radio, but it DOES function as a full duplex rig.
>
>At 09:30 AM 7/9/2004, John P. Toscano wrote:
>>Mike, it appears that YOUR Yaesu FT-50r doesn't work like MY Yaesu FT-50r 
>>(or some other folks' FT-50r's).  Mine is an older model, was originally 
>>an FT-50r and had the upgrade to FT-50rd done later (replacement keypad 
>>which added new tone and voice recording abilities), and it has the old 
>>firmware that is reportedly able to be more easily "freebanded" (though I 
>>never even tried that trick).
>>
>>Anyway, just to make sure, I programmed a UHF receive / VHF transmit pair 
>>into memory 96 just like you described.  Of course, I had no trouble 
>>doing that, I've always known the radio could do that, as I have some 
>>memory channels programmed like that for debugging our local VHF repeater 
>>via its UHF remote link frequencies.  **BUT** I then tuned my FT-847 to 
>>the programmed UHF reception frequency of the FT-50r, confirmed that when 
>>I keyed up the '847 that the '50r could hear it without trouble, and then 
>>keyed up the '50r.  NO MORE RECEPTION on UHF while the '50r was 
>>transmitting on VHF.  My FT-50r simply stops receiving while it is 
>>transmitting.  BTW, this is identical to my experience with the repeater 
>>setup.  I transmit on UHF, the local repeater hears me on the UHF link 
>>and re-transmits me on VHF, but I don't hear my own signal on VHF, I only 
>>hear the repeater courtesy beep when I unkey.  This is completely 
>>different from what happens with the FT-847 or FT-5100, where I do hear 
>>my VHF signal while I talk on UHF.
>>
>>So if your FT-50r can do this trick, congratulations to you, or too bad 
>>for me.  Maybe we need to compile a list of serial numbers that DO and 
>>DON'T operate this way, to see if we can figure out where the change 
>>occurred (if it is a firmware issue).  Mine is 6K112044.  Sorry if I 
>>contributed to any aggravation on your part, that was never my intention.
>
>
>----
>Sent via amsat-bb@amsat.org. Opinions expressed are those of the author.
>Not an AMSAT member? Join now to support the amateur satellite program!
>To unsubscribe, send "unsubscribe amsat-bb" to Majordomo@amsat.org


----
Sent via amsat-bb@amsat.org. Opinions expressed are those of the author.
Not an AMSAT member? Join now to support the amateur satellite program!
To unsubscribe, send "unsubscribe amsat-bb" to Majordomo@amsat.org