Hi sean, Thanks for the ideas. I tried the rudder sensor on my old autopilot, works fine there so nothing wrong with the sensor. Connected back to pypilot but the motor controller just seems not to detect it any more after the pypilot software update.
I noticed there are two sets of rudder configuration in the pypilot.conf file, one starting with "servo.rudder" and the other set starting with just "rudder.". Is that as it should be? which set should I revert to defaults, or both? Once I have reverted them, how do I make sure that change has been saved onto the motor controller? Is there a way to read the saved settings from the motor controller so I can check whether the .conf file has been copied over to it?
I don't think there should be any need to add resistors and things because the rudder sensing was working without additional resistors before I did the software update.
I ran the script you suggested, got this (note the "using default servo calibration" warning... is that normal?):
Any ideas? Thanks!
...Also, since running the opencpn android app the max slew has gone back to 98 again and still keeps reverting to that after I edit it, even with the updated software. Is there any way at all that I can force the pypilot to save the current contents of the pypilot.conf onto the motor controller after editing it manually? I still have no way to edit the slew other than editing the .conf file manually because that option is missing in macos plugin and always goes to 98 in the android plugin. I spent a lot of time trying to get the config tools working in macos and found most of the dependencies but I'm not there yet.
I noticed there are two sets of rudder configuration in the pypilot.conf file, one starting with "servo.rudder" and the other set starting with just "rudder.". Is that as it should be? which set should I revert to defaults, or both? Once I have reverted them, how do I make sure that change has been saved onto the motor controller? Is there a way to read the saved settings from the motor controller so I can check whether the .conf file has been copied over to it?
I don't think there should be any need to add resistors and things because the rudder sensing was working without additional resistors before I did the software update.
I ran the script you suggested, got this (note the "using default servo calibration" warning... is that normal?):
Code:
tc@box:/mnt/mmcblk0p2/tinypilot/pypilot/pypilot$ python servo.py
Servo Server
loading servo calibration /home/tc/.pypilot/servocalibration
WARNING: using default servo calibration!!
failed to open (u'/dev/serial/by-id/usb-1a86_USB2.0-Serial-if00-port0', 4800) for nmea data
connected to gpsd
arduino servo found on [u'/dev/ttyAMA0', 38400]
serialprobe success: /home/tc/.pypilot/servodevice [u'/dev/ttyAMA0', 38400]
voltage: 13.42 current 0.0 ctrl temp 20.96 motor temp False rudder pos False flags SYNC
voltage: 13.41 current 0.0 ctrl temp 20.96 motor temp False rudder pos False flags SYNC
voltage: 13.41 current 0.0 ctrl temp 20.96 motor temp False rudder pos False flags SYNC
voltage: 13.42 current 0.0 ctrl temp 20.96 motor temp False rudder pos False flags SYNC
voltage: 13.42 current 0.0 ctrl temp 20.97 motor temp False rudder pos False flags SYNC
voltage: 13.42 current 0.0 ctrl temp 20.97 motor temp False rudder pos False flags SYNC
voltage: 13.42 current 0.0 ctrl temp 20.97 motor temp False rudder pos False flags SYNC
voltage: 13.42 current 0.0 ctrl temp 20.97 motor temp False rudder pos False flags SYNC
gpsd is using device /dev/ttyUSB0
found gps on gpsd /dev/ttyUSB0
voltage: 13.42 current 0.0 ctrl temp 20.97 motor temp False rudder pos False flags SYNC
voltage: 13.42 current 0.0 ctrl temp 20.97 motor temp False rudder pos False flags SYNC
voltage: 13.42 current 0.0 ctrl temp 20.97 motor temp False rudder pos False flags SYNC
nmea ready for connections
listening on port 20220 for nmea connections
voltage: 13.42 current 0.0 ctrl temp 20.97 motor temp False rudder pos False flags SYNC
voltage: 13.42 current 0.0 ctrl temp 20.97 motor temp False rudder pos False flags SYNC
voltage: 13.42 current 0.0 ctrl temp 20.97 motor temp False rudder pos False flags SYNC
voltage: 13.42 current 0.0 ctrl temp 20.97 motor temp False rudder pos False flags SYNC
voltage: 13.42 current 0.0 ctrl temp 20.97 motor temp False rudder pos False flags SYNC
voltage: 13.42 current 0.0 ctrl temp 20.97 motor temp False rudder pos False flags SYNC
voltage: 13.42 current 0.0 ctrl temp 20.97 motor temp False rudder pos False flags SYNC
voltage: 13.42 current 0.0 ctrl temp 20.97 motor temp False rudder pos False flags SYNC
voltage: 13.42 current 0.0 ctrl temp 20.97 motor temp False rudder pos False flags SYNC
voltage: 13.42 current 0.0 ctrl temp 20.97 motor temp False rudder pos False flags SYNC
voltage: 13.42 current 0.0 ctrl temp 20.97 motor temp False rudder pos False flags SYNC
voltage: 13.42 current 0.0 ctrl temp 20.97 motor temp False rudder pos False flags SYNC
voltage: 13.42 current 0.0 ctrl temp 20.97 motor temp False rudder pos False flags SYNC
voltage: 13.42 current 0.0 ctrl temp 20.97 motor temp False rudder pos False flags SYNC
voltage: 13.42 current 0.0 ctrl temp 20.97 motor temp False rudder pos False flags SYNC
voltage: 13.42 current 0.0 ctrl temp 20.97 motor temp False rudder pos False flags SYNCAny ideas? Thanks!
...Also, since running the opencpn android app the max slew has gone back to 98 again and still keeps reverting to that after I edit it, even with the updated software. Is there any way at all that I can force the pypilot to save the current contents of the pypilot.conf onto the motor controller after editing it manually? I still have no way to edit the slew other than editing the .conf file manually because that option is missing in macos plugin and always goes to 98 in the android plugin. I spent a lot of time trying to get the config tools working in macos and found most of the dependencies but I'm not there yet.