[Dxspider-support] New version of Mojo (dx command fixed)
Kin
ea3cv at cronux.net
Fri Jan 31 08:03:27 GMT 2025
Sorry, bad copy for me.
This is correct:
* Behavior of ANN Transmission
1. If I run from the console:
ann full Test Ignore Please
I get the echo:
ann full 560 Test Ignore Please
2. If I run sh/ann, it does not appear in the list.
3. If I run sh/ann EA3CV, I get:
31Jan2025 at 07:04:28 EA3CV -> * 560 Test Ignore Please
4. If I run sh/ann from another node with a build <> 560, the announcement does not appear.
5. In debug/2025/031.dat:
1738307068769^(chan) <- I EA3CV ann full 560 Test Ignore Please
1738307068770^(*) PC93 sent from EA3CV-8 ignored as this channel is not yet initialised (state: DXProt=HASH(0x55c5bd16a018)-{state})
* Behavior of SPOT Transmission
1. If I run from the console:
dx 28000 EA0BB 560 Test Ignore 3
I get the echo:
DX de EA3CV: 28000.0 EA0BB 560 Test Ignore 3 0731Z
2. If I run sh/dx, the spot does not appear.
3. If I run sh/dx by EA3CV, I get:
sh/dx: 'by EA3CV' not found
4. If I run sh/dx by EA3CV from another node with a build <> 560, I get:
28000.0 EA0BB 31-Jan-2025 0731Z 560 Test Ignore 3 <EA3CV>
5. In spots/2025/031.dat, there is no entry for this spot.
Kin
De: Dxspider-support <dxspider-support-bounces at tobit.co.uk> En nombre de Kin via Dxspider-support
Enviado el: viernes, 31 de enero de 2025 8:57
Para: 'The DXSpider Support list' <dxspider-support at tobit.co.uk>; 'Keith, G6NHU' <g6nhu at me.com>
CC: Kin <ea3cv at cronux.net>
Asunto: Re: [Dxspider-support] New version of Mojo (dx command fixed)
Hi,
My test with Buid 560
* Behavior of ANN Transmission
1. If I run from the console:
ann full Test Ignore Please
I get the echo:
ann full 560 Test Ignore Please
2. If I run sh/ann, it does not appear in the list.
3. If I run sh/ann EA3CV, I get:
31Jan2025 at 07:04:28 EA3CV -> * 560 Test Ignore Please
4. If I run sh/ann from another node with a build <> 560, the announcement does not appear.
5. In debug/2025/031.dat:
1738307068769^(chan) <- I EA3CV ann full 560 Test Ignore Please
1738307068770^(*) PC93 sent from EA3CV-8 ignored as this channel is not yet initialised (state: DXProt=HASH(0x55c5bd16a018)-{state})
* Behavior of SPOT Transmission
1. If I run from the console:
dx 28000 EA0BB 560 Test Ignore 3
I get the echo:
DX de EA3CV: 28000.0 EA0BB 560 Test Ignore 3 0731Z
2. If I run sh/dx, the spot does not appear.
3. If I run sh/dx EA3CV, I get:
sh/dx: 'EA3CV' not found
4. If I run sh/dx from another node with a build <> 560, I get nothing.
5. In spots/2025/031.dat, there is no entry for this spot.
1738308708569^(chan) <- I EA3CV dx 28000 EA0BB 560 Test Ignore 3
1738308708570^(*) spotter EA3CV/EA3CV
1738308708571^(spotdup) Spot::dup: freq=28000 call=EA0BB d=1738308660 text='560 Test Ignore 3' by=EA3CV node=EA3CV-8 jf=1
1738308708571^(spotdup) Spot::dup ldupkey XEA0BB|EA3CV|28000|1738308600||560TESTIGNORE3 t '0' NEW
1738308708571^(spotdup) Spot::dup (OTEXT) ldupkey XEA0BB|EA3CV|28000|1738308600|560 TEST IGNORE t '0' NEW
1738308708572^(chan) -> X EA3CV DX de EA3CV: 28000.0 EA0BB 560 Test Ignore 3 0731Z
1738308708572^(spotdup) Spot::dup: freq=28000.0 call=EA0BB d=1738308660 text='560 Test Ignore 3' by=EA3CV node=34 jf=1
1738308708572^(spotdup) Spot::dup ldupkey XEA0BB|EA3CV|28000|1738308600||560TESTIGNORE3 t '0' NEW
1738308708572^(spotdup) Spot::dup (OTEXT) ldupkey XEA0BB|EA3CV|28000|1738308600|560 TEST IGNORE t '0' NEW
1738308708572^(spotdup) Spot::dup: freq=28000.0 call=EA0BB d=1738308660 text='560 Test Ignore 3' by=EA3CV node=34
1738308708572^(spotdup) Spot::dup ldupkey XEA0BB|EA3CV|28000|1738308600||560TESTIGNORE3 t '0' NEW
1738308708572^(spotdup) Spot::dup (OTEXT) ldupkey XEA0BB|EA3CV|28000|1738308600|560 TEST IGNORE t '0' NEW
1738308708572^(chan) -> D EA2CW-1 PC61^28000.0^EA0BB^31-Jan-2025^0731Z^560 Test Ignore 3^EA3CV^EA3CV-8^172.18.0.2^H30^~
1738308708572^(chan) -> D PY1NB-4 PC61^28000.0^EA0BB^31-Jan-2025^0731Z^560 Test Ignore 3^EA3CV^EA3CV-8^172.18.0.2^H30^~
1738308708572^(progress) CMD: 'dx 28000 EA0BB 560 Test Ignore 3' by EA3CV ip: 127.0.0.1 2mS
Conclusion:
ANN sending fails.
Sending of SPOTs is correct.
Kin EA3CV
De: Dxspider-support <dxspider-support-bounces at tobit.co.uk <mailto:dxspider-support-bounces at tobit.co.uk> > En nombre de Dirk Koopman via Dxspider-support
Enviado el: jueves, 30 de enero de 2025 23:28
Para: Keith, G6NHU <g6nhu at me.com <mailto:g6nhu at me.com> >; The DXSpider Support list <dxspider-support at tobit.co.uk <mailto:dxspider-support at tobit.co.uk> >
CC: Dirk Koopman <djk at tobit.co.uk <mailto:djk at tobit.co.uk> >
Asunto: Re: [Dxspider-support] New version of Mojo (dx command fixed)
I am confused. And it's late.
Are you saying that connecting via telnet and then sending a dx command that then echos the formatted spot and this is wrong? Because, according to versions before I starting messing with this, this was the behaviour that I see.
I have checked out the version dated Mon Jun 17 14:42:16 2024 +0100
And, connected via telnet I see this:
G1TLH de GB7TLH 30-Jan-2025 2157Z dxspider >
dx 7211 g7brn test
DX de G1TLH: 7211.0 G7BRN test 2158Z
G1TLH de GB7TLH 30-Jan-2025 2158Z dxspider >
and on the version 560 I see this:
G1TLH de GB7TLH 30-Jan-2025 2203Z dxspider >
dx 7120 g1tlh test
DX de G1TLH: 7120.0 G1TLH test 2203Z
I have just sent these spots from a telnet session for G1TLH and G7BRN and they all appeared on my console:
DX de G7BRN: 7203.0 G1TLH test 10 IO90 2211Z JO02
DX de G1TLH: 7201.0 G1TLH test 12 IO90 2212Z IO90
DX de G1TLH: 7011.0 G1TLH test 13 IO90 2221Z IO90
It's late, I cannot count.
You should be able to see these (+ a couple of others) with a 'sh/dx 5 call g1tlh or call g7brn ' as I can on several nodes not directly connected to me.
Dirk G1TLH
On 30/01/2025 19:55, Keith, G6NHU wrote:
Updated to 560. Note, all these different nodes I’m checking are node partners.
Logged on to my cluster via telnet as G0PKT and sent a self spot.
dx 7074 g0pkt test, please ignore
DX de G0PKT: 7074.0 G0PKT test, please ignore JO01 1919Z JO01
G0PKT de G6NHU-2 30-Jan-2025 1919Z dxspider >
As you can see, it was echoed straight back to me.
I then switched to my console window
sh/dx g0pkt
G6NHU de G6NHU-2 30-Jan-2025 1919Z dxspider >
7074.0 G0PKT 21-Jan-2025 1440Z test <G0PKT>
So the spot I sent at 1919z isn’t shown.
I switched back to the telnet session and sent a spot for G6NHU which was again echoed straight back to me.
dx 7074 g6nhu test, please ignore
DX de G0PKT: 7074.0 G6NHU test, please ignore JO01 1921Z JO01
Going back to the console window.
sh/dx g6nhu
G6NHU de G6NHU-2 30-Jan-2025 1921Z dxspider >
7074.0 G6NHU 30-Jan-2025 1659Z test <G0PKT>
It’s not there.
These are the two spots I’ve just submitted.
DX de G0PKT: 7074.0 G0PKT test, please ignore JO01 1919Z JO01
DX de G0PKT: 7074.0 G6NHU test, please ignore JO01 1921Z JO01
I can see that MX0NCA-2 has also updated to build 560.
rcmd MX0NCA-2 sh/dx g0pkt
RCMD 'sh/dx g0pkt' sent to MX0NCA-2
MX0NCA-2:sh/dx: 'g0pkt' not found
rcmd MX0NCA-2 sh/dx g6nhu
RCMD 'sh/dx g6nhu' sent to MX0NCA-2
MX0NCA-2:sh/dx: 'g6nhu' not found
G1FEF-2 is running build 559, both spots are there.
rcmd G1FEF-2 sh/dx g6nhu
RCMD 'sh/dx g6nhu' sent to G1FEF-2
G1FEF-2: 7074.0 G6NHU 30-Jan-2025 1921Z test, please ignore <G0PKT>
rcmd G1FEF-2 sh/dx g0pkt
RCMD 'sh/dx g0pkt' sent to G1FEF-2
G1FEF-2: 7074.0 G0PKT 30-Jan-2025 1919Z test, please ignore <G0PKT>
W9AEK is using build 499, both spots are there.
rcmd W9AEK sh/dx g6nhu
RCMD 'sh/dx g6nhu' sent to W9AEK
W9AEK: 7074.0 G6NHU 30-Jan-2025 1921Z test, please ignore <G0PKT>
rcmd W9AEK sh/dx g0pkt
RCMD 'sh/dx g0pkt' sent to W9AEK
W9AEK: 7074.0 G0PKT 30-Jan-2025 1919Z test, please ignore <G0PKT>
R5ACQ-1 has also updated to build 560, both spots are there.
rcmd R5ACQ-1 sh/dx g6nhu
RCMD 'sh/dx g6nhu' sent to R5ACQ-1
R5ACQ-1: 7074.0 G6NHU 30-Jan-2025 1921Z test, please ignore <G0PKT>
rcmd R5ACQ-1 sh/dx g0pkt
RCMD 'sh/dx g0pkt' sent to R5ACQ-1
G6NHU de G6NHU-2 30-Jan-2025 1937Z dxspider >
R5ACQ-1: 7074.0 G0PKT 30-Jan-2025 1919Z test, please ignore <G0PKT>
I don’t know why they’re not showing on MX0NCA-2 or my own node but they seem to be appearing on others.
So I’ve logged on to F1FCA-2 who is running build 560 as G0PKT and sent a spot.
As you can see, it was echoed back.
G0PKT de F1FCA-2 30-Jan-2025 1944Z dxspider >
dx g6nhu 7074 Testing, ignore me.
DX de G0PKT: 7074.0 G6NHU Testing, ignore me. 1944Z
But if I immediately check, it’s not there, although my spot from earlier was.
sh/dx g6nhu
G0PKT de F1FCA-2 30-Jan-2025 1945Z dxspider >
7074.0 G6NHU 30-Jan-2025 1921Z test, please ignore <G0PKT>
When I check my own node via the console, the spot I posted from F1FCA-2 is there.
sh/dx g6nhu
G6NHU de G6NHU-2 30-Jan-2025 1946Z dxspider >
7074.0 G6NHU 30-Jan-2025 1944Z Testing, ignore me. <G0PKT>
Hopefully all this is coming through OK and that the mailing list doesn’t strip out the bold text as it should make it easier to read.
It looks to me as though spots are being accepted and passed on but still not being displayed or saved locally. MX0NCA-2 is doing something very odd by not showing any of them but the rest are all behaving the same. The text with F1FCA-2 shows the same symptoms as when I submit spots locally, they’re passed on but not saved locally.
73 Keith G6NHU
On 30 Jan 2025 at 18:00 +0000, Dirk Koopman via Dxspider-support <mailto:dxspider-support at tobit.co.uk> <dxspider-support at tobit.co.uk>, wrote:
I have uploaded a new version of the code. Please update and try again.
Dirk
On 2025-01-30 17:07, Keith, G6NHU via Dxspider-support wrote:
To test this further, I've just logged onto one of my partner nodes (MX0NCA-2) as G0PKT. This node is running build 559.
The spots I've sent today from my node of G0PKT don't show on his node.
Now I've submitted a spot on his node
'dx 7074 g6nhu test'
Then tried to look for it
'sh/dx g6nhu'
sh/dx: 'g6nhu' not found
When I do the same check on my node, the spot isn't there.
When I look on PI4CC who is running build 547, the spot is there.
Checking another node running build 559 (R5ACQ-1), the spot is missing as well.
These aren't self spots, this is just normal spotting. I'm convinced something isn't right.
73 Keith G6NHU
On 30 Jan 2025 at 14:58 +0000, Keith, G6NHU via Dxspider-support <mailto:dxspider-support at tobit.co.uk> <dxspider-support at tobit.co.uk>, wrote:
I already have that variable set, I've had it configured that way since March 2023!
If you notice, some of those spots aren't self spots. Some were (G0PKT spotting itself) but others that don't appear locally were G6NHU spotting G0PKT.
There are no instances of 'swore' in the debug log and no instances of 'trying to self spot' either.
73 Keith G6NHU
On 30 Jan 2025 at 14:25 +0000, Dirk Koopman via Dxspider-support <mailto:dxspider-support at tobit.co.uk> <dxspider-support at tobit.co.uk>, wrote:
Which means that you are probably getting a message like this in the debug:
(DXCommand) G1TLH-2 swore: 7050 g1tlh (with words:G1TLH)
(*) spotter G1TLH/G1TLH
(DXCommand) G1TLH/G1TLH trying to self spot below 1240000KHz (7050 g1tlh) from 82.68.205.1, not passed on to cluster
I treat self spotting as "swearing" so it dumps you off after three (configurable) attempts.
My memory is not what it was, but I am still detecting a silent majority of sysops not liking self-spotting.
As it's getting near to contest time, I am holding off any more updates that alter the main code so you will have to set $Spot::minselfspotqrg = 0 if that's what you want to allow on your node. This only affects locally connected users, not any incoming spots.
Dirk G1TLH
On 30/01/2025 13:33, Keith, G6NHU via Dxspider-support wrote:
Considering this is where this all started from with the discussion about self spotting, I noticed this.
sh/var $Spot::minselfspotqrg
$Spot::minselfspotqrg = 1240000
Shouldn't the default be 0 now as per this: https://mailman.tobit.co.uk/pipermail/dxspider-support/2023-March/018036.html ?
73 Keith G6NHU.
On 30 Jan 2025 at 13:17 +0000, Keith, G6NHU via Dxspider-support <mailto:dxspider-support at tobit.co.uk> <dxspider-support at tobit.co.uk>, wrote:
I'm not sure it's quite right.
I sent some test self spots from within a normal telnet session.
So this is G0PKT self spotting and also G6NHU sending spots for G0PKT.
When I do a sh/dx g0pkt, from the telnet session, this is what I see. The spot isn't showing.
sh/dx g0pkt
G0PKT de G6NHU-2 30-Jan-2025 1308Z dxspider >
7074.0 G0PKT 21-Jan-2025 1440Z test <G0PKT>
I see the same if I do the same command from a console session.
However, if I do an rcmd to one of my partners, the test spots I made from both G0PKT and from G6NHU show.
rcmd pi4cc sh/dx g0pkt
RCMD 'sh/dx g0pkt' sent to PI4CC
G6NHU de G6NHU-2 30-Jan-2025 1308Z dxspider >
PI4CC: 7074.0 G0PKT 30-Jan-2025 1245Z test <G0PKT>
PI4CC: 7074.0 G0PKT 30-Jan-2025 1238Z test <G0PKT>
PI4CC: 7074.0 G0PKT 30-Jan-2025 1237Z <G6NHU>
PI4CC: 7074.0 G0PKT 30-Jan-2025 1214Z <G6NHU>
PI4CC: 7074.0 G0PKT 21-Jan-2025 1440Z test <G0PKT>
Here's the same command locally in the console.
sh/dx g0pkt
G6NHU de G6NHU-2 30-Jan-2025 1311Z dxspider >
7074.0 G0PKT 21-Jan-2025 1440Z test <G0PKT>
It's as though the spots have been sent but not shown or stored locally.
Can anyone test the same please, post some spots and then see if they are shown on the local node as well as remote ones.
73 Keith G6NHU (signing posts with my callsign now as there seem to be about three Keiths on here!).
On 30 Jan 2025 at 11:57 +0000, Dirk Koopman via Dxspider-support <mailto:dxspider-support at tobit.co.uk> <dxspider-support at tobit.co.uk>, wrote:
Please update in the normal way. This was an error inside the dx command
caused by me changing a naming convention. As always: more thought (and
better testing) required...
You don't need to restart. The fix will be picked up automatically when
you next enter a dx command.
Dirk G1TLH
On 30/01/2025 11:30, Mike G3YPP via Dxspider-support wrote:
How do we update the (mn) node command that Kin mentions. My node will not send spots
Mike G3YPP
Sent from my iPhone
On 30 Jan 2025, at 10:03, dxspider-support-request at tobit.co.uk <mailto:dxspider-support-request at tobit.co.uk> wrote:
Re: [Dxspider-support] New version of Mojo
_______________________________________________
Dxspider-support mailing list
Dxspider-support at tobit.co.uk <mailto:Dxspider-support at tobit.co.uk>
https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
_______________________________________________
Dxspider-support mailing list
Dxspider-support at tobit.co.uk <mailto:Dxspider-support at tobit.co.uk>
https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
_______________________________________________
Dxspider-support mailing list
Dxspider-support at tobit.co.uk <mailto:Dxspider-support at tobit.co.uk>
https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
_______________________________________________
Dxspider-support mailing list
Dxspider-support at tobit.co.uk <mailto:Dxspider-support at tobit.co.uk>
https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
_______________________________________________
Dxspider-support mailing list
Dxspider-support at tobit.co.uk <mailto:Dxspider-support at tobit.co.uk>
https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
_______________________________________________
Dxspider-support mailing list
Dxspider-support at tobit.co.uk <mailto:Dxspider-support at tobit.co.uk>
https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
_______________________________________________
Dxspider-support mailing list
Dxspider-support at tobit.co.uk <mailto:Dxspider-support at tobit.co.uk>
https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
_______________________________________________
Dxspider-support mailing list
Dxspider-support at tobit.co.uk <mailto: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/20250131/632c643b/attachment-0001.htm>
More information about the Dxspider-support
mailing list