Mine WAS working exactly like your images show.
I do not remember changing anything so I am stumped, it is easy to say it changed after the last update but I doubt it had anything to do with it.
This is the FMP-Map cfg (I don't understand what the 3rd line numbers are)
572 1022 ; first line must be map window height and width
11 ; second line must be map zoom level (0-18)
191126 146926 ; third line must be encoded map center
. ; fourth line must be path to OSM map data files
. ; fifth line must be path to FMP-Map.dat file
km ; sixth line must be miles or km plus optional bearing
----------------------------------------------------------------------------------------
This is FMP24 cfg
2.4 ; sampling rate (1.0, 2.0 or 2.4)
1024 ; spectrum window width
64 ; FFT size (16k, 32k, 64k)
15 ; spectrum update rate in Hz
5000 -6250 7500 12500 15000 25000 ; step size table; units = Hz; negate default
. ; DSD+ path
.\Canada.csv ; primary frequency list CSV
.\NY.csv ; auxiliary frequency list CSV
kilometers ; search units (miles or kilometers)
100 ; search distance
43.877523 -78.839893 ; search origin
-----------------------------------------------------------------------
When it was working and now - I zoomed out the now one so you can see where in the world it thinks I am.
'search origin' is going to be your problem.
Look at the FMPx console window, look for the line:
Base latitude/longitude:
Is the coordinates the same as whats in 'search origin' in 'FMP24.cfg'.
I bet it's showing:
Code:
Base latitude/longitude: 43.8775 23.0000
Make line in 'search origin' line in FMPx.cfg the following: (see below for more details about this)
Code:
43.8775 -78.8398 ; search origin
More details for those interested
Latest version of DSD+ (v2.228) has made internal changes to some of the external files used.
DSDPlus have failed to tell it's users of these changes which are causing havoc.
So far '
FMPx.cfg' and '
FMP-FreqList.csv' have been observed to have these changes.
In '
FMPx.cfg'
: The coordinates of the 'search origin' line.
The coordinates now MUST strictly follow this format:
Coordinates values are Latitude and Longitude
- Values MUST not be longer than
x.xxxx or
-x.xxxx (FMPx will pad if shorter)
If values are longer, then one of two errors occur.
1. If latitude uses
x.xxxxzz, then the zz will be used as longitude value and real longitude value will be ignored.
- This will cause your position to be wrong and FMPx will not show frequency details from 'FMP-FreqList.csv' or your position in FMP-Map. LRRP may be affected too.
2. If latitude uses
x.xxxx00, then the 00 will cause the 'Divide By Zero' error in FMPx.
The latitude and longitude value ranges are as follows:
Latitude: -90.0000 to 90.0000 (
real range -89.9974 to 89.9974)
Longitude: -180.0000 to 180.0000 (
real range -180.0000 to 180.0000)
If latitude or longitude value of "0" is required then 0.0001 is as close to 0 you can get before seeing the "Divide By Zero" error.
For some reason FMPx sees latitude and longitude value of 0 and any latitude value above -89.9974 or 89.9974 as been invalid. ('Divide By Zero' error)
Why is longitude range (-180.0000 to 180.0000) OK?
This is not a big deal unless you live at the poles or equator.
Those who create there own '
FMP-FreqList.csv', then problems can arise when the following is not done.
In '
FMP-FreqList.csv' The affected elements are '
TXfreq', '
Latitude', '
Longitude'
- '
TXfreq' this value MUST not be longer than x.xxxx (FMPx will pad if shorter)
- '
Latitude', '
Longitude' these values MUST not be longer than
x.xxxx or
-x.xxxx (FMPx will pad if shorter)
If '
TXfreq' values are longer, then entry will not be displayed.
If '
Latitude', '
Longitude' values are longer, then '
Latitude', '
Longitude' will interpreted incorrectly and the position could be
anywhere on map and most likely will be outside the '
search distance' set in '
FMPx.cfg'
