brianmathews
commented
4 months ago I added debugging console logging code to both SOTAMAT and SOTACAT.
What I see:
- SOTAMAT sometimes sends multiple WiFi REST calls to change frequency before the prior call has finished. This happens with the iOS frequency "Spinner" UI where the spinner can emit multiple events in a short time.
- I see the HTTP REST call initiated by SOTAMAT, but it hangs
- I don't see the REST call received by SOTACAT
- After several seconds a timeout occurs and SOTACAT receives the call, and SOTAMAT receives a response.
Even though this narrows the issue down considerably to just one line of code, I don't understand why it isn't working. Yes, I understand the threading concerns, but that doesn't seem to be the issue as far as I can tell at the moment. If I change the Xamarin HTTP timeout to just 2 seconds, I catch the timeout error but things are still in an odd state.
jeffkowalski
If you launch SOTAMAT in SOTACAT mode, you can use the SOTAMAT band/mode selector and the frequency selector to change the band/mode/frequency on the KX radio. Most of the time this works, but frequently making a new selection in SOTAMAT will not update the frequency on the radio, and all subsequent changes will be blocked at the radio. After about 1 minute of hanging the entire sequence of commands that had been buffered during the hang will all play out onto the KX radio.
I do not know the cause of the issue: is the hang on the SOTAMAT side or the SOTACAT side? Instrumenting with debugging console logs could help on the SOTACAT side to see when REST API calls are made and when radio commands are issued.