[Dxspider-support] [Trouble Ticket #845] DXSpider RTTY Spots

Sat Feb 12 13:15:51 GMT 2022

Human beings never cease to amaze me more and more every day.

We want to have as much information as possible in our window, but our
window has a standard size of 80 columns for all the fields we want to see
simultaneously.
Difficult solution to be able to please everyone without modifying or
losing something.

We are not very flexible and our input is the default complaint.

It is at least surprising that the N1MM developers do not keep track of the
main sources of spots, and in particular of the most used software on the
Net.

Kin EA3CV

El sáb, 12 feb 2022 a las 13:25, Rob Harrison via Dxspider-support (<
dxspider-support at tobit.co.uk>) escribió:

> My response to K3CT (one of the N1MM Dev Team) was:-
>
>
>
> Hi John,
>
> Yes the raw feed from the RTTY Skimmer includes RTTY in the comment field
> however DXSpider (the most popular cluster software) takes the RBN feed and
> reformats the spots to include better information in the comments
> field...... but the mode is written as RTT not RTTY. It would be helpful if
> N1MM  was to recognise the comment RTT as RTTY. Typical output from the
> DXspider cluster RBN version is as below.
>
> The RBN website encourages users to connect to a cluster not the telnet
> feed directly. *"**Our intent is that "retail" DX clusters should connect
> via telnet to one these nodes, and that end-users should connect to the
> "retail" nodes."*
>
> Regards
>
> Rob
>
> DX de DF7GB-#:   14106.3  RW4W         RTT 22dB Q:5* Z:15             1210Z
>
> DX de DO4DXA-#:  21085.6  TF1AM        RTT 16dB Q:3*+ Z:8             1210Z
>
> DX de SQ5M/P-#:   7038.0  PI4CC        CW   5dB Q:9+ Z:14             1210Z
>
> DX de HB9JCB-#:   7035.0  SP1AEN       CW  12dB Q:9+ Z:16             1210Z
>
> DX de HG8A-#:    10115.0  PA/IZ0NGH    CW  12dB Q:8* Z:14,40          1210Z
>
> DX de LY2XW-#:   14026.4  PE1BQE       CW  15dB Q:4* Z:5              1210Z
>
> DX de OE9GHV-#:   7050.4  G0FGI        RTT 29dB Q:3 Z:14              1210Z
>
> DX de OE9GHV-#:  14125.5  LB2TG        RTT 22dB Q:2 Z:14              1210Z
>
> DX de MM0ZBH-#:  10114.0  OM6AN/P      CW  17dB Q:6+ Z:15             1210Z
>
> DX de HA1AG-#:   14044.0  PA2JWN       CW   7dB Q:9*+ Z:20            1210Z
>
> DX de MM0ZBH-#:  21026.1  YO4PX        CW  30dB Q:9* Z:16,17,18       1210Z
>
> DX de DF7GB-#:   14135.3  OH1NOA       RTT 29dB Q:2+ Z:15             1210Z
>
> DX de G4ZFE-#:   14113.2  RL9LR        RTT 20dB Q:8* Z:5,15,16,20     1210Z
>
>
>
>
>
> *From:* Dxspider-support <dxspider-support-bounces at tobit.co.uk> *On
> Behalf Of *Rob Harrison via Dxspider-support
> *Sent:* 12 February 2022 12:21
> *To:* The DXSpider Support list <dxspider-support at dxcluster.org>
> *Cc:* Rob Harrison <g4ujs at outlook.com>
> *Subject:* [Dxspider-support] FW: [Trouble Ticket #845] DXSpider RTTY
> Spots
>
>
>
> Hi All
>
>
>
> See below, I reported to the N1M development team that Spider RBN RTTY
> spots are not recognised.. as RTTY due to RTT not RTTY in the comments… I
> have responded to K3CT with more detail regarding the reformatting of spots
> but we will see. One smart individual said to my post:
>
>
>
> *“**Looks to me as either a bug or faulty design RTTY has been called
> RTTY for over 60 years…*
>
>
>
> *However simple enough, set cluster to reject all spot comments except for
> RTT and then set N1MM to accept everything it receives.*
>
>
>
> *Alternative use a DX cluster that does not change RTTY to RTT.”*
>
>
>
> Not really useful….. Dirk it maybe useful if you emailed N1MM
>
>
>
> 73 Rob G4UJS
>
>
>
> *From:* N1MM TroubleTicket <Support at hamdocs.com>
> *Sent:* 12 February 2022 11:11
> *To:* rob.harrison at mis-specialists.co.uk
> *Subject:* [Trouble Ticket #845] DXSpider RTTY Spots
>
>
>
> *k3ct* wrote:
>
> We have a note in the source code that the rtty skimmer includes “RTTY” in
> the comment field.
>
> Could be a bug in the cluster software?
>
> John, K3CT
>
>
> https://n1mmwp.hamdocs.com/support/trouble-ticket/?support_page=open_ticket&ticket_id=845&auth_code=ZyKIRJbpfY
> <https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fn1mmwp.hamdocs.com%2Fsupport%2Ftrouble-ticket%2F%3Fsupport_page%3Dopen_ticket%26ticket_id%3D845%26auth_code%3DZyKIRJbpfY&data=04%7C01%7C%7Cc2584ad8e9144ca641b108d9ee223172%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637802652896299244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=DHIrISxHsiQvF2hAsq2m3Lgf4DiWbejhNsLwME2oO7g%3D&reserved=0>
> ------------------------------
>
> *G4UJS* *2022/02/12 04:23:53*(reply)
>
> Additional information. DXSpider reformats RBN spots, this is what the
> output looks like.
>
> DX de F6IIT-#: 7020.0 ON75ODE CW 31dB Q:9+ Z:15 0922Z
> DX de OH2BBT-#: 14090.0 9A5D RTT 49dB Q:8+ Z:20 0922Z
> DX de G4ZFE-#: 21101.8 UA3QJJ RTT 15dB Q:2 Z:20 0922Z
> DX de DE1LON-#: 21088.0 9A1A RTT 16dB Q:2+ Z:16 0922Z
> DX de DE1LON-#: 21116.8 R9OK RTT 24dB Q:2+ Z:20 0920Z
>
> 73 de Rob G4UJS
> ------------------------------
>
> *G4UJS* *2022/02/11 19:58:30*(report)
>
> RTTY RBN spots from DXSpider are identified by RTT as the first 3
> characters of the comments field.
>
> N1MM doesn't seem to identify these RTTY spots as RTTY spots!!
>
> Can this be adjusted please?
>
> 73 de Rob G4UJS
>
> If you have further queries on this ticket, please respond on-line by
> clicking on the link above.
>
> DO NOT REPLY to this email... it will fall into the email bit bucket!
> _______________________________________________
> 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/20220212/7026090f/attachment.htm>