Anchor alarm: typo in bow height property, no depth saved?
I have started using Anchor Alarm plugin and have noticed two things:
1. design.bowAnchorHight is probably typo for Height?
2. It seems that depth is not stored at Drop anchor. Would be useful to have together with position to be show in UI.v
Also, I have four GPS sources on the boat: 2x plotter, AIS and USB GPS in Cerbo. Only Cerbo is on during night as N2K network is off. I suspect, gps position is not enough to calculate heading and show how the boat is oriented, right? Maybe the UI should rotate the boat on screen to point to anchor position (most likely direction)?
And thanks to all SignalK developers, I am so glad to found it on my Cerbo and I am now exporing endless opportunities it provides.
26 Replies
Yep, that’s a typo
The depth is stored. It’s stored in the position as “Altitude”.
And yes, magnetic heading is needed to show the boat orientation.
But I don’t see any reason not to make it point at the anchor if heading is not available.
What do you think @Ilker ?
(And BTW, you reminded me that I needed to publish a new version, check it out)
@Scott Bender but I do not see altitude in my position, just lat/lon
Is depth available when you drop the anchor?
I just tried it.
I am on the lastest anchor alarm plugin,
Yes, depth was available when I droped the anchor. I turn n2k net off after anchoring. Will check next time I anchor.
New plugin is nice, particularly track. Was using freeboard-sk for track.
Interesting that freeboard does not show anchor circle anymore after upgrade of anchor plugin. Maybe because SK was restarted?
Hmm. Freeboard should be able to show after a restart
Was showing before, maybe update chanyed something that confuses freeboard?
I’ll test it out…
Yes it makes sense I think, though calculating that is a bit of an extra. I will look at it at the next round of updates.
Isn't
navigation.anchor.bearingTrue already pointing there?
I have just tested after upgrading the plugin...
It seems to work fine controlling from FSK.
The issue is that maxRadius is a string value when set from the plugin.
@AdrianP great find, it seems that was broken with last update of anchor alarm
@Scott Bender I have tested anchor drop again with N2K instruments turned on and the depth is still not stored in altitute in
navigation.anchor.position
Here are all position and depth properties available at time of drop.
Depth was used by plugin to calculate anchor radius correctly (5 x depth.belowTransducer).
And another minor thing: anchor alarm plugin allows one zoom too many for Satellite images. I suspect max_zoom is not set correctly for leaflet.
You need depthBelowSurface
derived data plugin can do it
@AdrianP I can’t reproduce the maxRadius issue
Do you have steps to reproduce?
Using the plugin UI I just pressed the ⚓ button and it produced the string value.
Also shifting it also produced the same result
If I used FSK (uses plugin API endpoints) then I get a number value
I swear I tried that! But I’m seeing it to now.
I published a fix
@Scott Bender fix works, tested now with freeboard. Also, derived data plugin got nov altitude in anchor.position to me.
Should the typo be also fixed or will this break some compatibility?
Yeah, If I fix that it will break anything that is using it now.
And I know WilhelmSK uses it, there may be others…
This depends on where you are. Satellite view has more detailed views in some places than others. For the majority of users and locations max_zoom works at the set level.
@Scott Bender maybe add new (correct) and support both until apps are migrated after a year or so?
Yep, makes sense