DX cluster load last 50 spots

18 posts / 0 new
Last post
SV2RCK
DX cluster load last 50 spots

It would be very good feature if there is a check box to load last 50 or 100 spots while dxcluster starts.

You may do that if you send this command in telnet
SH/DX/50

It would be very good because Band map will start with many station and you don't have to wait.

oh1kh
DX cluster load last 50 spots

Hi!
Have you tried Web-DxCluster?
When connected it loads last spots and populates Band map, too.

--
Saku
OH1KH

--
Saku
OH1KH

SV2RCK
Thank you Saku

Thank you Saku

I didn't tried web dxcluster.
I switch to web dx.

SV2RCK
I find a bug in web dxcluster

I find a bug in web dxcluster. If you configure an alert for a callsign. The alert will popup many times! Not only when first appears.

oh1kh
I find a bug in web dxcluster

Hi !
At start it fetches recent spots and alerts so many times this starting list has alerting callsign.

It seems that web cluster updates all spots to window every time one new spot is received.
That is why alerts are going on so long as the window holds alerting callsign at any line.
This is different than telnet cluster.

Once I lost this "everytime alert". I do not know why. There were still alerting callsigns on webcluster window.
So there seems to be something mysterious with webcluster.

This must be studied more!

Alerts are properly tested only with telnet.
Easiest fix would be disable alerting when webcluster is used.

--
Saku
OH1KH

--
Saku
OH1KH

oh1kh
I find a bug in web dxcluster

Hi!

Reason for alerts is that webcluster works different than telnet cluster.

When telnetcluster pushes every new spot to client when it appears, webcluster does not.
Client have to poll webcluster. Every 20sec webcluster is polled.
It is like issuing sh/dx on every 20secs in telnetcluster.

Then client is getting latest spots, but they may have alerting callsign several times again if there are no new, or just few new spots. So that issues alerts again and again.
Even many times in one go if group of spots has several alerting (same) callsigns.

There is no easy way at client side to prevent it. It would require connect time database to store every previous and latter callsign of alerting callsign to keep record if alert is issued or not.

So that's why disabling alert while webcluster in use is the solution. Unless "someone else"(tm) will write such procedure.

Other, and lot more easier, solution would be to change webcluster itself first .
Webcluster should keep ID number of every spot and send it as last line of answer to client request.
Next time after client timer (20sec) sends request it would be "give me all spots after ID number xxxxxx".

Answer would be new spots added with last ID number, or just ID number if no new spots available.

It would make alert work just like in telnetcluster.
And it would also reduce lot of webcluster network traffic.

So until one of these options comes true the fix will be alert disable during webcluster usage.

Other discussion would be creating "send user command after connecting" for telnetcluster that would allow sending "sh/dx 50" or something to populate bandmap.
That actually was the original subject of this message chain.

--
Saku
OH1KH

--
Saku
OH1KH

oh1kh
I find a bug in web dxcluster

Hi!
At my test binary website is now 2.2.0-107 that has alerts disabled when using webcluster.
In addition it has user defineable startConnectionCommand for telnet cluster.
It is sent to dxcluster when it's command prompt is received first time after connect.

Of course source is also available at my GitHub.

Comments?

--
Saku
OH1KH

--
Saku
OH1KH

SV2RCK
I think is a good idea. Could

I think is a good idea. Could you push it to ppa ?

oh1kh
I think is a good idea

No, I can't!

And there is no need.
Testing new binary is just replacing one file /usr/bin/cqrlog. No installation needed, just cp-command at console.
ZIP has instructions how to do it.

--
Saku
OH1KH

--
Saku
OH1KH

SV2RCK
I download binary 2.2.0-108

I download binary 2.2.0-108 but I cant find where I setup startConnectionCommand

oh1kh
I download binary 2.2.0-108

You did not read "Readme.OH1KH" as required in splash window (orange background, black text) that appears at first start.
Open the file. Go to the end of it and look date 30.01.2018

If you installed latest help files from ZIP it is also there: 1st chapter of "DX cluster operation"

--
Saku
OH1KH

--
Saku
OH1KH

SV2RCK
"Added StartConnectCommand

"Added StartConnectCommand for telnet dxcluster. Type DXCluter command to edit box, but not
send it to cluster, instead press Ctrl-S saves the command. It will be sent to DXCluster when
connection is established and DXCluster prompt received for first time for now on.
Command is cleared by pressing Ctrl-S when edit box is empty."

I still I cant find where :)

oh1mrr
You put "sh/dx/50 into

You put "sh/dx/50 into cluster window "COMMAND" line, when connected into cluster.
Do not enter, instead press "ctrl-s" and with next cluster open, you get listed last
dx spots.

Jarmo

oh1kh
You put "sh/dx/50 into

Thanks Jarmo !

Edit box is a common name of Lazarus component where you can write text.

I will fix this to readme.OH1KH and help files to be:

Type DXCluster command you want to use into DXCluster's "command:"-line, but not send it to cluster. Instead press Ctrl-S to save the command as StartConnectionCommand. You do not have to be connected to DXCluster while doing this, but it works also when you are connected.

--
Saku
OH1KH

--
Saku
OH1KH

ok7an
ok7an's picture
Re: You put "sh/dx/50 into

Saku, please add the start connection command to preferences instead using CTRL+S. It will be much easier to understand for users even without reading any help files. You can name is like Run this command after login to the cluster or something like that. I'd like to have CQRLOG user friendly. Thanks!

oh1kh
Re: You put "sh/dx/50 into

That's what test binaries are for...to find more/other views.
Idea is good, but not "instead". I do not like "preferences". It is too giant and that's why not user friendly any more for daily use.
It is ok when you set up program at first time or new log's properties, but for daily quick changes it is not very usable.

So we say "in addition" instead of "instead" :)

That way it can be found from preferences, but also can be changed or cleared without going to preferences.

Could it compromise even better result?

--
Saku
OH1KH

--
Saku
OH1KH

ok7an
ok7an's picture
Re: You put "sh/dx/50 into

Yes, that looks fine.

I think it's OK to have this in Preferences because I suppose you set in once and use it. I'm not sure how many times the startup command needs to be changed. As far as I know you can set this also to cluster you are connecting every day.

73 Petr

SV2RCK
Thanks Jarmo and Saku now its

Thanks Jarmo and Saku now its clear and working fine.