Search String: Display: Description: Sort:

Results:

References: [ +from:k.siwiak@ieee.org: 89 ]

Total 89 documents matching your query.

21. Re: [RTTY] ARRL Symbol rate proposal (score: 1)
Author: Kai <k.siwiak@ieee.org>
Date: Sat, 19 Oct 2013 16:20:04 -0400
Why are we arguing for MORE regulation? Perhaps a gross simplification of the US amateur regulations might be better. The Canadian Amateur regulations are a good starting point, see the Tables in "St
/archives//html/RTTY/2013-10/msg00271.html (11,096 bytes)

22. Re: [RTTY] ARRL Symbol rate proposal (score: 1)
Author: Kai <k.siwiak@ieee.org>
Date: Sat, 19 Oct 2013 21:02:20 -0400
How many DXers are there in the world? We might take a stab at "HF active hams" by looking at LOTW published figures. Today's snap shot: of LOTW: The average QSL rate is 2x76,455,901/525,115,672 = 0.
/archives//html/RTTY/2013-10/msg00285.html (13,286 bytes)

23. Re: [RTTY] ARRL Symbol rate proposal (score: 1)
Author: Kai <k.siwiak@ieee.org>
Date: Sat, 19 Oct 2013 21:35:07 -0400
The1 and 2 IARU region band plans are very similar; region 3 lays out bands by mode, see the links: http://www.iaru-r2.org/band-plan/ 1 and 2 recommend up to 2700 Hz in what are the USA phone bands.
/archives//html/RTTY/2013-10/msg00286.html (12,541 bytes)

