K3 memory editor

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

K3 memory editor

Alan - G4GNX
I just started using the K3 memory editor (v1.5.7.20 dated 2015) for the first time and I find it behaves in a strange way, depending whether a memory has content or not.

At present I have general memories 0 thru 23 loaded with data and memories 85 thru 99 also loaded. All other memories are ‘empty’.

If I try to read all memories from the K3, the editor program reaches memory 24 (empty) and stalls. If I click the Cancel button, it reports ‘cancelling’ but does nothing. I can abort the action by clicking the red close icon.
When I check the ‘spreadsheet’ I find that memories 0 thru 23 are filled and displayed, but not memories 85 thru 99. The only way to read memories 85 thru 99 is to ‘select’ them first, then read selected.
Attempting to read any empty memory individually results in the function stalling.

I also tried clearing a single memory entry and uploading it to the K3, which seems to work OK, but attempting to read it back, results in a stall.

Is this normal behavior – a bug, or do I have an old or corrupted memory editor.

73,

Alan. G4GNX

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: K3 memory editor

Brian D
I have exactly the same problem using it with my KX3 (win10).


"G4GNX" <[hidden email]> wrote:

> I just started using the K3 memory editor (v1.5.7.20 dated 2015) for the
> first time and I find it behaves in a strange way, depending whether a
> memory has content or not.
>
> At present I have general memories 0 thru 23 loaded with data and memories
> 85 thru 99 also loaded. All other memories are ‘empty’.
>
> If I try to read all memories from the K3, the editor program reaches
> memory 24 (empty) and stalls. If I click the Cancel button, it reports
> ‘cancelling’ but does nothing. I can abort the action by clicking the red
> close icon. When I check the ‘spreadsheet’ I find that memories 0 thru 23
> are filled and displayed, but not memories 85 thru 99. The only way to
> read memories 85 thru 99 is to ‘select’ them first, then read selected.
> Attempting to read any empty memory individually results in the function
> stalling.
>
> I also tried clearing a single memory entry and uploading it to the K3,
> which seems to work OK, but attempting to read it back, results in a
> stall.
>
> Is this normal behavior – a bug, or do I have an old or corrupted memory
> editor.

--
Brian D
G3VGZ  Yarm    England
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: K3 memory editor

Alan - G4GNX
I realise that it's only two of us so far, but I suspect it's a bug.

Hopefully, Elecraft will fix it.

73,

Alan. G4GNX

-----Original Message-----
From: Brian D
Sent: Saturday, June 24, 2017 11:33 AM
To: [hidden email]
Subject: Re: [Elecraft] K3 memory editor

I have exactly the same problem using it with my KX3 (win10).


"G4GNX" <[hidden email]> wrote:

> I just started using the K3 memory editor (v1.5.7.20 dated 2015) for the
> first time and I find it behaves in a strange way, depending whether a
> memory has content or not.
>
> At present I have general memories 0 thru 23 loaded with data and memories
> 85 thru 99 also loaded. All other memories are ‘empty’.
>
> If I try to read all memories from the K3, the editor program reaches
> memory 24 (empty) and stalls. If I click the Cancel button, it reports
> ‘cancelling’ but does nothing. I can abort the action by clicking the red
> close icon. When I check the ‘spreadsheet’ I find that memories 0 thru 23
> are filled and displayed, but not memories 85 thru 99. The only way to
> read memories 85 thru 99 is to ‘select’ them first, then read selected.
> Attempting to read any empty memory individually results in the function
> stalling.
>
> I also tried clearing a single memory entry and uploading it to the K3,
> which seems to work OK, but attempting to read it back, results in a
> stall.
>
> Is this normal behavior – a bug, or do I have an old or corrupted memory
> editor.

--
Brian D
G3VGZ  Yarm    England

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: K3 memory editor

Alan - G4GNX
The issue I was having with the Elecraft Frequency Memory Editor has now been resolved, thanks to a suggestion by Dick, K6KR.

Dick suggested using the Trace option to see if I could capture where the stall was taking place. When I went to turn the Trace option on, I realised that it was already on, so decided to firstly test the Editor with Trace turned off. Bingo! All works as expected with no stalling.

Having only just used the Editor for the first time, I did not realise that the Trace window is does not show in normal operation. The Editor still stalls with Trace on, but this may be normal. I’m not aware whether Trace is on by default when the program is installed, probably not, but it got turned on somehow!

I hope my experience will provide a fix for others who have experienced a similar ‘issue’.

Once again, this proves that the choice of Elecraft is the best there can be. Where else do you get a direct reply from the author of the software within hours?

Thanks Dick for taking time out of your busy schedule. I know you didn’t actually have to fix anything, but if you’d not made the suggestion about using Trace, it may have taken me many hours to find the problem.

73,

Alan. G4GNX
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]