Ah, reading back I see a problem. You expect to get a heading in the pypilot plugin because there is a gps heading in signalk? That won't happen, I'm afraid. Pypilot can only steer on its own heading - it needs the IMU. Without an IMU, I believe there is not much use for pypilot. With an IMU, Pypilot also produces heading, pitch and roll, and it consumes externally delivered gps tracks (route data), wind angle, to steer by apparent wind, and gps speed, to calculate true wind to steer by. That data is either exchanged to and from pypilot through nmea/20220 or signalk/3000. An IMU won't cost you the world, and I would suggest you buy them from the pypilot store, because these are tested before they are shipped. I don't have shares, btw ;-) https://pypilot.org/store/index.php?rt=p...uct_id=129
Having said that, it seems your pypilot is not even running to start with. If you have openplotter, you would need to start pypilot with the Raspberry->Openplotter->Pypilot facility, switch to Autopilot. Then, when you open the pypilot plugin, it should no longer show 'disconnected', what I see in your screen dumps, but 'Connected to <hostname>'.
Having said that, it seems your pypilot is not even running to start with. If you have openplotter, you would need to start pypilot with the Raspberry->Openplotter->Pypilot facility, switch to Autopilot. Then, when you open the pypilot plugin, it should no longer show 'disconnected', what I see in your screen dumps, but 'Connected to <hostname>'.