Date   

Re: [Elecraft_K3] Re: Remote On/Off Switch

Art - VE3UTT / W1AJT
 

I have been using Sonoff switches for about 7 months now.  They work great in a local environment.  The application they recommend eWeLink works great for all local work.  It does not have a remote webserver capability.   Of course there are many ways to achieve this.  For the best Sonoff prices, I bought mine here:

Good Luck,
Art - VE3UTT / W1AJT


Re: [Elecraft_K3] Re: Remote On/Off Switch

David Cutter
 


I've been looking at this device and I'm a little put off by the adverse comments from some buyers.  I would need an expert by my side, so, if this works for you, I'd like to know how easy it was to work with.
 
How do you flash with other software?  That might be the key.
 
73
 
David
G3UNA
 
 

----- Original Message -----
Sent: Thursday, March 08, 2018 4:41 PM
Subject: [Elecraft_K3] Re: Remote On/Off Switch

 

Yep, there are many low cost WIFI switch solutions to chose from. 


I will be experimenting with this switch soon.  Flashed with third party firmware called Tasmota.



Re: Remote On/Off Switch

N3HEE
 

Yep, there are many low cost WIFI switch solutions to chose from. 

I will be experimenting with this switch soon.  Flashed with third party firmware called Tasmota.



Re: Remote On/Off Switch

Michael Foerster
 

You might also consider something like this:


I have one on order, but obviously I haven’t tried it yet.

Mike, W0IH


KAP500 Tuner for sale

rich matos
 

One year old  KAP500 ,I bought from Elecraft on  3/9/17 is flawless in
all ways

cosmetics and operation   serial no 2271       Sell for $525.00 .

plus shipping .   w9cin @att.net


Re: [Elecraft_K3] Serial Port Sharing

Robert C. Crawford
 

RR

THANKS!

Bob
K8VFV since 1960
Charter Member Milford Amateur Radio Club & MiVUS

Email - K8VFV at ARRL dot NET
Web Site - http://www.k8vfv.com
Outgoing email checked by MSE
In GOD we trust

On 05 Mar 18 3:46 PM, Tom-KQ5S kq5stom@... [Elecraft_K3] wrote:
Is this what you were looking for?
-----Original Message-----
From:Elecraft_K3@... <mailto:Elecraft_K3@...>[mailto:Elecraft_K3@... <mailto:Elecraft_K3@...>]
Sent: Friday, March 02, 2018 11:38 AM
To:ve3iay@... <mailto:ve3iay@...>[Elecraft_K3]
Subject: Re: [Elecraft_K3] Re: K3 Utility, P3, DX Labs Commander, K3s USB
Sounds like you need to add a virtual serial port likeVSPEor Com-0-Com. As stated by Rich, you can NOT use the same serial port more then once. I use the 64 bit version ofVSPEand the Splitter option. This means I can use the same com# with 4 different programs. Just a thought.... I do like DxLab program, but many years ago decided to go with Win4K3Suite. Never looked back. It supports K3, K3S, KX2, KX3, KPA500, KAT500, KXPA100 and KXAT100. Could't ask for more... Good luck

There are two kinds of serial port splitters: dumb and smart.
Dumb splitters likeVSPEand Com-0-com know nothing about transceiver control protocols; they
just mindlessly route bytes to and from the client applications. If two client applications happen to be sending multi-byte commands simultaneously, a dumb splitter will send the transceiver an interdigitated mess. Nonetheless, dumb splitters are useful when all but one of the clients are simply monitoring the commands being sent to the transceiver and/or its responses (like a tuner or amplifier might do), or when you ensure than only one client application is actively sending commands at any one time (eliminating the need to manually switch COM ports when switching transceiver control applications).

