[Dxspider-support] Corrupted or bad spot?

[Dirk Koopman]

This is what my debug says:

grepdbg 2 JJD0003

04Oct2024 at 11:19:40 (chan) <- I K1TTT 
PC11^28090.0^JJD000390018^04-Oct-2024^1119Z^JN57IW<> tnx ft8, 
SF/H^DL4MFF^EA6VQ-2^H99^~
04Oct2024 at 11:19:40 (pc11) INPUT K1TTT: 
PC11^28090.0^JJD000390018^04-Oct-2024^1119Z^JN57IW<> tnx ft8, 
SF/H^DL4MFF^EA6VQ-2^H98^~ via: K1TTT recurse: 0
04Oct2024 at 11:19:40 (pc11) WAITING K1TTT: NEW PC11 spot 
28090.0|JJD000390018|1728040740|DL4MFF|EA6VQ-2 waiting for a better offer
04Oct2024 at 11:19:41 (chan) <- I GB7DJK 
PC11^28090.0^JJD000390018325018092^ 4-Oct-2024^1119Z^JN57IW<> tnx ft8, 
SF/H^DL4MFF^EA6VQ-2^H22^~
04Oct2024 at 11:19:41 (pc11) INPUT GB7DJK: 
PC11^28090.0^JJD000390018325018092^ 4-Oct-2024^1119Z^JN57IW<> tnx ft8, 
SF/H^DL4MFF^EA6VQ-2^H21^~ via: GB7DJK recurse: 0
04Oct2024 at 11:19:41 (pc11) WAITING GB7DJK: NEW PC11 spot 
28090.0|JJD000390018325018092|1728040740|DL4MFF|EA6VQ-2 waiting for a 
better offer
04Oct2024 at 11:19:42 (pc11) RECURSE K1TTT: PC11 spot 
28090.0|JJD000390018|1728040740|DL4MFF|EA6VQ-2 timed out waiting, resend
04Oct2024 at 11:19:42 (pc11) INPUT K1TTT: 
PC11^28090.0^JJD000390018^04-Oct-2024^1119Z^JN57IW<> tnx ft8, 
SF/H^DL4MFF^EA6VQ-2^H98^~ via: K1TTT recurse: 1
04Oct2024 at 11:19:42 (pc11) PROCESSING K1TTT: PC11 key: 
28090.0|JJD000390018|1728040740|DL4MFF|EA6VQ-2
04Oct2024 at 11:19:42 (progress) SPOT: JJD000390018 on 28090.0 @ 1119Z by 
DL4MFF at EA6VQ-2 'JN57IW<> tnx ft8, SF/H' route: K1TTT
04Oct2024 at 11:19:42 (chan) -> D GB7DJK 
PC11^28090.0^JJD000390018^04-Oct-2024^1119Z^JN57IW<> tnx ft8, 
SF/H^DL4MFF^EA6VQ-2^H98^~
04Oct2024 at 11:19:44 (chan) <- I WR3D PC11^28090.0^JJD000390018325018092^ 
4-Oct-2024^1119Z^JN57IW<> tnx ft8, SF/H^DL4MFF^EA6VQ-2^H21^~
04Oct2024 at 11:19:44 (pc11) INPUT WR3D: 
PC11^28090.0^JJD000390018325018092^ 4-Oct-2024^1119Z^JN57IW<> tnx ft8, 
SF/H^DL4MFF^EA6VQ-2^H20^~ via: WR3D recurse: 0
04Oct2024 at 11:19:44 (pc11) DUPE WR3D PC11 key: 
28090.0|JJD000390018325018092|1728040740|DL4MFF|EA6VQ-2 is saved, ignored
04Oct2024 at 11:19:44 (pc11) RECURSE GB7DJK: PC11 spot 
28090.0|JJD000390018325018092|1728040740|DL4MFF|EA6VQ-2 timed out 
waiting, resend
04Oct2024 at 11:19:44 (pc11) INPUT GB7DJK: 
PC11^28090.0^JJD000390018325018092^ 4-Oct-2024^1119Z^JN57IW<> tnx ft8, 
SF/H^DL4MFF^EA6VQ-2^H21^~ via: GB7DJK recurse: 1
04Oct2024 at 11:19:44 (pc11) PCPROT: Duplicate Spot  GB7DJK: PC11 
28090.0|JJD000390018325018092|1728040740|DL4MFF|EA6VQ-2 ignored

It seems to have come in via protocol and, since I stopped validating 
spot callsigns many years ago when all sorts of weird and wonderful 
"special event" callsigns proliferated, I simply pass through what I 
get. How it is displayed depends on whether one is looking at a "human 
oriented" raw telnet / console feed or using set/ve7cc. Unfortunately, 
because many client programs still insist on parsing the formatted raw 
telnet/console "fixed" format; when the callsign field (in particular) 
overflows - this sort of thing happens. Getting your client program 
author to use set/ve7cc format would solve this sort of thing.

Of course, having "passive" node connections from AR-C (4 in particular) 
software that try to parse the standard "human" fixed format data, when 
fields overflow, then annoyance ensues... Especially as there is no 
chance of fixing it.

73 Dirk G1TLH

On 05/10/2024 08:42, IZ2LSC via Dxspider-support wrote:
> and I guess it was stuck on hamclock...
>
> Andrea
>
> -->
>
>
> Il giorno ven 4 ott 2024 alle ore 20:14 Luigi Carlotto IK5ZUK via 
> Dxspider-support <dxspider-support at tobit.co.uk> ha scritto:
>
>     Hi Keith,
>     me too:
>
>     28090.0 JJD000390018325018092  4-Oct-2024 1119Z JN57IW<> tnx ft8,
>     S<DL4MFF>
>
>     73 Luigi IK5ZUK
>
>
>     Il 04/10/2024 20:06, Keith Maton via Dxspider-support ha scritto:
>>     I had this earlier, is it a bad spot or has it been corrupted in
>>     transit?
>>
>>     73 Keith
>>
>>
>>     DX de DL4MFF:    28090.0  JJD000390018325018092 JN57IW<> tnx ft8,
>>     SF/H 1119Z
>>     —
>>
>>
>>     _______________________________________________
>>     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/20241006/4bf99977/attachment.htm>