[Dxspider-support] Poorly defined connections?

Rudy Bakalov r_bakalov at yahoo.com
Sat Nov 9 22:04:22 GMT 2024 

 Frankly I am getting sick and tired of the black box approach to CCC. Sure, it is easy to setup, but there is a lot more to running a node than the initial setup. There isn't anything I can do to enable or disable PC92. There is a menu to show the traffic (I assume), but as far as I can tell it does absolutely nothing:


And then I wonder why I have this problem only with a few nodes. The rest of the partner nodes, both DXS and CCC, seem to be OK:



So it's puzzling and frustrating not knowing what's happening and how to fix.
Rudy N2WQ
    On Saturday, November 9, 2024 at 03:29:30 PM EST, Kin EA3CV <ea3cv at cronux.net> wrote:  
 
 I don't know where the documentation can be found, I have done reverse engineering and I have read almost all the messages published here.
>From what I see, the link between our nodes may not have been initialized to use pc9x. I think almost all CCCs don't use it, and I think it's due to configuration, because nodes like Lee's have it activated and I receive pc9x from him, and I reciprocate by doing the same. It would be necessary to capture an initialization of the link to see if it is correct, but in what you have gone through there is no problem in the format or content of the sentences.You would activate pc9x, it will not harm you and you will have information about who is a node or user.
Possibly Lee can know the cause of what is happening.

Kin EA3CV


De: Rudy Bakalov <r_bakalov at yahoo.com>
Enviado: sábado, noviembre 9, 2024 8:43:39 p. m.
Para: 'The DXSpider Support list' <dxspider-support at tobit.co.uk>; Kin EA3CV <ea3cv at cronux.net>
Asunto: Re: [Dxspider-support] Poorly defined connections?

 Where is the documentation that describes the protocol? I have been unable to locate it.
Here's what I am seeing on my end:

     EA3CV-3 -> 24 PC17^S52NY^S50CLX^H15^

     EA3CV-3 -> 24 PC16^RW3XA-8^RA3WII - 1^H15^

     EA3CV-3 -> 24 PC17^SV2HNC^EA6VQ-1^H15^

     EA3CV-3 -> 24 PC16^EA4URE-2^EA4CZ - 1^EA4IAJ - 1^H15^

     EA3CV-3 -> 24 PC17^K4BSZ^GB7DXG-1^H15^

     EA3CV-3 -> 24 PC41^KB9AIT-6^1^GARY HOEHNE^H25^~

     EA3CV-3 -> 24 PC41^KB9AIT-6^2^NEENAH^H26^~

     EA3CV-3 -> 24 PC19^1^IZ2LSC-99^0^5457^H15^

     EA3CV-3 -> 24 PC61^28094.0^CE6CGX^09-Nov-2024^1940Z^ ^N9MSG^AI9T^140.17787.3^H95^~

     EA3CV-3 -> 24 PC50^EA3CV-2^15^H99^

     EA3CV-3 -> 24 PC61^14240.0^NB9QV^09-Nov-2024^1940Z^USS Cobia Vet Say ses^AJ4BH^VE7CC-1^24.213.122.245^H98^~

     EA3CV-3 -> 24 PC61^1828.4^IZ3NVR^09-Nov-2024^1940Z^ok/om^LY7M^VE7CC-1^83.188.75.252^H98^~

     EA3CV-3 -> 24 PC19^1^IZ3MEZ-8^0^5457^H15^

Rudy N2WQ
    On Saturday, November 9, 2024 at 02:39:09 PM EST, Kin EA3CV <ea3cv at cronux.net> wrote:  
 
 Rudy, but have you analyzed the PC92 sentences you receive from those nodes? Do they reach 5 or 7, or with another value? If you don't get 5 or 7, you have to determine which couple you are getting.For my part, I've analyzed everything I send from EA3CV-3, and how it is received in one of its pairs, and I do not see anything incorrect in the PC92 A, D, C or K. 

Kin EA3CV


De: Rudy Bakalov <r_bakalov at yahoo.com>
Enviado: sábado, noviembre 9, 2024 6:48:34 p. m.
Para: 'The DXSpider Support list' <dxspider-support at tobit.co.uk>
CC: Kin <ea3cv at cronux.net>
Asunto: Re: [Dxspider-support] Poorly defined connections?

 I have an almost perpetual problem with EA3CV-3 (DXS), M0KGX-3 (DXS), and DL9GTB-2 (CCC) that most of the time appear to my cluster N2WQ-1 as users, not nodes. I have defined them as nodes, but the setting does not apply 99% of the time. N2WQ-1 runs CC Cluster.
Rudy N2WQ
    On Saturday, November 9, 2024 at 04:17:20 AM EST, Kin via Dxspider-support <dxspider-support at tobit.co.uk> wrote:  
 
 Hi,

I think I have detected some problems in the information exchanged between
nodes. Possibly as a consequence of an error in the definition of the
neighbour/peer node.

SM7GVF-6 has possibly wrongly defined callsign DL9GTB-1, it should be
DL9GTB-2.
W9TY-1 has possibly wrongly defined callsign K4HNT-1, should be K4HNT-2
IW1QLH-6 has possibly poorly defined callsign NX9G-6, should be NX9G
EI7SDX possibly has ill-defined callsign ON4KST, should be ON4KST-2
ON5MM-2 has possibly ill-defined callsign VK5GR, should be VK5GR-2


The following, I have doubts because I have not been able to trace them:

IW0QNL

1731140467^(chan) <- I HB9VQQ-2 PC92^PY1NB-4^30067^D^^5IW0QNL^H97^
1731115367^(chan) <- I HB9VQQ-2 PC92^PY1NB-4^4967^C^7IW0QNL:5000^H97^

KM3T-5

1731111449^(chan) <- I HB9VQQ-2 PC92^KM3T-10^1049^D^^5KM3T-5^H96^
1731112399^(chan) <- I HB9VQQ-2 PC92^KM3T-10^1999^C^7KM3T-5:5000^H96^

Sysops would be well advised to review their settings. 
In the case of DXSpider, it would be enough to look at its connection file
at: /spider/connect/

73 de Kin EA3CV



_______________________________________________
Dxspider-support mailing list
Dxspider-support at tobit.co.uk
https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
  
  
  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20241109/36cfcd9d/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 1731189624952blob.jpg
Type: image/png
Size: 13258 bytes
Desc: not available
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20241109/36cfcd9d/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 1731189744024blob.jpg
Type: image/png
Size: 37219 bytes
Desc: not available
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20241109/36cfcd9d/attachment-0003.png>

More information about the Dxspider-support mailing list