Plugin: DashBoard

[TBillings]

Originally Posted by bcn

Matthew,

a question: where is the complete SHR message described? Is this a proprietary one ($Px...)? Or part of the NMEA standard? You are padding a Talker ID of $IN(strument).

Searching I found a Sonar (WASSP) using it. Plus a Si-tech GPS/gyro sensor.
Other Sonar manuals are mentioning it but no reference or definition.

Hubert

I'm pulling it from here: NMEA Revealed

I tried to include the "heave" portion, but I have my accelerometer to run every .5 seconds, which isn't a good enough resolution to calculate heave. The only terms included are the timestamp, heading (true), roll, and pitch. I'm sure there's a way to calculate the accuracy estimates, but then again... I don't really have any application for this sentence.

Though I was under the impression that the talker ID doesn't matter too much, since none of my devices talk to each other (they all feed into the Arduino/Raspberry Pi). I haven't actually found any application for the SHR sentence, other than for correcting wind angle/speed, but that's taken care of before the SHR is even compiled, so I think for me at least it's more of a gee-whiz kind of thing since I only use OpenCPN--which, to the best of my knowledge, doesn't even recognize SHR (but it sounds like it recognizes XDR, so I may explore that route for data logging purposes)

The real interesting thing, though, is that the MPU-9150 also calculates rate of turn/pitch/roll, which I also ran through the Arduino to correct for the induced wind at the top of the mast from how fast it's pitching/rolling/turning.

Sadly, my anemometer stopped working and I'm waiting for a replacement...

Originally Posted by bcn

Håkan,

the good thing about the OxTS/RT3000 sentence is that it carries the time stamp.
And typical for an inertial measurement unit the error estimate of the internal Kalman filters which gives you a pretty good idea about the quality of your data in a given moment.
What we are getting on our boat are precisions of 0.1° for heading and 0.07° for pitch&roll with the unit we have at hand. 100hz output.
Overkill for what we need normally but a nice toy...

Hubert

Ps.: with the Arduino you might consider SignalK for your data streams

The nice thing about the MPU-9150 is that the code I'm using includes a simple Kalman filter. I certainly wouldn't use it as an Inertial Navigation Unit (such as you see in some older jets before GPS), but it holds it's accuracy very well so long as you don't really move for the first five seconds. I suppose if you reset it at sea, then it probably wouldn't work to well.

I'm also trying to rework the code so that it gets at least a 10hz resolution, but the problem I'm running into is the sentences start writing over each other when it runs that fast. Another problem is that I'm not a programmer, so it's a slow process.

[tom_BigSpeedy]

Just to keep you updated...
Work on the tactics/performance enhancement is still in progress...
I struggled pretty much with filtering the current (Problem : averaging 350° + 10° should end in a 0° value, but not 180° as it would be if you simply do a 350+10=360/2 = 180...)
I found a neat solution now, which really works in all cases/angles.

I can show the current now on the chart (optional setting with a checkbox)



As you see, the performance values are already calculated and I added a blue marker to the bearing compass (the blue triangle outside the rose) which shows the Target-VMG angle.
So simply bring the blue TWA-arrow inline with the blue marker, and you do the optimum VMG up- or downwind.

I implemented the Expedition Polar type upload yesterday (I hope that polar_pi exports Expedition polars in the correct format ..).

Next :
* Place a marker (Waypoint) on the chart and use it as the bearing pointer (red dot) in the bearing compass instead of the NMEA-RMB data record.
* Implement a manual "Heel-Polar" input ...
* Cleanup ...

Thomas

[Baikal]

Not very ergonomic happened.
The position of the vessel was not visible.

See how it implement others.
Maybe we should repeat something?

By the way here is the analogue for CPN CSC | Kompass für OpenCPN und Chart Navigator

[tom_BigSpeedy]

Originally Posted by Baikal

Not very ergonomic happened.
The position of the vessel was not visible.

Baikal,
the arrow on the chart is transparent. You do see the position of the vessel on the chart, I' m not crazy ...

If you don't like it, you can simply take it away while sailing with a setting.
It's just a checkbox ...



Thomas

[rgleason]

Thomas, today I was surprised by the progress. It gets better and better.
I thank Baikal for the good examples. The CSC | Kompass for OpenCPN und Chart Navigator for OpenCPN example is very interesting, never knew about it. There are some good things here too.

Tactics/performance Enhancement

Compass Key
-----------------------
Red Circle = BTW Bearing to Waypoint = 23 degrees
Brown Arrow = ???
Blue Arrow centered = Compass
Blue Arrow = TWA True Wind Angle = 47 degrees ?
Blue Triangle = Target VMG Angle = 49 degrees
Bring the blue TWA-arrow inline with the blue marker, and you do the optimum VMG up- or downwind.

