Log4OM

w9mdb

This should be a relatively simple fix. The suffix on spot reporters is being truncated in the cluster window in Log4OM. For example.... W1NT-6 shows up as W1NT. ARCluster software does not understand suffixes at all so W1NT-6 gets put in CQ Zone 3 due to the W1 and Log4OM removes the suffix so we c...

w9mdb

Using 1.40.0.0

I've got "Use clublog..", "use Special...", and "Realtime Lookup..." checked.

TX7T is in clublog.xml correctly.

Unchecked are "Fill data..." and "Realtime previous..."

Turning on debug to max I see this

w9mdb

TX7T does not show up correctly here. I've updated all the databases and restarted Log4OM. I also tried logging it (from WSJT-X) and it does get inserted correctly as JTAlert does the DXCC lookup...but still the F2 tab in Log4OM shows Clipperton. I tested with a friend and his shows correctly on the...

w9mdb

In V2 the caching will solve most of the problem. The other problem besides being slow is the constant updating that takes places when hooked to one of the CW Skimmer cluster sites. They come in so often as to make clicking on anything impossible. So that's why I have my queueing program just dumpin...

w9mdb

I've seen this error a few times in the last couple of weeks. I've seen this in my own code using a "foreach" statement on a list and modifying the list inside of it. You have to use an ".Items" to get a copy of the list to work with. See the end of this message for details on in...

w9mdb

But why do we care about prefix/suffix? Seems we should have an option to turn this off so the query can be done with "=" instead of LIKE as I don't care about matching prefixes/suffixes. There's no database I know of that does anything but a full scan for LIKE selections. No way to index ...

w9mdb

It would appear that Log4OM cluster processing does not recognize the sh/dx command results? This is from w3lpl.net sh/dx/30 10115.0 A82X 30-Sep-2019 2225Z Up EL <W5ZN> 18130.0 TI2CC 30-Sep-2019 2224Z CQ DX +TI <TI2SS> 14195.0 HQ9X 30-Sep-2019 2224Z +HR <KC7ZON> 14238.0 WW0WWV 30-Sep-2019 2224Z 59 I...

w9mdb

Note also that when sqlite is the database the Log4OM is using 100% CPU during the spot updates. Here's the log from the sqlite database -- it's about 700ms per query 2019-09-29 15:06:21.7177 DEBUG: SQLiteDatabaseManagement: SELECT QSOID, CALL, QSODATE, TIMEON, QSODATEOFF, TIMEOFF, RSTSENT, RSTRCVD,...

w9mdb

And I can send you my log database if you want to test it yourself.

Mike

w9mdb

It's not the cluster site that is slow -- it's Log4OM doing it's thing on each spot. You can see the internal time delays in Log4OM as it process the spot. I discovered this as I'm trying to make the cluster spotting useful so I wrote a queuing program which talks to the cluster site and sends the d...

Search found 310 matches

Cluster spotting with wrong CQ Zone

Re: Call sign challenge

Re: Call sign challenge

Re: cluster is slow

New Error

Re: cluster is slow

sh/dx cluster processing

Re: cluster is slow

Re: cluster is slow

Re: cluster is slow