Date   

Re: Logging question

Rebecca Milligan
 

Hi,

 

I had the same message but there was a dialogue box that asked me if I wanted to log it anyway.  It logged correctly after selecting the option to log anyway.

 

N4EFS

 

From: robert
Sent: Tuesday, November 26, 2019 5:37 AM
To: n3fjp users
Subject: [N3FJPSoftwareUsers] Logging question

 

During this weekends DX contest I wrkd.  MW/R6AF. The software said error. The 3rd digit must be a number. So I logged Him as MW1/R6AF which logged OK. Later i wrkd. FS/VA3DF. Same thing. I just quickly redid the call as VA3DF/FO & it logged OK. Not run into this in previous contests.

K9IL

 


Logging question

robert
 

During this weekends DX contest I wrkd.  MW/R6AF. The software said error. The 3rd digit must be a number. So I logged Him as MW1/R6AF which logged OK. Later i wrkd. FS/VA3DF. Same thing. I just quickly redid the call as VA3DF/FO & it logged OK. Not run into this in previous contests.
K9IL


Re: Log too big?

Dale Martin, KG5U
 

Many thanks to all for the comments. 

The computer is an i5  at 3GHz. RAM is a puny 8GB. I may have a suitable memory card in another computer I no longer use. I'll pop that in and see if there's a difference. 

But, keeping the display list to 50 works for me.

73,
dale, kg5u


Re: Log too big?

Jim Shorney
 

All good points Mike. I was aiming at the lowest common denominator here, the ham that is not very computer savvy and just wants to make'ergofaster. The easiest answer there is to just get a bleeding edge computer. Any current front-line gaming rig should do.

73

-Jim
NU0C

On Mon, 25 Nov 2019 06:21:46 -0700
"Mike Olbrisch" <mike-2020@elp.rr.com> wrote:

Good morning.



There is more to it than just the volume of records. Amount of memory, amount of FREE memory, processor and speed, and what other programs running in the background can all make a huge difference.



One ”FREE” thing you can do to speed it up is this. Open your task manager and see what-all you have running. Look to see what processes might be monopolizing your processor cycles, or reserving your memory. Turn off those things you don’t need.



Look at my QRZ profile-photo of the operating desk. That is an older Win-7 (64 bit) I got from an SK sale. It isn’t anything special. The only thing I did was double the memory and clean out all the programs it wouldn’t need. All I use it for is logging and digital work. Sure, a nice new Win-10 box would be nicer. But this works, and I see no need to spend $$$$ for a replacement.



If I have to upgrade it from Win-7 to Win-10, it may suffer and need to be replaced once Win-7 is no longer supported. We’ll see.



Give it a look. Best of luck!



Mike – KD5KC -- El Paso -- Texas.



The canyons are calling, colorful and deep. But I have promises to keep.

And miles to go still in my Jeep... And miles to go still in my Jeep...







ADVENTURE: The respectful pursuit of trouble.









On Sun, Nov 24, 2019 at 6:36 PM Jim Shorney <jshorney@inebraska.com <mailto:jshorney@inebraska.com> > wrote:


27,000 QSOs will slow the database down. That's just the way it is. You can either run in Last 50 mode like most of us probably do or you can buy the fastest bad-boy computer you can get your hands on and equip it with the most RAM and fastest SSD you can get.

73

-Jim
NU0C

On Sun, 24 Nov 2019 15:49:25 -0600
"Dale Martin" <kg5u@att.net <mailto:kg5u@att.net> > wrote:

Any suggestions other than just using the logsheet in the 'Last 50' mode?
There's a lot of 'downtime' in FT8, so I use it to go through the log and
update the not-yet-confirmed QSOs S/R status to Y/Y and removing the
confirmed QSO from LOTW.







Re: Log too big?

Frank MacKenzie-Lamb
 

I’m with you Don……especially staying with ACLog

 

73

Frank

NG1I

 

From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> On Behalf Of Don N4KC
Sent: Monday, November 25, 2019 10:00 AM
To: N3FJPSoftwareUsers@groups.io
Subject: Re: [N3FJPSoftwareUsers] Log too big?

 

