2021-03-07, 02:53 PM
(2021-03-06, 11:25 PM)ironman Wrote: Well this is already impressive! You seem to have made a successful UI connection to a tinypilot (connected to...) , and if I'm not mistaking, your tinypilot has a successful connection with an Arduino controller ('idle'). Am I right? Furthermore, you have provided your tinypilot successfully with gps messages (blue lines in the nmea debug) and pypilot on the tinypilot responds positively by showing 'gps' as autopilot mode in the dropdown. This is probably because there is also an RMC message, but I cannot see that in your output.
The overcurrent_fault you get because the arduino measures the current that goes through your motor. It does this by measuring a voltage on one of its pins (A1), which pin is supposed to be tied to a shunt resistor, that is tied on one end to ground, on the other end to the motor driver. If you don't tie up that pin, its voltage will float around and could trigger that error. I don't know exactly what line you have commented out, but the overcurrent error I believe cannot be disabled. I't try to tie A1 to ground and see if that gets rid of the message. Over all, I see no reason to throw your towel into the ring at this point. Next step would be to get hold of one of those IMU's.
Hi Ironman
Every time I try and set-up Pypilot on Openplotter I get an error message saying I must create a connection between SignalK and Pypilot (Picture 1) and so I tried to configure a connection under SignalK server using the TCP server as in picture 2 but that is not what the programme wants and the error keeps coming up, any ideas.
Secondly, before I make a complete fool of myself can I ask you the hardware set-up for Openplotter. As I understand it you only need the IMU/GPS and the motor controller. Thus, do you still need the pi zero, and arduino (motor.ino)?