Four Corners
--------------
Upper Left = Bearing to Waypoint? = 23 degree - Red Circle inside Compass
Upper Right = Waypoint Name
Lower Left = DTW Distance to Waypoint
Lower Right = Predicted SOG = ~4.1 kn

Dashboard List
-----------------
SOG 4.01 kn
Current Speed 234 degrees
Current Direction .43 kn
Heel 5.8 < degrees
Leeway 1.9 < degrees
STW 4.24 kn
Polarspeed 73% / 5.82 kn
Performance VMG 2.61kn
Target VMG Angle 49 degrees
Target VMG 72%/ 3.6kn

=========
I may not understand this very well.
Where is the Target Boatspeed?
Are you using Target VMG Angle and Target VMG instead?

What exactly is Polarspeed 73% / 5.82 kn ?
What do the numbers represent?

What is the Perfomance VMG 2.61kn? Is that the Actual VMG?
Is Target VMG 72% / 3.60 kn numbers similar to Polarspeed numbers? Target VMG is 3.60 kn and that value is 72% of something? or is this expressing a divisor?

I really like the two blue arrows matching up. It helps us know what to do.
I am having trouble visualizing how to use the data presented elsewhere.
It seems to me that if we are concerned about
target values | actual values
target VMG | actual VMG
target VMG angle | actual
target Polarspeed | actual STW
They should be presented in this manner, so it is easier to comprehend.
(I may have this a bit messed up due to understanding)

[tom_BigSpeedy]

Originally Posted by rgleason

Thomas, today I was surprised by the progress. It gets better and better.
I thank Baikal for the good examples. The CSC | Kompass for OpenCPN und Chart Navigator for OpenCPN example is very interesting, never knew about it. There are some good things here too.

Tactics/performance Enhancement

Compass Key
-----------------------
Red Circle = BTW Bearing to Waypoint = 23 degrees
Brown Arrow = ???
Blue Arrow centered = Compass
Blue Arrow = TWA True Wind Angle = 47 degrees ?
Blue Triangle = Target VMG Angle = 49 degrees
Bring the blue TWA-arrow inline with the blue marker, and you do the optimum VMG up- or downwind.

Four Corners
--------------
Upper Left = Bearing to Waypoint? = 23 degree - Red Circle inside Compass
Upper Right = Waypoint Name
Lower Left = DTW Distance to Waypoint
Lower Right = Predicted SOG = ~4.1 kn

Dashboard List
-----------------
SOG 4.01 kn
Current Speed 234 degrees
Current Direction .43 kn
Heel 5.8 < degrees
Leeway 1.9 < degrees
STW 4.24 kn
Polarspeed 73% / 5.82 kn
Performance VMG 2.61kn
Target VMG Angle 49 degrees
Target VMG 72%/ 3.6kn

=========
I may not understand this very well.
Where is the Target Boatspeed?
Are you using Target VMG Angle and Target VMG instead?

What exactly is Polarspeed 73% / 5.82 kn ?
What do the numbers represent?

What is the Perfomance VMG 2.61kn? Is that the Actual VMG?
Is Target VMG 72% / 3.60 kn numbers similar to Polarspeed numbers? Target VMG is 3.60 kn and that value is 72% of something? or is this expressing a divisor?

I really like the two blue arrows matching up. It helps us know what to do.
I am having trouble visualizing how to use the data presented elsewhere.
It seems to me that if we are concerned about
target values | actual values
target VMG | actual VMG
target VMG angle | actual
target Polarspeed | actual STW
They should be presented in this manner, so it is easier to comprehend.
(I may have this a bit messed up due to understanding)

Rick,

don't take it too serious with the current diplay (and naming) of the performance data in the "text style instruments", please. I gouped the stuff together for now to verify the data against the loaded polar.
* percentage values are always the reference from your momentary speed
to the calculated (optimum) speed. It's simply STW/<opt.speed>*100
* The brown (orange) arrow in the compass instrument is AWA
* Blue arrow is TWA, correct.
* Polarspeed is the speed your boat can theoretically do based on the
polar data at the current wind angle and speed. Useful if you cannot go for the target-VMG angle for whatever reason, or if you're reaching instead of going up-/downwind.
* Performance VMG = actual VMG, correct. I will rename it to actual VMG.
I called it Perf.VMG as there is already a "VMG" instrument in dashboard.
* the blue centered arrow (in the compass instrument and in the chart) is the (sea) current.
* Target VMG = target boatspeed at target VMG (+% value as reference to your momentary STW)
The vertical layline in the compass instrument points to COG, so it may move aside, the width of the laylines represent your boat yawing around the vertical axis (needs still some improvement), so you really see the "target/waypoint area" you're COG indicator points to.
There's a right click menu on the dashboard to show/hide the laylines in the chart.
There's a checkbox in the dashboard settings to show/hide the current display (blue arrow) in the chart.

