PhantomSDR V2.0 testing / Bug List

[hb3xdc]

Hi Steven,

Today I installed the new version at home. It works great and is a nice upgrade! I've found a few small improvement opportunities that I'd like to share:

Frequency Step Settings
It would be helpful to allow 1 / 5 / 9 / 10 kHz tuning steps for the mouse wheel.
For SW/MW listeners, it might be a good idea to automatically switch the tuning step to 5 kHz for shortwave broadcasts and 9 kHz for MW/LW.
When the mouse wheel step is set to 25 Hz, the software occasionally freezes.

Filters
On the ham radio bands, I miss the static IF filters that were available in Phil's version.
Auto Adjust WF (Waterfall)
When I turn off "Auto Adjust WF," the brightness doesn't return to the original level.

Squelch
For FM/CB listeners, an auto squelch option would be very useful.

CAT Sync
One of the few major drawbacks of PhantomSDR is its incompatibility with the well-known CATSync application.

Unfortunately, the developer of CATSync is not willing to adapt his software, but he has shared how it integrates with other software like OpenWebRX.
https://www.phantomsdr.fun/index.php?topic=165.msg929
Perhaps we could adapt PhantomSDR to support it based on that information.

Decoder
The FT8 decoder doesn't work with the default config.toml.
This might be due to the audio sample rate being over 12 kHz, similar to the issue in the old version.

Thanks again for the great work on this release.

Best regards,
Gianni

[Bas ON5HB]

Step settings can be changed. As for AM, only Europe has 9KHz steps, the USA has 10KHz (if not mistaken).
Same for AM stations, most are 9KHz wide, but often they use 15KHz.
However, 9KHz is the best setting as the filter isn't too steep and it works for almost all stations.

Squelsh can be set in the frontend if you want, for set it for FM by default is an impossible task, as FM is used mixed with other modes.
Too much freq's. If you run smallband SDR; you can set it for the entire band.

FT8 must use 12KHz, this is NOT the sample-rate, it's the audio output and 12KHz is more then enough for any application.
Setting it higher brings nothing but eat more bandwith for your server.

As for Catsync, Phantom is not to blame, it's opensource unlike others, the developer of Catsync should have no problem adapting to it.
He can tab into the server directly.

[Phil - NY4Q]

Steven,

Do I need to recompile the system after the grid square change? I ask because the wasterfall.js file only has a frequency plan for ITU 1 in the bands section for 40m.

I'm not sure how you are generating that file.

Phil

[magicint1337]

It should detect it on the Grid locator without recompile, i made an error probably. Will be fixed in next hotfixes as well as all the stuff listed here

[9a7aof]

Steven,

Do I need to recompile the system after the grid square change? I ask because the wasterfall.js file only has a frequency plan for ITU 1 in the bands section for 40m.

I'm not sure how you are generating that file.

Phil

Hi Phil,

simply edit the waterfall.js located in the
PhantomSDR-Plus/frontend/src directory and compile the UI again.

It works, I shortened the medium wave (to 1602kHz) and 80m band (3.5-3,8MHz), deleted and added bands, it's a quick patch until the official revision comes.

To remove unnecessary bands and add new bands in the Bands menu, you need to edit the BandsMenu.svelte file located in the PhantomSDR-Plus/frontend/src/components directory.
(tip: I make soft link ln -s BandsMenu.svelte band.js and then edit  "bands.js" with my favorite editor, joe does not have color sintax for .svelte files )

After compiling the interface, the redundant ones disappear and the desired bands appear.

Changes in the user interface are added without restarting the entire "phantom"

Kind regards,
Darko, 9a7aof

[Phil - NY4Q]

Steven,

Do I need to recompile the system after the grid square change? I ask because the wasterfall.js file only has a frequency plan for ITU 1 in the bands section for 40m.

I'm not sure how you are generating that file.

Phil

Hi Phil,

simply edit the waterfall.js located in the
PhantomSDR-Plus/frontend/src directory and compile the UI again.

Hello Darko,

Weird, but I did edit the waterfall.js and recompile and it made no change, so that had me scratching my head. ha

Steven will find the issue. I did not use the pre-built packages. I downloaded the individual packages and built my system that way.

Phil

[9a7aof]

Hello Darko,

Weird, but I did edit the waterfall.js and recompile and it made no change, so that had me scratching my head. ha

Steven will find the issue. I did not use the pre-built packages. I downloaded the individual packages and built my system that way.

Phil

Hi Phil,

also downloaded all files from Steven's github with git clone..... (I am old School linux user, since 1996 )
I edit these two files and start npm run build.
I Added MW, 180m and Troika band to watefall.js and BandsMenu.svelte
After this I have new waterfall and Bands look.

I attach my edited files:
/home/websdr/PhantomSDR-Plus/frontend/src/waterfall.js to waterfall.js
/home/websdr/PhantomSDR-Plus/frontend/src/components/BandsMenu.svelte


Result is here:
http://9a7aof.ddns.net:8906

Best regards,
Darko, 9a7aof

[Phil - NY4Q]

Hi Phil,

also downloaded all files from Steven's github with git clone..... (I am old School linux user, since 1996 )
I edit these two files and start npm run build.
I Added MW, 180m and Troika band to watefall.js and BandsMenu.svelte
After this I have new waterfall and Bands look.

I attach my edited files:
/home/websdr/PhantomSDR-Plus/frontend/src/waterfall.js to waterfall.js
/home/websdr/PhantomSDR-Plus/frontend/src/components/BandsMenu.svelte


Result is here:
http://9a7aof.ddns.net:8906

Best regards,
Darko, 9a7aof

I see your result, but I also saw what happened to me. Donno why. Maybe when I checked, the browser pulled from cache and did not refresh. I only tried once then had to get to other things.

I will look into it later today if I get time.

[hb3xdc]

Unfortunately, I haven't been able to quickly fix the bug with the non-working tuning steps via the mouse wheel.
25 Hz doesn't work, and 12.5 Hz doesn't either if the VFO is used.
Also, larger steps like 1 / 9 / 10 kHz are missing.

Is there a way I can adjust this somewhere in the code, maybe by adapting the working steps code  from the Community version?