[Dxspider-support] R: R: AGN R: Problem new build 360 With RXCLUS program Logged IN every 6 minutes

[ik5pwj at gmail.com]

I would like to clarify that the problem .... let's call it that arose on some programs that manage the right spots for checking the various degrees. 

Any terminal with no problems receives commercials and that's it. 

Not being a programmer, I can't go into what Dirk wrote, but I understand the meaning of his msg. and therefore improving the various protocols is certainly a positive thing.

If this were to happen for commercial programs, it would be logical to have, before making substantial changes that could affect the functioning of programs connected to it, solutions to the problem created. 

 

So I fully understand Dirk that you want to improve things, and it will be up to you to decide, as you seem to have already written, what you will do in the next few days.

Then the others (HB9BZA etc.) will adapt ...

At the moment, having seen the problems created, I returned to vers. 157 build 342 if then Dirk will make a temporary update to return to the old system, I will do the update before the next Contest.

Thanks

73 Alex ik5pwj

 

Da: Dxspider-support <dxspider-support-bounces at tobit.co.uk> Per conto di Dirk Koopman via Dxspider-support
Inviato: giovedì 25 novembre 2021 16:02
A: dxspider-support at tobit.co.uk
Cc: Dirk Koopman <djk at tobit.co.uk>
Oggetto: Re: [Dxspider-support] R: AGN R: Problem new build 360 With RXCLUS program Logged IN every 6 minutes

 

On 25/11/2021 08:43, Alex via Dxspider-support wrote:Hi Luigi and all, 

I received the answer from Robert HB9BZA and below I report what he wrote to me. 
I hope he can solve the problem but I'm not sure if he can do it in a short time.
 
here is Robert HB9BZA's answer:
Hi Alex,
Thanks for reporting this problem.
The change made in the latest version of dxspider makes received DX spots to be no more identified as such, so they are only displayed in the terminal 1 to 4 (which display all text they received), but not on the DX, Alarm and LoTW windows, and they wont trigger any alarm as they are not DX spots for RXCLUS.
At my humble opinion, this change is a very poor idea which will break the compatibility of dxspider with many client programs without bringing much to the users.
About RXCLUS, I must tell you this software is now only minimally maintained and supported, as I have no more time for this project.
I will see if I can do something, but don't expect it to be quick, or even guaranteed.
I'll let you know if I can do something.
 
 
A Dirk question:        "Is the change in the string of the right spot you made essential or can it be reset to how it was previously?"
 


I have a serious problem with client programs' attitude to a format which was going out of date when it first appeared in the original AK1A PacketCluster software in the 1980's. Particularly given the various tweaks I and others have made to it over the years, for example around the time field at the end of the line. As I have said in previous emails, many main stream logging and contesting programs have all either changed to using the ve7cc CC11 spot line format or they are parsing the line more flexibly than this author. 

But, I recognise that the last major contest of the year is happening this weekend and so I will put it back the way it was. For the next week or the next update to the mojo after this weekend ONLY.  This should appear later on today or early tomorrow. I will announce it on here when it is available. I will also announce when it is put the way it is now.

For better or for worse DXSpider and CC Server are the only two actively maintained cluster node programs and we have both decided that enough is enough on the client program interface issues that are NOT of our making. Client software have to make their own choices as to how to implement their interfaces to nodes, much as I have to put up with the format of the (wasteful) RBN spot lines that I client to. If someone changes something "upstream" I shall have to "suck it up" (as I believe the yoof of today say).  Client software that connect to modern DX Cluster nodes will have to do the same.

While I am here, I may as well mention that I shall be working toward moving the master branch to "legacy" and the mojo branch will become the new master branch. You can expect this change to happen when I have made the update process as smooth as I can. It will - until someone (else) has the time and interest to sort it - be a unix/linux/bsd etc only system. I suspect that the smoothest way of running a modern version of DXSpider under Windows will require something like WSL(2) as, as far as I can tell, none of the pure Windows perls will support Mojolicious and DB_File(spit) without (some) C code and a compiler. 

73 Dirk G1TLH

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20211125/76a09ef7/attachment-0001.htm>