Smart splitters know that they are mediating access to a transceiver that uses a specific CAT control protocol. They are typically implemented around an emulator of the transceiver being controlled. Each client gets conflict-free access to the emulator, and the emulator is kept up to date via direct access to the radio. LP-Bridge includes a smart splitter. Win4K3Suite also includes a smart splitter.
By the way, Win4K3Suite interoperates with DXLab, providing the Win4K3Suite user with capabilities like logging, DX spot analytics, award tracking and management, digital mode operation, QSL route discovery, and propagation prediction and analysis.
73,
Dave, AA6YQ
-----------------
73,
Tom - KQ5S
On Mon, Mar 5, 2018 at 1:26 PM, Robert Crawford k8vfv@... <mailto:k8vfv@...> [Elecraft_K3] <Elecraft_K3@... <mailto:Elecraft_K3@...>> wrote:
__
A few days ago a note was posted about two different types of Serial
Port sharing programs.
One group included VPSE and LP. The group had Com-O-Com in it.
If the author of that note or if someone saved copy, would you send it
to me. My DELETE finger was faster than my SAVE finger....
THANKS,
Bob
K8VFV since 1960
Charter Member Milford Amateur Radio Club & MiVUS
Email - K8VFV at ARRL dot NET
Web Site - http://www.k8vfv.com
Outgoing email checked by MSE
In GOD we trust


Re: [Elecraft_K3] Serial Port Sharing

Tom-KQ5S <kq5stom@...>
 

Is this what you were looking for?

-----Original Message-----
From: Elecraft_K3@... [mailto:Elecraft_K3@yahoogroups.com] 
Sent: Friday, March 02, 2018 11:38 AM
To: ve3iay@... [Elecraft_K3]
Subject: Re: [Elecraft_K3] Re: K3 Utility, P3, DX Labs Commander, K3s USB

Sounds like you need to add a virtual serial port like VSPE or Com-0-Com. As stated by Rich, you can NOT use the same serial port more then once. I use the 64 bit version of VSPE and the Splitter option. This means I can use the same com# with 4 different programs. Just a thought.... I do like DxLab program, but many years ago decided to go with Win4K3Suite. Never looked back. It supports K3, K3S, KX2, KX3, KPA500, KAT500, KXPA100 and KXAT100. Could't ask for more... Good luck

>>>There are two kinds of serial port splitters: dumb and smart.

>>>Dumb splitters like VSPE and Com-0-com know nothing about transceiver control protocols; they just mindlessly route bytes to and from the client applications. If two client applications happen to be sending multi-byte commands simultaneously, a dumb splitter will send the transceiver an interdigitated mess. Nonetheless, dumb splitters are useful when all but one of the clients are simply monitoring the commands being sent to the transceiver and/or its responses (like a tuner or amplifier might do), or when you ensure than only one client application is actively sending commands at any one time (eliminating the need to manually switch COM ports when switching transceiver control applications).

>>>Smart splitters know that they are mediating access to a transceiver that uses a specific CAT control protocol. They are typically implemented around an emulator of the transceiver being controlled. Each client gets conflict-free access to the emulator, and the emulator is kept up to date via direct access to the radio. LP-Bridge includes a smart splitter. Win4K3Suite also includes a smart splitter.

>>>By the way, Win4K3Suite interoperates with DXLab, providing the Win4K3Suite user with capabilities like logging, DX spot analytics, award tracking and management, digital mode operation, QSL route discovery, and propagation prediction and analysis.

73,

Dave, AA6YQ

-----------------
73,
Tom - KQ5S

On Mon, Mar 5, 2018 at 1:26 PM, Robert Crawford k8vfv@... [Elecraft_K3] <Elecraft_K3@...> wrote:
 

A few days ago a note was posted about two different types of Serial
Port sharing programs.

One group included VPSE and LP. The group had Com-O-Com in it.

If the author of that note or if someone saved copy, would you send it
to me. My DELETE finger was faster than my SAVE finger....

THANKS,
Bob
K8VFV since 1960
Charter Member Milford Amateur Radio Club & MiVUS

Email - K8VFV at ARRL dot NET
Web Site - http://www.k8vfv.com
Outgoing email checked by MSE
In GOD we trust



Re: [Elecraft_K3] Serial Port Sharing

Dave AA6YQ
 

Reposting as requested...

----Original Message-----
From: Dave AA6YQ [mailto:@AA6YQ]
Sent: Friday, March 02, 2018 12:27 PM
To: 'Elecraft_K3@...'
Subject: RE: [Elecraft_K3] Re: K3 Utility, P3, DX Labs Commander, K3s USB

