Log4OM

I use the internal cluster in Log4Om to consolidate spots from different clusters.

Using the Win4Yaesu ClubLog window to issue the sh/dx command using the button offered at the bottom of the window. I tracked down what happens in the internal cluster when I click on it:
It looks like the internal cluster discards the command. Does anyone know how to authorize the connection to allow the command to propagate upstream to the primary cluster?

Hi Ron

I would advise to use CC User ver3 by VE7CC which allows multiple connections to the dx clusters. This should also lighten up the usually busy logger

ei6kw wrote: 01 Sep 2023, 19:20 Hi Ron

I would advise to use CC User ver3 by VE7CC which allows multiple connections to the dx clusters. This should also lighten up the usually busy logger

Thank you for your suggestion however, CC User does not support more than one cluster. SpotCollector from DX Labs supports up to 5 clusters but it does but does not have an internal telnet server. Log4OM2 does it all for me. The internal cluster was sort of repaired with the last release. I am looking for an way to authorize a connection to allow an external command to refresh the spot listing in Club Log.

ng7v wrote: 01 Sep 2023, 19:41

ei6kw wrote: 01 Sep 2023, 19:20 Hi Ron

I would advise to use CC User ver3 by VE7CC which allows multiple connections to the dx clusters. This should also lighten up the usually busy logger

Thank you for your suggestion however, CC User does not support more than one cluster.

So am I an magician?

https://1drv.ms/i/s!As-3kbWRAp3ig5sejj6 ... Q?e=YVsWKV

Thank you.

Sometimes, I am clueless. The version of CCUser I had (v2.x) had a broken downloader module that was fixed a while back but that I missed. I got the new downloader and was able to upgrade CCUser to version 3.0, that for some reason isn't really available through the main site as far as I could tell. Only then could I set CCUser up to work as you indicated.

With that all said and done, I now got the end result I wanted. I need to mention that I am not a mind reader but I do get clues sometimes that make me think that what I ask for and what I get from Log4OM dev team is just that: a huge clue. I should have figured out that what they were telling me with their partial fix (fixing the response given by the internal cluster) but, the response was a cryptic "Request discarded, AUTH Required" really means: "We will not do that because it is a security risk".

Duh...

With all of that, I am now going to go away and keep my nose clean. I really love this logger and the people behind it. I am just a little frustrated.

I don't know why upgrading to version 3 works in this way. But in the end you got what you needed and that's the point.

Fixed in Version 2.29.0.0.

Thank you to the Team of Developers who participated in this fix. I am very grateful to have such a great logger.

Sincerely,