Greg Young - anchor watch guage…am i correct t...
anchor watch guage…
am i correct that this is blank? untill anchor is dropped . (im just seeing a black screen when i add it to a layout)
93 Replies
Did you get build 237?
It should say “The anchor is not deployed”
yep
yep build 237.
nope, just blank
Can you get a screenshot?
Oh. Using the Light theme?
i dropped the anchor . it shows the circles arrows etc … as expected i think.
but as soon as i raise it… get black … nothing
Ok. I think I have it fixed.
Is it also not showing the distance from anchor in top left when it is dropped?
nope
Ok. It will be fixed in the next build.
ok.
will test with a coffee tomorrow morning 🙂
Appreciate it!
in testflight description, it shows “screenshots” ,
for 4 types of devices,namely Ipad, iphone. APPLETV, watch.
i thought you dropped appleTV support?
New topic.
New layouts and Templates editor
have been using it a bit lately, but confused.
the first group are the active ones in current layout,
second group “custom” .. appear to be identical to above?
then when clicking “add” .. i then see “all” my custom templates appear, and can add them into active layout.
im not sure if this has any improvement over the older editor?
Q: still not sure how to delete unwanted custom templates … from older editing sessions …
also, new editor no longer? shows the built in templates? (which i typically dont use anyway)
The second group “Custom Templates”, are all the templates used in this layout.
The first group are all your pages.
ah ok.
May be identical if you have a different template for each page?
maybe that’s it
You should see the builtins when you add a new page.
The second group there
And you are right no way to delete unused template.
Will add…
anchor guage.
just testing (boat on dock) … so fixed heading, no movement.
my boat at dock has heading almost dead north, and current wind is also same.
so i see a red arrow at top (awa?) .. good so far
however periodically the red arrow spins all the way around the dial…
i think this is because of the heading and wind direction being virtually the same? and it recalculates? the red arrow
and sometimes it does a 360 circle to new AWA angle?
The Apple TV app is still there, but I have not updated it in a long time.
appleTv. noted.. not goimg down that rabbit hole 🙂
The red arrow is true wind direction
Sorry
Confusing names
TWD
hmm, i need to think this one .. as i dont use “true wind”.. need check , i guess its computed in derived ata
So that relative to north
i dont have STW .. so typ use AWA and GWD
Not “true wind”, like TWA
ah … the “true wind” definitions bite me
agreed!
In that case, is “true” as apposed to magnetic
The boat pointer uses heading true
ok its there
I am seeing some strange “flipping” also…
yep,
with wind angle moving a few degrees either side of boat heading,
the red arrow does the “full circuit” … so rather than going from say +5 degrees to -5 degrees,
its going the long way around rather than across the top
something is up with boat heading also…
my boat is on pontoon, heading not changing, and heading guage agrees,
but the boat arrow in anchor guage is movimg around.. unexaplainable?
ah, just realised the arrow is COG…. and its moving because of GPS jitter .. i can see the boat track and the arrow moving with the boat track wandering
The “boat arrow” is heading true
in that case … there is an issue .. its movimg all over the place - yet boat is not, as confirmed by my heading guage .
Your heading gauge in WilhelmSK is not jumping around also?
ok my bad …
i have multiple sources of heading, and i think its causing it.
im te-checking my priorities in signalk connections for heading. (and also derived data)
(wsk heading guage is locked to correct source)
but anchor watch guage is obviously seeing the different sources and jumping between them ..
nope that didnt fix it …
the boat arrow is “flipping” back and forth… mostly correct, but momentarily jumps in weird direction ..
still looking … but now have priosity for trueheading in signalk set for derived data source,
that should have fixed it?
that should have fixed it?
example below
I’ll try to see if I can reproduce it tomorrow…
hold off… i think i fixed it,
took a little for all my changes to settle ….
setting the priority in connections to derived data and removing other sources fixed it i believe
nope it didnt fix it.
i have trueheading set for only ONE source in signalk connections .
i have wsk heading guages setup for each of the sources anyway side by side,
and they are rock solid , no movement.
yet the boat arrow in anchor watch guage flips around … but none of the heading paths in signalk are moving (correct)
… tomorows problem! 🙂
Can you get me a log file?
n2k connection log file? or just a skserver log file?
n2k
confirming that latest test flight build has solved the various errors above.
i now see the distance text (& “anchor not deployed “ etc).
wind from wrong direction at moment, cant confirm the wind thru North movement yet.
curious .. if your using the anchor watch guage on your iwatch… the distance text must be very small?
ah something weird happening with boat position?
when anchor distance is small, boat position is wrong..
im using the navionics guage side by side with anchor watch..
navionics looks correct, anchor watch wrong.
is it using the wrong “position” calc? (bow vs gps position?)
Yeah it’s actually because the boat position is based on bearing to anchor
Which is from the bow
If you move the anchor away from the bow, it’s fine because then the difference between the gps and bow is small compared to the distance from anchor
It would totally make sense if I drew the boat to scale
ok further testing ..
scenario
boat at pontoon (hence not movimg)
drop anchor (obviously directly below bow, and boat doesnt move .. except for known GPS “wander”)
anchor watch guage
boat position jumps around … obviously driven by gps wander.. and at times boat position is forward of anchor - ok so far.
and the “distance to anchor ” (text on top left) shows ~9m (which is the “GPS distance to bow” that i have set in settings)
however comparing to navionics guage, it shows boat “always”. behind the anchor.
.. so i think the difference is how the “position” is displayed? or maybe the navionics guage (aka chart & track etc) displys different?
once i manually move anchor position to out in front of boat .. both agree.
.. so its when the anchor distance is small (in this extreme scnerio… anchor “under bow”) that the two guages show differently .
.. and thinking about it… anchor watch guage is actually displaying correctly ? .. as the gps wanders.
Can you confirm..
for anchor watch guage, the boat position (arrow) .. is this “GPs position? or “bow position “?
oops, didnt see you response above when i hit enter on my msg ..
*
so is the text in top left consistent with whats beung displayed?
eg the text is showing GPS position to anchor (in my case the 9m bow-gps offset)
however the boat position arrow is actually bow position?
Correct
I should change that to distance from bow
ok .. its my nonsensical scenario which is creating the confusion …
… to save my confusion, in the navionics anchor watch layout that i use , i show BOTH distance to bow and distance to “boat”
.. yep and make the outer circle red (the alarm circle)
I did that at first, but I thought it was kinda confusing
I thought it looked like something bad was happening
this is what i use when at anchor
Yeah, but there you can see right away that it’s ok.
yeah.. i guess so .. but its then inconsistent to how its shown on navionics guage
oh, one point i forgot to mention, at high (max) zoom level on navionics (as example above)
the boat symbol disappears.. and no ammount of fiddling with size and transparency settings can make it work
I’ll switch it back to red and see if I get any other feedback…
im ok either way …
thought.
can the circle “flash” when it breached them?
eg when you at the warning radius.. have it blink?
I do fill it red or yellow like on the map
.. and havent as yet tested what it displays when it hits the alert?
(aside the expected wsk notificatins)
Can you show me what your boat looks like when it does show on the map?
Mine is not disappearing
i have ship size set to max in settings … in below examples.
zoomed out a bit .. to when icon shows
max zoom in
if i reduce ship size in settings… it only appears at even more zoomed out levels..
It’s supposed to draw to scale
hmmm not doint that on my ipad
and FWIW its “always” been the same .. not a recent change
your example above … max zoom in? what settimg for “ship size”?
Max zoom in, ship size set to minimum
ok. very different.
i have to have max ship size set .. for it to show at first zoom out threshold .. (doesnt show at max zoom in)
Can you send me your baseDeltas.json
thats using the + /- zooms buttons
There’s some logic there about deciding to show the boat at scale, or show the “triangle” boat symbol
sent via PM
Ok, I’ll play with it tomorrow.
Something about the size/dimensions of your boat…
yeah .. its not big enough! 🙂 haha
That’s what she said
Looks fine, something strange in my code that draws the boat
You can actually see your boat in that screenshot
There’s strange red shape there
yeah its a long red sliver
and every now and then a weak boat icon flashes up and then dissapears
i tried moving the anchor position way further fwd .. doesnt help
Yeah, that won’t effect it
definitely some correlation between zoom level and "ship szie"settings .. doesnt like it at the max zoom in level
Yeah, that affects when I try to draw the boat to scale.
Instead of showing the icon
transparency setting doesnt effect it
.. just trying everything to ee what infleunces it
.. "tomorrows"problem .. (thats why i hadnt ever bothered to tell you)
Do you see any other boats drawn like the ones in my screenshots?
like ais you mean
ais targets size is a different setting?
the close by (not moving) AIS targets are larger as compared to the moving ones in above snapshot.
but isnt ais target size also dependant on whats in its AIS message about boat size?
Your log and your baseDeltas, looks fine for me. WTF?
Hmm. Ok. It’s messed up on the iPad
Ha! It’s because your beam is coming as zero from AIS
The only way I was able to fix it was by using the path-filter plugin
For some reason source priorities are not working in this case.
ok , will check my AIS txr (presumably this is where its picking up beam zero .. although its correct in basedeltas).
changes looks good, except, the distance to anchor in anchor watch guage has dissapeared?
i do get the “amchor not deployed” text showing(when anchor raised of course)
Hmm. I changed it to distance from bow
the workaround for zero beam has fixed the boat size in navnionics 👍
eitherway, the text aint showing
Do you see anchor distance from bow in the data browser?
If you add design.beam to the path-filter plugin, it will draw your boat to scale
all looks normal on my usual anchor watch layout
thanks for the heads up on my AIS data - indeed boat data had not been fully setup in AIS
(none of the dimensional data had been input)
now my ship size is scaling as expected. (& position data from my AIS will agree with other main GPS reciver!!)
solved
Ais should not be overwriting the stuff in settings, but that’s another problem…
I also now ignore beam and length if they are zero
i wonder if this is in any way related to that other error i reported ?
(we discussed it above) .. the "type error".. which is related to my vessel rego ?
only two places my vessel rego appears - AIS txr & basedeltas
Nov 16 12:28:05 TypeError: Cannot create property 'meta' on string 'MEN59Q' at /usr/lib/node_modules/signalk-server/node_modules/@signalk/signalk-schema/dist/fullsignalk.js:224:35 at Array.reduce (<anonymous>) at addValue (/usr/lib/node_modules/signalk-server/node_modules/@signalk/signalk-schema/dist/fullsignalk.js:216:27) at addValues (/usr/lib/node_modules/signalk-server/node_modules/@signalk/signalk-schema/dist/fullsignalk.js:188:5) at FullSignalK.addUpdate (/usr/lib/node_modules/signalk-server/node_modules/@signalk/signalk-schema/dist/fullsignalk.js:110:5) at FullSignalK.addUpdates (/usr/lib/node_modules/signalk-server/node_modules/@signalk/signalk-schema/dist/fullsignalk.js:97:10) at FullSignalK.addDelta (/usr/lib/node_modules/signalk-server/node_modules/@signalk/signalk-schema/dist/fullsignalk.js:54:8) at DeltaChain.doProcess (/usr/lib/node_modules/signalk-server/lib/deltachain.js:15:18) at /usr/lib/node_modules/signalk-server/lib/deltachain.js:34:22 at Array.<anonymous> (/home/pi/.signalk/node_modules/signalk-path-mapper/index.js:65:9) at DeltaChain.doProcess (/usr/lib/node_modules/signalk-server/lib/deltachain.js:18:26) at /usr/lib/node_modules/signalk-server/lib/deltachain.js:34:22 at Array.<anonymous> (/home/pi/.signalk/node_modules/@signalk/calibration/index.js:88:15) at DeltaChain.doProcess (/usr/lib/node_modules/signalk-server/lib/deltachain.js:18:26) at DeltaChain.process (/usr/lib/node_modules/signalk-server/lib/deltachain.js:11:21) at Server.app.handleMessage (/usr/lib/node_modules/signalk-server/lib/index.js:233:38)
..
that is .. i wonder if the vessel rego coming in from the AIS transceiver is also overwriting the same in base.deltas ...
and its the "format"? of the vessel rego in the AIS message that causing this erro
teppo and i have a separate thread runnig on this one
I don’t think they are related