When DX labels are edited, the Flydog upper frequency limit changes from 65MHz to 32MHz and stays.

[G8JNJ]

Since this change was added into Flydog  v1.573

When using the full 65MHz bandwidth, and when editing DX labels, the Flydog upper frequency limit changes from 65MHz to 32MHz, and a restart is required to obtain the full frequency coverage.

In addition if an upconvertor offset used, a pop up banner requesting browser refresh is shown, which continually pops up and will not clear.

This is probably because since V1.571 KiWi has made changes to the way the DX labels work on frequencies above 32MHz.

From KiWi forum

"v1.571 Dec 27, 2022  Admin page DX tab: CAUTION: If you have a "normal" Kiwi with HF DX labels only you don't need to  perform the conversion process described below. You don't need to do anything.     From this release forward new DX labels stored in the dx.json file will use  their true frequency instead of their normalized baseband freq (0 to 30/32 MHz). This will allow  proper label display when using a variable frequency downconverter (such as the freq extender  developed by Glenn, N6GN, www.sonic.net/~n6gn/BCReferenceBlock.png)     So for example if dx.json contains a combination of HF labels and airband labels (108-137 MHz)  then the airband labels won't be used until the Kiwi frequency offset is configured for  108 MHz (via either the admin interface or the "foff=108000" user page URL parameter).     However, this means there needs to be a conversion process for pre-v1.571 Kiwis with non-HF  labels in dx.json (e.g. those setup for airband or vhf/uhf ham bands). The label frequencies  must be adjusted from baseband to their true frequencies. This could be done (rather painfully)  one label at a time via the admin DX tab.  But in v1.571 a bulk mechanism for adding the freq offset to ALL the labels has been added.  It will appear at the top of the admin DX tab, but only if a non-zero frequency offset if set  (i.e. Kiwi is setup (presumably) for non-HF operation). When the "Add offset" button is pressed  a one-time addition of the current frequency offset is made to ALL labels in dx.json  The mechanism will then disappear and not be shown again since this is a one-time operation.  There is also a button saying: "Skip this and don't ask again". A backup copy of dx.json is  made for safety. Ask on the Kiwi forum if you get into trouble.     If you never removed the HF labels before beginning non-HF operation then DON'T perform the  above conversion. You don't want the HF labels to be shifted into your non-HF band.  Instead, with v1.571 or later, just begin adding labels with non-HF frequencies and they will  be stored with their true frequencies distinguishing them from the existing HF labels.     This change prevents the EiBi database labels from appearing when a frequency offset  is in effect. The change also makes the labels appear properly when only a part of the  HF band is visible (e.g. a frequency offset of 25 MHz is used with a converter that captures  the 10, 8 and 6m ham bands together).  ----"

[G8JNJ]

This problem has not been fixed.

If a DX label is added in the frequency range 32 to 60MHz the receiver tunes to the correct frequency, and the waterfall frequency display is correct, but the waterfall and the spectrum display show frequencies in the 0-30MHz spectrum and not the correct range of 0-60MHz.

[G8JNJ]

This has still not been fixed.

As an example

If you are using the full 0-62MHz spectrum and have a signal a signal at 20MHz, and then create and save a new marker tab on a frequency greater than 32MHz , it is all good until you retune or zoom to a frequency below 32MHz.

The waterfall display the frequency scale and new marker will remain showing 0 to 62MHz, but the actual tuning range reverts to 0 to 32MHz, so the 20MHz signal shows at approximately 38MHz, and it is no longer possible to receive anything in the frequency range between 32 and 62MHz.

Flydog has to be restarted to correct this problem.

Images showing before and after adding a 50MHz tag.