2020-05-05, 11:34 PM
(2020-05-05, 06:24 PM)seandepagnier Wrote: It's a great idea to make ap and client work at the same time, I didn't consider this for tinypilot.
You can switch between client/ap using the lcd and remote, so maybe this is easier than taking the sd card out and editing the network file. Also, using bluetooth may not work well because it is disabled to get the hardware serial of the pi for the motor controller.
I have not had issues with tinypilot as a client so maybe the problem is in the access point?
Back to the original idea if you had network discovery possibly avahi setting could stay the same even if the network gets changed. I feel odd suggesting this because for a long time always removed it :-(
Your correct about the serial port issue for tinypilot. I see that hciattach has /dev/ttyAMA0 open on my controller. Wouldn't think that would be a very efficient way to interface to bluetooth.
Guess I'm just a bit paranoid about wifi after 20 years of dealing with flaky wifi as an it manager.
Like you say usually an access point problem.