Open edegraaff opened 7 months ago
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
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:
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
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 https://github.com/RPiks/pico-WSPR-tx/issues/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