Search String: Display: Description: Sort:

Results:

References: [ +from:g3yyd@btinternet.com: 114 ]

Total 114 documents matching your query.

41. Re: [RTTY] GRITTY (score: 1)
Author: "David G3YYD" <g3yyd@btinternet.com>
Date: Sun, 12 Apr 2015 16:33:39 -0500
Jim I have thought about doing just that. Using it to select the best from the decoders that are built in to 2Tone. What seems to an experienced human to be a simple task to choose the best decode is
/archives//html/RTTY/2015-04/msg00072.html (9,940 bytes)

42. Re: [RTTY] GRITTY (score: 1)
Author: "David G3YYD" <g3yyd@btinternet.com>
Date: Mon, 13 Apr 2015 04:57:48 -0500
Bill It has been done. First you use a synchronous format, which is exactly the same for each and every transmission. Pity RTTY is asynchronous and the stop bit length varies all over the place along
/archives//html/RTTY/2015-04/msg00080.html (9,669 bytes)

43. Re: [RTTY] More GRITTY observations (score: 1)
Author: "David G3YYD" <g3yyd@btinternet.com>
Date: Mon, 27 Apr 2015 11:42:03 -0500
2Tone does vary its character synchronisation to cope with various stop bit lengths. It works best with stop bits at 1.5 bit time. If the stop bit is longer than 2.2 bit times it will go to asynchron
/archives//html/RTTY/2015-04/msg00178.html (14,492 bytes)

44. Re: [RTTY] More GRITTY observations (score: 1)
Author: "David G3YYD" <g3yyd@btinternet.com>
Date: Mon, 27 Apr 2015 15:57:22 -0500
Ever since I started using 2Tone,it has always worked with Unshift on Space (USOS) for both transmit and receive. I have not had any problem with it. I suspect a newbie who has USOS off will soon lea
/archives//html/RTTY/2015-04/msg00186.html (11,240 bytes)

45. Re: [RTTY] SPE 2K-FA amplifier duty cycle (score: 1)
Author: "David G3YYD" <g3yyd@btinternet.com>
Date: Mon, 18 May 2015 06:34:36 -0500
High intensity RTTY contesting consists of 10 to 15 seconds of TX followed by similar receive times. The worse case I have come across in my operations is SO1R CQing with no replies where average TX
/archives//html/RTTY/2015-05/msg00064.html (8,764 bytes)

46. Re: [RTTY] any way (score: 1)
Author: "David G3YYD" <g3yyd@btinternet.com>
Date: Mon, 20 Jul 2015 17:58:48 -0500
With sound card decoders then the limit on dynamic range is the receiver distortion. If the receiver is at 2.4KHz bandwidth then it will be a combination of harmonic distortion and Intermodulation pr
/archives//html/RTTY/2015-07/msg00064.html (10,391 bytes)

47. Re: [RTTY] RTTY SO2R "leakage"? (score: 1)
Author: "David G3YYD" <g3yyd@btinternet.com>
Date: Sat, 05 Sep 2015 07:01:36 -0500
Tim The amplitude range that 2Tone will work over is enormous. It samples at 48KHz at 16 bits and decimates that to a low sample rate. This alone increases the 90dB of the sound card by 30dB. Then th
/archives//html/RTTY/2015-09/msg00009.html (10,062 bytes)

48. Re: [RTTY] Upcoming 75 baud contest (score: 1)
Author: "David G3YYD" <g3yyd@btinternet.com>
Date: Fri, 18 Sep 2015 11:11:51 -0500
Even simpler with 2Tone go to Setup, Settings and click on 75 baud within the Speed box. I do not recommend using FSK TX for transmission unless you are using at least a 4 core multi-GHZ processor as
/archives//html/RTTY/2015-09/msg00032.html (8,101 bytes)

49. Re: [RTTY] Tinyfsk, 2Tone and USOS (score: 1)
Author: "David G3YYD" <g3yyd@btinternet.com>
Date: Sun, 27 Sep 2015 15:15:11 -0500
Chuck 2Tone sends ITA5 characters that have a ITA2 translation to TinyFSK (& rpiFSK same interface). All characters that do not have a ITA2 equivalent are ignored. The USOS is part of the TinyFSK in
/archives//html/RTTY/2015-09/msg00069.html (8,863 bytes)

50. Re: [RTTY] Tinyfsk, 2Tone and USOS (score: 1)
Author: "David G3YYD" <g3yyd@btinternet.com>
Date: Sun, 27 Sep 2015 16:05:07 -0500
Like I said TinyFSK sets the shift pattern not 2Tone. As you have the source code can always modify it. Personally I always use 2Tone DOOK. 73 David I just swapped out interfaces and put in an FSKit
/archives//html/RTTY/2015-09/msg00072.html (10,713 bytes)