AA6YQ comments below
-----Original Message-----
From: Elecraft_K3@... [mailto:Elecraft_K3@...]
Sent: Friday, March 02, 2018 11:38 AM
To: ve3iay@... [Elecraft_K3]
Subject: Re: [Elecraft_K3] Re: K3 Utility, P3, DX Labs Commander, K3s USB

Sounds like you need to add a virtual serial port like VSPE or Com-0-Com. As stated by Rich, you can NOT use the same serial port more then once. I use the 64 bit version of VSPE and the Splitter option. This means I can use the same com# with 4 different programs. Just a thought.... I do like DxLab program, but many years ago decided to go with Win4K3Suite. Never looked back. It supports K3, K3S, KX2, KX3, KPA500, KAT500, KXPA100 and KXAT100. Could't ask for more... Good luck

There are two kinds of serial port splitters: dumb and smart.
Dumb splitters like VSPE and Com-0-com know nothing about transceiver control protocols; they just mindlessly route bytes to and from the client applications. If two client applications happen to be sending multi-byte commands simultaneously, a dumb splitter will send the transceiver an interdigitated mess. Nonetheless, dumb splitters are useful when all but one of the clients are simply monitoring the commands being sent to the transceiver and/or its responses (like a tuner or amplifier might do), or when you ensure than only one client application is actively sending commands at any one time (eliminating the need to manually switch COM ports when switching transceiver control applications).
Smart splitters know that they are mediating access to a transceiver that uses a specific CAT control protocol. They are typically implemented around an emulator of the transceiver being controlled. Each client gets conflict-free access to the emulator, and the emulator is kept up to date via direct access to the radio. LP-Bridge includes a smart splitter. Win4K3Suite also includes a smart splitter.
By the way, Win4K3Suite interoperates with DXLab, providing the Win4K3Suite user with capabilities like logging, DX spot analytics, award tracking and management, digital mode operation, QSL route discovery, and propagation prediction and analysis.
73,

Dave, AA6YQ


-----Original Message-----
From: Elecraft_K3@... [mailto:Elecraft_K3@...]
Sent: Monday, March 05, 2018 2:27 PM
To: Elecraft_K3@...
Subject: [Elecraft_K3] Serial Port Sharing



A few days ago a note was posted about two different types of Serial Port sharing programs.

One group included VPSE and LP. The group had Com-O-Com in it.

If the author of that note or if someone saved copy, would you send it to me. My DELETE finger was faster than my SAVE finger....

THANKS,
Bob
K8VFV since 1960
Charter Member Milford Amateur Radio Club & MiVUS


Serial Port Sharing

Robert C. Crawford
 

A few days ago a note was posted about two different types of Serial Port sharing programs.

One group included VPSE and LP. The group had Com-O-Com in it.

If the author of that note or if someone saved copy, would you send it to me. My DELETE finger was faster than my SAVE finger....

THANKS,
Bob
K8VFV since 1960
Charter Member Milford Amateur Radio Club & MiVUS

Email - K8VFV at ARRL dot NET
Web Site - http://www.k8vfv.com
Outgoing email checked by MSE
In GOD we trust


Re: [Elecraft_K3] Extreme QRPp using the KX2, KX3, K3, or K3S

 

Hi David,

Wait... aren’t you guys supposed to be buried in snow (stolen from the Arctic), hunkered down over kerosene lamps, waiting for the power to come back on?

Back to your question:  yes, the K3 (or any of our rigs) work well as very clean signal generators. You can run key-down indefinitely with power output set to a low value. 

The source impedance will already be reasonably close to 50 ohms, but if you want it to be nearly dead-on, use a 10 ohm pad and increase the output level to compensate. 

73,
Wayne

On Mar 3, 2018, at 9:50 AM, 'David Cutter' d.cutter@... [Elecraft_K3] <Elecraft_K3@...> wrote:

 



Wayne
 
At these power levels is it practical to fit a resistive pad to emulate the 50ohm source impedance of a signal generator?  With the low phase noise, low harmonic output of a K3S I now have a fairly good signal source.  
 
