Log4OM

oe9shv

Hello, happy new year - I did a SOTA activation and could manage to upload the log out of L4OM based on ADIF export. I had the configuration station callsign with extension /P as well as operator callsign with extension /P. However after uploading ADIF to SOTA DB the logged QSOs are shown without th...

oe9shv

Basically because there are no "info" about existance of a secondary callsign on QRZ.COM, so Log4OM needs to make 2 different calls, one to "full callsign" and one to "simple one", slowing down the process. I can eventually handle this situation, but whis will possibly...

oe9shv

Thank you Daniele for your reply and thoughts. I am really also interested how the community handle this - I am most of the time mobile / portable in foreign countries - others might not see this as an issue at all. The slowdown for lookups would only occur for those callsigns with a prefix followed...

oe9shv

Hello, while operating outside of the own country.... when entering a callsign with a country prefix for which there is a separate QRZ.COM entry available, is ignored. Example with my QRZ - QSO lookup on F/OE9SHV shows the data of OE9SHV even there is a subpage F/OE9SHV which you can see at QRZ.COM ...

oe9shv

Hello, I have recently changed my logprogram from HRD to Log4OM and I am quite happy with the change. I could manage to connect my radio Yaesu FT-710 using the FT-DX10 Omnirig settings. However I face one problem: When I am in VFO-B and try to double click on a cluster entry, Log4OM takes the callsi...

Search found 5 matches

SOTA ADIF upload - callsign suffix ignored

Re: L4OM ignores QRZ Callsign lookup with country prefix

Re: L4OM ignores QRZ Callsign lookup with country prefix

L4OM ignores QRZ Callsign lookup with country prefix

FT-710 Omnirig Cluster CAT Control on VFO-B