2021-11-04, 08:29 AM
(This post was last modified: 2021-11-04, 09:03 AM by aardvarkash10.)
(2021-11-04, 06:37 AM)seandepagnier Wrote: it is in the ~/.pypilot directory a file named serial_ports or a file blacklist_serial_ports
What specifically is the program conflicting? I will like to build logic in the future to help negotiate these issues if possible.
Hi Sean - thanks for your response. Below is the post I originally put on the openplotter forum a couple of days ago.
Hi all. A plug-n-play, non-technical type here so bear with me and speak slowly.
I've been building a basic Openplotter system now for a couple of months, plodding along as we work our way through our COVID-19 restrictions and winter.
I now have it up and mostly running. Physically, its a RPi 4B 2Gb with a separate powered 4-port USB 3.0 hub. A 12v -> 5v 3A converter powers each device separately ie 2 x 3A supplies. An IMU is installed via GPIO. Power supply includes a 12v battery module with its own BMS in parallel with the main supply from house batteries (or a wall wart at home). HDMI output drives and external monitor. USB keyboard and mouse.
A 'U-blox 7' mouse-style gps device is plugged into the USB hub. It shows in the serial connection app as ttyACM0 and has the alias ttyOP_gpsmouse.
OpenCPN 5.2.4 is installed. SignalK is installed. OpenCPN gets all its data from the SignalK server on :localhost 3000
The gps device shows in the SignalK dashboard and with JUST OpenCPN running, the gps data gets to OpenCPN
If I install PyPilot 2.1.1 and make its connections to SignalK, it runs initially, but on reboot the gps data stream stops dead in its tracks - neither OpenCPN or Pypilot get gps data. The device still shows on the serial connection app, but no data coming or going to SignalK.
So, I read through Tony's thread today and his problem is identical - and it make sense since an error message I get (I think in SignalK server) is that the gps device is busy or being used by another program. I just could not figure out which program. This is what led me to removing openplotter apps until the problem resolved.
So, now from your answers for Tony, I understand that Pypilot is probing the USB ports on bootup and so the device is not available to SignalK and then to OpenCPN, because PyPilot got there first. I understand that I need to include a short line in the config file to blacklist the gps device so that PyPilot doesn't probe and attach to the port.
My problem now is I have no idea how to do this from the terminal console. This - "~/.pypilot" means nothing to me.I am a complete, rank beginner in linux, and the last time I wrote any code it was on portapunch FORTRAN cards at school in the 1970s.
What I actually need is for someone to take me through it, step by step, command by command, line by line.