2022-08-01, 03:25 AM
(2022-07-31, 06:36 PM)drbarritt Wrote: Hi Sean, I have doneIt is safe to ignore, it cant convert 'None' for course. I updated pypilot to handle None.
Exception converting signalk->pypilot unsupported operand type(s) for /: 'NoneType' and 'float' {'pypilot': {}, 'GP': {'navigation.position': {'longitude': -4.051491166666667, 'latitude': 50.316603}, 'navigation.courseOverGroundTrue': None, 'navigation.speedOverGround': 0.09877335835591701}}
Exception converting signalk->pypilot unsupported operand type(s) for /: 'NoneType' and 'float' {'pypilot': {}, 'GP': {'navigation.position': {'longitude': -4.051491166666667, 'latitude': 50.316603},
Quote:All looks OK (I don't have an arduino connected at the moment) except for the SignalK error, which I have not seem before. The Calibration Loaded message seems to indicate the config file has been loaded OK.
I then calibrated the Accelerometer and then the compass (see screenshot attached) and left the system running for a while. The compass was reading correctly all the time. I checked the pypilot.conf file and the compass calibration reading had been updated:
imu.gyrobias=[2.170, -3.104, -1.021]
imu.accel.calibration.locked=false
imu.accel.calibration.points=[[-1.477, -0.626, -0.342], [-1.490, -0.631, -0.256], [-1.511, -0.652, -0.135], [-1.162, -1.646, -1.325], [-1.520, -1.446, 0.644], [-0.289, -1.290, -0.154], [-1.197, -0.597, -0.341], [-0.800, -1.673, -1.230], [-1.284, -2.000, -0.395], [-1.189, -1.545, 0.699], [-2.000, -1.648, -0.360], [-0.230, -1.667, -0.276]]
imu.compass.calibration.locked=false
imu.compass.calibration.points=[[22.565, -26.972, -12.068], [0.357, -20.012, -21.695], [20.611, -49.877, -18.364], [12.677, -45.714, -19.003], [11.747, -32.099, -16.014], [13.487, -24.927, -14.874], [42.104, -30.923, -13.414], [5.981, -10.747, -21.193], [36.552, -51.640, -18.912], [10.365, -20.223, -16.448], [18.705, -40.635, -14.600], [24.066, -22.528, -12.068], [38.554, -24.056, -12.707], [45.774, -38.989, -15.125], [34.193, -15.944, -13.893], [48.943, -49.759, -98.025], [20.135, 1.035, -22.402], [40.436, -46.114, -16.562], [11.342, -35.861, -16.539], [5.576, -29.559, -18.569], [35.552, -10.441, -15.992], [29.785, -3.339, -18.569], [49.658, -41.776, -101.744], [23.256, -53.122, -19.938], [34.050, -45.479, -15.398], [35.432, -52.463, -19.505], [18.300, -12.252, -15.809], [36.934, -48.865, -102.177]]
I then re-booted the pi and the compass was not working at all and calibration values lost (see screenshot). The OpenCPN Pypilot plugin is working fine, although I do have to click on the config button and then OK to get it to connect to pypilot.
As always, any help much appreciated!lo
Regards
David
What pypilot plugin version?
Can you try running as you had, then stop pypilot. Check the config file. Make sure the calibration is correct. Backup the pypilot.conf file. Now start pypilot again, make sure it works and doesnt reset calibration. Now reboot. Check the contents of the config file. It must be getting rewritten somewhere? If the config file has the correct file when you run pypilot it is ok?
You are the first to report this issue.