There might be more box leakage than desirable but in my fantasy head I could operate it remotely in another room and use low leakage coax... now I'm beginning to dream.  But wait, I already have the radio, all I need is a pad in a box and some good coax and what else?
 
David
G3UNA
 
 
----- Original Message -----
Sent: Saturday, March 03, 2018 3:48 PM
Subject: [Elecraft_K3] Extreme QRPp using the KX2, KX3, K3, or K3S

 

Power output on the KX2, KX3, K3 and K3S can be set as low as 0.1 W directly using the PWR control.

However, you can actually set power output to much lower levels (< 1 milliwatt), with fine control, by turning off ALC in the menu and adjusting the drive level manually.

Here’s the recommended procedure for accurately setting power to levels below 0.1 watt:

1. Connect an external milliwatt meter between the transceiver and the antenna or dummy load. If you don’t have such a meter, you can alternatively connect a dummy load (such as the Elecraft DL2) then use an oscilloscope or an RF voltmeter. (The DL2 includes a rectifier so you can just use a DC voltmeter. The manual for the DL2 provides a translation from DC volts to power level.)

2. For most accurate results, bypass the ATU. This is done in the menu on the KX2 and KX3. The K3/K3S has an ATU switch function on the front panel for this purpose.

3. Start with PWR set to 0.1 W and verify that you hit about this level on the external meter. Hold TUNE to generate a continuous carrier. (This automatically switches to CW mode temporarily, even if you’re using a different mode.) Then exit TUNE by tapping XMIT.

Note: The 0.1-W level is not well-calibrated at the rig’s internal wattmeter, because this only forward-biases the rig’s SWR detector diodes by a small amount. Also, the SWR (shown on VFO A) will appear as “--“, because reflected power will be too low to accurately calculate it.

5. Go into the menu and turn off TX ALC. This is done using the TX GAIN menu entry on the KX2 (page 41 of the manual) or KX3 (page 49). Use the CONFIG:TX ALC menu entry on the K3 or K3S (approx. page 66).

Note: On all of the rigs, the TECH MD menu entry must be set to ON in order to see the TX GAIN or TX ALC menu entries. This is a precaution to make sure such menu settings are not changed unintentionally. On the KX2 and KX3, you also need to UNLOCK the ALC on/off feature as explained in the manual (MENU section).

6. With ALC turned OFF, the PWR control now directly controls the transmit drive level in fine increments. I just tested my lab KX2 and found I could set the power smoothly down to as low as about 1/2 milliwatt.

When you have ALC turned off, the PWR display (on VFO B) will include an asterisk (*) as a reminder. It will not show actual power level for reasons described above.. An external metering method will be needed to dial in the desired level.

Wayne
N6KR


Re: [Elecraft_K3] Extreme QRPp using the KX2, KX3, K3, or K3S

David Cutter
 


Wayne
 
At these power levels is it practical to fit a resistive pad to emulate the 50ohm source impedance of a signal generator?  With the low phase noise, low harmonic output of a K3S I now have a fairly good signal source.  
 
There might be more box leakage than desirable but in my fantasy head I could operate it remotely in another room and use low leakage coax... now I'm beginning to dream.  But wait, I already have the radio, all I need is a pad in a box and some good coax and what else?
 
David
G3UNA
 
 

----- Original Message -----
Sent: Saturday, March 03, 2018 3:48 PM
Subject: [Elecraft_K3] Extreme QRPp using the KX2, KX3, K3, or K3S

 

Power output on the KX2, KX3, K3 and K3S can be set as low as 0.1 W directly using the PWR control.

However, you can actually set power output to much lower levels (< 1 milliwatt), with fine control, by turning off ALC in the menu and adjusting the drive level manually.

Here’s the recommended procedure for accurately setting power to levels below 0.1 watt:

1. Connect an external milliwatt meter between the transceiver and the antenna or dummy load. If you don’t have such a meter, you can alternatively connect a dummy load (such as the Elecraft DL2) then use an oscilloscope or an RF voltmeter. (The DL2 includes a rectifier so you can just use a DC voltmeter. The manual for the DL2 provides a translation from DC volts to power level.)

