WriteLog
[Top] [All Lists]

Re: [WriteLog] BARTG 75 setup

To: writelog@contesting.com
Subject: Re: [WriteLog] BARTG 75 setup
From: Jerry Pixton <jpixton@shentel.net>
Date: Thu, 25 Apr 2013 23:45:43 +0000
List-post: <writelog@contesting.com">mailto:writelog@contesting.com>
AFSK seems to work with mmtty as the primary rttyrite TU (uncheck "fix 45.5 baud" and change decode to 75. Change 2Tone clone to 75. It seems to work but no signals to test. Will see on Sunday, hi

Jerry, W6IHG

On 4/25/2013 2:39 AM, Don AA5AU wrote:
Gary is correct. Looks like there is a reason to keep the MMTTY plug-in 
installed. The only setup that works correctly for 75 baud FSK is using the 
MMTTY plug-in as shown in the tutorial shown here:

http://rttycontesting.com/75baudrtty/75baudrtty.html


MMTTY via XMMT.ocx does work but the transmit buffering is such that the 
characters do not go out as they are typed if transmitting live at the 
keyboard. When sending messages, the timing between what goes out and what is 
showing on the screen in blue characters is not the same but the messages are 
going out so fast it's hard to tell the difference. The messages do go out and 
are decoded correctly on the receive end when using MMTTY via XMMT.ocx.

The best option is to use the MMTTY plug-in for BARTG Sprint 75 on Sunday if 
you are transmitting FSK and allow MMTTY to control FSK. That setup is shown in 
section 3, on this page:

http://rttycontesting.com/writelog/rttyrite/rttyrite-fsk-mmtty-plugin.html


I have not tested AFSK yet, but I'm guessing it will work regardless of using 
WinRTTY, MMTTY plug-in, 2Tone or MMTTY via XMMT.ocx. When I have time, I will 
test them.

Thanks for the heads up Gary!

73, Don AA5AU



________________________________
From: Don AA5AU <aa5au@bellsouth.net>
To: Gary AL9A <al9a@mtaonline.net>; Writelog Reflector <writelog@contesting.com>
Sent: Wednesday, April 24, 2013 9:05 PM
Subject: Re: [WriteLog] BARTG 75 setup


Gary, thanks for the all the information. And don't worry about your head 
spinning because mine gets that way all the time when going through all these 
various setups with WL. I have not tested 75 baud with XMMT.ocx yet. But will 
do so tonight if I have time and report back. I have obtained an older XP 
desktop with legacy COM ports which I am going to start using with my second 
radio so I can do SO2R in BARTG 75. My present setup is with a laptop and USB 
adapter which won't work for 75 baud.

73, Don AA5AU



________________________________
From: Gary AL9A <al9a@mtaonline.net>
To: Writelog Reflector <writelog@contesting.com>
Sent: Wednesday, April 24, 2013 8:53 PM
Subject: Re: [WriteLog] BARTG 75 setup


Now I'm in the deep end of the swamp!  I just reviewed Don's notes on setting 
up for running 75 baud on www.rttycontesting.com and have apparently stumbled 
into a conundrum that has no obvious solution.  As previously noted and 
discussed, using the XMMT.ocx interface with RttyRite set to Hardware FSK 
causes severe timing problems and jerky sending of macro messages.  The 
solution is to go forego Hardware FSK and use Software FSK and let MMTTY take 
care of the keying and timing problems.  However, in Don's notes, dating back 
to June of 2011, it is stated that use of Software generated FSK will limit the 
transmit speed to ONLY 45 baud.  With Software generated FSK it isn't possible 
to achieve 75 baud speed!

So unless I am missing something here, when using the XMMT.ocx interface it 
will not be possible to achieve 75 baud unless you use Hardware generated FSK.  
But Hardware generated FSK with XMMT.ocx will produce the buffer timing speed 
issue that is unacceptable.  So now my thinking is that in order to run 75 baud 
for the BARTG 75 I must go back and reinstall the MMTTY plug-in and use that 
for the RttyRite transmit window at 75 baud  instead of XMMT.ocx?  As I am 
typing this my mind is now asking should I delete all my RttyRite sections in 
the ini file an let WL rebuild those too?  Life ain't simple out here on the 
bleeding edge!

73,
Gary AL9A



----- Original Message ----- From: "Gary AL9A" <al9a@mtaonline.net>
To: "Writelog Reflector" <writelog@contesting.com>
Sent: April 24, 2013 5:22 PM
Subject: Re: [WriteLog] BARTG 75 setup


Think I just figured it out.  Upon closer listening I don't think my main 
RttyRite window is sending at 75 baud!  It sounds like it is still sending at 
45 baud, despite the Mode being set to 75 and the MMTTY Decode tab being set to 
75 baud.  What the heck else needs to be set?

73,
Gary AL9A


----- Original Message ----- From: "Gary AL9A" <al9a@mtaonline.net>
To: "Writelog Reflector" <writelog@contesting.com>
Sent: April 24, 2013 5:10 PM
Subject: [WriteLog] BARTG 75 setup


Ok, I'm puzzled.  I'm setting up WL for the BARTG 75 this next Sunday. I'm 
using V11.11C with the TU type in RttyRite set to XMMT.ocx as my main send and 
receive window.  I have a clone RttyRite setup with XMMT.ocx for 2Tone and 
another clone RttyRite setup with XMMT.ocx using the AA6YQ FIR512 profile.  All 
windows perform decode normally at 45 baud.

In all three RttyRite windows I changed the Mode to 75 baud. However, in the 
clone 2Tone Setup if the speed is changed to 75 Baud it prints my send macros 
as gibberish.  If I leave it set at 45.45 Baud (with the RttyRite Mode speed 
set to either 45 baud or 75 baud) it prints my macros normally.

In the RttyRite clone window the the AA6YQ profile, if I set the Mode to 75 
baud and set that instance of MMTTY to 75 baud, it also prints my macros as 
gibberish.  Change the Mode back to 45 baud and RttyRite will now print my 75 
baud sending correctly.  The MMTTY instance is still set to 75 baud, but since 
this is a clone receive window apparently the speed in that MMTTY instance 
doesn't matter.

So the questions are, why do both 2Tone and RttyRite clone windows correctly 
decode what is being sent at 75 baud when they are set to 45 baud?  Also, since 
2Tone running in the clone window is not the transmit window, why does it print 
gibberish when its Setup speed is changed to 75 Baud?  Something seems goofy, 
but I'm darned if I can come up with a plausible answer.

73,
Gary AL9A
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web:  http://www.writelog.com/


_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web:  http://www.writelog.com/


_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web:  http://www.writelog.com/



_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web:  http://www.writelog.com/



_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web:  http://www.writelog.com/


--
-----------------------------------------------
Dr. Jerry R. Pixton, PIXOS Designs
http://www.shentel.net/pixosdesigns/RadioTuner/
jpixton@shentel.net
-----------------------------------------------
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web:  http://www.writelog.com/

<Prev in Thread] Current Thread [Next in Thread>