Re: [Elecraft] 60 meters

2019-06-05 Thread krug261--- via Elecraft
 The second suggestion by Don sounds like it would be "more fun" and not take 
up an additional five memories.

BobKA2TQVOn Tuesday, June 4, 2019, 8:22:28 PM EDT, Don Wilhelm 
 wrote:  
 
 The other easy solution is to use only 5 channel hopping memories and 
create a Macro to move the VFO A up or down 1.5kHz depending on whether 
you stored SSB or CW frequencies in VFO A.  The frequency shift is 
constant for all channels, so one Macro will do for all channels.
Assign the Macro to a PF button.

73,
Don W3FPR

On 6/4/2019 7:52 PM, Fred Jensen wrote:
> That doesn't work Wes, the problem is simpler than that.  However, Don 
> has confirmed the behavior, and now it's time for me to be a "Real Ham" 
> and do something here in NE Sparks NV [instead of on the list] to fix 
> "my" problem.  Don's [and one other's] solution with 10 memories is a 
> first-run candidate. Since I haven't been on SSB in years, ignoring what 
> happens to VFO B may be an answer too. [:-)
> 
__
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to krug...@yahoo.com   
__
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to arch...@mail-archive.com 

Re: [Elecraft] 60 meters

2019-06-04 Thread Don Wilhelm
The other easy solution is to use only 5 channel hopping memories and 
create a Macro to move the VFO A up or down 1.5kHz depending on whether 
you stored SSB or CW frequencies in VFO A.  The frequency shift is 
constant for all channels, so one Macro will do for all channels.

Assign the Macro to a PF button.

73,
Don W3FPR

On 6/4/2019 7:52 PM, Fred Jensen wrote:
That doesn't work Wes, the problem is simpler than that.  However, Don 
has confirmed the behavior, and now it's time for me to be a "Real Ham" 
and do something here in NE Sparks NV [instead of on the list] to fix 
"my" problem.  Don's [and one other's] solution with 10 memories is a 
first-run candidate. Since I haven't been on SSB in years, ignoring what 
happens to VFO B may be an answer too. [:-)



__
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to arch...@mail-archive.com 

Re: [Elecraft] 60 meters

2019-06-04 Thread Fred Jensen
That doesn't work Wes, the problem is simpler than that.  However, Don 
has confirmed the behavior, and now it's time for me to be a "Real Ham" 
and do something here in NE Sparks NV [instead of on the list] to fix 
"my" problem.  Don's [and one other's] solution with 10 memories is a 
first-run candidate. Since I haven't been on SSB in years, ignoring what 
happens to VFO B may be an answer too. [:-)


73,
Fred ["Skip"] K6DGW
Sparks NV DM09dn
Washoe County

On 6/4/2019 4:31 PM, Wes wrote:
I do what Don suggests.  That said, I think if you do an A/B it will 
fix your problem, if I understand it correctly.


Wes  N7WS

On 6/4/2019 4:21 PM, Don Wilhelm wrote:

Fred and all,

I have observed what you found.  On Channel Hopping, VFO A follows 
the hop to the next channel, but VFO B does not.


While a "fix" may be coming sometime, it is not likely to be coming 
soon.  So I propose a workaround.


The simple solution is to set 10 channel hopping memories instead of 
only 5.  5 for SSB/DATA and 5 more for CW.  I doubt that you are 
using all 100 memory slots in the K3.


Arrange them any way you want - each CW memory next to the SSB 
memory, or go through all 5 SSB memories and then the next 5 are CW.  
Put some identifier in the label so you can see which is which 
without referring to the frequency.


73,
Don W3FPR

On 6/4/2019 3:02 PM, Fred Jensen wrote:
This began as a simple question, I can't understand why it is so 
hard to explain:  K3 frequency memories hold frequency, mode, and 
DSP BW for both VFO A and VFO B.  I used the K3 Frequency Editor to 
load the CW parameters into VFO A and USB parameters into VFO B in 5 
consecutive memory channels.  Those 5 are "ganged together" with an 
"*" in the name, IIRC.


When I rotate the Big Knob, I expected the VFO's to rotate through 
the channels [end-around].  VFO A does, but VFO B does not follow, 
it remains on whatever channel I originally selected. 