2. For most accurate results, bypass the ATU. This is done in the menu on the KX2 and KX3. The K3/K3S has an ATU switch function on the front panel for this purpose.

3. Start with PWR set to 0.1 W and verify that you hit about this level on the external meter. Hold TUNE to generate a continuous carrier. (This automatically switches to CW mode temporarily, even if you’re using a different mode.) Then exit TUNE by tapping XMIT.

Note: The 0.1-W level is not well-calibrated at the rig’s internal wattmeter, because this only forward-biases the rig’s SWR detector diodes by a small amount. Also, the SWR (shown on VFO A) will appear as “--“, because reflected power will be too low to accurately calculate it.

5. Go into the menu and turn off TX ALC. This is done using the TX GAIN menu entry on the KX2 (page 41 of the manual) or KX3 (page 49). Use the CONFIG:TX ALC menu entry on the K3 or K3S (approx. page 66).

Note: On all of the rigs, the TECH MD menu entry must be set to ON in order to see the TX GAIN or TX ALC menu entries. This is a precaution to make sure such menu settings are not changed unintentionally. On the KX2 and KX3, you also need to UNLOCK the ALC on/off feature as explained in the manual (MENU section).

6. With ALC turned OFF, the PWR control now directly controls the transmit drive level in fine increments. I just tested my lab KX2 and found I could set the power smoothly down to as low as about 1/2 milliwatt.

When you have ALC turned off, the PWR display (on VFO B) will include an asterisk (*) as a reminder. It will not show actual power level for reasons described above. An external metering method will be needed to dial in the desired level.

Wayne
N6KR


Extreme QRPp using the KX2, KX3, K3, or K3S

 

Power output on the KX2, KX3, K3 and K3S can be set as low as 0.1 W directly using the PWR control.

However, you can actually set power output to much lower levels (< 1 milliwatt), with fine control, by turning off ALC in the menu and adjusting the drive level manually.

Here’s the recommended procedure for accurately setting power to levels below 0.1 watt:

1. Connect an external milliwatt meter between the transceiver and the antenna or dummy load. If you don’t have such a meter, you can alternatively connect a dummy load (such as the Elecraft DL2) then use an oscilloscope or an RF voltmeter. (The DL2 includes a rectifier so you can just use a DC voltmeter. The manual for the DL2 provides a translation from DC volts to power level.)

2. For most accurate results, bypass the ATU. This is done in the menu on the KX2 and KX3. The K3/K3S has an ATU switch function on the front panel for this purpose.

3. Start with PWR set to 0.1 W and verify that you hit about this level on the external meter. Hold TUNE to generate a continuous carrier. (This automatically switches to CW mode temporarily, even if you’re using a different mode.) Then exit TUNE by tapping XMIT.

Note: The 0.1-W level is not well-calibrated at the rig’s internal wattmeter, because this only forward-biases the rig’s SWR detector diodes by a small amount. Also, the SWR (shown on VFO A) will appear as “--“, because reflected power will be too low to accurately calculate it.

5. Go into the menu and turn off TX ALC. This is done using the TX GAIN menu entry on the KX2 (page 41 of the manual) or KX3 (page 49). Use the CONFIG:TX ALC menu entry on the K3 or K3S (approx. page 66).

Note: On all of the rigs, the TECH MD menu entry must be set to ON in order to see the TX GAIN or TX ALC menu entries. This is a precaution to make sure such menu settings are not changed unintentionally. On the KX2 and KX3, you also need to UNLOCK the ALC on/off feature as explained in the manual (MENU section).

6. With ALC turned OFF, the PWR control now directly controls the transmit drive level in fine increments. I just tested my lab KX2 and found I could set the power smoothly down to as low as about 1/2 milliwatt.

When you have ALC turned off, the PWR display (on VFO B) will include an asterisk (*) as a reminder. It will not show actual power level for reasons described above. An external metering method will be needed to dial in the desired level.

Wayne
N6KR