Well, I have a fairly fast Win10 machine with plenty of RAM, yet when I switch from "Last 50" to "All" it takes 13 seconds to display the data. I have about 24,000 records in ACLog. I can see how this would delay showing that your FT8 QSO had been successfully logged. Obviously, ACLog has to do a lot of work each time a change is made, including logging a new contact, when you are displaying that many records.

I'd say you have three choices:

1) As KD5KC (great suffix, Mike!) suggests above, invest in the fastest machine you can and stop all processes you don't need so as to save RAM, or

2) Accept that it will take ten to fifteen seconds for WSJT-X to confirm that you have successfully logged the FT8 QSO, or

3) Keep ACLog on ""Last 50" and do the database housekeeping when you are not logging contacts.

Note that I did not suggest trying other logging programs. I suspect you'd see similar behavior with most (if not all) and, more importantly, there are none as good as ACLog...in my humble opinion.

73,

Don N4KC
www.donkeith.com
www.n4kc.com
  


Re: Winkeyer Emulator and RemoteRig RRC Query

Scott Davis
 

Hi Dennis,

Thanks for your follow up.  To change the Winkey settings in the software, click Settings > Transmit > CW.  Then click the Winkeyer button on the form that appears, but I doubt you need to change anything from defaults as Winkeyer isn't rig dependent..

Again, if you have your radio configured for keyer instead of straight key, it will not work.  You must have Winkeyer plugged into your straight key jack.

Good luck!


73, Scott
N3FJP

Serving the Amateur Radio community with contesting and general logging software since 1997.

1 Peter 3 vs 15: Always be prepared to give an answer to everyone who asks you to give the reason for the hope that you have. But do this with gentleness and respect...


-----Original Message-----
From: Dennis - WU6X <wu6x@...>
To: N3FJPSoftwareUsers <N3FJPSoftwareUsers@groups.io>
Sent: Mon, Nov 25, 2019 12:48 pm
Subject: Re: [N3FJPSoftwareUsers] Winkeyer Emulator and RemoteRig RRC Query

What it sounds like is that the macros are keying the radio and sending CW, but not distinguishing the difference between a dot or dash. Is there a software setting in the CW transmission settings I may need to change? Currently everything is set to defaults. 
Dennis WU6X 


Re: Winkeyer Emulator and RemoteRig RRC Query

Dennis - WU6X
 

What it sounds like is that the macros are keying the radio and sending CW, but not distinguishing the difference between a dot or dash. Is there a software setting in the CW transmission settings I may need to change? Currently everything is set to defaults. 

Dennis WU6X 


Re: Log too big?

Frank MacKenzie-Lamb
 

Mike, you hit the nail on the head….my laptop 32GB memory and 1T solid state drive…all works well

 

Have a nice T-Day everyone!

 

Frank

NG1I

 

From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> On Behalf Of Mike Olbrisch
Sent: Monday, November 25, 2019 8:22 AM
To: N3FJPSoftwareUsers@groups.io
Subject: Re: [N3FJPSoftwareUsers] Log too big?

 

Good morning.

 

There is more to it than just the volume of records.  Amount of memory, amount of FREE memory, processor and speed, and what other programs running in the background can all make a huge difference.

 

One ”FREE” thing you can do to speed it up is this. Open your task manager and see what-all you have running.  Look to see what processes might be monopolizing your processor cycles, or reserving your memory.  Turn off those things you don’t need.

 

Look at my QRZ profile-photo of the operating desk.  That is an older Win-7 (64 bit) I got from an SK sale.  It isn’t anything special.  The only thing I did was double the memory and clean out all the programs it wouldn’t need.  All I use it for is logging and digital work.  Sure, a nice new Win-10 box would be nicer.  But this works, and I see no need to spend $$$$ for a replacement.

 

If I have to upgrade it from Win-7 to Win-10, it may suffer and need to be replaced once Win-7 is no longer supported.  We’ll see.

 

Give it a look.  Best of luck!

 

Mike – KD5KC -- El Paso -- Texas.

 

The canyons are calling, colorful and deep.  But I have promises to keep.

And miles to go still in my Jeep...   And miles to go still in my Jeep...

 

Big Bend JEEP Rear

 

ADVENTURE:  The respectful pursuit of trouble.

 

 

 

 

On Sun, Nov 24, 2019 at 6:36 PM Jim Shorney <jshorney@...> wrote:


