2020-03-25, 08:32 PM
(2020-03-25, 05:44 PM)jamos.tan@gmail.com Wrote: Hmm, might it be a power management thing that causes the problem? What's also strange is that the option is greyed out, shouldn't be the case, at least with me it is still selectable. Never had it greyed out. What do you have connected to your USB headers and to the GPIO pins? Do you use an external (powered) usb hub?
Also, another question. After you do the re-select changing the serial port so that it works again, does it keep working as long as you have the pi booted? Does it reset and break only after reboot?
Also, what i find sometimes helped me in serial management troubles, is to remove all the connections and press reset. Then re-assign everything again. See if there are still things greyed out then.
All good questions! Once I reselect it continues working as long as openplotter is running. I can sail around all day on autopilot. But if I manually exit openplotter, or reboot the system, pypilot does not restart.
I think the key might be in here ...
Code:
connect failed to localhost:21311... which does not seem to happen once k-plex and serial ports are restarted. Could there be a timing issue during the startup scripts? I tried a 10-second delay but it didn't help. I'm digging into Sean's code to try and understand the startup sequence but it's a bit advanced for me.
I'd assumed I cannot select device because the Pi serial port doesn't identify itself with a vendor and product ID.
Power problems are an interesting idea. I'm running 2 x USB devices -- GPS puck and FTDTL serial port connected to the AIS receiver -- and GPIO powering a panel LED. Maybe I'm pushing the limits of a 3A power supply during openplotter startup. Hmm ... back to the boat for more experiments ...