Re: [Elecraft_K3] Re: K3 Utility, P3, DX Labs Commander, K3s USB

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: Elecraft_K3@... [mailto:Elecraft_K3@...]
Sent: Friday, March 02, 2018 11:38 AM
To: ve3iay@... [Elecraft_K3]
Subject: Re: [Elecraft_K3] Re: K3 Utility, P3, DX Labs Commander, K3s USB

Sounds like you need to add a virtual serial port like VSPE or Com-0-Com. As stated by Rich, you can NOT use the same serial port more then once. I use the 64 bit version of VSPE and the Splitter option. This means I can use the same com# with 4 different programs. Just a thought.... I do like DxLab program, but many years ago decided to go with Win4K3Suite. Never looked back. It supports K3, K3S, KX2, KX3, KPA500, KAT500, KXPA100 and KXAT100. Could't ask for more... Good luck

There are two kinds of serial port splitters: dumb and smart.
Dumb splitters like VSPE and Com-0-com know nothing about transceiver control protocols; they just mindlessly route bytes to and from the client applications. If two client applications happen to be sending multi-byte commands simultaneously, a dumb splitter will send the transceiver an interdigitated mess. Nonetheless, dumb splitters are useful when all but one of the clients are simply monitoring the commands being sent to the transceiver and/or its responses (like a tuner or amplifier might do), or when you ensure than only one client application is actively sending commands at any one time (eliminating the need to manually switch COM ports when switching transceiver control applications).
Smart splitters know that they are mediating access to a transceiver that uses a specific CAT control protocol. They are typically implemented around an emulator of the transceiver being controlled. Each client gets conflict-free access to the emulator, and the emulator is kept up to date via direct access to the radio. LP-Bridge includes a smart splitter. Win4K3Suite also includes a smart splitter.
By the way, Win4K3Suite interoperates with DXLab, providing the Win4K3Suite user with capabilities like logging, DX spot analytics, award tracking and management, digital mode operation, QSL route discovery, and propagation prediction and analysis.
73,

Dave, AA6YQ


Re: [Elecraft_K3] Re: K3 Utility, P3, DX Labs Commander, K3s USB

harry latterman <harrylatterman@...>
 

Sounds like you need to add a virtual serial port like VSPE or Com-0-Com. As stated by Rich, you can NOT use the same serial port more then once. I use the 64 bit version of VSPE and the Splitter option. This means I can use the same com# with 4 different programs. Just a thought.... I do like DxLab program, but many years ago decided to go with Win4K3Suite.  Never looked back. It supports K3, K3S, KX2, KX3, KPA500, KAT500, KXPA100 and KXAT100.  Could't ask for more... Good luck

73 Harry  K7ZOV


On Friday, March 2, 2018, 6:27:42 AM MST, ve3iay@... [Elecraft_K3] wrote:


 

This sounds like you have an incorrect cable setup between the K3S/P3 and the computer. 


You have a USB cable between the computer and the K3S, and that has created port COM3. You also appear to have a USB-to-serial adapter between the computer and the P3, which has created port COM8. You also mentioned COM5, but that appears to be for something else (a rotor controller, a Winkeyer, a KPA500, or some other device) that doesn't enter into the picture.

Take a look at the P3 manual, revision H1, pages 5 and 6. If you want to use the K3S's USB connection for rig control (that's COM3), then to get the P3 to work correctly you must have a CBLP3Y connected between the K3S and both RS232 connectors on the P3, as on page 5. Your software (K3 Utility, Commander or any other rig control software) must use COM3. In the K3S, CONFIG:RS232 is set to USB with this cable connection. The COM8 cable is not connected to the P3 and doesn't do anything for you in this setup; you can use it to control some other device if you want.

If your cable setup is like the one on page 6 of the manual, then you must set the K3S's CONFIG:RS232 to 38400 and use COM8 for rig control. Your software must use COM8; COM3 is not used in this setup.

Whichever setup you settle upon (using COM3 with a CBLP3Y, or using COM8 with a connection between the computer and the P3), only one program can use the serial port at a time.

73,
Rich VE3KI



---In Elecraft_K3@..., wrote :

I have k3 utility, latest version 1.16.7.25.

Computer Device manager says I have com ports of 3,5,8.


K3s has line from USB port to my computer, it is COM 3.

  This is confimed when I unplug the line and COM3 disappears from the ports list.