__
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to arch...@mail-archive.com 

Re: [Elecraft] 60 meters

2019-06-04 Thread Wes
I do what Don suggests.  That said, I think if you do an A/B it will fix your 
problem, if I understand it correctly.


Wes  N7WS

On 6/4/2019 4:21 PM, Don Wilhelm wrote:

Fred and all,

I have observed what you found.  On Channel Hopping, VFO A follows the hop to 
the next channel, but VFO B does not.


While a "fix" may be coming sometime, it is not likely to be coming soon.  So 
I propose a workaround.


The simple solution is to set 10 channel hopping memories instead of only 5.  
5 for SSB/DATA and 5 more for CW.  I doubt that you are using all 100 memory 
slots in the K3.


Arrange them any way you want - each CW memory next to the SSB memory, or go 
through all 5 SSB memories and then the next 5 are CW.  Put some identifier in 
the label so you can see which is which without referring to the frequency.


73,
Don W3FPR

On 6/4/2019 3:02 PM, Fred Jensen wrote:
This began as a simple question, I can't understand why it is so hard to 
explain:  K3 frequency memories hold frequency, mode, and DSP BW for both VFO 
A and VFO B.  I used the K3 Frequency Editor to load the CW parameters into 
VFO A and USB parameters into VFO B in 5 consecutive memory channels.  Those 
5 are "ganged together" with an "*" in the name, IIRC.


When I rotate the Big Knob, I expected the VFO's to rotate through the 
channels [end-around].  VFO A does, but VFO B does not follow, it remains on 
whatever channel I originally selected. 


__
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to arch...@mail-archive.com 

Re: [Elecraft] 60 meters

2019-06-04 Thread Don Wilhelm

Fred and all,

I have observed what you found.  On Channel Hopping, VFO A follows the 
hop to the next channel, but VFO B does not.


While a "fix" may be coming sometime, it is not likely to be coming 
soon.  So I propose a workaround.


The simple solution is to set 10 channel hopping memories instead of 
only 5.  5 for SSB/DATA and 5 more for CW.  I doubt that you are using 
all 100 memory slots in the K3.


Arrange them any way you want - each CW memory next to the SSB memory, 
or go through all 5 SSB memories and then the next 5 are CW.  Put some 
identifier in the label so you can see which is which without referring 
to the frequency.


73,
Don W3FPR

On 6/4/2019 3:02 PM, Fred Jensen wrote:
This began as a simple question, I can't understand why it is so hard to 
explain:  K3 frequency memories hold frequency, mode, and DSP BW for 
both VFO A and VFO B.  I used the K3 Frequency Editor to load the CW 
parameters into VFO A and USB parameters into VFO B in 5 consecutive 
memory channels.  Those 5 are "ganged together" with an "*" in the name, 
IIRC.


When I rotate the Big Knob, I expected the VFO's to rotate through the 
channels [end-around].  VFO A does, but VFO B does not follow, it 
remains on whatever channel I originally selected.



__
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to arch...@mail-archive.com 

Re: [Elecraft] 60 meters

2019-06-04 Thread Fred Jensen
This began as a simple question, I can't understand why it is so hard to 
explain:  K3 frequency memories hold frequency, mode, and DSP BW for 
both VFO A and VFO B.  I used the K3 Frequency Editor to load the CW 
parameters into VFO A and USB parameters into VFO B in 5 consecutive 
memory channels.  Those 5 are "ganged together" with an "*" in the name, 
IIRC.


When I rotate the Big Knob, I expected the VFO's to rotate through the 
channels [end-around].  VFO A does, but VFO B does not follow, it 
remains on whatever channel I originally selected.


The sequence M>V, Select memory, M>V sets both VFO's to the parameters 
stored in that memory, as one would expect.  Selecting a new memory with 
the BK should load the parameters for that memory into both VFO's, or so 
it would seem.  It does for VFO A. It doesn't for VFO B.  My question 
was, "Is this a bug or intentional behavior?"  If it's intentional, I'd 
be curious what the use case is for that behavior.  I'm also aware this 
is a K3 question and likely to get lost in all the K4 commotion.


