Hendrik,

There are markers that can be automatically generated and
markers that we write manually in mymarkers.json

If we only want automatically generated markers, we do this:
cd PhantomSDR-Plus
cd frequencylist
chmod +x update-markers.sh
./update-markers.json
If we also want hand-written markers, then we need to copy the mymarkers.json file to
PhantomSDR-Plus/frequencylist
and start
./update-markers.json

this will merge the hand-written and auto-generated markers into a single file, markers.json,
and copy that file to your PhantomSDR-Plus directory.

It takes one minute for PhantomSDR to load the new markers.json.
It works without error after Emmanuel fixed the two files in the frontend/src directory.
Attached you have my hand-written mymarkers.json and markers.json made using the update-markers.sh script.

You can put markers.json in your PhantomSDR-Plus test directory for testing,
you will see that everything works as it should.

In mymarkers.json you have the correct syntax so you can edit,
delete mine, write yours and then run update-markers.sh

Best regards,
Darko, 9a7aof

Many thanks for your fast response.

If i use the markers.json in this manner, works all perfect - except the markers.
On 77,5 kHz is no marker to see.
(I currently use it so on http://mellesdr.rqhk191saz25euus.myfritz.net/)

73 de Hendrik

Quote from: Hendrik on May 05, 2026, 07:15 PM[
    {
      "frequency": 77500,
      "name": "DCF77",
      "mode": "CW"
    }
  ]

This one is the good !

73's

I've still not understood what the right format for the markers.json is. To find the right flavour i reduced this file to a tiny value:
{
  "markers": [
    {
      "frequency": 77500,
      "name": "DCF77",
      "mode": "CW"
    }
  ]
}

If i use the markers.json at this manner so i get all the strange issues like the missing s-meter.

Quote from: F1NSK on May 05, 2026, 12:17 PMAdd a custom install-Deb12.sh and launch

I am going to add this script to the repo. Thank you!

RADE update process and script, has also been changed. If you now run again ./install_rade.sh, the script will update your radae installation. This will be more useful later, when the V2 of RADE will be released, Then, I'll have to make also some changes to .svelte files, but don't worry, the FreeDV RADE team is not ready yet for the V2.
The newer version will give the same quality of sound as V!, but using only 800 Hz bandwith, instead of 1500 Hz now used from V1.

RADE V2 builds on V1 with several algorithmic improvements:
Please refer to: https://github.com/drowe67/radae/

Hello Guy's

On my side all work fine with 3.2.0 on Debian 12.
I play with GUI colors to match with the background 

To install on Deb12 quiet and safe :

I've downloaded the full code.zipfile
Extract in home/user/PhantomSDR-Plus
Add a custom install-Deb12.sh and launch

Tested on three differents PC without any issues.

Sometimes I lost the RX888 and the server crashes ! I've found the Bug ! The PC power supply voltage drops ! On a laboratory power supply no issues and the CPU temp decrease of 10°C

73's to everybody

One last thing I would like to share with you.
From the moment you have a working v.3.2.0, you have now the opportunity to be shown on https://sdr.shbrg.nl/sdr/ AND on websdr.org map.
The modification is made in .toml file you use as follows (this is mine):

[websdr]
register_online=true # Enable directory registration updates
register_urls=[
  "https://sdr-list.xyz/api/update_websdr",
  "https://www.shbrg.nl/api/update_websdr"
  ] # One or more directory endpoints that accept the same JSON payload
name="SV1BTL CATsync PhantomSDR+" # Name that is shown on https://sdr-list.xyz and/or https://sdr-list.xyz/api/update_websdr
antenna="EndFed 160-10m." # Antenna that is shown on https://sdr-list.xyz
grid_locator="KM17VX" # 4 or 6 length Grid Locatlr shown on https://sdr-list.xyz and for the Distance of FT8 Signals
hostname="phantomsdr.no-ip.org" # If you use ddns or something to host with a domain enter it here for https://sdr-list.xyz

[websdr.org]
enabled    = true
public_host = "phantomsdr.no-ip.org"
public_port = 8900
qth        = "KM17VX"
description = "SV1BTL PhantomSDR+ Athens GR"
email      = "sv1btl@otenet.gr"
logo        = "logo.jpg" #located in frontend/public, you can replace it with your own

A recompile of frontend maybe is needed so logo.jpg to be placed in the folder "dist", and restart of the server of course.

You can try....

Well, I think,
I FOUND IT

Two wrong files in frontend/src and the syntax of markers.json.

In a bright new Ubuntu 24.04 the installation and running without problems.

P.S. about "statistics". Please check if a new folder "log" there are new generated files with extension .jsonl

P.S.2 markers.json generated by update-markers.sh, works for me, but then the syntax of markers.json is different.

markers.json
{
  "markers": [
    {
      "frequency": 77500,
      "name": "DCF77",
      "mode": "CW"
    },
    {
      "frequency": 100000,
      "name": "LORAN",
      "mode": "AM"
    },
......
  ]
}

mymarkers.json in frequencylist folder is in this format
[
    {
      "frequency": 77500,
      "name": "DCF77",
      "mode": "CW"
    },
.....
    {
      "frequency": 28585000,
      "name": "28585",
      "mode": "USB"
    }
]

instead of the original markers.json, located in github:
{
  "markers": [
{
      "frequency": 77500,
      "name": "DCF77",
      "mode": "CW"
    },
......
    {
      "frequency": 28330000,
      "name": "FreeDV",
      "mode": "USB"
    }   
  ]
}


Confirmed!
Great job Darko, thank you. Without or empty "markers.json" release V3.2.0 runnig here very well too!

Best regards,
Hendrik

I found that markers.json crashes and distorts v3.2.0

I tried with markers.json generated by update-markers.sh, it crashes. I tried with manually generated markers.json, it crashes.

It only helps when I delete markers.json, then the page looks normal (without markers).

I turned off the proxy, the Users button seems to work, I'm not sure about the Stats button.

73!
Darko, 9a7aof

P.S.
http://orsat.ddns.net:8080/ and
http://lu5dnpwebsdr.sytes.net:8901/
does NOT have markers.json.