Some suggestions for improvement

[edegraaff]

First thanks for sharing this code! Can't wait to get it working on my system.

Some suggestions: regarding the main.c
#define CONFIG_CALLSIGN "R2BDY"
#define CONFIG_LOCATOR4 "KO85"

1. Is it an idea to use a seperate config file for those?
2. if a gps module is used, is the locator variabele still needed? Lets asume i take the beacon with me to another location and the gps is working, as a clock but also as a gps, the location is availible as coordinates. On the another hand, i could imagine you don't want to have all code in the module to calculate the gps coordinates to the grid.

Regarding the issue #6
Suggestion to add the variabeles
gpio_set_function(uart_id ? 8 : 12, GPIO_FUNC_UART);
gpio_set_function(uart_id ? 9 : 13, GPIO_FUNC_UART);
Also in the main config/init file ?

Regards
Eelco

[RPiks]

Hi Eelco,

Sorry for the belated answer, but I really had the hands full.

Thank you for the suggestions: they help to focus on necessary improvements.
A few weeks ago I added the console function to the core of this project (pico-hf-oscillator). The user can set what they need by enter simple commands such as SETFREQ 24915000. Other commands are available too.

This holidays I'm planning to implement similar function in this WSPR project.

So, I would like to address a question to you: what do you think about such console? What commands would you add to it? I possess my own view on this, but such alternative mention would be useful.

Please look at an example video in pico-hf-oscillator. Thank you in advance.

Cheers, Roman
R2BDY

[edegraaff]

Hey Roman, a console as alternative to do quick changes is an practical approach for some areas i mentioned. If we take a closer look to the needs, and time investments. Just being blund my backlog:

1. As a user i want to be able to have a wspr beacon that is flexible and can be used in a permanent location ans during holidays in other locations.
2. As a user i want to have the main settings permanent and be able to make changes in the configuration. Roel Kroes, has made this in his https://github.com/RoelKroes/TBTracker-RX project, main settings compiled, and changes by web interface, it is a bit like your console idea.
3. As a HAM i want to have a permanent stable signal (no drifting) on the main bands with almost none harmonics. This one demands possible a bit more details, and maybe external filters or modules. But lets give this one focus and make the demission what band would be the best candidate (as an rookie i think 20 m band)
4. As a technitian i would suggest always to set some variables permanent, in such a way the beacon will after startup always follow regulations as the default frequency used for WSPR
5. As a user i want to have some schema's and documentation and a logical approach to build the project (and this is something that asks time and energy and in most cases you do this after the POC is done:-)
6. For me as non electronics guy i need to understand the main approaches and get it in a working model. Like ok if i add an antenna, do i flollow the guideline for 20 half band diplodipole and connection to pens, and some examples,

I am waiting for my pico, i expect it today, i have a GPS module for my Roel Kroes projects here in the stash, i have a pi5 with the SDK on it and it compiled your code. Next steps is to build the device and see if i can receive the beacon in the Shack.

I have looked as non programmer in your pico hf project i like the idea behind it, I would suggest to share the amplifier model, but because i am not that experienced. I was wondering will the pico be able to give a true stable basic frequency? In most projects i have seen (arduino) they use external clocks or crystals.

I also used Meshtastic, they go even further on, and have a Bluetooth interface and web interface to make changes in the config, or have true interaction with the device with an app over Bluetooth. But, it all depends time, and effort.
My goal would be, have the device stable in a watertight box and have a stable beacon others can use to check propagation, and or use the beacon, to report it as start for a conversation:-)

I hope my input will give you some ideas..

Keep you posted over my progress.

Some extra thoughts also based on other questions, when you use a console or something similar.
TimeSource (TC) = GPS or NTP