K3 problem with logging program after download upgrade

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

K3 problem with logging program after download upgrade

Buck - k4ia

The downloader utility did not reset the baud rate back from the 38,400  for
the download to the 4800 specified for the rig control - I know I read  
somewhere it was supposed to do this.  As a result my logging program  stopped
responding to the radio.   I reset the logging program to  accept 38,400 and now
the DxLab and the K3 are talking to each other  again.
 
Also, the Mic Sel of Line In stopped working.  Once I cycled through  the
other choices back to Line In, it started working again.

Craig  "Buck"
k4ia
Fredericksburg, Virginia USA
 



**************************************Check out AOL's list of 2007's hottest
products.
(http://money.aol.com/special/hot-products-2007?NCID=aoltop00030000000001)
_______________________________________________
Elecraft mailing list
Post to: [hidden email]
You must be a subscriber to post to the list.
Subscriber Info (Addr. Change, sub, unsub etc.):
 http://mailman.qth.net/mailman/listinfo/elecraft   

Help: http://mailman.qth.net/subscribers.htm
Elecraft web page: http://www.elecraft.com
Reply | Threaded
Open this post in threaded view
|

RE: K3 problem with logging program after download upgrade

Greg - AB7R
Buck.  Please report issues such as this to the [hidden email]
address that was included with the radio.

I'll pass this on to our software person who designed the downloader.  This
must be associated with the new downloader as I've not seen this reported
before.

The issue of Line-In staing active through a power cycle has already been
identified and was corrected today.  It will be available
in the next FW update.

Thanks.

73
Greg
AB7R


-----Original Message-----
From: [hidden email]
[mailto:[hidden email]]On Behalf Of [hidden email]
Sent: Monday, December 03, 2007 6:54 PM
To: [hidden email]
Subject: [Elecraft] K3 problem with logging program after download
upgrade



The downloader utility did not reset the baud rate back from the 38,400  for
the download to the 4800 specified for the rig control - I know I read
somewhere it was supposed to do this.  As a result my logging program
stopped
responding to the radio.   I reset the logging program to  accept 38,400 and
now
the DxLab and the K3 are talking to each other  again.

Also, the Mic Sel of Line In stopped working.  Once I cycled through  the
other choices back to Line In, it started working again.

Craig  "Buck"
k4ia
Fredericksburg, Virginia USA




**************************************Check out AOL's list of 2007's hottest
products.
(http://money.aol.com/special/hot-products-2007?NCID=aoltop00030000000001)
_______________________________________________
Elecraft mailing list
Post to: [hidden email]
You must be a subscriber to post to the list.
Subscriber Info (Addr. Change, sub, unsub etc.):
 http://mailman.qth.net/mailman/listinfo/elecraft

Help: http://mailman.qth.net/subscribers.htm
Elecraft web page: http://www.elecraft.com

_______________________________________________
Elecraft mailing list
Post to: [hidden email]
You must be a subscriber to post to the list.
Subscriber Info (Addr. Change, sub, unsub etc.):
 http://mailman.qth.net/mailman/listinfo/elecraft   

Help: http://mailman.qth.net/subscribers.htm
Elecraft web page: http://www.elecraft.com
Reply | Threaded
Open this post in threaded view
|

RE: K3 problem with logging program after download upgrade

Dick Dievendorff
Hi, Buck.

The K3 Utility attempts to communicate with the MCU initially to establish
its baud rate.  This is done by sending a small command at each of the
supported speeds.  If the MCU responds at one of those speeds, the baud rate
is saved and an attempt is made to restore that setting after firmware load.
Firmware loading is done at 38,400.

If the K3 Utility can't communicate with a "live" MCU (which can happen if
you've pressed and held the power key for 10 seconds), then the established
baud rate can't be determined, and the K3 Utility leaves the baud rate at
38,400 after loading firmware.  Since the utility couldn't figure out the
initial baud rate, it can't reestablish it after the load.

Is this repeatable, or a one-off occurrence?  I test this, and I don't think
I've changed that behavior recently. While typing this note I set the baud
rate to 4800, loaded the MCU and DSP1, and found the baud rate back at 4800
after the load.

If any of the firmware loading is interrupted and the K3 Utility doesn't get
to the end of the firmware load and have a chance to restore the baud rate,
it'll be left at 38,400.

The intent is to restore the baud rate that the rig was set to before the
firmware load.  If all goes well, that usually happens. But interruptions
can upset that behavior.

73 de Dick, K6KR


-----Original Message-----
From: [hidden email]
[mailto:[hidden email]] On Behalf Of Greg
Sent: Monday, December 03, 2007 7:04 PM
To: [hidden email]; [hidden email]
Cc: K3 Support
Subject: RE: [Elecraft] K3 problem with logging program after download
upgrade

Buck.  Please report issues such as this to the [hidden email]
address that was included with the radio.

I'll pass this on to our software person who designed the downloader.  This
must be associated with the new downloader as I've not seen this reported
before.

The issue of Line-In staing active through a power cycle has already been
identified and was corrected today.  It will be available
in the next FW update.

Thanks.

73
Greg
AB7R


-----Original Message-----
From: [hidden email]
[mailto:[hidden email]]On Behalf Of [hidden email]
Sent: Monday, December 03, 2007 6:54 PM
To: [hidden email]
Subject: [Elecraft] K3 problem with logging program after download
upgrade



The downloader utility did not reset the baud rate back from the 38,400  for
the download to the 4800 specified for the rig control - I know I read
somewhere it was supposed to do this.  As a result my logging program
stopped
responding to the radio.   I reset the logging program to  accept 38,400 and
now
the DxLab and the K3 are talking to each other  again.

Also, the Mic Sel of Line In stopped working.  Once I cycled through  the
other choices back to Line In, it started working again.

Craig  "Buck"
k4ia
Fredericksburg, Virginia USA




**************************************Check out AOL's list of 2007's hottest
products.
(http://money.aol.com/special/hot-products-2007?NCID=aoltop00030000000001)
_______________________________________________
Elecraft mailing list
Post to: [hidden email]
You must be a subscriber to post to the list.
Subscriber Info (Addr. Change, sub, unsub etc.):
 http://mailman.qth.net/mailman/listinfo/elecraft

Help: http://mailman.qth.net/subscribers.htm
Elecraft web page: http://www.elecraft.com

_______________________________________________
Elecraft mailing list
Post to: [hidden email]
You must be a subscriber to post to the list.
Subscriber Info (Addr. Change, sub, unsub etc.):
 http://mailman.qth.net/mailman/listinfo/elecraft   

Help: http://mailman.qth.net/subscribers.htm
Elecraft web page: http://www.elecraft.com

_______________________________________________
Elecraft mailing list
Post to: [hidden email]
You must be a subscriber to post to the list.
Subscriber Info (Addr. Change, sub, unsub etc.):
 http://mailman.qth.net/mailman/listinfo/elecraft   

Help: http://mailman.qth.net/subscribers.htm
Elecraft web page: http://www.elecraft.com