Watchdog Plugin

[Baikal]

is it possible to teach landfall taking coastline of the vector chart objects COALNE, SLCONS?

[seandepagnier]

not yet, it is planned and also for depth. This is needed for weather routing as well, but I need to digest the oenc stuff and implement it.

[seandepagnier]

Originally Posted by Hakan

Sean....again
First build and now also run for test. - Two issues:
1.
It seems that if the GL/glext.h is present the Landfall guard is pointing to a false direction. See the two pictures. The first is todays pull including GL/glext.h. The next is when I again has commented out as of the diff above. I haven't tested if it is only a graphic failure or if also the calculations are false.

Wow, really? For me it won't compile without glext.h

2.
If I check the Landfall "Graphics enabled" box the yellow line is drawn, as in the pictures, but then Watchdog, and OCPN, hangs.
See the pictures. Translation from Swedish: Watchdog (Svarar inte) = Watchdog (Don't respond) This program halt is independent of if I have commented out GL/glext.h or not.

More details?, please ask.
Håkan

I will try this.

[seandepagnier]

Please try git now and see if it still is locking up

[Hakan]

Sean..
The Landfall is now fine. No locking up and the yellow line points to nearest land. Many thanks.
But...Deadman is now not counting up when "Auto follow" is active and the chart is moving on the screen. If I switch auto follow of with F2 the counter starts. Another F2 and the counter goes to zero is if I had moved the mouse.
Håkan

[rgleason]

Have compiled new Watchdog plugin for Opencpn v4.1.818 with opencpn.lib for 4.1.818 since any plugin for the current newer versions is automatically not compatible with 4.0 due to change to wxwidgets 3.0

I have tried it but not checked Hakan's Deadman problem yet. I am going to try it with the Ocpn_Draw plugin and the new Boundary functions.

Opencpn Beta File Thingie rguser rgpass
Under 4.1.818 PI Win directory
watchdog_pi-1.9002-ov4.1.818-win32

[rgleason]

Tried to create an Ocpn_Draw Boundary around Portes de Morts Passage in Lake Michigan, Move the boat inside the boundary, then copy the GUID from the Boundary's Properties, into Watchdog Edit > Boundary > GUID area, close the Edit and the GUID looks ok, but the Watchdog Alarm window shows "Boundary Time Invalid". I hit "Reset" and it still says "Boundary Time Invalid".

I am not sure what I am doing wrong here.

RE: Landfall Alarm - Need to do this GPS running on the boat to test properly, which I will do when back on boat. Hakan confirmed it works though.

[Baikal]

Add to new watchdog_pi.pot missing string for translation.
Did the translation into Russian watchdog_pi.mo, as a result of the new lines are not translated in the English left

[rgleason]

I should have put the message here, under Watchdog,
instead it is here
http://www.cruisersforum.com/forums/...ml#post1970365

[seandepagnier]

basically, jon broke it with his patch because there are two enabled flags (one if the plugin is enabled, one if the actual alarms are enabled) and he got them confused, but it's no problem, corrected in git now.

[rgleason]

Thanks Sean, for diagnosing. Will try it.

[Hakan]

Sean..
Sorry, no alert, nor red text. I've test both 1 and 2 minutes.
Test is however functional.

Håkan

[seandepagnier]

Sorry, try again now

[Hakan]

Sean
Much better Now it's working, both red alert and sound. Thanks.

While on the line.....
Is it suitable to discuss the timer function for the Deadman?
The timer restarts if I move the mouse over the chart but also when the boat is still and the chart moves on screen, F2 - Auto follow mode. I think I understand the logic. You reset the timer when this function is called:

void watchdog_pi::SetCursorLatLon(double lat, double lon)
{
    m_cursor_lat = lat;
    m_cursor_lon = lon;
    m_cursor_time = wxDateTime::Now();
}

And it's called from OCPN every time the cursor has a new position. In F2 mode when cursor is moved over the OCPN screen edge the last position is saved as some kind of "edge" point. Now when the chart is moving there will be a new position for that edge point and the SetCursorLatLon is called and "our" timer is reset.
I agree this way of a moving cursor detection is efficient and smart to not build the wheel again since it was already there.
But for me the Deadman now has limited use since I mostly use the F2 function. Of course I could stop using F2 if I'm close to falling in sleep, but if I've that focus I'm probably not risky tired?

Is there another way for me to "fool" the plugin then to undo F2-mode?
Or could we discuss why OCPN needs a new cursor position when it's outside the edge, a fresh one is achieved as soon the cursor is within the edge again?
Or...?

Håkan

[seandepagnier]

Hakan,

I think I understand your problem. So the cursor is actually outside the opencpn window? In that case we can modify opencpn to not emit cursor positions as it makes little sense anyway.

Otherwise, what about the case in auto follow mode where the cursor is in the window?

Maybe we can just see if this routine is called at least twice in less than a second which would possibly work. Or we could query the actual screen coordinates of the cursor. What do you think?