Date   

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
 

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@...> 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 <@NU0C> 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?

Lou Everett, Sr.
 

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> 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> 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

 

 


Missing Header top line

Jim Hamlin
 

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: N3FJP Country Files - 20 November 2019

Bo W4GHV
 

Jim, we all appreciate the giant effort you do to provide this valuable resource!
--
73, Bo W4GHV since '54


Re: Fldigi

Tom Ellis
 

Jeff,

 

This should get you in the right place.

 

http://www.n3fjp.com/help/digitalsetup.html

 

Tom

K5TEE

 

 

From: N3FJPSoftwareUsers@groups.io [mailto:N3FJPSoftwareUsers@groups.io] On Behalf Of Jeff Grantham
Sent: Saturday, November 23, 2019 7:51 AM
To: N3FJPSoftwareUsers@groups.io
Subject: [N3FJPSoftwareUsers] Fldigi

 

Is there a how to somewhere on setting up FLDigi to work with ACLog?  Thought I saw one somewhere but can’t find it now. 

 

Thanks 

 


Fldigi

KB5WCK
 

Is there a how to somewhere on setting up FLDigi to work with ACLog?  Thought I saw one somewhere but can’t find it now. 

Thanks 


Re: New Issue

KB5WCK
 

The ones I see messing up are just normal call signs. If I tell it to look up based on call it fills it all in. Just a weird issue.


From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> on behalf of Wilbur Doolittle via Groups.Io <johndeere75549011@...>
Sent: Friday, November 22, 2019 9:37:09 PM
To: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io>
Subject: Re: [N3FJPSoftwareUsers] New Issue
 
examine the call sign if the search does not come up it usually some added characters or a slash in the callsign it does not recognize(idea)

On Fri, Nov 22, 2019 at 10:26 PM Jeff Grantham <jeff@...> wrote:
When logging via WSJTX, sometimes it pulls the name and info and sometimes it doesn’t. Any ideas why this could be happening?


Re: New Issue

Wilbur Doolittle
 

examine the call sign if the search does not come up it usually some added characters or a slash in the callsign it does not recognize(idea)


On Fri, Nov 22, 2019 at 10:26 PM Jeff Grantham <jeff@...> wrote:
When logging via WSJTX, sometimes it pulls the name and info and sometimes it doesn’t. Any ideas why this could be happening?


New Issue

KB5WCK
 

When logging via WSJTX, sometimes it pulls the name and info and sometimes it doesn’t. Any ideas why this could be happening?


Re: Good practice to start new logbook for new call sign

AI3KS
 

I actually have many entries with my own (3) callsigns in the call field. License upgrades, equipment changes or notes, address changes, etc.

On 19/11/22 20:23, Jim Shorney wrote:
This also works if you note your new call in the comments of the first contact you make with it. Search will find it.

73

-Jim
NU0C

On Fri, 22 Nov 2019 18:15:46 -0700
"Mike Olbrisch" <mike-2020@...> wrote:

When I changed call signs, I just made an entry with my callsign in the next line sequentially.  That way, all the QSOs I ever made under my old call or my new call are there for me if I am looking for something.  And if for any reason I ever need to know when I changed calls, and what QSOs were made with the old call, I only need to search for my call in the log and note the sequence number.