HRDLog does not show correct locators
Posted: 23 Apr 2020, 07:32
Today when I saw my HRDLog map I wondered about the new markers, which are not set correct as they are in the center of the DXCC:
I went into the details of the HRDLog logbook and saw that the locator does not match the one stored in Log4OM.
Im my Log4OM I have FN46 stored (from WSJT-X): Im my Log4OM I have QF23 stored (from WSJT-X): I switched from Log4OM v1 to v2 2.4.0.0 only a week ago and immediately updated to 2.5.0.0.
I can say that it worked with v1 correctly.
Is it possible that no locator is sent via API and HRDlog just uses a default locator with the country?
Does it possibly also have something to do with the new duration between entry in the log and sending the data to HRDLog? I have the feeling that the new feauture may be related to the problem.
Can I somewhere check the raw api-data sent by Log4OM to external sources?
I went into the details of the HRDLog logbook and saw that the locator does not match the one stored in Log4OM.
Im my Log4OM I have FN46 stored (from WSJT-X): Im my Log4OM I have QF23 stored (from WSJT-X): I switched from Log4OM v1 to v2 2.4.0.0 only a week ago and immediately updated to 2.5.0.0.
I can say that it worked with v1 correctly.
Is it possible that no locator is sent via API and HRDlog just uses a default locator with the country?
Does it possibly also have something to do with the new duration between entry in the log and sending the data to HRDLog? I have the feeling that the new feauture may be related to the problem.
Can I somewhere check the raw api-data sent by Log4OM to external sources?