'Options' Dialog Stops Connections Output

[RobbieW]

Hi,
I'm using OCPN 3.2.2 on Win 7 Ultimate.

I have two connections in current use (taken from the ini file):

DataConnections=...
1;0;192.168.20.118;10111;0;;4800;1;1;\
1;HDM,HDG,HDT,RMB,RMC,WPL,RTE,GLL,VTG,GSV,GGA,GPwpl,APB,AIVDM,AIVDO,FRPOS,CD;\
0;ECRMB,ECRMC,ECAPB;0;0;1;0;1|
1;0;192.168.20.10;10110;0;;4800;1;0;0;;0;;0;0;1;0;1
...

What I'm doing is using kplex running on a router to distribute NMEA data through the boats wifi AP. The USB cables that used to plug into the laptop now plug into the router.

These two connections are what I have found I need to emulate the hard wired connections to my laptop. The only talkers are a Furuno GPS and a NASA AIS engine, kplex multiplexes those onto port 10110 on the router. The output connection from port 10111 goes to a Raymarine Autopilot via the same connection as the GPS data, it has an Actisense adapter to split input from output. This all works.

When the 'options' dialog is opened in OCPN, the output port suspends transmission (from viewing the NMEA Debug window). When the 'Options' dialog is closed, transmission on the output port resumes.

Is this by design ?

The net effect is that the kplex listener sees the data stream end and closes itself when the 'Options' dialog is opened.

Thanks ...

[muttnik]

Originally Posted by RobbieW

The net effect is that the kplex listener sees the data stream end and closes when the dialog is opened.

Not answering the question asked (sorry) but...with kplex acting as a tcp server (which I believe it is in this set-up) even if OCPN closes a client connection there should be no problem with it being re-opened.

If kplex is acting as the client and OCPN is acting as the server you'd have a problem with kplex 0.2.11 if OCPN shut down the server and then restarted it, but that's fixed with the tcp persistence option (to reconnect to tcp servers which have bounced for some reason) in the 1.0 release.

[muttnik]

A bit of testing shows that opencpn calls the Close() method of datastreams when the options dialogue is closed (and then reopens them) even if the datastrean configuration was unchanged.

You'd definitely need the persist option on kplex in client mode. In server mode (with ocpn as the client), ocpn should of course reconnect

[bdbcat]

RobbieW...

Thanks for the report.

A fix for this behavior is in the todo list.
As usual, an Flyspray Task Entry will bring the issue to the fore a bit sooner.

Thanks
Dave