-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DOA Issue: Kraken stops functioning set at 1.68 ghz (NOAA wx balloons) #49
Comments
Interesting, I was able to replicate it. This needs more investigation, but for now I was able to get around the issue by tuning to 1500 MHz first, and then to 1680 MHz. Could be something to do with VCO current needing to ramp up faster with larger frequency changes. |
Wow, that worked here too. Maybe I can chase some balloons now 😃 |
(Sorry to hijack the issue!) |
If you are located in Michigan as your QRZCQ profile suggests, then both launch sites here are now running on the 400-406 MHz band: You can see what's launching here: https://tracker.sondehub.org/#!mt=Mapnik&mz=7&qm=12h&mc=44.06764,-83.63587&f=22033469 |
Thanks for the info, that explains the epic fail first try 😃. Guess I watched the wrong youtube videos. |
The switch to 400 MHz sondes has really only happened in the last 12 months, so whatever you found on youtube is probably out of date :-) |
V1.4 image, DOA is working fine at 853.85mhz (antenna array supports 700-1700 mhz). If I change frequency to 1.680 ghz, the config shows errors (see photo) and won't recover without Software Restart.
The text was updated successfully, but these errors were encountered: