2021-07-12, 07:01 PM
In my first posts, I was on a system that had previously pypilot from openplotter. (that would explain why ~/.pypilot already existed).
Now for testing purpose I'm on a "clean" system, just cloned and python3 install...
Creating the ~/.pypilot folder worked, pypilot can now run.
The connection to OpenCPN plugin works perfectly.
But in the calibration GUI, the data only refreshes at 1 delta per second (either in accelerometers or compass). Sometimes, multiple red dots will be created at the refresh if the IMU is moved enough in 1s.
Maybe not related, but when I try to calibrate, the points are way out of the globe, which isn't the case with the 2.1.1 version...
Leveling the boat works without issue (in a few seconds)
pypilot_client -c imu.rate says 20/second
pypilot_client -c imu.gyro produces a lot of output per second (possibly 20)
The compass value in pypilot & signalk is updated very rapidly, probably 20 times per second
after running pypilot_web, the web client (localhost:8000) works also well, with heading/pitch/roll updating rapidly.
Now for testing purpose I'm on a "clean" system, just cloned and python3 install...
Creating the ~/.pypilot folder worked, pypilot can now run.
The connection to OpenCPN plugin works perfectly.
But in the calibration GUI, the data only refreshes at 1 delta per second (either in accelerometers or compass). Sometimes, multiple red dots will be created at the refresh if the IMU is moved enough in 1s.
Maybe not related, but when I try to calibrate, the points are way out of the globe, which isn't the case with the 2.1.1 version...
Leveling the boat works without issue (in a few seconds)
pypilot_client -c imu.rate says 20/second
pypilot_client -c imu.gyro produces a lot of output per second (possibly 20)
The compass value in pypilot & signalk is updated very rapidly, probably 20 times per second
after running pypilot_web, the web client (localhost:8000) works also well, with heading/pitch/roll updating rapidly.