Open CPN won't receive XB-8000 Data over WiFi

[sailingunity]

I have a Vesper XB-8000 AIS with both WiFi and USB at the nav station. When I connect it via USB OpenCPN picks up my position and AIS targets just fine (and any other NMEA data). When I connect to the WiFi network, it will pick up the data for just a moment, usually 1-3 seconds, then it stops.

Not a problem with the wifi because I can use iNavX on iPad via wifi all day long.

Any ideas how to address this problem? I'm on the latest version of OpenCPN.

[Tehani]

iNavx uses a WiFi TCP / IP connection. In the manual of the Vesper XB-8000 AIS there is no mention of the type of connection, but if it is working with iNavx it is using the same type.
Verify that the connection with Ocpn is also TCP / IP (Not UDP).

José Luis

[sailingunity]

Originally Posted by Tehani

iNavx uses a WiFi TCP / IP connection. In the manual of the Vesper XB-8000 AIS there is no mention of the type of connection, but if it is working with iNavx it is using the same type.
Verify that the connection with Ocpn is also TCP / IP (Not UDP).

José Luis

Yes I'm using TCP/IP with open CPN.

[nohal]

Can we see a screenshot of your connection settings and your logfile?

[Neptune's Gear]

Ive done quite a few of these setups (although not on V5 opencpn) and had no issues. It works fine. It will be your setup. As above, settings and log files should show the issue...

[rgleason]

Read:
https://support.vespermarine.com/hc/...bile_site=true

[sailingunity]

Yep I have all of those configurations correct, but I didn't think to look at the log file. I'll get that.

[rgleason]

If you have not figured it out from the instructions,

when you send the log files and the config files, also include a screenshot of your connection too please.

Originally Posted by sailingunity

Yep I have all of those configurations correct, but I didn't think to look at the log file. I'll get that.

[transmitterdan]

Consider whether the Windows firewall is blocking the TCP connection. You may have some firewall rule that prevents that port #.

[sailingunity]

Sorry for the delay. Here are the requested files. I already tried disabling firewall, no luck there.

It wouldn't let me attach the txt files because they were over 1kb. Here is the log file from today.

6:29:31 PM: Opening NMEA Datastream Serial:COM4
6:29:31 PM: Opening NMEA Datastream TCP:192.168.15.1:39150
6:29:31 PM: NMEA input device open failed: COM4
6:29:31 PM: PlugInManager: plugins loading from C:\Program Files (x86)\OpenCPN\plugins
6:29:31 PM: PlugInManager searching for PlugIns in location C:\Program Files (x86)\OpenCPN\plugins
6:29:31 PM: PlugInManager: Loading PlugIn: C:\Program Files (x86)\OpenCPN\plugins\chartdldr_pi.dll
6:29:32 PM: PlugInManager: C:\Program Files (x86)\OpenCPN\plugins\chartdldr_pi.dll
API Version detected: 113
PlugIn Version detected: 103
6:29:32 PM: chartdldr_pi: C:\Users\Mike\Documents\Charts
6:29:32 PM: chartdldr_pi: C:\Users\Mike\Documents\Charts
6:29:32 PM: PlugInManager: Loading PlugIn: C:\Program Files (x86)\OpenCPN\plugins\dashboard_pi.dll
6:29:32 PM: PlugInManager: C:\Program Files (x86)\OpenCPN\plugins\dashboard_pi.dll
API Version detected: 106
PlugIn Version detected: 102
6:29:33 PM: PlugInManager: Loading PlugIn: C:\Program Files (x86)\OpenCPN\plugins\wmm_pi.dll
6:29:33 PM: PlugInManager: C:\Program Files (x86)\OpenCPN\plugins\wmm_pi.dll
API Version detected: 108
PlugIn Version detected: 101
6:29:33 PM: WMM: WMM model data loaded from file C:\Program Files (x86)\OpenCPN\plugins\wmm_pi\data\WMM.COF.
6:29:34 PM: Opencpn language load for: en_US
6:29:34 PM: Loading catalog for: opencpn-chartdldr_pi
6:29:34 PM: Loading catalog for: opencpn-dashboard_pi
6:29:34 PM: Loading catalog for: opencpn-wmm_pi
6:29:34 PM: Loading catalog for opencpn core.
6:29:34 PM: Getting DefaultSystemLocale...
6:29:34 PM: Found LanguageInfo for: English
6:29:43 PM: TCP Datastream connection established: TCP:192.168.15.1:39150
6:29:43 PM: Changing NMEA Datasource for GPRMC to TCP:192.168.15.1:39150 (Priority: 0)
6:29:44 PM: Changing NMEA Datasource for GPVTG to TCP:192.168.15.1:39150 (Priority: 0)
6:29:44 PM: Changing NMEA Datasource for GPGGA to TCP:192.168.15.1:39150 (Priority: 0)
6:29:44 PM: Changing NMEA Datasource for GPGSA to TCP:192.168.15.1:39150 (Priority: 0)
6:29:44 PM: Changing NMEA Datasource for GPGSV to TCP:192.168.15.1:39150 (Priority: 0)
6:29:44 PM: Changing NMEA Datasource for GPGLL to TCP:192.168.15.1:39150 (Priority: 0)
6:29:44 PM: Changing NMEA Datasource for GPGST to TCP:192.168.15.1:39150 (Priority: 0)
6:29:44 PM: Changing NMEA Datasource for AIMTW to TCP:192.168.15.1:39150 (Priority: 0)
6:29:44 PM: Changing NMEA Datasource for AIHDG to TCP:192.168.15.1:39150 (Priority: 0)
6:29:44 PM: Changing NMEA Datasource for AIVHW to TCP:192.168.15.1:39150 (Priority: 0)
6:29:44 PM: Changing NMEA Datasource for AIXDR to TCP:192.168.15.1:39150 (Priority: 0)
6:29:44 PM: Changing NMEA Datasource for AIMDA to TCP:192.168.15.1:39150 (Priority: 0)
6:29:44 PM: Changing NMEA Datasource for AIDPT to TCP:192.168.15.1:39150 (Priority: 0)
6:29:44 PM: Changing NMEA Datasource for AIVDO to TCP:192.168.15.1:39150 (Priority: 0)
6:29:51 PM: options: got device count: 1
6:30:02 PM: TCP Datastream watchdog timeout: TCP:192.168.15.1:39150
6:30:04 PM: ***GPS Watchdog timeout at Lat:29.9902 Lon: -81.6611
6:30:07 PM: TCP Datastream connection established: TCP:192.168.15.1:39150
6:30:15 PM: TCP Datastream watchdog timeout: TCP:192.168.15.1:39150
6:30:17 PM: ***GPS Watchdog timeout at Lat:29.9901 Lon: -81.6611
6:30:20 PM: TCP Datastream connection established: TCP:192.168.15.1:39150
6:30:25 PM: TCP Datastream watchdog timeout: TCP:192.168.15.1:39150
6:30:30 PM: TCP Datastream connection established: TCP:192.168.15.1:39150
6:30:32 PM: LOGBOOK: 2019-05-05 23:30:32 UTC DR Lat 29.99015 Lon -81.66114
6:30:35 PM: TCP Datastream watchdog timeout: TCP:192.168.15.1:39150
6:30:40 PM: TCP Datastream connection established: TCP:192.168.15.1:39150
6:30:50 PM: TCP Datastream watchdog timeout: TCP:192.168.15.1:39150
6:30:52 PM: ***GPS Watchdog timeout at Lat:29.9901 Lon: -81.6611
6:30:56 PM: TCP Datastream connection established: TCP:192.168.15.1:39150
6:31:20 PM: TCP Datastream watchdog timeout: TCP:192.168.15.1:39150

[rgleason]

You've configured correctly according to Vesper Directions
https://support.vespermarine.com/hc/...bile_site=true

And you have checked "receive input" only, which is fine.


It looks like it connected ok


6:29:43 PM: TCP Datastream connection established: TCP:192.168.15.1:39150
6:29:43 PM: Changing NMEA Datasource for GPRMC to TCP:192.168.15.1:39150 (Priority: 0)
6:29:44 PM: Changing NMEA Datasource for GPVTG to TCP:192.168.15.1:39150 (Priority: 0)


What is happening on the screen is your location shown?



Then the log shows one device is found, the Vesper, I guess, and you are getting Long / Lat at each gps timeout.


6:29:51 PM: options: got device count: 1
6:30:02 PM: TCP Datastream watchdog timeout: TCP:192.168.15.1:39150
6:30:04 PM: ***GPS Watchdog timeout at Lat:29.9902 Lon: -81.6611
6:30:07 PM: TCP Datastream connection established: TCP:192.168.15.1:39150
6:30:15 PM: TCP Datastream watchdog timeout: TCP:192.168.15.1:39150
6:30:17 PM: ***GPS Watchdog timeout at Lat:29.9901 Lon: -81.6611


Which should be fine. I think it should be working now.

Didn't the boat move to Lat:29.9901 Lon: -81.6611 on the chart?

--------
Glad you cut the log down. You can simply add .doc at the end which can be bigger and works, or .pdf (and say to take the .pdf off) which is allowed to be even bigger, which is what we generally do.

[sailingunity]

It does locate the boat, and the boat turns red, and the instruments start recording, but only for a moment, then it turns grey again and everything stops logging.

It seems to repeat this behavior, connecting for 3 or 4 seconds, then disconnecting for 10-20 seconds.

[rgleason]

So it is doing what it is told to do, and Opencpn is too.
Where is your timeout created?
Perhaps the Vesper?
Maybe Opencpn, but that is just recieving.


Get into your Vesper manual, I think.

[sailingunity]

You've lost me there but I will try to find it.

[jeffrobbins]

Your connection parameters look correct so I don't know why it is reconnecting every 10 seconds or so. But you can see that in the log with the repeated TCP connection established messages and I don't think that's normal.

Have you had a look at the NMEA debug window (a check box at the top of the connections setup tab). You should see a stream of $GPxxx sentences coming once a second.

Not sure I'm being much help but maybe the NMEA debug window will tell us something.