update 'markers.json' automaticly with only active broadcast stations

[Hendrik]

It bothered me, thats all broadcasting stations shown as static via 'markers.json' - even if their active or not. The appending script sort out all inactiv station (so about 70 %) aligning on the HFCC database. For the install have a look at the readme file please. If you find it useful feel free to integrate it into the repo.

If somebody interested: the automaticly update by the HFCC DB could be the next step.

Sail on a good (short)wave,
Hendrik

[Emmanuel SV1BTL]

If somebody interested: the automaticly update by the HFCC DB could be the next step.

The whole thing is very interesting and useful for SW listeners. I'll take a look and try during weekend.

A disaster to my main pc with the server, kept me away for some days, until to restore everything. Now I have the tool to test.

Meanwhile, I've added an internal audio spectrogram to my last version, which is not uploaded yet. You can call the function by clicking a button near the FT8 one. A spectrogram will be shown just bellow the waterfall. The new thing is that audio is taken through audio.js. Please check, and if you find it useful, let us add it to the github too. There are many radioamateurs here in Greece, that they are interested in HiFi SSB and I think they were waiting for something like this.

[Hendrik]

Please stand brave with your disaster situation. I cross the fingers on booth hands for a fast recover.
I tried to check your new release, but shurely currently you've to fight with your come back - the SDR is down.
Could you raise the finger here, if you setup working again, please?

Appending the latest release by the the automatic update by the 'markers.json' file. (Please put all files at the frequencylist folder and take a look at the short readme file) At the meantime is also the update by the HFCC database (only is needed) integrated. It's only tested for some days. So be careful and let me know please, if anything runs at the wrong direction.


a good reception to all,
Hendrik

[Emmanuel SV1BTL]

I tried to check your new release, but shurely currently you've to fight with your come back - the SDR is down.

Well now the is another situation... No currency in the QTH, because yesterday Greece faced a really bad weather catastrophe and there are big areas without electricity. I belong to these areas!.. . BUT I already had asked Darko to test the setup and you can see it here: http://9a7aof.ddns.net:8905/. You only need to click Audio Spectrogram -> Show and a new popup window will appear under the waterfall with a real time audio spectrogram of what you are hearing. With Audio Spectrogram -> Hide, the window disappears.

I will open your files you've sent during the weekend. And of course there will be included in the next release among the last changes, as v.1.6.7

I have to notice that a new sysop must be very careful with npm, nve, vite, and all these tools, because there are new releases not compatible with svelte v4 we use, so I have desided to rewrite the install.sh with a new one, to force download and install the correct version, otherwise the compile will not go on.

[Hendrik]

I hope the power come back in your house soon. We're all no longer familaer to live without.

The new function on Darkos(thanks for support) site is very helpful. Due to the fine scale it's easy to determine the rtty shift for an example.   I can only greet to bring this function at the new release.

May be it would be make sense to mention the compatibility topic (svelte v4) at the manual. I don't know if have every potential PhantomSDR Plus owner the relation to this forum.

Best regards,
Hendrik

[Emmanuel SV1BTL]

Well, the problem with your script is that replace all data in the markers.json with the newer data. The other problem is that if you have already some manually added markers, they are going to be replaced too.
I've decided to make some modifications to your files. So, I've added a "mymarkers.json" into the frequency folder, and then with a modified "update-markers.sh" I force the generated files from SW data base to be combined with the mymarkers and together to create a new "markers.json" to the root PhantomSDR folder. I am testing the whole thing, and I'll be ready to upload them, with other modifications, to the newer v.1.6.7.

Check my server, markers.json are build with this method.

I've not tested the cron setup yet.

The new function on Darkos(thanks for support) site is very helpful. Due to the fine scale it's easy to determine the rtty shift for an example.   I can only greet to bring this function at the new release.

May be it would be make sense to mention the compatibility topic (svelte v4) at the manual. I don't know if have every potential PhantomSDR Plus owner the relation to this forum.

RTTY is already tested, but the decoder functions with too many mistakes.

New install.sh is created, which will correct all these errrs during initial setup.

[Emmanuel SV1BTL]

How to update markers.json

• Unzip the file "frequencylist.zip" into the folder cd $HOME/PhantomSDR-Plus/frequencylist/.
• Modify the file "manual-markers.json" with your own markers.
• download from https://new.hfcc.org/data/ the newest list, at the buttom of page, current: B25allx2.zip - B25 Operational Schedule - Last updated on 08-Jan-2026
• unzip the downloaded file from the database into the folder frequencylist.
• ensure that "B25all00.TXT" and "broadcas.txt" are located in the "frequencylist" folder
• modify "update-markers.sh" line 5 to your personal full path --> "cd $HOME/PhantomSDR-Plus/frequencylist/". Make this file executable.
• NB don't use '~ ' if you use the cron service e.g. use cd home/user/PhantomSDR-Plus/frequencylist/
• run update script with "update-markers.sh" manually or let it run automaticly by a cron job (for example update every 15 minutes a hour 'sudo crontab -e' and enter '0,15,30,45 * * * * /usr/bin/bash /home/user/PhantomSDR-Plus/frequencylist/update-markers.sh')
• The script will generate the "shortwavestations.json" based on the data given from the database and finaly will merge it with "manual-markers.json", so to create the final "markers.json" in the root PhantomSDR-Plus folder).
• NB Your markers in mymarkers.json will overwrite and replace the duplicate markers from shortwavestations.json in the final markers.json file which will be generated. The given mymarkers.json contains some demo markers, you can replace them with your own!