Still trouble running NMEA data stream and Radar in parallel. Any help?

[Be Free]

Originally Posted by Franziska

I agree, double checking makes sense.
Here you go:

I double check before I make a mistake. Imagine how many times I have to check to actually get it right!

[Franziska]

I also found the attached settings in Bios. Note that I did not enable the Bios to control the network setting.


I did enable the network Uefi Stack just now. Not sure if that helps.

[Be Free]

It won't help but it won't hurt either. UEFI is only in play while you are booting.



The first setting should stay off just like you have it.

[Franziska]

Thank you, what a thorough answer, just saw it! I'll check this tomorrow morning.

Originally Posted by Be Free

In post #6 you show the ipconfig output when your radar is disconnected and the WIFI is working. Your computer has an address of 192.168.1.225. Your router is 192.168.1.1. Since your phones connect to the same WIFI network they will also be in the 192.168.1.x range. All is good. It also shows the Ethernet adapter disconnected (as expected).

In post #9 you showed the ipconfig output when only the radar was connected. It looks exactly as I would expect: it is using an autoconfig ip address (169.254.x.x) the x.x can change and does not matter for this problem. Your radar will also be 169.254.x.x. If it were not then you would see no data from it. Your WIFI is now disconnected so now your phones are unable to see the data coming from OpenCPN. This is the expected behavior with default Windows settings.