24. Re: [RTTY] ARRL attack on current RTTY users (score: 1)
Author: Kai <k.siwiak@ieee.org>
Date: Wed, 20 Nov 2013 18:01:17 -0500
Thanks for the w8ji link. That was very instructional. But be careful. The signal occupied bandwidth (what we presume to want to regulate) does not always relate to the noise bandwidth (which relates
/archives//html/RTTY/2013-11/msg00091.html (10,309 bytes)

25. Re: [RTTY] ARRL attack on current RTTY users (score: 1)
Author: Kai <k.siwiak@ieee.org>
Date: Wed, 20 Nov 2013 20:48:00 -0500
Hi Chen While I personally agree with you about much lower BW in a clean-slate world, consider the following. If the ARRL had chosen 2200 Hz instead of 2800 Hz, their proposal would have affected abs
/archives//html/RTTY/2013-11/msg00104.html (13,224 bytes)

26. Re: [RTTY] ARRL attack on current RTTY users (score: 1)
Author: Kai <k.siwiak@ieee.org>
Date: Fri, 22 Nov 2013 17:00:12 -0500
EXACTLY! I've brought this up obliquely before, but in more detail here: BW limit means "occupied BW" defined as less than 0.5% of power is below and less than 0.5% power is above the bandwidth. Ther
/archives//html/RTTY/2013-11/msg00157.html (11,707 bytes)

27. Re: [RTTY] ARRL attack on current RTTY users (score: 1)
Author: Kai <k.siwiak@ieee.org>
Date: Sat, 23 Nov 2013 11:00:30 -0500
Hi Joe, I was referring to the future, not the past. We DO want to keep the door open to innovation. That's why I agree that getting the baud language out of the regs is good. But I also think that 2
/archives//html/RTTY/2013-11/msg00167.html (17,081 bytes)

28. Re: [RTTY] ARRL attack on current RTTY users (score: 1)
Author: Kai <k.siwiak@ieee.org>
Date: Sat, 23 Nov 2013 14:08:41 -0500
Hi Chen Have at it! I'm just posting information as I can find it. Info: Note that PACTOR-III was built for the commercial market. I think only PACTOR-III SL1 and SL2, the two lowest order speeds fit
/archives//html/RTTY/2013-11/msg00180.html (11,540 bytes)

29. Re: [RTTY] ARRL attack on current RTTY users (score: 1)
Author: Kai <k.siwiak@ieee.org>
Date: Sat, 23 Nov 2013 18:20:30 -0500
John, The appropriate course of action now would be to file comments about the ARRL proposal (and just the proposal). One approach may be, a step by step effort to defeat any BW greater than 2,200 Hz
/archives//html/RTTY/2013-11/msg00200.html (11,629 bytes)

30. Re: [RTTY] Hints and tips on how to file comments on RM-11708 (score: 1)
Author: Kai <k.siwiak@ieee.org>
Date: Sun, 24 Nov 2013 13:07:54 -0500
I've now studied the ARRL proposal and take the position that symbol rate language is indeed unnecessarily restrictive for modern advances in the state of the amateur radio arts. So most of the ARRL
/archives//html/RTTY/2013-11/msg00230.html (11,357 bytes)

31. Re: [RTTY] Hints and tips on how to file comments on RM-11708 (score: 1)
Author: Kai <k.siwiak@ieee.org>
Date: Sun, 24 Nov 2013 21:30:01 -0500
Chen I finally found non-ARRL info about PACTOR-III. The manufacturer claims an occupied BW of 2.2 kHz not 2.4 kHz as I used in my argument before. So where I used '2.4 kHz' before I now put '2.2kHz'
/archives//html/RTTY/2013-11/msg00245.html (11,486 bytes)

32. Re: [RTTY] Hints and tips on how to file comments on RM-11708 (score: 1)
Author: Kai <k.siwiak@ieee.org>
Date: Sun, 24 Nov 2013 22:07:52 -0500
Hi Joe, It squares this way. PACTOR uses multiple tones, but not tone shifting, so shift is zero. PACTOR baud rate is around 100 Hz, so it is well below the 300 Hz max, so legal. The key is that PACT
/archives//html/RTTY/2013-11/msg00248.html (14,762 bytes)

33. Re: [RTTY] Hints and tips on how to file comments on RM-11708 (score: 1)
Author: Kai <k.siwiak@ieee.org>
Date: Sun, 24 Nov 2013 22:26:31 -0500
Joe Let's be careful about associating PACTOR with "inefficient modes". My VERY PRELIMIARY assessment is that PACTOR-III in its lowest data rate of about 76 user bps may outperform "Steam-RTTY" by as
/archives//html/RTTY/2013-11/msg00250.html (13,510 bytes)

34. Re: [RTTY] Need to lawyer up for 60 meters (score: 1)
Author: Kai <k.siwiak@ieee.org>
Date: Sun, 24 Nov 2013 23:12:16 -0500
Bill The FCC/NTIA want you to: (1) monitor the channel for possible upper SSB transmissions if you are to be told to stop. (2) The RTTY tones must be 1500 Hz +/- 85 Hz above the SSB rig dial frequenc
/archives//html/RTTY/2013-11/msg00257.html (9,366 bytes)

35. Re: [RTTY] Hints and tips on how to file comments on RM-11708 (score: 1)
Author: Kai <k.siwiak@ieee.org>
Date: Sun, 24 Nov 2013 23:22:49 -0500
"Steam-RTTY" is Chen's affectation for 45.45 baud 170 Hz shift Baudot RTTY. We use it with respect and affection! It is an aulde modulation that has stood the test of time. 73 Kai Steam-RTTY REPLY: H
/archives//html/RTTY/2013-11/msg00259.html (10,404 bytes)

36. Re: [RTTY] Hints and tips on how to file comments on RM-11708 (score: 1)
Author: Kai <k.siwiak@ieee.org>
Date: Sun, 24 Nov 2013 23:39:23 -0500
Chen The FCC have also stated that Note 23 on page 11 of ARRL filing: "As the commission noted in Mark Miller, supra, changing the rules to prohibit a communications technology that is currently in u
/archives//html/RTTY/2013-11/msg00262.html (12,340 bytes)

37. Re: [RTTY] Need to lawyer up for 60 meters (score: 1)
Author: Kai <k.siwiak@ieee.org>
Date: Mon, 25 Nov 2013 11:20:40 -0500
... and in UPPER SSB... Remember that the 60 m band channels are UPPER SSB, so in AFSK, use upper SSB. If you use MMTTY than you also select "rev". Note that the MMTTY "Mark" nomenclature is incorrec
/archives//html/RTTY/2013-11/msg00271.html (10,999 bytes)

38. Re: [RTTY] Need to lawyer up for 60 meters (score: 1)
Author: Kai <k.siwiak@ieee.org>
Date: Mon, 25 Nov 2013 14:15:16 -0500
That information is badly outdated. The FCC and NTIA have since interpreted it far more leniently. For Amateur-RTTY, see the Technical Correspondence, QST, Sept 2013 for an example of how to use Amat
/archives//html/RTTY/2013-11/msg00276.html (12,614 bytes)

39. Re: [RTTY] Need to lawyer up for 60 meters (score: 1)
Author: Kai <k.siwiak@ieee.org>
Date: Mon, 25 Nov 2013 17:44:28 -0500
Hi Bill Actually those are examples ("such as") of permitted modes, and NTIA have said they are not limiting. Note that 2K80J2D: the 2K80 means 2.8 kHz, and the J2D means SSB suppressed carrier with
/archives//html/RTTY/2013-11/msg00284.html (15,698 bytes)

40. Re: [RTTY] Need to lawyer up for 60 meters (score: 1)
Author: Kai <k.siwiak@ieee.org>
Date: Tue, 26 Nov 2013 13:17:59 -0500
MSK is FSK with shift (as understood by hams) equal to half the baud rate. So 45.45 baud with 22.725 shift would be approximately MSK. if you've used 45.45 baud with 23 Hz shift you were close enough
/archives//html/RTTY/2013-11/msg00302.html (10,928 bytes)


This search system is powered by Namazu