[Dxspider-support] Strange behaviour with sh/dx command HB9ON-8 Node

[Dirk Koopman]

It is possible that there was some error or other introduced during the 
WWA debacle. But that seems now to be fixed (in test).

On GB7DJK:

sh/dx 4u1
G1TLH de GB7DJK  4-Feb-2025 1517Z dxspider >
   28372.0 4U1A         4-Feb-2025 1516Z 59++ near Boston <NA1R>
   29372.0 4U1A         4-Feb-2025 1514Z 59++ near Boston <NA1R>
   28372.0 4U1A         4-Feb-2025 1510Z 20 over signal in New Orleans 
<KC5PL>
   28372.0 4U1A         4-Feb-2025 1510Z <N8YBY>
   28372.0 4U1A         4-Feb-2025 1508Z call dx <CX3AT>
   28372.0 4U1A         4-Feb-2025 1458Z <KA8Q>
   28372.0 4U1A         4-Feb-2025 1455Z <KB7TGR>
   28372.0 4U1A         4-Feb-2025 1455Z Op: John N4TII <YL2QN>
   28372.0 4U1A         4-Feb-2025 1448Z 5/9 tks <VE3YW>
   28372.0 4U1A         4-Feb-2025 1443Z

sh/dx hb9
G1TLH de GB7DJK  4-Feb-2025 1518Z dxspider >
   24946.0 HB9ETH       4-Feb-2025 1511Z balcony longwire antenna test 
<HB9ETH>
   18151.4 HB9ETH       4-Feb-2025 1445Z balcony longwire antenna test 
<HB9ETH>
   21140.0 HB9LEU       4-Feb-2025 1400Z FT4 -09dB 1497Hz <YC1JEL>
   10119.0 HB9DGV/P     4-Feb-2025 1341Z SOTA <HA8WX>
   14044.0 HB9BIN/P     4-Feb-2025 1330Z HBFF-0374 SOTA VD-042 <EA1EV>
   10119.0 HB9DGV/P     4-Feb-2025 1326Z SOTA HB/BE-165 <EI2KC>
   28022.2 HB9DAX       4-Feb-2025 1314Z <RZ9YI>
   14044.0 HB9BIN/P     4-Feb-2025 1313Z hbff-0374 +sota <OH1MM>
  432480.0 HB9G/B       4-Feb-2025 1255Z 519 qsb <F5DQK>
  432432.0 HB9F/B       4-Feb-2025 1255Z 529-539 <F5DQK>


Dirk G1TLH

On 04/02/2025 15:04, Keith, G6NHU via Dxspider-support wrote:
> This does feel as though the behaviour has changed, I often do an 
> sh/dx with a partial callsign and it’s always worked.  Now it doesn’t.
>
> *sh/dx hb9*
> *G6NHU de G6NHU-2  4-Feb-2025 1502Z dxspider >*
> *  sh/dx: ‘hb9' not found*
>
>
> 73 Keith G6NHU
> On 4 Feb 2025 at 14:54 +0000, HB9DHG Fulvio via Dxspider-support 
> <dxspider-support at tobit.co.uk>, wrote:
>> Thanks, everyone!
>> Kin, it works just as Jan said, but this behavior seems like a small 
>> bug to me. :)
>> Anyway, it's not a big deal—I just wanted to keep the group informed!
>> Keep up the good work guys!
>> 73 de HB9DHG Fulvio
>>
>> sh/ver
>> DXSpider v1.57 (build 562 git: mojo/691ed8f6[r]) using perl v5.40.0 
>> on Linux
>> Copyright (c) 1998-2025 Dirk Koopman G1TLH
>>
>> On Tue, Feb 4, 2025 at 3:33 PM Jan via Dxspider-support 
>> <dxspider-support at tobit.co.uk> wrote:
>>
>>     I see the same here
>>     Sh/dx 4u1 gives 4u1 not found
>>     However sh/dx 4u1a shows all dx with 4u1a
>>     So it look like you cannot do a sh/dx on a prefix
>>
>>     73
>>     Jan
>>     PA4JJ
>>
>>     Op 4-2-2025 om 15:13 schreef HB9DHG Fulvio via Dxspider-support:
>>>
>>>     I have a strange issue with the latest Mojo releases. I don't
>>>     know if it's just on my end, but when I used to run the
>>>     command|sh/dx hb9|, it would list all the HB9 stations that had
>>>     been spotted. Now, however, I receive this message:
>>>
>>>     sh/dx: 'hb9'not found
>>>
>>>     This happens with other prefixes as well.
>>>
>>>     Here is part of the help for|SHOW/DX|:
>>>
>>>     SH/DX 9m0
>>     |SH/DX on 20m info iota SH/DX 9a on vhf day 30 SH/DX rf1p qsl
>>     SH/DX iota SH/DX iota eu-064 SH/DX qra jn86 SH/DX dxcc oq2 SH/DX
>>     dxcc oq2 by w dxcc SH/DX zone 4,5,6 SH/DX by_zone 4,5,6|
>>
>> If I run the command |SH/DX iota|, I get this error message:
>>
>> sh/dx iota
>> |sh/dx parse error '1' token 'iota|' not recognised |
>>
>> What am I doing wrong?
>>
>> Thanks for shedding some light on this :)
>>
>> --
>>
>>
>> 	
>> *HB9DHG*
>> Fulvio Galli
>> CWops #2889
>> High Speed Telegraphy Swiss Team
>> 2018/2022 WRTC Referee
>> https://www.qrz.com/db/hb9dhg
>> https://hb9dhg.net
>> + 41 79 640 23 81
>>
>>
>> _______________________________________________
>> Dxspider-support mailing list
>> Dxspider-support at tobit.co.uk
>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>>
>> --
>> ____________________________________________________
>> my dxspider clusters running on a raspberry pi:
>> pa4jj-2 77.174.195.163 port 7300
>> pa4jj-3 77.174.195.163 port 7388
>> _______________________________________________
>> Dxspider-support mailing list
>> 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
>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>
> _______________________________________________
> 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/20250204/697e1211/attachment-0001.htm>