microHAM's baud rate has always been within acceptable tolerance.
The "issue" if there is one is the difference between 45 and 45.45
bps (0.22 ms in the length of a bit) or 45.45 and 46 bps (0.26 ms
in the length of the bit. That's less than 1.2% and 45.45 bps and
the tolerance is even closer at at other (50, 75, 100 and 110 bps.)
supported rates.
If you want to quibble about <.3 ms in the length of a bit when
EXTFSK and other interfaces are lucky to be +/- 1 msec., have at
it but just be sure you keep it in context! Oh, by the way EXTFSK
is limited to "45 baud" only and most other multi-function FSK
interfaces will not do some or all of the other common rates.
73,
... Joe, W4TV
On 2/11/2013 4:47 PM, Jay WS7I wrote:
So the incorrect baud rate that microham uses instead of 45.45 has been
fixed ?
On 2/11/2013 11:58 AM, Joe Subich, W4TV wrote:
Now on the subject of slow, or odd sounding RTTY, I can confirm that
if you use a microHam router with MMTTY, and you have Strict BPS
enabled, the resulting sent stream of text is much slower than
usual.
That was true in the past but so much with the new version of microHAM
Router and more recent Eltima VSPAX code. I just timed a 130 character
string ("<CR><LF>DE W4TV W4TV W4TV W4TV " x 5) from MMTTY - the message
was about three seconds longer with Strict BPS enabled vs. Strict BPS
disabled. The timing was done with only a digital clock but "by ear"
there was very little change in the "sound".
_______________________________________________
RTTY mailing list
RTTY@contesting.com
http://lists.contesting.com/mailman/listinfo/rtty
_______________________________________________
RTTY mailing list
RTTY@contesting.com
http://lists.contesting.com/mailman/listinfo/rtty
|