[Dxspider-support] sh/dx by ?
Dirk Koopman
djk at tobit.co.uk
Wed Feb 8 11:39:14 GMT 2023
For what it is worth, I get these (identical) results on GB7DJK, WR3D,
GB7BAA and WA9PIE-2.
sh/dx by g6nhu
G1TLH de WA9PIE-2 8-Feb-2023 1121Z dxspider >
14275.0 IK0VSY 31-Dec-2022 1128Z Roberto, very loud, thank
you. <G6NHU>
14207.0 S523PMC 28-Dec-2022 1129Z Joc - SES <G6NHU>
14236.0 OK1NP/P 11-Dec-2022 1058Z FF
<G6NHU>
In order to test this, I generally run up a console, pick a few
callsigns that are spotting, here is a few copy'n'pastes of a console on
GB7DJK
DX de IU5KZF: 14081.1 IU8PAX JM88 1121Z JN53
DX de EA1JW: 28180.0 4S7AB FT4 -13dB IN73GM<>NJ07 NJ07 1122Z
IN82
DX de IZ2FDU: 7187.0 IQ5QO/P 15 1122Z JN55
DX de 9M2LAN: 7026.1 JH1HDT thx fer qso CW 25 1122Z 28
DX de IN3HOT: 7187.0 IQ5QO/P DCI AR087 15 1122Z 15
DX de VE1KF: 21074.0 SP9JBT FT8 Sent: +00 Rcvd: -08 JO90
1122Z FN84
DX de EI9KP: 60013.0 EI1KNH IO54MB<>IO63VE FT8 -4dB 14 1122Z IO54
DX de OM2GM: 21105.0 3Y0J 100 FT8 callers without RX of
3Y0J OK85 1122Z JN87
DX de R1AC: 28492.3 VU2DK 22 1122Z KO59
DX de IK4UXA: 14080.0 II4STL ANNUAL AWARD "MARCONI WAS
HERE!" JN54
1123Z JN54
DX de UN4PG: 21014.1 LZ319TS tnx QSO 20 1123Z MO60
DX de R9CC: 28403.0 ON8ON tnx QSO JO10 1123Z 17
DX de ON4PE: 28430.0 J52EC 58 35 1123Z JO10
DX de RG3Z: 28485.0 9K5LX TNX 73 21 1123Z 16
DX de VE1KF: 21074.5 IZ2SXZ FT8 Sent: +23 Rcvd: +22 JN56
1124Z FN84
DX de SQ2EAR: 21258.0 IU1HGO TNX for QSO 73! JN44 1124Z JO92
DX de LU6YR: 21074.0 R100AE FT8 db-05 From, FF51 1965 Hz TNX
QSO 16 1124Z FF51
DX de SP8QC: 28300.0 EA1MD/P POTA EA-2135 14 1124Z KO10
DX de DD5MD: 28430.0 J52EC 59 TNX QSO Livio! 35 1124Z JO31
DX de EA1DAL: 21105.0 3Y0J circo callers " mad callers" OK85
1125Z IN73
DX de DL2IAJ: 14255.0 2E0FTD/P GFF-337 + LH tnx David 14 1125Z 14
DX de *N8ACP*: 7188.0 KP2J LSB 8 1125Z 4
DX de VE1KF: 21074.5 DH2NJS FT8 Sent: +02 Rcvd: -10 JO50
1125Z FN84
DX de EA1JW: 28178.5 UK8IF FT4 -01dB MM39 1125Z IN82
DX de YT1HA: 24975.0 4X6TT KM72 1126Z KN04
DX de IU5KZF: 14081.1 EA6/DK1XAM 14 1126Z JN53
DX de M0BSV: 24975.0 4X6TT cq dx KM72 1126Z IO92
DX de K5XI: 10136.0 4S7AB NJ07 1126Z DM09
DX de EA1JW: 28178.5 PY2SRB FT4 -15dB GG48 1127Z IN82
DX de VE1KF: 21074.5 DJ4DN FT8 Sent: -14 Rcvd: -01 JO31
1127Z FN84
DX de R1AC: 28480.1 VU2XO 22 1127Z KO59
DX de JA1NVF: 18072.0 3Y0J up QSX 18080.0 TNX OK85 1127Z PM95
DX de W3LPL: 3518.0 BG4GOV Heard in OR 24 1127Z FM19
DX de RA3WII: 24915.0 RN9N FT8 TNX QSO 73! MO64
1127Z KO71
DX de *EA1JW*: 28178.5 OK2BRD FT4 +05dB IN73GM<>JN99 JN99
1127Z IN82
DX de DO5SJ: 28430.0 J52EC tnx 73 35 1128Z 14
DX de VE1KF: 21074.5 DG0OME FT8 Sent: -07 Rcvd: -17 JO51
1128Z FN84
-1128Z------------------------------------------------------------------------------------------------------------------41x147-G1TLH at GB7DJK-500-500
sh/dx by g6nhu
Then pick a few *callsigns* that are spotting on that console screen e.g:
sh/dx by *EA1JW*
G1TLH de GB7DJK 8-Feb-2023 1129Z dxspider >
28178.5 OK2BRD 8-Feb-2023 1127Z FT4 +05dB IN73GM<>JN99 <EA1JW>
28178.5 PY2SRB 8-Feb-2023 1127Z FT4 -15dB <EA1JW>
28178.5 UK8IF 8-Feb-2023 1125Z FT4 -01dB <EA1JW>
28180.0 4S7AB 8-Feb-2023 1122Z FT4 -13dB IN73GM<>NJ07 <EA1JW>
28178.5 E75W 8-Feb-2023 1119Z FT4 +13dB IN73GM<>JN93 <EA1JW>
14078.5 EA3FNZ 8-Feb-2023 1117Z FT4 +03dB DME-22087 <EA1JW>
7130.0 EA2FC 8-Feb-2023 0924Z 59 CBI-305 EFBI-005 DME-48009
<EA1JW>
7185.0 EA1MD/P 8-Feb-2023 0924Z 59 POTA EA-2135 DME-39056 <EA1JW>
18099.0 JA1LSY 8-Feb-2023 0911Z FT8 -08dB IN73GM<>PM95PR <EA1JW>
18099.0 JH0OXS 8-Feb-2023 0909Z FT8 -09dB IN73GM<>PM96 <EA1JW>
or
sh/dx by *N8ACP*
G1TLH de GB7DJK 8-Feb-2023 1130Z dxspider >
7188.0 KP2J 8-Feb-2023 1125Z LSB <N8ACP>
7195.0 PV8AL 8-Feb-2023 1041Z LSB <N8ACP>
7177.0 IK4GRO 8-Feb-2023 0625Z LSB <N8ACP>
14270.0 CE7VP 7-Feb-2023 0017Z USB <N8ACP>
3816.0 W1AW/4 7-Feb-2023 0004Z LSB <N8ACP>
7138.0 SN7D 5-Feb-2023 0551Z LSB <N8ACP>
7165.0 CT2HOV 5-Feb-2023 0549Z LSB <N8ACP>
21300.0 VE7CUP 4-Feb-2023 2351Z USB <N8ACP>
28470.0 VE7JAR 4-Feb-2023 2345Z USB <N8ACP>
18140.0 XE1CIC 4-Feb-2023 2335Z USB <N8ACP>
and so on. My conclusion is that, on the face of what I can see in these
four nodes (as well as GB7TLH), 'sh/by <call>' works.
So we probably need to look somewhere else to find out what is going on.
73 de Dirk G1TLH
On 08/02/2023 10:35, Peter via Dxspider-support wrote:
> Hi
>
> Its working well on DXSpider v1.57 (build 497)
>
> sh/dx by pc2a
> PC2A-3 de PI4CC 8-Feb-2023 1033Z dxspider >
> 14247.0 T77LA 31-Dec-2022 0852Z
> <PC2A>
> 28552.0 PI4CC 11-Dec-2022 0956Z
> <PC2A>
> 28426.5 PI4CC 10-Dec-2022 1450Z
> <PC2A>
> 28416.0 PI4CC 10-Dec-2022 0843Z ARRL 10m
> <PC2A>
>
>
> Peter
> PC2A
>
> Op 8-2-2023 om 11:19 schreef Luc Goeman - ON1GL via Dxspider-support:
>> its not working for me either, seems to me that the 'sh/dx by xxx'
>> and 'sh/dx on xxx' is broken :-(
>>
>> sh/dx by g6nhu
>>
>> ON1GL-2 de ON1GL 8-Feb-2023 1017Z dxspider >
>> DXProt::spawn_cmd: call ON1GL-2 error Subprocesses do not support
>> fork emulation
>>
>> sh/ver
>> DXSpider v1.57 (build 497 git: mojo/378cbf24[r]) using perl v5.32.1
>> on MSWin32
>> Copyright (c) 1998-2023 Dirk Koopman G1TLH
>>
>> 73
>>
>> Luc
>>
>> On 8/02/2023 10:46, Kin via Dxspider-support wrote:
>>> It works for me:
>>>
>>>
>>> sh/ver
>>>
>>> DXSpider v1.57 (build 497 git: mojo/378cbf24[r]) using perl v5.30.3
>>> on Linux
>>>
>>> Copyright (c) 1998-2023 Dirk Koopman G1TLH
>>>
>>> EA3CV de EA3CV-2 8-Feb-2023 0944Z dxspider >
>>>
>>>
>>> sh/dx by g6nhu
>>>
>>> EA3CV de EA3CV-2 8-Feb-2023 0944Z dxspider >
>>>
>>> 14275.0 IK0VSY 31-Dec-2022 1128Z Roberto, very loud, thank
>>> you<G6NHU>
>>>
>>> 14207.0 S523PMC 28-Dec-2022 1129Z Joc -
>>> SES <G6NHU>
>>>
>>> 14236.0 OK1NP/P 11-Dec-2022 1058Z
>>> FF <G6NHU>
>>>
>>>
>>> But do you have history stored in local_data/spots ?
>>>
>>>
>>> Kin EA3CV
>>>
>>>
>>> De: Dxspider-support <dxspider-support-bounces at tobit.co.uk> En
>>> nombre de Keith Maton via Dxspider-support
>>> Enviado el: miércoles, 8 de febrero de 2023 10:41
>>> Para: The DXSpider Support list <dxspider-support at tobit.co.uk>
>>> CC: Keith Maton <g6nhu at me.com>
>>> Asunto: [Dxspider-support] sh/dx by ?
>>>
>>>
>>> Forgive me if I’m wrong but I thought that the sh/dx by [callsign]
>>> command would show spots sent by that callsign.
>>>
>>>
>>> When I try it now, I get the response below.
>>>
>>>
>>> I’m fairly sure this used to work, is anyone seeing the same? I’m on
>>> build 497.
>>>
>>>
>>> Thanks,
>>>
>>>
>>> 73 Keith
>>>
>>>
>>> sh/dx by g6nhu
>>>
>>> G6NHU de G6NHU-2 8-Feb-2023 0935Z dxspider >
>>>
>>> sh/dx: 'by g6nhu' not found
>>>
>>>
>>>
>>> _______________________________________________
>>> 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/20230208/5bca5b54/attachment-0001.htm>
More information about the Dxspider-support
mailing list