27,000 QSOs will slow the database down. That's just the way it is. You can either run in Last 50 mode like most of us probably do or you can buy the fastest bad-boy computer you can get your hands on and equip it with the most RAM and fastest SSD you can get.

73

-Jim
NU0C

On Sun, 24 Nov 2019 15:49:25 -0600
"Dale Martin" <kg5u@...> wrote:

> Any suggestions other than just using the logsheet in the  'Last 50' mode?
> There's a lot of 'downtime' in FT8, so I use it to go through the log and
> update the not-yet-confirmed QSOs S/R status to Y/Y and removing the
> confirmed QSO from LOTW.



Re: Missing Header top line

Jim Hamlin
 

Problem solved.  Turns out I inadvertently scrolled the window vertically.  Feeling embarrassed!  Thanx for your response.
W8JRH
From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> on behalf of Wilbur Doolittle <johndeere75549011@...>
Sent: Sunday, November 24, 2019 5:42:39 PM
To: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io>
Subject: Re: [N3FJPSoftwareUsers] Missing Header top line
 
screenshot pls

On Sun, Nov 24, 2019 at 4:03 PM Jim Hamlin <Jhamlin2015@...> wrote:
All of a sudden I'm not seeing the top heading line, which shows menu, sort options, view, etc.  The logging function seems to be running fine.
What am I missing?  Thinking I've done something inadvertently.  Thanx in advance for your help!

W8JRH


Re: Log too big?

 

Well, I have a fairly fast Win10 machine with plenty of RAM, yet when I switch from "Last 50" to "All" it takes 13 seconds to display the data. I have about 24,000 records in ACLog. I can see how this would delay showing that your FT8 QSO had been successfully logged. Obviously, ACLog has to do a lot of work each time a change is made, including logging a new contact, when you are displaying that many records.

I'd say you have three choices:

1) As KD5KC (great suffix, Mike!) suggests above, invest in the fastest machine you can and stop all processes you don't need so as to save RAM, or

2) Accept that it will take ten to fifteen seconds for WSJT-X to confirm that you have successfully logged the FT8 QSO, or

3) Keep ACLog on ""Last 50" and do the database housekeeping when you are not logging contacts.

Note that I did not suggest trying other logging programs. I suspect you'd see similar behavior with most (if not all) and, more importantly, there are none as good as ACLog...in my humble opinion.

73,

Don N4KC
www.donkeith.com
www.n4kc.com
  


Re: Log too big?

Mike Olbrisch
 

Good morning.

 

There is more to it than just the volume of records.  Amount of memory, amount of FREE memory, processor and speed, and what other programs running in the background can all make a huge difference.

 

One ”FREE” thing you can do to speed it up is this. Open your task manager and see what-all you have running.  Look to see what processes might be monopolizing your processor cycles, or reserving your memory.  Turn off those things you don’t need.

 

Look at my QRZ profile-photo of the operating desk.  That is an older Win-7 (64 bit) I got from an SK sale.  It isn’t anything special.  The only thing I did was double the memory and clean out all the programs it wouldn’t need.  All I use it for is logging and digital work.  Sure, a nice new Win-10 box would be nicer.  But this works, and I see no need to spend $$$$ for a replacement.

 

If I have to upgrade it from Win-7 to Win-10, it may suffer and need to be replaced once Win-7 is no longer supported.  We’ll see.

 

Give it a look.  Best of luck!

 

Mike – KD5KC -- El Paso -- Texas.

 

The canyons are calling, colorful and deep.  But I have promises to keep.

And miles to go still in my Jeep...   And miles to go still in my Jeep...

 

Big Bend JEEP Rear

 

ADVENTURE:  The respectful pursuit of trouble.

 

 

 

 

On Sun, Nov 24, 2019 at 6:36 PM Jim Shorney <jshorney@...> wrote:


27,000 QSOs will slow the database down. That's just the way it is. You can either run in Last 50 mode like most of us probably do or you can buy the fastest bad-boy computer you can get your hands on and equip it with the most RAM and fastest SSD you can get.

73

-Jim
NU0C

On Sun, 24 Nov 2019 15:49:25 -0600
"Dale Martin" <kg5u@...> wrote:

