[Dxspider-support] Suggestions for a future PC-spot

[Kin]

And we can take a big step forward:

Instead of maintaining the rigidity of "^"s with fields in a fixed position
and of fixed length, we can migrate to a flexible system: the JSON format.
This would allow us to evolve seamlessly in the future, adding any field we
want.
And it would be used bidirectionally if set/dxspider is used.

Who's bidding?

Continuing...

Kin EA3CV


-----Mensaje original-----
De: Dxspider-support <dxspider-support-bounces at tobit.co.uk> En nombre de Kin
via Dxspider-support
Enviado el: miércoles, 9 de abril de 2025 13:23
Para: 'The DXSpider Support list' <dxspider-support at tobit.co.uk>
CC: Kin <ea3cv at cronux.net>
Asunto: [Dxspider-support] Suggestions for a future PC-spot

Hi,

1. Add a comment subfield with the "mode" and create a file with the mode
tags to normalize them (sh/modes????).
This would help a lot when creating better filters.
Users could use it along with the "freq" to make their automatic selections
in third-party software.
2. To make it truly functional, a set/dxspider command could be created,
similar to set/ve7cc, that would provide an extended format with the new
field.
Something like DXnn or DSnn or DXSnn, ... (just imagine).
If this is promoted to the software developers, I'm sure they'd welcome it.
3. The "DX" command would have to be modified, but I'm sure it wouldn't be a
problem for Dirk.
4. Since I imagine PC61 will be maintained for compatibility, the fields
would be merged in this sentence.
5. Since a new command is being created, some more empty fields can be
created, considering the future.
6. Possibility of including a byte of spot quality, which would be sent in
the assumed DXnn and in the PC61 (perhaps along with the origin ???)

Others.

1. Something I miss is that timestamp doesn't display up to milliseconds. I
haven't checked if this is useful for the PC92 sequence, but if it is, it
would be great.
In the log files, it would be very useful for trace analysis, as it provides
greater precision.
2. Following the same line of thought, it could be added the cnum to "chan",
so that a specific channel can be traced from the beginning.
3. If the logging is maintained as it is: When a user registers, all
possible SSIDs for that user should be registered.
4. Same for the password in all user variants.

What do you think?

Kin EA3CV



_______________________________________________
Dxspider-support mailing list
Dxspider-support at tobit.co.uk
https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support