73,
Fred ["Skip"] K6DGW
Sparks NV DM09dn
Washoe County

On 6/3/2019 4:13 PM, K8TE wrote:

While you can scan or dial through VFO A, once you "land" on a particular
channel, the VFO B frequency and mode associated with that channel is
available by using the VFO A/B button.

I originally loaded the 60m CW frequencies in VFO A for my 60m channels
since I'm more likely to use them working SOTA activators.  However, I
usually scan the SSB channels.  Thus, I swapped between VFO A and B so I can
scan USB channels and select the appropriate VFO B CW channels when needed.
This comes in handy when someone suggests 60m for USB or when I see a SOTA
dude spotted on 60m CW.

73, Bill, K8TE, waiting "patiently" to return home and start using HF again!
BCNU at Ham-Com.



__
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to arch...@mail-archive.com 

Re: [Elecraft] 60 meters

2019-06-03 Thread K8TE
While you can scan or dial through VFO A, once you "land" on a particular
channel, the VFO B frequency and mode associated with that channel is
available by using the VFO A/B button.

I originally loaded the 60m CW frequencies in VFO A for my 60m channels
since I'm more likely to use them working SOTA activators.  However, I
usually scan the SSB channels.  Thus, I swapped between VFO A and B so I can
scan USB channels and select the appropriate VFO B CW channels when needed. 
This comes in handy when someone suggests 60m for USB or when I see a SOTA
dude spotted on 60m CW.

73, Bill, K8TE, waiting "patiently" to return home and start using HF again! 
BCNU at Ham-Com.



--
Sent from: http://elecraft.365791.n2.nabble.com/
__
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html


Re: [Elecraft] 60 meters

2019-06-03 Thread Fred Jensen

On 6/3/2019 12:14 PM, Rick WA6NHC wrote:

I'm not sure what your question is, can you restate it?

I'll try although it wasn't a question, it was an unexpected observation.


Each of the memories can be programmed so that both VFO (and mode for 
each if I recall, been some years) are set, in this case one VFO for 
USB/FT8 and the other for CW, with their specific frequencies as 
required.
Yes, and very thoughtful of Wayne.  That's exactly what I did.  In 
addition, I set the "channel hopping" mode ["*" in the name IIRC] for 
the 5 of them so that once recalled, the Big Knob jumps through each of 
them meaning you don't have to recall the next one, it's automagic ... 
for VFO A at least.


Then you would simply use the A/B for the mode choice of the moment 
and tap mode if you want DATA A from USB for example.
El Correcto ... at least that was my plan. Unfortunately, when I channel 
hop to the next one with the BK, VFO A hops very proficiently, however 
it doesn't drag VFO B along to the next channel with it.


To change channels, recall another memory slot; correct the mode if 
needed.
That's what my slick little scheme was supposed to avoid -- having to do 
a recall [tap M>V, select, tap M>V]


I went a slightly different route, using ten memories, I have each 
channel programmed for a specific mode, "1 CW", "1 USB" etc.  then if 
data, remember that the USB channel is used, but switch to DATA mode.
That works too, and it's not like I'm going to run out of memory slots, 
and if all 10 were placed into a channel hopping block, you can move 
from one to the next with the BK only.