I must set K3s RS232 to be 38400 for P3 to work properly.

It does not display correctly when K3s RS232 is set to USB.


DX Labs commander wants to use Port 8.

When I try to use the K3 Utility, it will not use 3,5,or 8 

unless I turn DXLABS commander off, then it uses port 8. 


If I SET K3s RS232 to be USB the utility also will work,

  using port 3.


So to use the Utility, I have to do a work around.  


Is this normal?


Ken K5WK




 


Re: [Elecraft_K3] K3 Utility, P3, DX Labs Commander, K3s USB

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: Elecraft_K3@... [mailto:Elecraft_K3@...]
Sent: Friday, March 02, 2018 12:01 AM
To: Elecraft_K3@...
Subject: [Elecraft_K3] K3 Utility, P3, DX Labs Commander, K3s USB

I have k3 utility, latest version 1.16.7.25.

Computer Device manager says I have com ports of 3,5,8.


K3s has line from USB port to my computer, it is COM 3.

This is confimed when I unplug the line and COM3 disappears from the ports list.


I must set K3s RS232 to be 38400 for P3 to work properly.

It does not display correctly when K3s RS232 is set to USB.


DX Labs commander wants to use Port 8.

To what device is COM8 connected?
73,

Dave, AA6YQ


Re: K3 Utility, P3, DX Labs Commander, K3s USB

ve3ki
 

This sounds like you have an incorrect cable setup between the K3S/P3 and the computer. 

You have a USB cable between the computer and the K3S, and that has created port COM3. You also appear to have a USB-to-serial adapter between the computer and the P3, which has created port COM8. You also mentioned COM5, but that appears to be for something else (a rotor controller, a Winkeyer, a KPA500, or some other device) that doesn't enter into the picture.

Take a look at the P3 manual, revision H1, pages 5 and 6. If you want to use the K3S's USB connection for rig control (that's COM3), then to get the P3 to work correctly you must have a CBLP3Y connected between the K3S and both RS232 connectors on the P3, as on page 5. Your software (K3 Utility, Commander or any other rig control software) must use COM3. In the K3S, CONFIG:RS232 is set to USB with this cable connection. The COM8 cable is not connected to the P3 and doesn't do anything for you in this setup; you can use it to control some other device if you want.

If your cable setup is like the one on page 6 of the manual, then you must set the K3S's CONFIG:RS232 to 38400 and use COM8 for rig control. Your software must use COM8; COM3 is not used in this setup.

Whichever setup you settle upon (using COM3 with a CBLP3Y, or using COM8 with a connection between the computer and the P3), only one program can use the serial port at a time.

73,
Rich VE3KI



---In Elecraft_K3@..., <kenw817821@...> wrote :

I have k3 utility, latest version 1.16.7.25.

Computer Device manager says I have com ports of 3,5,8.


K3s has line from USB port to my computer, it is COM 3.

  This is confimed when I unplug the line and COM3 disappears from the ports list.



I must set K3s RS232 to be 38400 for P3 to work properly.

It does not display correctly when K3s RS232 is set to USB.


DX Labs commander wants to use Port 8.

When I try to use the K3 Utility, it will not use 3,5,or 8 

unless I turn DXLABS commander off, then it uses port 8. 


If I SET K3s RS232 to be USB the utility also will work,

  using port 3.


So to use the Utility, I have to do a work around.  


Is this normal?


Ken K5WK




 


Re: [Elecraft_K3] K3 Utility, P3, DX Labs Commander, K3s USB

Joe Subich, W4TV
 

DX Labs commander wants to use Port 8.
When I try to use the K3 Utility, it will not use 3,5,or 8
unless I turn DXLABS commander off, then it uses port 8.
That's correct. Windows will not allow two programs to use
the same port at the same time. To use Commander, close the
K3 Utility; to use the K3 Utility, close Commander.

73,

... Joe, W4TV


