Internal Cluster response

[ng7v]

Hello - I use the internal cluster in Log4OM v2. I noticed that I could not issue a command from the ClubLog window in Win4Yaesu. I started a telnet client and connected to the server:

Code: Select all

Welcome to Log4OM NG Telnet Server, hosted by Log4OM NG 2.28 rev. 0
This server is managed by Log4OM instance.
All commands will be forwarded.
Login:
NG7V
DX de KO7SS-#:   24929.2  WR5U         CW 17 dB 27 WPM CQ          LA 1758Z AZ
SH/MYDX
DX de WA7AI-#:   14020.5  W6EO         CW  6 dB 24 WPM CQ          CA 1758Z WA

1) there was no response to my login (already reported and put in line for new feature)
2) did not forward my SH/MYDX command winch is a commonly used command even if the banner indicates that all commands will be forwarded (first report of this bug I think)

[G4POP]

Are you registered with the external cluster server?

If so is the external cluster server that your registered with the 'Primary' cluster server in Log4OM?

[ng7v]

Terry,
Yes and yes. Thx for the response.

Ron

[G4POP]

Terry,
Yes and yes. Thx for the response.

Ron

I no longer have Win4K3 having switched to the SunSDR a couple of years ago, can someone else confirm this is an issue please

[ng7v]

Hi,

In support of my earlier response, a cut an paste of my registration on VE7CC-1 using their client:

Code: Select all

Cluster: 325 nodes  900 Locals  4154 Total users   Uptime  24 days 19:23

Date        Hour   SFI   A   K Forecast                               Logger
24-Jul-2023   21   165   8   2 No Storms -> Minor w/S1               <AE5E>
25-Jul-2023    0   165   7   3 No Storms -> No Storms                <AE5E>
NG7V de VE7CC-1 25-Jul-2023 0041Z   CCC >
   <- SH/SETTINGS
NG7V de VE7CC-1 25-Jul-2023 0041Z   CCC >
Location                              Sunrise   Sunset      SP      LP
NG7V  K - AZ-ID-MT-NV-OR-UT-WA-WY     12:34     03:10
DN13        Grid Square               12:29     03:18      338      158
NG7V-0 de VE7CC-1 25-Jul-2023 0041Z   CCC >
       Callsign: NG7V-0
           Name: Ronald Poulin
      Home Node:
       Home QTH: Meridian, ID
       Location: 43 0 N 116 44 W
        Locator: DN13SO
 Login Info Req: No
   Req Announce: Yes
       Req Beep: No
       Req Echo: No
       Req Talk: Yes
        Req WCY: No
        Req WWV: Yes
         Req WX: Yes
   Req DX Spots: Yes
 Dx 2 Digit Res: No
  Req BoB Spots: No
 Req Self Spots: No
Req Beacon Spot: No
Req FT4   Spots: No
Req FT8   Spots: No
Req CW    Spots: Yes
Req RTTY  Spots: No
Req PSK   Spots: No
Req MSK144 Spot: No
Req SkimmerSpot: Yes
Req Skimmer Own: Yes
Req SkimmerDupe: No
Enhanced DxSpot: No
  Show US State: Yes
 Show Cty/State: No
   Show CQ Zone: No
   Show DX Grid: No
  Show ITU Zone: No
  DX Spot Width: 75
   Type of User: U
   <-  
   <- set/ve7cc
   <- sh/filter
   <- KeepAlive Rx 3  V2.4481
NG7V-0 de VE7CC-1 25-Jul-2023 0041Z   CCC >
 -> ^VE7CC^
DX de KO7SS-#:   14055.5  W9W          CW 11 dB 23 WPM CQ             0041Z AZ

And support for having set this cluster as the primary:

[ng7v]

Hi,

Looks like nobody confirmed my earlier bug report. The responses from the internal cluster server are still broken which really impacts the interoperability with Win4Yaesu's Club Log window or any other app that may have dependencies on the server's response like the one I saw in the cluster plugin of SDRUno.

Will there be a fix for this someday?

[ng7v]

Fixed in Version 2.29.0.0.

Thanks go to the Development team who work on the best logger of its kind!

Sincerely,