Tiny pilot > signalk connection & accel calibration

[PaddyB]

Couple questions..
Setting up a tinypilot on a Zero 2w connected to openplotter, pretty much there but yet to get signalk pith & roll into signalk running on openplotter. I can see the nmea on tcp 20220 but can't find any sigK data - does tinypilot output Sigk? MDNS is turned on in the sigK server.

Also calibration, think I had it but does it "uncalibrate?"
Saw this in the opencpn plug calibration tab >

Code:

need more range 0.5199796348810196
need more range 0.5199796348810196
need more range 0.2911652068297068
need more range 0.2911652068297068


need more range 0.19012243158843684
need more range 0.2664944892483099
need more range 1.0538310772860828
need more range 1.0555171346912784
sphere3 fit [-0.017128628355838026, -0.0214192270643163, 0.03854657004806471, 1.0223460571350413] [0.08315672347785737, 0.0]
calibration distance too small  0.005906637264818559
sphere3 fit [-0.01653031537249967, -0.022856549753975917, 0.05546575987008896, 1.0226817513736448] [0.07741974752223754, 0.0]
calibration distance too small  0.0009588511889133668
calibration distance too small  0.0014724202246462212
calibration distance too small  0.008852011333180605
sphere3 fit [-0.01609303751368233, -0.012434784484183198, 0.05035921264096224, 1.0213177372455335] [0.08092463002513647, 0.0]
sphere3 fit [-0.03436867971747875, -0.01175890760784436, 0.03773435914847985, 1.026718344928173] [0.07861036504018855, 0.0]
sphere3 fit [-0.03399093456092911, -0.011425630407026363, 0.03888269924930126, 1.0263387117277727] [0.07816269605395511, 0.0]
sphere3 fit [-0.04027631788977234, -0.011974837929133765, 0.03779908981411573, 1.0253047869122576] [0.07753764658107902, 0.0]
sphere3 fit [-0.03650774211221297, -0.01258915111750129, 0.03764521810750497, 1.0255375990363733] [0.0879688139896362, 0.0]
sphere3 fit [-0.03854745059843447, -0.013237726845483548, 0.03580181432730549, 1.0260765567027215] [0.07837648825161524, 0.0]

need more range 0.007370885829925511

need more range 0.007370885829925511

With "sphere3 fit" thought that was that but maybe not - does "need more range" mean it's "uncalibrated" itself? Should I lock it after a " sphere3 fit" message. 

One last one, is it possible to enable/disable & +10/-10 using a wifi put command or similar? Would be nice to have a little remote using a spare  esp8266.

Thanks! Install was pretty quick and easy really 

[hans-martijn]

Hi PaddyB,

did you check on your signalk server under security? There should be a new access request. When you allow it, both systems should be connected. It looks as if you have to calibrate indeed.

-Hans

[PaddyB]

Hi PaddyB,

did you check on your signalk server under security? There should be a new access request. When you allow it, both systems should be connected. It looks as if you have to calibrate indeed.

-Hans

No access requests received in the server. I found this being broadcast on tcp port 2947 on the zero IP address when the PiZero boots up.
{"class":"VERSION","release":"3.23.1","rev":"3.23.1","proto_major":3,"proto_minor":14}
NMEA being received on tcp 20220
$APXDR,A,-32.820,D,PTCH*6D
$APXDR,A,54.258,D,ROLL*57
$APHDM,357.476,M*37



The calibration seems weird, I need to take the setup ashore the get a stable platform to calibrate, if it needs recalibrating then that looks like it will happen every time the sensor is on the boat.

[hans-martijn]

Did you look at the following thread: https://forum.openmarine.net/showthread....754&page=9 ? There were several updates to make it work. Calibration hasn't been an issue for me; first tell when the boat is horizontal, then I usually make a few rounds on the engine. It took me a while to get a good sensor though. If I had to start over I'd buy one from Sean, since he tests them before sending.

-Hans

[ironman]

You might want to check off the items on signalk connection first at https://github.com/pypilot/workbook/wiki...k-zeroconf. To troubleshoot, disable the pypilot service, run pypilot at the prompt, and post the output here.

Here you will also find the following remark: "With regard to heel and pitch, these readings are affected by the compass heading offset that is set in the compass calibration screen. See https://forum.openmarine.net/showthread....2#pid17922. This effect makes the usability of pitch and heel somewhat non-universal." In other words: there is a big chance that pitch and heel are not usable because they are intermixed. What you need them for?

[PaddyB]

You might want to check off the items on signalk connection first at https://github.com/pypilot/workbook/wiki...k-zeroconf. To troubleshoot, disable the pypilot service, run pypilot at the prompt, and post the output here.

Here you will also find the following remark: "With regard to heel and pitch, these readings are affected by the compass heading offset that is set in the compass calibration screen. See https://forum.openmarine.net/showthread....2#pid17922. This effect makes the usability of pitch and heel somewhat non-universal." In other words: there is a big chance that pitch and heel are not usable because they are intermixed. What you need them for?

Think it's very close to being  sorted, thanks  hans-martijn!! 
This post did it https://forum.openmarine.net/showthread....7#pid23717 though not managed get it saved to tinypilot yet. 

Heel & pitch > " What you need them for? "  - don't know yet   
Though had it working before with pypilot on a Pi4 & logging, was interesting seeing when the fishing boats went out with a blip in the graphs as the wash rocked the boat in the anchorage. Might be handy to compare sail trim & speed to heel when reefing, or maybe a rough idea of sea state. I just love data, sometimes you find things in the plots that are useful but unexpected. 

THANKS GUYS!! 

[PaddyB]

Think it loads on boot now. From https://forum.openmarine.net/showthread....7#pid23717 ..

I went into tinypilot over ssh, user tc, password pypilot then

Code:

sudo nano   /opt/bootlocal.sh 

added  python3.8-urllib3 python3.8-chardet python3.8-certifi python3.8-idna to the  # start pypilot section 

now looks like>

Code:

date
echo 'loading pypilot drivers'
time chpst -utc tce-load -is $PYTHON-serial $PYTHON-RTIMULib $PYTHON-ujson liblzma libudev $PYTHON-pyudev $PYTHON-six pypilot python3.8-urllib3 python3.8-chardet python3.8-certifi python3.8-idna

then
filetool.sh -b
to save the changes to disk.

Now after rebooting tinypilot it creates a websocket in signalk (after device added read/write) and send pitch/roll7yaw & heading data.
YAY!!