On 3/2/2018 12:01 AM, kenw817821@... [Elecraft_K3] wrote:
I have k3 utility, latest version 1.16.7.25.
Computer Device manager says I have com ports of 3,5,8.
K3s has line from USB port to my computer, it is COM 3.
This is confimed when I unplug the line and COM3 disappears from the ports list.
I must set K3s RS232 to be 38400 for P3 to work properly.
It does not display correctly when K3s RS232 is set to USB.
DX Labs commander wants to use Port 8.
When I try to use the K3 Utility, it will not use 3,5,or 8
unless I turn DXLABS commander off, then it uses port 8.
If I SET K3s RS232 to be USB the utility also will work,
using port 3.
So to use the Utility, I have to do a work around.
Is this normal?
Ken K5WK


K3 Utility, P3, DX Labs Commander, K3s USB

kenw817821@...
 

I have k3 utility, latest version 1.16.7.25.

Computer Device manager says I have com ports of 3,5,8.


K3s has line from USB port to my computer, it is COM 3.

  This is confimed when I unplug the line and COM3 disappears from the ports list.



I must set K3s RS232 to be 38400 for P3 to work properly.

It does not display correctly when K3s RS232 is set to USB.


DX Labs commander wants to use Port 8.

When I try to use the K3 Utility, it will not use 3,5,or 8 

unless I turn DXLABS commander off, then it uses port 8. 


If I SET K3s RS232 to be USB the utility also will work,

  using port 3.


So to use the Utility, I have to do a work around.  


Is this normal?


Ken K5WK



Re: [Elecraft_K3] K3 - Strange ATU behavior

Bob McGraw - K4TAX
 

Loose and poor connections are the source of a many mysterious of issues. 

My thoughts on this: 

All jumpers and DC power leads should have crimped and soldered proper ring terminals.  

All PL-259 connectors will be snugged with 4" Channel Lock pliers.  Finger tight is never good enough.

Each piece of equipment is bonded to the station power supply ground {not negative} using #10 AWG stranded wire.  Auto primary wire works best.

73

Bob, K4TAX


On 3/1/2018 7:24 AM, John Saxon johnbsaxon@... [Elecraft_K3] wrote:
 
I hope I don't embarrass myself here, but here goes:

Started getting erratic behavior with my K3 + ATU (@100w) loading my vertical.  The ATU having performed beautifully for several years, all of a sudden it wouldn't load up - sometimes.  Sometimes the relays would chatter a long time, stop chattering without a SWR being displayed.  A few minutes later it might load up just fine...or not.  The same antenna loaded just fine all the time connected to my vintage gear through a Kenwood manual tuner.  Didn't seem to be a function of band, mode, power,etc.  Even misbehaved connected to a dummy load.

SO...out to the bench with K3 + Power supply + Dummy load.   Same behavior.  I noticed that the power leads from PS to K3 were not connected all that well and the wire was a bit tarnished.  I had simply twisted the wire around the stud and tightened the knob.  I snipped the wire a bit, and crimped on lugs.  It has been perfect ever since.

To be best of my knowledge and recollection, adding the lugs to the power cable was all I did.

Could a bad power connection cause such behavior from the ATU?

Puzzled in Pearland, TX,
John
K5ENQ


K3 - Strange ATU behavior

John Saxon
 

I hope I don't embarrass myself here, but here goes:

Started getting erratic behavior with my K3 + ATU (@100w) loading my vertical.  The ATU having performed beautifully for several years, all of a sudden it wouldn't load up - sometimes.  Sometimes the relays would chatter a long time, stop chattering without a SWR being displayed.  A few minutes later it might load up just fine...or not.  The same antenna loaded just fine all the time connected to my vintage gear through a Kenwood manual tuner.  Didn't seem to be a function of band, mode, power,etc.  Even misbehaved connected to a dummy load.

SO...out to the bench with K3 + Power supply + Dummy load.   Same behavior.  I noticed that the power leads from PS to K3 were not connected all that well and the wire was a bit tarnished.  I had simply twisted the wire around the stud and tightened the knob.  I snipped the wire a bit, and crimped on lugs.  It has been perfect ever since.

To be best of my knowledge and recollection, adding the lugs to the power cable was all I did.

Could a bad power connection cause such behavior from the ATU?

Puzzled in Pearland, TX,
John
K5ENQ