Posts: 2
Joined: Sun Sep 06, 2009 7:47 pm

GpsGate Client blocking output.

Sun Sep 06, 2009 11:59 pm

Ok. This is my settup.
Forward route:
AIS with AIS and GPS data -> Bluetooth link -> GpsGate Client ->
|-> Filter(Block AIS -> Virtual COM4 ->MaxSea : GPS Data
|-> Filter(AIS Only) -> Virtual COM6 ->MaxSea : AIS Data

Reverse route:
Autopilot Data MaxSea -> Virtual COM4 -> GpsGate Client->
Bluetooth link -> Autopilot

Now thing is. As soon as I filter the forward GPS data coming
from my AIS the reverse link over Virtual COM4 is blocked.
This isn't right is it?



Posts: 96
Joined: Sun Jul 17, 2005 6:33 pm

RE: GpsGate Client blocking output.

Sat Sep 12, 2009 2:54 pm

What happens to Maxsea if you remove filter on COM4? If Maxsea just ignores AIS data (as it should having second dedicated AIS input) then your reverse feed to autopilot should work.

Although I have used reverse feed successfully, I find the concept a bit flaky as it allows any/all of your virtual COM ports to feed back to one source.


Posts: 2
Joined: Sun Sep 06, 2009 7:47 pm

RE: GpsGate Client blocking output.

Sun Sep 13, 2009 12:07 am

If I don't filter COM4, I do get data feed back to the autopilot
and everything works ok. Yes, MaxSea ignores the AIS data
on that port.
One might then ask why there is a filtering capability at all.
Why not feed everything to all outputs?
You can block data to selected outputs to ensure that only data from
one source is feed back.
I guess I was just puzzled by the behaviour. It's not obvious that
reverse data should be blocked if you filter the forward data.
In this case it's ok to forward everything and let MaxSea skip
what is not needed.

Return to “GpsGate Splitter - How to setup and use”