> Any suggestions other than just using the logsheet in the  'Last 50' mode?
> There's a lot of 'downtime' in FT8, so I use it to go through the log and
> update the not-yet-confirmed QSOs S/R status to Y/Y and removing the
> confirmed QSO from LOTW.




Re: Log too big?

Steven Weeks <swweeks@...>
 

Responding to

"I notice when logging FT8 QSOs in ACL from JTAlert/WSJT-X, that it takes 18 seconds for the QSO line entry to appear after clicking on OK in the J/W log pop-up window. I have 27k log entries. "

Have you closed and restarted ACLog recently?  I have a very similar number of entries in my log and the response from the program (and JTAlert) is almost instantaneous -- as long as ACLog has not been running too long.  If it has been running for multiple days with lots of entries being added, it gets very slow and has the same issues that you mentioned.  Scott may know what causes this -- buffers fill up, temporary files get too large, some obscure Windows problem, an issue within JTAlert? -- the reason is unknown to me, but it happens consistently and is easily remedied.  It is certainly not an inherent or unavoidable problem resulting from 27,000 records, which is not a large number for an Access database. 

73, Steve AA8SW

 


Re: Log too big?

Jim Shorney
 

Yes, it will in Last 50 view. But it will bog down if you go to All view.



On Sun, 24 Nov 2019 23:57:06 -0600
"Lou Everett, Sr." <loueverettsr@gmail.com> wrote:

I have 50,000 in mine and it zips along fine. I am running an old
computer. The op SYS is Win 7.

Lou WA5LOU

On Sun, Nov 24, 2019 at 6:36 PM Jim Shorney <jshorney@inebraska.com> wrote:


27,000 QSOs will slow the database down. That's just the way it is. You
can either run in Last 50 mode like most of us probably do or you can buy
the fastest bad-boy computer you can get your hands on and equip it with
the most RAM and fastest SSD you can get.

73

-Jim
NU0C

On Sun, 24 Nov 2019 15:49:25 -0600
"Dale Martin" <kg5u@att.net> wrote:

Any suggestions other than just using the logsheet in the 'Last 50'
mode?
There's a lot of 'downtime' in FT8, so I use it to go through the log and
update the not-yet-confirmed QSOs S/R status to Y/Y and removing the
confirmed QSO from LOTW.



--
Lou WA5LOU



Re: Log too big?

Lou Everett, Sr. <loueverettsr@...>
 

I have 50,000 in mine and it zips along fine.  I am running an old computer.  The op SYS is Win 7.

Lou WA5LOU

On Sun, Nov 24, 2019 at 6:36 PM Jim Shorney <jshorney@...> wrote:

27,000 QSOs will slow the database down. That's just the way it is. You can either run in Last 50 mode like most of us probably do or you can buy the fastest bad-boy computer you can get your hands on and equip it with the most RAM and fastest SSD you can get.

73

-Jim
NU0C

On Sun, 24 Nov 2019 15:49:25 -0600
"Dale Martin" <kg5u@...> wrote:

> Any suggestions other than just using the logsheet in the  'Last 50' mode?
> There's a lot of 'downtime' in FT8, so I use it to go through the log and
> update the not-yet-confirmed QSOs S/R status to Y/Y and removing the
> confirmed QSO from LOTW.




--
Lou WA5LOU



Re: Log too big?

Larry Banks
 

I've change my "Last NNN" to 500 and it seems to be fast enough, a good compromise if you want to quickly look at the past few months of Qs.

73 -- Larry -- W1DYJ

-----Original Message-----
From: Jim Shorney
Sent: Sunday, November 24, 2019 19:36
To: N3FJPSoftwareUsers@groups.io
Subject: Re: [N3FJPSoftwareUsers] Log too big?


27,000 QSOs will slow the database down. That's just the way it is. You can either run in Last 50 mode like most of us probably do or you can buy the fastest bad-boy computer you can get your hands on and equip it with the most RAM and fastest SSD you can get.

73

-Jim
NU0C

On Sun, 24 Nov 2019 15:49:25 -0600
"Dale Martin" <kg5u@att.net> wrote:

Any suggestions other than just using the logsheet in the 'Last 50' mode?
There's a lot of 'downtime' in FT8, so I use it to go through the log and
update the not-yet-confirmed QSOs S/R status to Y/Y and removing the
confirmed QSO from LOTW.


Re: Log too big?

