www.dl2rum.de

I installed RUMlogNG about a week ago and I have been using it without any major problems. However, I have not been able to figure out a few things...

I cant seem to get the auto-connect feature to work in the Terminal mode for the VE7CC cluster. Auto-connect works fine for other clusters e.g. W3LPL, K3LR, DXUSA.
In order to get the VE7CC cluster to connect, I must manually enter my callsign. Known issue/bug? or am I perhaps missing something?

I use multiple monitors, but RUMlogNG seems to only know of one monitor. While I am able to use both monitors with RUMlogNG, when I quit and go back into RUMlogNG, it doesnt remember the screen layout and as such, it puts all the various RUMlogNG windows into a single monitor. Is there some way to save my two monitor layout?

I use the CW Tools window and I poll from TRX (Elecraft K3). Is there some way to clear the polling window?

In the DXCC window there is a dropdown to select Paper and/or LOTW. What about eQSL? Id like to be able to include those QSOs in my totals. I dont really care that the ARRL wont accept eQSL QSLs for DXCC Credit. I like to keep score of ALL my Qs from ALL sources. There doesnt seem to be a window or option to include all Qs in my log to summarize DXCC entities worked. Am I missing something?

73, Ron WB2PKR

P.S. Thanks Tom, the new version (NG) is great! I was able to migrate from DxLab without a hitch and finally retire the last Windoze machine in the shack.

I cant seem to get the auto-connect feature to work in the Terminal mode for the VE7CC cluster.

Auto connects fine here, do you have set your user name for this cluster in the preferences?

Is there some way to save my two monitor layout?

Some adjustments in the System Preferences settings are required: Further more you have to right click the RUMlog Icon in the Dock and select the Options menu and choose: „Assign to this space“ (Not sure about the english wording)

I use the CW Tools window and I poll from TRX (Elecraft K3). Is there some way to clear the polling window?

Menu-->Logbook-->Clear while this window has the focus

What about eQSL?

Just the numbers of your eQSL confirmations are available:

Tom,

Auto connects fine here, do you have set your user name for this cluster in the preferences?

Yes, strange. I've tried it both ways: specifying my call in the preferences as well as clearing it and using the default. Neither work for VE7CC only. Works for all the others. Oh well. I will just live with it for now.

Multiple Monitor Layout Saved. Cool. I wasnt aware of that feature in Mission Control. In fact, I've never used Mission Control. Thx.

Just the numbers of your eQSL confirmations are available:

Yeah, I saw that , but you cant just add those totals to the other totals. Would be nice to have a grand total for all QSL sources.
Perhaps you might consider this as a future requirement/feature.

Thanks for the timely response.

Hope to catch you on the bands. 73, Ron WB2PKR

Can you post the content of the terminal window for VE7CC?

Here is a screenshot of my preferences for the terminal connections as well as the terminal window.
As you can see, the VE7CC is waiting for me to type in my callsign. If I dont type in my callsign, eventually it times out and disconnects.
This doesnt happen with W3LPL and K3LR. As you can see, they are both logged in.

Try changing your call sign to all upper case. I recall at least one Cluster site that didn't like lower case, but would take all upper case. I don't remember which one that was, but once I changed it then autoconnect would work.

Dave
K3DCW

Try changing your call sign to all upper case.

Good idea Dave. However, as you can see in the attached screenshot, no luck.

However, this morning I decided to add another source to the DX Cluster Preferences.
As you can see, VTEST, which is also VE7CC, auto connects.
Very strange. I subsequently moved the VTEST to the first location in the list and it did NOT auto connect.
I moved it to the other locations (2nd,3rd location) and it connected. There must be something about it being the first one in the list.

Followup question: In the DX Spots window, is there a way to determine what cluster source a particular spot came from?

I tried a lot of combinations. I'm not able to duplicate the problem.

In the DX Spots window, is there a way to determine what cluster source a particular spot came from?

No.

In the DX Spots window, is there a way to determine what cluster source a particular spot came from?

No.[/quote]

That would be a handy feature, to have an optional column for the DX cluster name.

Right now, I'm getting spots from DX, SOTA, and JOTA clusters, but I have no idea which ones are for JOTA (Scoutings Jamboree on the Air).

wunder