It would be FAR simpler in the US if the BAND was permitted (as other 
countries allow), not limited to specific frequencies and that would 
also allow simpler contact with other that have different channel 
requirements (yeah, it's become a DX band, duh).
Well, 60 m is what it is worldwide and being one of the regulators is 
way above my pay grade.  A great number of countries have allocated the 
WRC-15 decision of 5351.500 - 5366.500 KHz [15 KHz] which overlaps the 
US "Channel 3" at 5358.500.  At WRC-12, 5250 - 5450 was originally proposed.


73,
Fred ["Skip"] K6DGW
Sparks NV DM09dn
Washoe County




__
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

Re: [Elecraft] 60 meters

2019-06-03 Thread Rick WA6NHC

I'm not sure what your question is, can you restate it?

Each of the memories can be programmed so that both VFO (and mode for 
each if I recall, been some years) are set, in this case one VFO for 
USB/FT8 and the other for CW, with their specific frequencies as required.


Then you would simply use the A/B for the mode choice of the moment and 
tap mode if you want DATA A from USB for example.


To change channels, recall another memory slot; correct the mode if needed.

I went a slightly different route, using ten memories, I have each 
channel programmed for a specific mode, "1 CW", "1 USB" etc.  then if 
data, remember that the USB channel is used, but switch to DATA mode.


It would be FAR simpler in the US if the BAND was permitted (as other 
countries allow), not limited to specific frequencies and that would 
also allow simpler contact with other that have different channel 
requirements (yeah, it's become a DX band, duh).


Rick nhc

PS The dual VFO programming in one memory simplifies programming of say, 
6M repeaters where the offset is not a constant (i.e. -500 kHz in CA but 
-1700 kHz in Idaho).



On 6/3/2019 11:50 AM, Fred Jensen wrote:
I loaded the 5 US 60 m "channels" into my K3 frequency memories, with 
VFO A set to CW parameters, VFO B to USB parameters for each one, and 
set to step through the 5 of them when recalled from memory.  It works 
great, just turn the Big Knob to step through the channels ... 
remember CB? ... with one wrinkle:  Moving the BK moves only VFO A, it 
doesn't take VFO B along with it.  The VFO B knob adjusts the 
frequency in whatever steps are set just like all other bands.  The 
result is that I can switch between CW and USB on the channel I 
originally recalled from memory using the A/B switch, but can't if I 
move VFO A.


Usually, when I discover an unexpected operation like this, there's a 
very good reason why it is so that I never thought of. Does anyone 
know the reason for this one?


73,
Fred ["Skip"] K6DGW
Sparks NV DM09dn
Washoe County
__
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

__
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

Re: [Elecraft] 60 meters and the K3S

2017-09-29 Thread Fred Jensen
Bill, while the original post was about the 60 m channels, the K3 Memory 
Editor works for all frequencies for all bands.  As you note, split 
operation makes essentially no sense on the 5 60 m channels in the US.  
It does make sense elsewhere.


73,

Fred ["Skip"] K6DGW
Sparks NV DM09dn
Washoe County

On 9/29/2017 5:29 PM, Nr4c wrote:

Split on 60 meters takes two channels and is a waste of BW.

Remember there is no "up 1k" on 60 meters. TX is only authorized on the 
channels.

Sent from my iPhone
...nr4c. bill



__
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to arch...@mail-archive.com

Re: [Elecraft] 60 meters and the K3S

2017-09-29 Thread Bob McGraw K4TAX


Comments on the R & O - Effective  EST on March 5, 2012.

Amateurs are permitted to operate on five specific frequency channels, 
each having an effective bandwidth of 2.8 kHz.


*Table 1:*
Channel 1: 5330.5 kHz
Channel 2: 5346.5 kHz
Channel 3: 5357.0 kHz
Channel 4: 5371.5 kHz
Channel 5: 5403.5 kHz

These frequencies are available for use by stations having a control 
operator holding a General, Advanced or Amateur Extra class license. It 
is important to note that the frequencies shown above _are suppressed 
carrier frequencies_ – the frequencies that appear in your transceiver’s 
tuning display when your transceiver is in the USB mode.


Amateurs may transmit with an effective radiated power of 100 W or less, 
relative to a half-wave dipole. If you’re using a commercial directional 
antenna, FCC Rules require you to keep a copy of the manufacturer’s gain 
specifications in your station records. If you built the directional 
antenna yourself, you must calculate the gain and keep the results in 
your station records.


When using a directional antenna, you must take your antenna gain into 
account when setting your RF output power. For example, if your antenna 
offers 3 dB gain, your maximum legal output power on 60 meters should be 
no more than 50 W (50 W plus 3 dB gain equals 100 W Effective Radiated 
Power).


*Upper Sideband Operation*
Upper Sideband operation on 60 meters is simple. Just tune your 
transceiver to one of the channel frequencies shown in Table 1 and 
operate, being careful you do not over modulate and create “splatter” 
that would fall outside the 2.8 kHz channel bandwidths. If your 
transceiver allows you to adjust your maximum SSB transmit bandwidth, 
setting it to 2.4 kHz should keep you well within the legal limit.


*CW Operation*
CW operation must take place at the _center of your chosen channel_. 
This means that your transmitting frequency must be 1.5 kHz above the 
suppressed carrier frequency as specified in the Report and Order (see 
Table 1). Operating at strict channel-center frequencies may come as a 
disappointment to many, but cooperating with the NTIA is key to expanded 
privileges in the future.

The channel center frequencies are:

Channel 1: 5332.0 kHz
Channel 2: 5348.0 kHz
Channel 3: 5358.5 kHz
Channel 4: 5373.0 kHz
Channel 5: 5405.0 kHz

Consult your transceiver manual. Some transceivers transmit CW at the 
exact frequencies shown on their displays, but others offset the actual 
transmission frequency by a certain amount (for example, 600 Hz). If 
your manual is not clear on this point, contact the manufacturer. If you
have access to a frequency counter, this is an excellent tool for 
ensuring that your CW signal is on the channel center frequency.


*Digital Operation*
Our expanded privileges on 60 meters were the result of collaboration 
between the FCC and the NTIA – the National Telecommunications and 
Information Administration, the agency that manages and coordinates 
telecommunications activities among US government departments, the 
primary users of the band. The NTIA expressed concern about possible 
interference and requested that amateurs limit digital operating to 
PSK31 and PACTOR III only.


It is certainly possible to interpret the FCC Report and Order somewhat 
broadly as it concerns digital operating on the band, but be careful not 
to read too much into the text.Therefore, as a practical matter it 
appears that any J2D data emission is to be permitted up to a bandwidth 
of 2.8 kHz, provided that care is exercised to limit the length of 
transmissions


With an eye to the potential for expanded 60 meter privileges in the 
future, the ARRL believes it is critical to cooperate fully with the 
NTIA. Therefore, the ARRL asks all amateurs to *_restrict 60-meter 
digital operations to PSK31 or PACTOR III._**_

_*
With PSK31 you must operate on the following channel center frequencies:
Channel 1: 5332.0 kHz
Channel 2: 5348.0 kHz
Channel 3: 5358.5 kHz
Channel 4: 5373.0 kHz
Channel 5: 5405.0 kHz

The easiest way to achieve this is to place your transceiver in the USB 
mode and tune to one of the suppressed carrier channel frequencies shown 
in Table 1.


With your PSK31 software display configured to indicate audio 
frequencies, click your mouse cursor at the 1500 Hz mark (see below). 
With your radio in the USB mode, this marker indicates the center of the 
channel and it is the frequency on which you should be transmitting.


PACTOR III operation on 60 meters is straightforward. With your 
transceiver in the USB mode, tune to one of the suppressed carrier 
channel frequencies shown in Table 1. Note that only live 
keyboard-to-keyboard operation of PACTOR III is allowed. Unattended 
automatic operation is not permitted.



73
Bob, K4TAX


__
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: 

Re: [Elecraft] 60 meters and the K3S

2017-09-29 Thread Nr4c
Split on 60 meters takes two channels and is a waste of BW. 

Remember there is no "up 1k" on 60 meters. TX is only authorized on the 
channels. 

Sent from my iPhone
...nr4c. bill


> On Sep 29, 2017, at 7:50 PM, Fred Jensen  wrote:
> 
> I used the K3 Memory Editor and set up the 5 "channels" for both CW and SSB.  
> Worked really slick and I could give them meaningful names that appear in VFO 
> B.  It's on the Elecraft site, "K3/K3s, KX3, and K2 Control Software."  The 
> memories contain both VFO A and B data, so you can set up one for SSB and one 
> for CW or maybe PSK31.  You can even do split, CTCSS tones, etc.  There are a 
> half-million [or so] memories so you're not likely to run out.
> 
> Note: Part 97 uses the term "RTTY" for an authorized emission on 60 meters, 
> but the emission designator sure looks like PSK31, not 170 Hz FSK.
> 
> 73,
> 
> Fred ["Skip"] K6DGW
> Sparks NV DM09dn
> Washoe County
> 
>> On 9/29/2017 1:20 PM, w...@comcast.net wrote:
>> Some time back there was some great information on setting up the K3(s) to
>> operate on 60 meters.  It involved saving the frequencies in memories and
>> recalling them.  I had my K3 set up that way but with the K3S changeover,
>> that's gone and I can't seem to find that information on the web (perhaps
>> I'm not searching on the right terms).
>> 
>>  
>> Does anyone remember that and can point me in the right direction?
>> 
> 
> __
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:Elecraft@mailman.qth.net
> 
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
> Message delivered to n...@widomaker.com

__
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to arch...@mail-archive.com


Re: [Elecraft] 60 meters and the K3S

2017-09-29 Thread Bob McGraw K4TAX
I use memories 61, 62, 63, 64 & 65 for 60 meter frequencies and mode.  
You can choose memories of your choice.  By doing this then pressing V-M 
one can "tune" through the memories.  Finding one you wish to use,then 
press V-M again and the radio goes there.


Those frequencies are are as follows and all are USB mode. Maximum power 
is 100 watts.


5330.5,    5346.5,    5357.0,    5371.5,    5403.5

73

Bob, K4TAX

K3S s/n 10163


On 9/29/2017 3:20 PM, w...@comcast.net wrote:

Some time back there was some great information on setting up the K3(s) to
operate on 60 meters.  It involved saving the frequencies in memories and
recalling them.  I had my K3 set up that way but with the K3S changeover,
that's gone and I can't seem to find that information on the web (perhaps
I'm not searching on the right terms).

  


Does anyone remember that and can point me in the right direction?

  


Thanks,

  

  


Pete, W1RM

w...@comcast.net

  


__
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to rmcg...@blomand.net




__
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to arch...@mail-archive.com

Re: [Elecraft] 60 meters and the K3S

2017-09-29 Thread Fred Jensen
I used the K3 Memory Editor and set up the 5 "channels" for both CW and 
SSB.  Worked really slick and I could give them meaningful names that 
appear in VFO B.  It's on the Elecraft site, "K3/K3s, KX3, and K2 
Control Software."  The memories contain both VFO A and B data, so you 
can set up one for SSB and one for CW or maybe PSK31.  You can even do 
split, CTCSS tones, etc.  There are a half-million [or so] memories so 
you're not likely to run out.


Note: Part 97 uses the term "RTTY" for an authorized emission on 60 
meters, but the emission designator sure looks like PSK31, not 170 Hz FSK.


73,

Fred ["Skip"] K6DGW
Sparks NV DM09dn
Washoe County

On 9/29/2017 1:20 PM, w...@comcast.net wrote:

Some time back there was some great information on setting up the K3(s) to
operate on 60 meters.  It involved saving the frequencies in memories and
recalling them.  I had my K3 set up that way but with the K3S changeover,
that's gone and I can't seem to find that information on the web (perhaps
I'm not searching on the right terms).

  


Does anyone remember that and can point me in the right direction?



__
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to arch...@mail-archive.com

Re: [Elecraft] 60 meters and the K3S

2017-09-29 Thread Nr4c
You might try the manual section on using memories. A 60 meter frequency works 
like any other. 

Also note that a "*" in the right place allows that group of memories to be 
selected with VFO knob. 

Sent from my iPhone
...nr4c. bill


> On Sep 29, 2017, at 4:20 PM,   wrote:
> 
> Some time back there was some great information on setting up the K3(s) to
> operate on 60 meters.  It involved saving the frequencies in memories and
> recalling them.  I had my K3 set up that way but with the K3S changeover,
> that's gone and I can't seem to find that information on the web (perhaps
> I'm not searching on the right terms).
> 
> 
> 
> Does anyone remember that and can point me in the right direction?
> 
> 
> 
> Thanks,
> 
> 
> 
> 
> 
> Pete, W1RM
> 
> w...@comcast.net
> 
> 
> 
> __
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:Elecraft@mailman.qth.net
> 
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
> Message delivered to n...@widomaker.com

__
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to arch...@mail-archive.com


Re: [Elecraft] 60 meters and the K3S

2017-09-29 Thread Don Wilhelm

Pete,

Check page 42 of the K3S manual.  What you are likely seeking is 
"Channel Hopping".  BTW, the same thing works for other than 60 meters 
if you have a need - like checking the bands for DX Beacons.


73,
Don W3FPR

On 9/29/2017 4:20 PM, w...@comcast.net wrote:

Some time back there was some great information on setting up the K3(s) to
operate on 60 meters.  It involved saving the frequencies in memories and
recalling them.  I had my K3 set up that way but with the K3S changeover,
that's gone and I can't seem to find that information on the web (perhaps
I'm not searching on the right terms).



Does anyone remember that and can point me in the right direction?

__
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to arch...@mail-archive.com


Re: [Elecraft] 60 Meters for dummies - K3 Version

2011-11-21 Thread Richard Ferch
Mike,

A couple of corrections:

1. In CW, the K3 normally uses LSB. CW-REV is USB. This makes no 
difference to the recommendation (in CW or CW-REV, just tune the K3's 
dial to the channel center).

2. In RTTY using either FSK D or AFSK A, the K3's dial displays the RTTY 
Mark frequency (the higher of the two transmitted frequencies). 
Therefore, for an RTTY signal to be exactly centered in the channel, the 
K3's dial should be set 85 Hz above the channel center frequency in 
these two modes. Just as for CW sidetone, the choice of audio tone pairs 
is immaterial in either FSK D or AFSK A, provided the software (or TU) 
and the radio are both set to use the same tones.

Using DATA A, on the other hand, the dial displays the suppressed 
carrier frequency (DATA A is USB). One way to send AFSK RTTY on the 
channel center using DATA A would be to set the K3's dial to the channel 
carrier frequency and the audio RTTY tones to 1415/1585 Hz (Reverse 
for MMTTY users, since MMTTY assumes the radio is in LSB). This is not 
one of the standard tone pairs that MMTTY provides, so MMTTY users would 
have to enter a custom Mark frequency of 1415 Hz.

Alternatively, if they wanted to use a standard audio tone pair, users 
would have to work out the correct dial setting for each channel 
depending on which tone pair and sideband (DATA A = USB, DATA A-REV = 
LSB) they preferred to use.

73,
Rich VE3KI
__
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html


Re: [Elecraft] 60 Meters for dummies - K3 Version

2011-11-20 Thread John Oppenheimer
 Do I understand where the CW transmission actually is (600 Hz above dial 
 frequency)?  Please explain.

If XIT and SPLIT are off, the K3's CW transmit frequency is the
displayed VFO frequency.

The users desired CW pitch frequency is set with the K3's PITCH setting.
If the received CW pitch frequency matches the PITCH setting, then the
VFO will indicate the other stations transmitted frequency.

NOTE: Switching between the K3's CW and CW-REV (ALT button) will result
with no pitch change if the receiver VFO frequency display is set to the
other station's transmit frequency.

Test: tune to WWV at 10.000.000 MHz, CW mode, 50Hz BW. If the K3 is
aligned, switching between CW and CW-REV will result with no pitch
frequency change. (My K3 requires a setting of 10.000.002 to achieve the
no pitch change condition, indicating that my K3's frequency alignment
is 1Hz off.)

To comply with the 60M FCC statement For CW emissions (emission
designator 150HA1A), the carrier frequency is set to the center
frequency. with a K3, set SPLIT and XIT off and set the VFO to 5332,
5348, 5358, 5373, or 5405 kHz. Assuming the other station is complying
with the same rule, on the K3 with RIT off, the received pitch frequency
will be the K3's PITCH setting.

The received pitch frequency is fully the operator's discretion by
adjusting the receiver BFO frequency offset setting. For the K3, with
the PITCH setting.

John KN5L
__
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html


Re: [Elecraft] 60 Meters for dummies - K3 Version

2011-11-20 Thread Mike Morrow
Jim wrote:

 Do I understand where the CW transmission actually is (600 Hz above dial 
 frequency)?  Please explain.

No.  As Don pointed out, most modern transceivers always show transmitter
carrier frequency in the display.  On USB and LSB, that will also be
the receiver carrier frequency.  On CW, however, if the receiver functions
in USB mode the receiver carrier frequency will be shifted BELOW the
transmitter carrier frequency (always shown in the display) by the offset
(pitch) being used.  The receiver carrier frequency is *never* actually
shown in the display while in CW mode.  (I don't know if the K3 allows
the option of using the receiver in LSB mode for CW mode.  If so, then
this whole discussion would need changes to take that into account
if the LSB-CW option is being executed.)

For examples in the discussion below, I'll use the new 60m channel
of 5358.5 kHz (center), or 5357.0 (carrier), as defined in section
97.303(h).

 USB - set VFO to the lower edge of the channel (1500 Hz below center 
 frequency). Giving audio emissions from 300 to 3000 Hz above that.

Correct.  Put 5357.0 in the display.  That's all that's needed in USB mode.

Do the same for Data and RTTY transmissions (including PSK31), using USB mode.

 K3 and CW - on my waterfall (in HRD) the trace made by my CW transmission is 
 at the (+)600 marker above the bottom of the waterfall.  This is where I 
 conclude the transmission actually is, resulting in the 600 Hz tone above 
 where I am actually tuned.

All true.  But on CW, your receiver's carrier frequency is NOT the frequency
shown in the K3 display.  On CW only, the receiver carrier frequency is BELOW
the transmitter carrier (and displayed) frequency by the amount of your pitch
offset...0.6 kHz for you.  If the K3 shows 5358.5 kHz on CW, your receiver
carrier frequency is 5757.9 kHz, USB.

 Now, do they want this actual +600 Hz transmission in the center of the
 channel?

Yes...but leave out that +600 Hz part.  More precisely, your transmitted CW
signal **must** always be ON the channel center frequency.  Set the dial for
5358.5 kHz in CW mode.

 Or do they want us to tune to the center of the band and transmit 600 Hz
 above that?

Definitely not!  To do so would place you 0.6 kHz too high (5359.1 kHz) above
the correct frequency (5358.5 kHz).  Plus, since the K3 ALWAYS shows transmit
carrier frequency, you must have the display showing 5359.1 in order to
transmit 600 Hz above the channel center frequency.  In that case, your
receiver's carrier frequency is 5358.5 kHz, but that's not what you want.

(By band, you mean channel.)

 If they are tuned to the lower edge of the band...

 ...do they want to hear a 2100 Hz tone (with us tuned to the center frequency)

No.  Dump that whole line.

 ...or do they want to hear a 1500 Hz tone...

If they had a receiver in USB mode tuned to the channel's *carrier*
frequency of 5357.0 kHz (defined for phone, data, and RTTY modes), then your
CW signal on the correct frequency of 5358.5 kHz would produce a 1500 Hz
tone in their receiver.

 (with us tuned 600 Hz below center frequency)?

Establishing your CW transmission on the channel center frequency (5358.5 kHz)
means that will be what is shown in the K3 display.  But on CW, the carrier
frequency of your receiver will NOT be what's in the display, but rather
what's in the display minus your CW offset.  So, your receiver's actual USB
carrier frequency will be 5358.5 kHz - 0.6 kHz = 5357.9 kHz, or 0.9 kHz ABOVE
the channel's specified carrier frequency of 5357.0 kHz.  But there's no real
significance to that.  The rules don't care where your receiver carrier
frequency is...only you do, for the desired sidetone pitch.  Someone who
liked an 800 Hz pitch would have his receiver carrier frequency set at
5357.7 kHz.

Just make sure on CW that the channel center frequency is shown in the display.
That always shows transmitter carrier frequency.  Everything else will turn
out all right. 

 On PSK31 - Do they want us to tune to the bottom of the channel and then 
 transmit only a single signal directly on the 1500 Hz marker?  There would 
 be room for many others as well without exceeding the bandwidth allocated to 
 us.

No.  The new section 97.303(h) says in part ...control operators of stations
transmitting phone, data, and RTTY emissions (emission designators 2K80J3E,
2K80J2D, and 60H0J2B, respectively) may set the carrier frequency 1.5 kHz
below the center frequency as specified in the table...

You must use USB to transmit your PSK31 (60H0J2B) signal, and you may set 
the USB transmitter carrier frequency 1.5 kHz below the channel center
frequency.  The channelized mode of operation means that most hams will use
fixed frequencies stored in memory rather than a VFO, so putting any phone,
RTTY, or data transmission on that suggested carrier frequency would seem
prudent, even if it can be argued that the rule allows the USB carrier
frequency to be below the channel center frequency by less than