2021-03-06, 11:46 AM
(2021-03-05, 05:18 PM)ironman Wrote: 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>'.
Hi ironman
Thank you for your reply. Yes, I sort of assumed that the pypilot plugin had all the necessary software to run pypilot. I have, despite my age and stupidity, made some progress and can semi run the programme from the OpenCPN plugin as shown in the picture. However, if you have some time could you help me a bit. As I am static in my room the COG does not change is this the reason the status for pypilot is "idle" as in the picture? Secondly, why do I still get the SYNC OVERCURRENT_FAULT even though I have corrected the motor.ino code and deleted the "//" before the define the sensors lines.
As regards running Pypilot from Openplotter I am having all kinds of trouble and think I am just too old and stupid for this so will give it up for a day or two.
Best wishes
Richard