Jim Shorney
 

27,000 QSOs will slow the database down. That's just the way it is. You can either run in Last 50 mode like most of us probably do or you can buy the fastest bad-boy computer you can get your hands on and equip it with the most RAM and fastest SSD you can get.

73

-Jim
NU0C

On Sun, 24 Nov 2019 15:49:25 -0600
"Dale Martin" <kg5u@att.net> wrote:

Any suggestions other than just using the logsheet in the 'Last 50' mode?
There's a lot of 'downtime' in FT8, so I use it to go through the log and
update the not-yet-confirmed QSOs S/R status to Y/Y and removing the
confirmed QSO from LOTW.


Re: Log too big?

Wilbur Doolittle
 

27000 ?


On Sun, Nov 24, 2019 at 4:49 PM Dale Martin <kg5u@...> wrote:

 

I notice when logging FT8 QSOs in ACL from JTAlert/WSJT-X, that it takes 18 seconds for the QSO line entry to appear after clicking on OK in the J/W log pop-up window. I have 27k log entries.

 

As soon as I click to log the entry in ACL, ACL logsheet field goes blank. About 10 seconds later, a JTAlert Message box appears telling me the QSO was not logged in ACL but is logged in WSJT-X adi file. About 10 seconds after that, the logsheet contents reappear with the new log entry at the top. If I click on the ’50 recent’ the QSO line entry appears immediately.

 

Do I have too many log entries in ACL for it to be able to properly handle them?  

 

Or is this a JTAlert/WSJT-X thing? I’ve read through the WSJT-X and JTAlert docs but have not found anything that suggests the QSO-not-getting-logged pop-up message timing can be adjusted so it ‘sees’ the QSO did actually get logged—if that makes any sense.

 

Any suggestions other than just using the logsheet in the  ‘Last 50’ mode? There’s a lot of ‘downtime’ in FT8, so I use it to go through the log and update the not-yet-confirmed QSOs S/R status to Y/Y and removing the confirmed QSO from LOTW.

 

Thanks for any info anyone can provide.

 

73,

Dale, kg5u

 

 


Re: Missing Header top line

Wilbur Doolittle
 

screenshot pls


On Sun, Nov 24, 2019 at 4:03 PM Jim Hamlin <Jhamlin2015@...> wrote:
All of a sudden I'm not seeing the top heading line, which shows menu, sort options, view, etc.  The logging function seems to be running fine.
What am I missing?  Thinking I've done something inadvertently.  Thanx in advance for your help!

W8JRH


Re: Missing Header top line

Wilbur Doolittle
 

what or jtalert


On Sun, Nov 24, 2019 at 4:03 PM Jim Hamlin <Jhamlin2015@...> wrote:
All of a sudden I'm not seeing the top heading line, which shows menu, sort options, view, etc.  The logging function seems to be running fine.
What am I missing?  Thinking I've done something inadvertently.  Thanx in advance for your help!

W8JRH


Log too big?

Dale Martin, KG5U
 

 

I notice when logging FT8 QSOs in ACL from JTAlert/WSJT-X, that it takes 18 seconds for the QSO line entry to appear after clicking on OK in the J/W log pop-up window. I have 27k log entries.

 

As soon as I click to log the entry in ACL, ACL logsheet field goes blank. About 10 seconds later, a JTAlert Message box appears telling me the QSO was not logged in ACL but is logged in WSJT-X adi file. About 10 seconds after that, the logsheet contents reappear with the new log entry at the top. If I click on the ’50 recent’ the QSO line entry appears immediately.

 

Do I have too many log entries in ACL for it to be able to properly handle them?  

 

Or is this a JTAlert/WSJT-X thing? I’ve read through the WSJT-X and JTAlert docs but have not found anything that suggests the QSO-not-getting-logged pop-up message timing can be adjusted so it ‘sees’ the QSO did actually get logged—if that makes any sense.

 

Any suggestions other than just using the logsheet in the  ‘Last 50’ mode? There’s a lot of ‘downtime’ in FT8, so I use it to go through the log and update the not-yet-confirmed QSOs S/R status to Y/Y and removing the confirmed QSO from LOTW.

 

Thanks for any info anyone can provide.

 

73,

Dale, kg5u

 

 

7941 - 7960 of 46942