Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[RTTY\]\s+More\s+GRITTY\s+observations\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[RTTY\]\s+More\s+GRITTY\s+observations\s*$/: 21 ]

Total 21 documents matching your query.

1. [RTTY] More GRITTY observations (score: 1): Author: Tim Shoppa <tshoppa@gmail.com>; Date: Mon, 27 Apr 2015 10:02:34 -0400; Used three decoders in SP DX contest this past weekend. One each of MMTTY, 2Tone, and GRITTY. The fabulous 15M openings to JA and YB we've had the past couple weeks in my mornings, were a real treat.; /archives//html/RTTY/2015-04/msg00174.html (8,598 bytes)
2. Re: [RTTY] More GRITTY observations (score: 1): Author: "Larry Gauthier $K8UT$" <K8UT@charter.net>; Date: Mon, 27 Apr 2015 10:43:07 -0400; Tim, Thanks for sharing. I am particularly interested in your statement that "MMTTY works better on "slowish RTTY" senders", which lends credence to the notion that the best way to improve RTTY recep; /archives//html/RTTY/2015-04/msg00175.html (9,947 bytes)
3. Re: [RTTY] More GRITTY observations (score: 1): Author: "Joe Subich, W4TV" <lists@subich.com>; Date: Mon, 27 Apr 2015 11:08:53 -0400; Do you have any insight into the source of those slowish transmissions? A particular RTTY program or product? Or a particular hardware device? (1) The K3 paddle to RTTY mode where the user is not "le; /archives//html/RTTY/2015-04/msg00176.html (12,438 bytes)
4. Re: [RTTY] More GRITTY observations (score: 1): Author: "Kermit $aka Ken$ via RTTY" <rtty@contesting.com>; Date: Mon, 27 Apr 2015 11:17:37 -0400; Hi Tim, Did you run GRITTY standalone or in a logger? I've used it standalone along with classic N1MM/MMVARI/MMTTY/2Tone. Generally, my experience agrees with yours. 73, Ken, AB1J In a message dated; /archives//html/RTTY/2015-04/msg00177.html (7,563 bytes)
5. 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)
6. Re: [RTTY] More GRITTY observations (score: 1): Author: Kok Chen <chen@mac.com>; Date: Mon, 27 Apr 2015 09:35:37 -0700; There is actually a rational reason for this. Especially outside a contest, where the millisecond counters don't thread :-). If you are sending USOS, and the other end receives with a non-USOS decode; /archives//html/RTTY/2015-04/msg00179.html (8,545 bytes)
7. Re: [RTTY] More GRITTY observations (score: 1): Author: Bill Turner <dezrat@outlook.com>; Date: Mon, 27 Apr 2015 11:03:27 -0700; -- ORIGINAL MESSAGE --(may be snipped) REPLY: The need for AFC has always been an annoyance for me. AFC was developed back in the days of crystal control when crystals were not necessarily all on the; /archives//html/RTTY/2015-04/msg00180.html (8,974 bytes)
8. Re: [RTTY] More GRITTY observations (score: 1): Author: "Ed Muns" <ed@w0yk.com>; Date: Mon, 27 Apr 2015 10:35:50 -0700; I disagree that AFC should be on when running. I prefer AFC OFF all the time, so that I can choose where my VFO is tuned, rather than leaving that decision to my equipment. Ed W0YK -- ORIGINAL MESSAG; /archives//html/RTTY/2015-04/msg00181.html (7,972 bytes)
9. Re: [RTTY] More GRITTY observations (score: 1): Author: Phil Sussman <psussman@pactor.com>; Date: Mon, 27 Apr 2015 14:09:02 -0400; Chen, As usual, I'm confused by USOS and the functionality between stations. I understand there are only 16 possible combinations. -See below Is there an easy explanation of the best way to set your; /archives//html/RTTY/2015-04/msg00182.html (11,726 bytes)
10. Re: [RTTY] More GRITTY observations (score: 1): Author: Kok Chen <chen@mac.com>; Date: Mon, 27 Apr 2015 11:21:36 -0700; I had described USOS in the "Unstructured Digital Modes" section of Chapter 16 of the ARRL Handbook , viz. a space character is considered to be an implicit LTRS shift by both USOS sender and USOS re; /archives//html/RTTY/2015-04/msg00183.html (8,505 bytes)
11. Re: [RTTY] More GRITTY observations (score: 1): Author: Phil Sussman <psussman@pactor.com>; Date: Mon, 27 Apr 2015 15:02:43 -0400; After reading the information referenced, I wonder if the assumption can be made that the "USOS sender assumes that the receiver has shifted to LTRS shift after the sender transmits a space character; /archives//html/RTTY/2015-04/msg00184.html (10,148 bytes)
12. Re: [RTTY] More GRITTY observations (score: 1): Author: iw1ayd - Salvatore Irato <iw1ayd@gmail.com>; Date: Mon, 27 Apr 2015 21:17:40 +0200; Hi all, I am still not using GRITTY. There are some issues that leave me not so comfortable. Just not to be annoying to anyone and also not to waste bandwidth here I'd made a documents stored here ..; /archives//html/RTTY/2015-04/msg00185.html (8,270 bytes)
13. 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)
14. Re: [RTTY] More GRITTY observations (score: 1): Author: Jeff Stai <wk6i.jeff@gmail.com>; Date: Mon, 27 Apr 2015 13:15:31 -0700; In a non-scientific survey - mostly by gleaning from post contest comments and asking around - this is by far the leading cause of slow, non-diddled transmissions in contests. Unless they get a decen; /archives//html/RTTY/2015-04/msg00187.html (9,763 bytes)
15. Re: [RTTY] More GRITTY observations (score: 1): Author: Kok Chen <chen@mac.com>; Date: Mon, 27 Apr 2015 13:17:40 -0700; A USOS transmitter needs to send an explicit LTRS shift when sending certain sequences, if the receiver is not using USOS. Otherwise, a "599 OR" from the USOS transmitter will be received as "599 94"; /archives//html/RTTY/2015-04/msg00188.html (9,495 bytes)
16. Re: [RTTY] More GRITTY observations (score: 1): Author: "John GW4SKA" <ska@bartg.org.uk>; Date: Mon, 27 Apr 2015 21:21:24 +0100; GRITTY AFC is superb. I hate hate hate MMTTY AFC, if I leave it on all the time it wanders off to infinity. Tim N3QE Tim, That is user error. It only 'wanders off' as far as you have allowed. Go to; /archives//html/RTTY/2015-04/msg00189.html (9,288 bytes)
17. Re: [RTTY] More GRITTY observations (score: 1): Author: Bill Turner <dezrat@outlook.com>; Date: Mon, 27 Apr 2015 15:03:40 -0700; -- ORIGINAL MESSAGE --(may be snipped) REPLY: I'm trying to think of what advantage that gives one. Can you explain? 73, Bill W6WRT _______________________________________________ RTTY mailing list R; /archives//html/RTTY/2015-04/msg00190.html (9,376 bytes)
18. Re: [RTTY] More GRITTY observations (score: 1): Author: "Joe Subich, W4TV" <lists@subich.com>; Date: Mon, 27 Apr 2015 17:46:27 -0400; Go to setup; AFC/ATC/PLL then set the 'sweep' number to something like 0.4. I believe the figure is directly related to the shift frequency, so setting it to 0.4 allows the AFC to 'wander' by 0.4 x 1; /archives//html/RTTY/2015-04/msg00192.html (10,425 bytes)
19. Re: [RTTY] More GRITTY observations (score: 1): Author: Jeff Stai <wk6i.jeff@gmail.com>; Date: Mon, 27 Apr 2015 15:03:04 -0700; In a contest pileup especially, the best tuning point may not always be the one the decoder is trying to choose. You might want to wander off to one side... 73 jeff wk6i -- Jeff Stai ~ wk6i.jeff@gmai; /archives//html/RTTY/2015-04/msg00193.html (9,629 bytes)
20. Re: [RTTY] More GRITTY observations (score: 1): Author: "Ed Muns" <ed@w0yk.com>; Date: Mon, 27 Apr 2015 23:16:15 -0700; I think it is safe to assume that most, but maybe not all, stations you work will have USOS enabled. Therefore, your best odds are to have USOS enabled for both RX and TX at your station. No more ana; /archives//html/RTTY/2015-04/msg00195.html (11,998 bytes)

Current List: 1 - 20
Page: [1] [2]