51. Re: [RTTY] SO2R (score: 1)
Author: "David G3YYD" <g3yyd@btinternet.com>
Date: Mon, 28 Sep 2015 15:24:22 -0500
As a SO2R operator the CQ call is key. If made too short, for instance CQ M7T, then it does not give enough time for a complete reply to my CQ call on the other radio to be made. The idea is to time
/archives//html/RTTY/2015-09/msg00091.html (9,409 bytes)

52. Re: [RTTY] Decoder performance on crowded bands (score: 1)
Author: "David G3YYD" <g3yyd@btinternet.com>
Date: Mon, 28 Sep 2015 15:56:54 -0500
Tim Interesting comments. I wonder which decoder or was it decoders you were using in 2Tone? They are there for a purpose. I normally run two 2Tones per DI one with selective decoder and the other wi
/archives//html/RTTY/2015-09/msg00095.html (10,292 bytes)

53. Re: [RTTY] SO2R (score: 1)
Author: "David G3YYD" <g3yyd@btinternet.com>
Date: Mon, 28 Sep 2015 16:29:18 -0500
Simple it is the last opportunity that he has to ensure I have his call correct (I lose points for incorrect call) and for that station if he has QRM to know I have successfully worked him. In a busy
/archives//html/RTTY/2015-09/msg00102.html (11,408 bytes)

54. Re: [RTTY] Decoder performance on crowded bands (score: 1)
Author: "David G3YYD" <g3yyd@btinternet.com>
Date: Wed, 30 Sep 2015 10:33:15 -0500
One way of eliminating the problem is to analyse the previous text. So if received was CQ M7T M7T CQ AA5AU AA5AU there is sufficient information to parse the text to realise the CQ is by M7T and the
/archives//html/RTTY/2015-09/msg00161.html (13,458 bytes)

55. Re: [RTTY] CRLF ? (score: 1)
Author: "David G3YYD" <g3yyd@btinternet.com>
Date: Wed, 30 Sep 2015 15:34:48 -0500
Paul CRLF is carriage return and line feed. In the old teleprinter days both characters had to be sent to cause the print head to be aligned at the start of a new line, that is carriage return to mov
/archives//html/RTTY/2015-09/msg00171.html (8,531 bytes)

56. Re: [RTTY] RTTY Cut Numbers (score: 1)
Author: "G3YYD" <g3yyd@btinternet.com>
Date: Sun, 10 Jan 2016 14:29:06 -0500
If the checksum character is in error? Use another character to checksum the checksum? Or would it be easier to just send the serial number twice? Then if the 2 are different do a AGN request (shorte
/archives//html/RTTY/2016-01/msg00066.html (10,664 bytes)

57. Re: [RTTY] USOS Transmitting Again (score: 1)
Author: "G3YYD" <g3yyd@btinternet.com>
Date: Fri, 15 Jan 2016 07:01:51 -0500
Jim 2Tone has USOS on for receive and transmit. There is no option to turn it off. My design philosophy is to make 2Tone human interface as simple as possible. 2Tone's current TX behaviour for all so
/archives//html/RTTY/2016-01/msg00085.html (8,990 bytes)

58. Re: [RTTY] USOS Transmitting Again (score: 1)
Author: "G3YYD" <g3yyd@btinternet.com>
Date: Fri, 15 Jan 2016 07:15:40 -0500
Did you notice my deliberate error? Last paragraph should read: So with USOS off 599 WA WA would decode as 599 2- 2-. 2- being the figs shift of WA. Simple way to overcome this would be to send 599WA
/archives//html/RTTY/2016-01/msg00086.html (9,400 bytes)

59. Re: [RTTY] The more RTTY I do, the more fun I have... (score: 1)
Author: "G3YYD" <g3yyd@btinternet.com>
Date: Sun, 07 Feb 2016 09:20:21 -0500
The IARU Region 1 (Basically EU and AF) band plan is for 500Hz width transmissions to be between 7040 to 7050 with PSK starting at 7040. 7050 and up is 2.7KHz all digimodes to 7060. In practice most
/archives//html/RTTY/2016-02/msg00036.html (10,369 bytes)

60. Re: [RTTY] Some basic RTTY radio questions (score: 1)
Author: "G3YYD" <g3yyd@btinternet.com>
Date: Mon, 07 Mar 2016 05:10:52 -0500
Actually with RTTY the AGC setting should be slow. The reason for this is the best decoders decode each tone separately and make use of the signal amplitude and measured noise over time. They compare
/archives//html/RTTY/2016-03/msg00020.html (10,210 bytes)


This search system is powered by Namazu