Spot report: my callsign

[ah6fx]

Terry,

Thanks for the great support and the great Log4OM2 program. I installed ver 2.21.1.0 a few days ago on my Dell XPS 8930 running Microsoft Windows Pro 10 10.0.19043 build 19043 … 16 GB ram. Rig: FTdx101MP.

Problem: I sent a spot report recently using the button to the right of “Operator Name” on the main logging screen. I noticed it sent my callsign as AH6FX. [[[LOG4OM2 cluster, DXHeat, and DX Summit all showed me as AH6FX as the reporter or sender]]] I always send my call as AH6FX/W4 while in Virginia. The AH6FX/W4 stuff worked flawlessly in all previous Log4OM versions for the last 15-18 years or so.

I checked Settings > Personal Configuration > Station Information and saw everything was ok. Station callsign = AH6FX/W4 … also Operator Callsign = AH6FX/W4. Owner Callsign unchanged as AH6FX. Also reviewed the latest version of the user guide, and did not see anything to resolve this issue.

Also went to “Cluster management” and manually entered AH6FX/W4, freq, and spot info … the clicked “Send Spot.” Same results: shows sent by AH6FX. [[Note: Saw the “Set personal info” tab but it was grayed-out and I could not open it to investigate.]]

Recently returned home from AH6-land. Did not use Log4OM2 there. However, I did change my callsign and grid on DXHeat and QRZ to indicate I was back in Hawaii and not Virginia. I changed my call back to AH6FX/W4 on those two sites a few day ago after returning to Virginia. I doubt they affect my Log4OM2 spot report. Have never had this problem after other trips back to Hawaii.

Not sure what happened. Not sure if the updated version dropped my /W4 when reporting a spot report to a DX reflector.

How can I get AH6FX/W4 to be sent with spot reports again?

Thanks very much.

Regards,
Danny
AH6FX/W4 -- Virginia

[G4POP]

Firstly I can confirm there seems to be a glitch when sending live spots in that the suffix is dropped from the spot reporters call sign is not included, I will add this to our Mantis list.

However I found the spot simulator in the Cluster management control to work OK, see below

Screenshot 2022-04-25 080013.png (6.46 KiB) Viewed 797 times

Spot simulator.jpg (87.79 KiB) Viewed 797 times

[ah6fx]

Terry,

Thanks for adding that problem to your Mantis list.

As you read in my initial message ... I tried submitting a spot report from Cluster management to send an actual "live spot" to the reflectors. It did not work. Rather it just send AH6FX and not AH6FX/W4.

I also tried the Spot simulation as you did. It worked OK by reporting me as AH6FX/W4 but of course it is only a simulation and does not send the spot report to the reflectors.

Thanks for your help.

Regards,
Danny
AH6FX/W4 - Virginia