I can already place a temporary waypoint on the chart from the plugin.
Goal is -- as in Baikals screenshot -- to print the target-VMG angles onto that Waypoint and intersect it with your laylines. But that's to be done yet.
I hope that clearifies it a bit...

Thomas

[rgleason]

Thanks that really helps. I am going to think some more about it.

[Rasbats]

Constructed an electronic compass recently with the help of this blog:

King Tide Sailing

Connor responded quickly to a small issue I had with wiring up the RS232 connection (in my case both tx and rx wires had to be connected, as well as grnd).

The NMEA output from the compass has been used to stabilise a Garmin radar display, via the chartplotter, but it also feeds OpenCPN Dashboard without any problems.

The stabilised radar display is impressive.

The tilt compensation looks good.

Mike

[rgleason]

I have not seen any data from my 1994 raymarine fluxgate compass from the ST bus after being translated to Nmea 0183. I know my autopilot is receiving via a direct nmea 0183 connection but this data may not be available on the ST bus... if so it might be easier to use the arduino. How accurate and fast the compass?

[rgleason]

On arduino setup?

[Hakan]

I use this for my radar. Good enough. I produce the NMEA by Arduino and via a Simrad IS15 system to O but could as well go direct.
http://www.cruisersforum.com/forums/...ml#post1495725
Håkan

[Rasbats]

The posted KingTide setup uses a refresh rate of 1 Hz, to avoid NMEA sentences over-writing. However, because I am only using heading I increased the refresh to 10 Hz, without causing problems. 10 Hz is generally given as the minimum for radar stabilisation.

Accuracy is not known but must be similar to other recent DIY setups.

Mike

[jserink]

Hello All:

Problems wiht the dashboard:
This is my system:
jserinki7 jserink # uname -a
Linux jserinki7 4.1.12-gentoo #1 SMP PREEMPT Thu Nov 5 09:56:42 SGT 2015 x86_64 Intel(R) Core(TM) i7-2720QM CPU @ 2.20GHz GenuineIntel GNU/Linux
jserinki7 jserink # equery list 'opencpn*'
* Searching for opencpn* ...
[IP-] [ ] sci-geosciences/opencpn-4.0.0-r1:0
[IP-] [ ] sci-geosciences/opencpn-plugin-ocpndebugger-1.0-r1:0
[IP-] [ ] sci-geosciences/opencpn-plugin-statusbar-0.5-r1:0
[IP-] [ ] sci-geosciences/opencpn-plugin-wmm-1.0-r1:0

My problem is I'm sending the theses NMEA strings:
NMEA-GGA(1Hz), NMEA-ZDA(1Hz), NMEA-VTG(1Hz), NMEA-GSV(1Hz), NMEA-GSA(1Hz), NMEA-RMC(1Hz), NMEA-GLL(1Hz), NMEA-GBS(1Hz), NMEA-GNS(1Hz), they are all coming in via a TCP/IP socket and that is fine, I can see them in the debug windows, works fine.
Things that work:
1. lats and longs coming up fine,
2. Clock coming up fine,

Problems:
1. GPS in view is blank,
2. GPS status, the sky plot, is empty,
3. There is no other information.

I would have thought the dash board would be looking at the RAIM entry in the RMC string?

I have enabled the IEC61162-1:2010 compatibility and "Report extended information in NMEA GGA and RMC strings".

Is any one else seeing these issues?
perhaps its because I'm using a versin that is slightly out of date?

Cheers,
john

[rgleason]

Nmea Compass Solutions

Mathew Durst http://www.cruisersforum.com/forums/...ml#post1942813 Thank you.

MPU-9150 | InvenSense
MPU-9150 InvenSense | 1428-1009-1-ND | DigiKey

Mike Rasbats MPU-9130 compass & accel http://www.cruisersforum.com/forums/...ml#post1955635

Hakan arduino compass http://www.cruisersforum.com/forums/...ml#post1955694

Mike and Hakan Thanks, these are encouraging. MPU-9130 does not look very expensive either.

[rgleason]

Set and Drift or Speed and Direction of Tidal Current -by Connor -King Tide
King Tide Sailing: Set and Drift; or, the Speed and Direction of the Tidal Current (NMEA-0183 VDR)
Some excellent explanations and formulas.

--Via Mike Rasbats who found King Tide website.