[Dxspider-support] dx command actions + announce problems + links + who commands

[Dirk Koopman]

I'm afraid announces are still a work in progress. For instance the 
deduping will detect duplicate announces but instead of a "Sorry, this 
is a duplicate" it simply gives you a prompt. But I cannot reproduce 
your results here. As this is a fairly major contest weekend, I am not 
going publish any further changes until next week. But I *do* want to 
get this deduping right.

The generating machine (G1TLH-2 at GB7TLH):

ann local this is a test 1
To LOCAL de G1TLH-2: this is a test 1
G1TLH-2 de GB7TLH 31-Jan-2025 2232Z dxspider >
ann local this is a test 2
To LOCAL de G1TLH-2: this is a test 2
G1TLH-2 de GB7TLH 31-Jan-2025 2232Z dxspider >
DX de AC2PB:     10136.0  R3LC         73 Sergei KO64 2232Z FN20
ann local this is a test 3
To LOCAL de G1TLH-2: this is a test 3
G1TLH-2 de GB7TLH 31-Jan-2025 2232Z dxspider >

Another user (G7BRN at GB7TLH):

DX de SM3XGV:    14076.4 WX0Z 4 2232Z 14
To LOCAL de G1TLH-2: this is a test 1
To LOCAL de G1TLH-2: this is a test 2
DX de AC2PB:     10136.0  R3LC         73 Sergei 16 2232Z  5
DX de IU0PXQ:     3614.0  II0WWA       SSB tu! 15 2232Z 15
To LOCAL de G1TLH-2: this is a test 3
DX de IK1SOW:     7035.0  II1WWA       PSK TNX

Dirk

PS announce always defaults to local so the 'local' keyword is optional.

On 31/01/2025 20:47, Martin Davies G0HDB wrote:
> On 31 Jan 2025 at 17:16, ken Sharman via Dxspider-support wrote:
>
>> Hi Keith G6NHU
>> Tested both on my test spider
>> Announce and Announce/full are both working in build 526
>>   
>> 73 Ken G7VJA
>> GB7HTL
> Hello Ken, did you test the Announce function by sending several separate announcements?
>
> Earlier today, after I'd updated the GB7DXC-5 node to build 562, I did a single-line test
> announcement from the G0HDB-2 sysop console; the announcement seemed to have been
> sent successfully and was received and displayed on my telnet-connected G0HDB 'user'
> console.
>
> I then tried to send a series of announcements each of which was <80 characters long.  As
> can be seen in the extract below the first two messages went out to LOCAL and were
> received and displayed on my G0HDB user console but then the third announcement didn't
> go to LOCAL.  Instead it went to '*' and didn't appear on the user console.  A further two
> announcements did get sent to LOCAL and appeared on the user console.
>
> 31Jan2025 at 14:50:40 G0HDB-2 -> LOCAL
> 31Jan2025 at 14:51:04 G0HDB-2 -> LOCAL
> 31Jan2025 at 14:51:28 G0HDB-2 -> *
> 31Jan2025 at 14:51:47 G0HDB-2 -> LOCAL
> 31Jan2025 at 14:52:14 G0HDB-2 -> LOCAL
>
> It would seem that there's something still not quite right with the Announce function which is
> causing some messages to not be sent correctly to LOCAL but are instead going to '*'
> wherever that is!
>
> I haven't tried the Announce/Full option to see if the same behaviour happens.
>
> --
> 73, Martin G0HDB
>
>