This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
OP2 pypilot driver_timeout
#1
Sean et al,

Thank you for the excellent OP2 upgrade! I'm excited for the Signal-K integration.

So, some problems getting pypilot to play nicely ... Starting with a NOOBs Headless image, I installed newest pypilot as of last week (2.0.8beta I think?). IMU data is good, gps is good, OpenCPN plugin overlay is working.  But when I select AP it throws DRIVER_TIMEOUT.  No servo data on Statistics or Scope.  (see attachments)

Reverting to 1.2, the motor works normally so it's not hardware.

What am I missing?

Best,
Alan


Attached Files Image(s)
       
Reply
#2
Code:
       # if not moving or faulted, disengauge
       if not speed or self.fault():
            #print('timeout', t - self.command_timeout)
  
I find myself wondering ... since I have no position sensor, is it choking when it tries to infer rudder speed?

Best,
Alan
Reply
#3
DRIVER_TIMEOUT is really just a warning. It indicates that the motor controller is driving the motor but no current is measured in the motor. It usually occurs if the motor is disconnected but the controller is working.

I would check the connections and make sure manual control is working. If not, try backing up and then deleting pypilot.conf, maybe there is a setting in there that is preventing the motor from moving correctly.
Reply
#4
Manual control works. Motor control works in pypilot 1.2.

Ok, I think I found the problem: Bad IMU.

pypilot detects the IMU and receives data at first, but then zeros out.  See screen shots.  I think the crashing problem before was when it failed to detect the IMU.

Unfortunately, I'm in the middle of a 10-day trip. Is there any way to force navigation using only gps data?

Best,
Alan


Attached Files Image(s)
       
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)