Cluster hiccups ?

[KI5IO]

Been working on the 13-Colonies Special Event last several days and have noticed that the 3-character calls (K2A, K2B, etc.) don't always show up in the cluster list.

I've double-checked my VE7CC (CC User) setup and can't seem to locate something strange I've set up to cause such. Those same spots are showing up at DX Summmit and DX Heat, etc..

One thing I've noticed this morning is that when I shut down LOG4OM and restart it the 3-character spots will show up for a little while and then they will stop showing up. However, that does not last very long.

I've also had VE7CC running in the background while LOG4OM is running and have not noted any difference there either.

I also don't see the 3-character (13 Colony) spots at VE7CC either.

I've posted a message on their reflector as well.

Maybe it is time to re-install the VE7CC cluster and see what happens there.

[G4POP]

When you first run a cluster (Any cluster) the first spots will not be subject to your filters, once the initial load has finished all future spots have your filters applied.

[KI5IO]

Terry,

Makes perfect sense ... another cup of coffee might have let me see that earlier this AM.

Albeit I did log into CC User directly and set everything back to default and I can't even see the 3-character spots there as well.

I know it is something very simple (might I suggest stupid) that I did that is causing the problem.

BTW ... Does having CC User running in the background while Log4OM is running cause any problems?

I know I used to have the ve7cc.exe set to start as an external program when Log4OM started and you had unchecked that box as it is not needed from what I deduced after you made some corrections to my installation a few months back.

Got to run an errand with my wife and when I get back I go through the CC User setups again and see if I can get it back to ground zero.

Thanks so much.

[G4POP]

BTW ... Does having CC User running in the background while Log4OM is running cause any problems?

No problem at all

[KI5IO]

Terry,

With so much to learn with Log4OM and the "proper" setup operation of VE7CC Cluster has certainly given me a handful.

Lee Sawkins (CC User developer) sent me a very good reply to my question about my situation. Basically I was doing far more to the 'pass / not pass' selections for countries, states, etc., etc.. He also gave me a quick hint on how to set up to capture just the 13-Colony sites.

So, I'll eventually get there.

Only reason I've turned on CC User int he background was as I was setting it up and then watching both that cluster display and how it tracked into Log4OM. That was how I noted the slight delay in sometimes seeing the 3-character sites.

Thanks again so much for your help and patience.

[KI5IO]

Here are the cut/paste replies from Lee Sawkins for my errors with CC User setup:

First Reply to my setup errors:

Hi Nolan

I see you are using VE7CC-1. The default for DX State is for all states to pass. However, you have individually set each state to pass. Each US call is therefore run through the state filter. All US calls that do not match a state in your filter list are rejected. Since all US special calls are not in the FCC database they will all have unknown states and will not match any state in your list. This is why they are all rejected. If you turn off your state filter by removing all states, you will start seeing all US calls, including the ones you are looking for.

Lee VE7CC



2nd Message about configuring CC User to capture the 13-Colony Event Stations:

There is a way to set filtering to PASS only Special Event US calls.

Set the DX Country filter to PASS K
Set the DX State filter to REJECT all US states.
Since none of the 13 Colonies Special Event calls are in the FCC database, they will all pass as all of them have unknown states.

Lee VE7CC