Copasetic Flow

 During yesterday's POTA activations, I kept losing my control panel connection to Project TouCans. I restarted the rig's Pico-W several times to re-establish the connection before it occurred to me to think through the symptoms which were: Productively using the control panel to key the rig Switch to any other app on the phone besides the Chrome browser Return to control panel on Chrome browser and the connection is gone. On my implementation, the control panel's On button first opens a WebSocket to Project TouCans' Pico-W. As an experiment, rather than power cycling the Pico-W, I simply hit the 'On' button again even though the rig was already on. Sure enough, that did it. The connection was back up and running. I asked ChatGPT what might have caused this. I mentioned that the phone, as Samsung Galaxy 23 had forced an update of One UI. The answer that came back was that versions of One UI newer than 6, (I'm on 7 now), do indeed cut socket connections when...

 We moved to a web based control panel for Project TouCans a few months back. It's worked really well. Changing the network model of the system to one where TouCans uses a smart phone for network resources as a client even unexpectedly reduced the audio noise in the rig. Even though the control of the rig is now done via browser, KO6BTY and I hadn't tried to control the rig from more than one smart phone until our recent US-4578 POTA. Before I go any further, here's a brief introduction to the control panel. On a POTA activation last week, I set up the rig to talk to my smartphone via a mobile hotspot. KO6BTY then set up her smart phone to use my smart phone as as Wi-Fi source. The rig was immediately available to her at the same internet address! TouCans has almost moved into the cloud! For now, it's moved into the WLAN! The control panel doesn't have the concept of multiple users yet, so Hamie and I had to adjust keying speeds when each of us took control over fr...