DX Cluster issues?

Usage Questions
1

I was wanting to try the cluster, but it isn’t really working at all.

For example, ve7cc.net port 23 it just says connecting to 23.

I read here about using the enter key in each field, but that doesn’t move me to the next field. Tab does, but still no connection. And if I click “ADD” the program closes without a message.

To alleviate any firewall etc. issues, I can use a telnet program and use the cluster on the same windows machine using the same internet connection.

Is there a log file someplace? I guess I could send it in.

So far the software is pretty darn cool. Using 7610 on the LAN from my desk at work! :slight_smile:

2

tried:

For example, ve7cc.net port 23 it just says connecting to 23.

inserted my call as per login request. and then

AR User program now at ver. 2.447
Please enter your call:

login: pa3met

[ nothing ]

so that one isn’t working at all.

3

If you are saying that the issue is with the ve7cc node, it is not. I can connect to it and it works perfectly with a telnet client and two logging programs.

Using WFView 2.11 on two different PCs, at two different locations, one Win 10 and the other Win 11, I get the same behavior as stated above. With VE7CC or any other node I attempted to use.

N7OR

4

Capture
Capture1964×618 122 KB

5

I telnetted, got text and the login prompt. sent call. nothing happened.

6

As I have said a number of times here (try the search function, it works really well), the cluster window currently only supports dxspider nodes, it has not been tested with any other cluster server and probably will not work

7

Yes, the search does work. I used it yesterday.

What doesn’t work is WFView’s cluster function.

DXSpider nodes do not work. I tried several yesterday after I used the search function.

AR Cluster nodes do not work.

CC Cluster nodes do not work.

VE7CC Cluster is up and functioning perfectly, BTW.

8

Hello.
The issue is with the line ending code.
Windows-based telnet uses CRLF, while UNIX-based systems use CR.
ve7cc.net processes line endings as CRLF, so it works fine with Windows telnet.
Tera Term uses CR by default, but changing it to CRLF allowed the connection.
For UNIX telnet, you can change the line ending code with:
set crlf…

Just my two cents:
I think it would be better if ve7cc.net used CR.

DE NAKAO

9

As part of the complete rewrite of the wfview user interface to use a more modern architecture (Qt Quick vs QWidgets) I will revisit both the cluster configuration form and the cluster parser to make it more flexible. This is a long-term goal though as it requires rewriting of literally every part of the wfview user interface.

10

That makes sense.

I wonder if anyone who has it working on any cluster using the win64 2.11 would share the workaround.

I can’t connect to any on 3 different installs.

Thanks!

11

the cluster works with dxc.pi4cc.nl port 8000

works with telnet, works with wfview. your suggested link does not.

12

Now that I see what is possible to do, never mind.

Have fun and good luck.

Screenshot 2026-01-10 071321
Screenshot 2026-01-10 071321564×287 49.8 KB

DX Cluster Connection
14

the post above was deleted, asking for an example

for reference as a working example:

click on TCP cluster connection
servername dx.packet-radio.nl and click on add/update

port 7300
username
spot timeout

click on TCP cluster connection

save the config.

Now, there may be some small things you need to take care of
and that is excessive spaces upfront, after values.
I have seen, but that’s me, that it starts working after exit/relaunch wfview.
(but that was some time ago during testing phase so it may be fixed)