One very confusing shot is your UDP output connection setting in OpenCPN (post #7). It is fuzzy but appears to be using 192.168.43.152.x.x on port 10110. I'm not familiar with the OpenCPN code but I do know what OpenCPN needs to know in order to do what it's supposed to do. That address is not giving it any useful information.

I suspect that this field is actually only used by OpenCPN to indicate which interface to transmit on. I also suspect that OpenCPN looks at the obviously wrong address and pretends like you entered 0.0.0.0 and just sends it out on all interfaces. That's why your phones can see it even though the connection setting is wrong. It should be 192.168.1.225 with your current configuration. 0.0.0.0 would also work and is probably the preferred setting in case your computer's IP address changes.

Just for grins, try hooking up the connections in a different order. Try Ethernet first, then WIFI. If the problem is still there then connect WIFI then Ethernet. It should not make a difference but it's worth a try.

If the problem is still there then reboot your computer, connect the WIFI, and verify that you see data on it. It is very important that you reboot. I want to know we are starting from a known state and that the WIFI is working.

Next, hook up the Ethernet and see if the problem is still there. If it is, send the output from an ipconfig /all command with the radar and the WIFI connected (or supposed to be connected). If that does not show where the problem is the next step will be Group Policy and registry checks.

[Franziska]

First issue UDP adress.

I tried changing it to the suggested 192.168.1.225 within OpenCPN and in the receiving phone.
No data stream as result.
Changed it back to the previous 192.168.43.152.x.x within OpenCPN and it comes back on the phone. Interesting enough on the phone I did not convert back and kept the suggested 192.168.1.225.



Second issue plugging in and out test.

Makes no difference which way round I connect.

If I unplug the Ethernet then disconnect the WiFi and then plug in the Ethernet followed by connecting to WiFi I have no data stream until I depower the radar.

Similar the other way round.

Data stream only when radar is depowered.




Third test, WiFi after rebooting.

As soon as I connect to the router via WiFi, the data stream works (when the radar is off).

When I then plug in the radar Ethernet with the radar on, the stream stays, but I can not switch the radar transmission on in the plug in.

[Franziska]

Correction to my previous message, last test, please ignore the very last phrase in the post.



The data stream dies when I plug in the powered on radar ethernet cable.

[Franziska]

Here the ipconfig /all with radar on and connection to WiFi router on too:


Microsoft Windows [Version 10.0.19045.4170]
(c) Microsoft Corporation. Alle Rechte vorbehalten.

C:\Users\Catamaran Lady Rover>ipconfig /all

Windows-IP-Konfiguration

Hostname . . . . . . . . . . . . : Catamaran-Lady-Rover-Nav
Primäres DNS-Suffix . . . . . . . :
Knotentyp . . . . . . . . . . . . : Hybrid
IP-Routing aktiviert . . . . . . : Nein
WINS-Proxy aktiviert . . . . . . : Nein
DNS-Suffixsuchliste . . . . . . . : lan

Ethernet-Adapter Ethernet:

Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Intel(R) Ethernet Connection I218-LM
Physische Adresse . . . . . . . . : EC-F4-BB-19-AE-0C
DHCP aktiviert. . . . . . . . . . : Ja
Autokonfiguration aktiviert . . . : Ja
Verbindungslokale IPv6-Adresse . : fe80::6d56:9698:af76:6262%15(Bevorzugt)
IPv4-Adresse (Auto. Konfiguration): 169.254.158.177(Bevorzugt)
Subnetzmaske . . . . . . . . . . : 255.255.0.0
Standardgateway . . . . . . . . . :
DHCPv6-IAID . . . . . . . . . . . : 267187387
DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-2B-99-6A-EF-EC-F4-BB-19-AE-0C
DNS-Server . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS über TCP/IP . . . . . . . : Aktiviert

Drahtlos-LAN-Adapter WLAN:

Verbindungsspezifisches DNS-Suffix: lan
Beschreibung. . . . . . . . . . . : Intel(R) Dual Band Wireless-AC 7260
Physische Adresse . . . . . . . . : AC-7B-A1-0D-25-19
DHCP aktiviert. . . . . . . . . . : Ja
Autokonfiguration aktiviert . . . : Ja
Verbindungslokale IPv6-Adresse . : fe80::8a2:e2ec:2f40:5241%13(Bevorzugt)
IPv4-Adresse . . . . . . . . . . : 192.168.1.225(Bevorzugt)
Subnetzmaske . . . . . . . . . . : 255.255.255.0
Lease erhalten. . . . . . . . . . : Donnerstag, 28. März 2024 08:36:31
Lease läuft ab. . . . . . . . . . : Donnerstag, 28. März 2024 20:36:31
Standardgateway . . . . . . . . . : 192.168.1.1
DHCP-Server . . . . . . . . . . . : 192.168.1.1
DHCPv6-IAID . . . . . . . . . . . : 95189921
DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-2B-99-6A-EF-EC-F4-BB-19-AE-0C
DNS-Server . . . . . . . . . . . : 192.168.1.1
NetBIOS über TCP/IP . . . . . . . : Aktiviert

Drahtlos-LAN-Adapter LAN-Verbindung* 1:

Medienstatus. . . . . . . . . . . : Medium getrennt
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
Physische Adresse . . . . . . . . : AC-7B-A1-0D-25-1A
DHCP aktiviert. . . . . . . . . . : Ja
Autokonfiguration aktiviert . . . : Ja

Drahtlos-LAN-Adapter LAN-Verbindung* 2:

Medienstatus. . . . . . . . . . . : Medium getrennt
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #2
Physische Adresse . . . . . . . . : AE-7B-A1-0D-25-19
DHCP aktiviert. . . . . . . . . . : Ja
Autokonfiguration aktiviert . . . : Ja

Ethernet-Adapter Bluetooth-Netzwerkverbindung:

Medienstatus. . . . . . . . . . . : Medium getrennt
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Bluetooth Device (Personal Area Network)
Physische Adresse . . . . . . . . : AC-7B-A1-0D-25-1D
DHCP aktiviert. . . . . . . . . . : Ja
Autokonfiguration aktiviert . . . : Ja

C:\Users\Catamaran Lady Rover>route print
================================================== =========================
Schnittstellenliste
15...ec f4 bb 19 ae 0c ......Intel(R) Ethernet Connection I218-LM
13...ac 7b a1 0d 25 19 ......Intel(R) Dual Band Wireless-AC 7260
6...ac 7b a1 0d 25 1a ......Microsoft Wi-Fi Direct Virtual Adapter
17...ae 7b a1 0d 25 19 ......Microsoft Wi-Fi Direct Virtual Adapter #2
11...ac 7b a1 0d 25 1d ......Bluetooth Device (Personal Area Network)
1...........................Software Loopback Interface 1
================================================== =========================

IPv4-Routentabelle
================================================== =========================
Aktive Routen:
Netzwerkziel Netzwerkmaske Gateway Schnittstelle Metrik
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.225 40
127.0.0.0 255.0.0.0 Auf Verbindung 127.0.0.1 331
127.0.0.1 255.255.255.255 Auf Verbindung 127.0.0.1 331
127.255.255.255 255.255.255.255 Auf Verbindung 127.0.0.1 331
169.254.0.0 255.255.0.0 Auf Verbindung 169.254.158.177 266
169.254.158.177 255.255.255.255 Auf Verbindung 169.254.158.177 266
169.254.255.255 255.255.255.255 Auf Verbindung 169.254.158.177 266
192.168.1.0 255.255.255.0 Auf Verbindung 192.168.1.225 276
192.168.1.225 255.255.255.255 Auf Verbindung 192.168.1.225 276
192.168.1.255 255.255.255.255 Auf Verbindung 192.168.1.225 276
224.0.0.0 240.0.0.0 Auf Verbindung 127.0.0.1 331
224.0.0.0 240.0.0.0 Auf Verbindung 169.254.158.177 266
224.0.0.0 240.0.0.0 Auf Verbindung 192.168.1.225 276
255.255.255.255 255.255.255.255 Auf Verbindung 127.0.0.1 331
255.255.255.255 255.255.255.255 Auf Verbindung 169.254.158.177 266
255.255.255.255 255.255.255.255 Auf Verbindung 192.168.1.225 276
================================================== =========================
Ständige Routen:
Keine

IPv6-Routentabelle
================================================== =========================
Aktive Routen:
If Metrik Netzwerkziel Gateway
1 331 ::1/128 Auf Verbindung
15 266 fe80::/64 Auf Verbindung
13 276 fe80::/64 Auf Verbindung
13 276 fe80::8a2:e2ec:2f40:5241/128
Auf Verbindung
15 266 fe80::6d56:9698:af76:6262/128
Auf Verbindung
1 331 ff00::/8 Auf Verbindung
15 266 ff00::/8 Auf Verbindung
13 276 ff00::/8 Auf Verbindung
================================================== =========================
Ständige Routen:
Keine

C:\Users\Catamaran Lady Rover>

[Hakan]

I've trouble being of much help since wifi and wired radar scanner are working simultaneously on all my three Win PCs I've tried.
Reading this link to control what's seems reasonable settings neither of registry key: "fMinimizeConnections" nor Group policy "Allow simultaneous connections" was set on my system.
Maybe you can follow these advises and compare to your system?
The Group policy method (#2) may be convenient if you not feel safe to tweak the registry.
The "Group policy "Allow simultaneous connections" is there but "not configured" on my system. If it happens to be used on your system try set it to "0" as advised.

[Franziska]

Originally Posted by Hakan

I've trouble being of much help since wifi and wired radar scanner are working simultaneously on all my three Win PCs I've tried.
Reading this link to control what's seems reasonable settings neither of registry key: "fMinimizeConnections" nor Group policy "Allow simultaneous connections" was set on my system.
Maybe you can follow these advises and compare to your system?
The Group policy method (#2) may be convenient if you not feel safe to tweak the registry.
The "Group policy "Allow simultaneous connections" is there but "not configured" on my system. If it happens to be used on your system try set it to "0" as advised.

Thanks Hakan.

Group policy is set to zero.

Priority to Vlan is disabled.

Also tried these. All without success. Frustrating.



Disable 'IPsec Policy Agent' service and
setting the registry key
HKLM\Software\Policies\Microsoft\Windows\WcmSvc\Gr oupPolicy!fMinimizeConnections to 0.

Prohibit connection to non-domain networks when connected to domain-authenticated network"

GPO Path: Computer Configuration/Administrative Templates/Network/Windows Connection Manager/

RegKey: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Micr osoft\Windows\WcmSvc\GroupPolicy fBlockNonDomain

[Be Free]

This reminds me of my IBM mainframe days. The developers for the operating system were based in Germany and England. The five-hour time difference sometimes made communication a challenge.

Believe it or not: you are actually making progress!

The ipconfig output you sent shows the Ethernet and the WIFI both connected at the same time. The route table shows reasonable routes to both networks. That is progress.

That means you should be sending data out on WIFI. Now the challenge is to find out where the data is going.

From a command prompt type ping 192.168.1.1

That will send a short message to your router and your router will echo it back to you. Please post the results.

Hakan: can you check your connection and see what address you have on your UDP connection in OpenCPN? I'm really hoping it's 0.0.0.0

[wholybee]

For UDP broadcast, the sender (PC) should have an IP address of 192.168.1.255. The receiver, the IP address doesn't matter, but is usually set to 0.0.0.0.

[Be Free]

Originally Posted by wholybee

For UDP broadcast, the sender (PC) should have an IP address of 192.168.1.255. The receiver, the IP address doesn't matter, but is usually set to 0.0.0.0.

The OpenCPN manual is less than clear but I believe you are right. It appears that the address field in a UDP output connection is the destination for the UDP packet, not the source.

IF that is correct then the address should be 192.168.1.255 if you wish to broadcast the data. It would be the address of the specific machine on the network you want to send to if you wanted to restrict it.

That does not explain why it works with the 192.168.43.152.x.x address but we're here to get Franziska working, not to debug OpenCPN (or the manual) so I'm going to put that question on the back burner for now.

So, Franziska, if 0.0.0.0 does not work then please try again with 192.168.1.255. I would recommend restarting OpenCPN any time you change anything on the connections screen. I'm not sure if it is required but it does seem to help.

[Franziska]

Originally Posted by Be Free

This reminds me of my IBM mainframe days. The developers for the operating system were based in Germany and England. The five-hour time difference sometimes made communication a challenge.

Believe it or not: you are actually making progress!

The ipconfig output you sent shows the Ethernet and the WIFI both connected at the same time. The route table shows reasonable routes to both networks. That is progress.

That means you should be sending data out on WIFI. Now the challenge is to find out where the data is going.

From a command prompt type ping 192.168.1.1

That will send a short message to your router and your router will echo it back to you. Please post the results.

Hakan: can you check your connection and see what address you have on your UDP connection in OpenCPN? I'm really hoping it's 0.0.0.0

Here you go the Ping result:


C:\Users\Catamaran Lady Rover>ping 192.168.1.1 Ping wird ausgeführt für 192.168.1.1 mit 32 Bytes Daten: Antwort von 192.168.1.1: Bytes=32 Zeit=1ms TTL=64 Antwort von 192.168.1.1: Bytes=32 Zeit=1ms TTL=64 Antwort von 192.168.1.1: Bytes=32 Zeit=3ms TTL=64 Antwort von 192.168.1.1: Bytes=32 Zeit=2ms TTL=64 Ping-Statistik für 192.168.1.1: Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0 (0% Verlust), Ca. Zeitangaben in Millisek.: Minimum = 1ms, Maximum = 3ms, Mittelwert = 1ms C:\Users\Catamaran Lady Rover>

[Franziska]

Regarding UDP, as mentioned above:


I tried changing the connection to the suggested 192.168.1.225 within OpenCPN and in the receiving phone. No data stream as result.
Changed it back to the previous 192.168.43.152.x.x within OpenCPN and it comes back on the phone. Interesting enough on the phone I did not convert back to 0.0.0.0 and kept the suggested 192.168.1.225 and it receives data (although still not when the radar is on).


Btw.I love how you cheer me up regarding progress. Good positive motivation!

[s/v Jedi]

For UDP traffic you also need to define the UDP port which is to be used. The port number must be the same on each device that sends or receives that UDP data.

I don’t understand why this port number isn’t mentioned by anyone?