OpenCPN Radar Overlay PlugIn

[bdbcat]

Matt, et al...

The gradar code that searches for access to the scanner does this:

a. enumerates all of the TCP/IP addresses available on the machine, and reports the list in the log.

b. Using that list, with associated netmasks, he tries to find an interface that will theoretically access the scanner at 172.16.2.0.

All of this is done without actually sending any traffic over any interface. We are simply evaluating the interfaces available. If he finds no interface that can possibly reach the scanner, (due to address/netmask) he does not even try to talk to the scanner.

So, all of the above logic works whether the scanner is powered up, or not. It works even if there is no scanner at all.

We must figure out why there is no 172... address in the list initially reported by the PlugIn on the debug log. Until we see that, there will be no access to the scanner.

We need a Windows network guru to suggest why the 172... address does not appear in the list, even though you have configured it in the control panel.

All this works for me, and I'm sure for Chuck as well. It must be something to do with your TCP/IP settings.

Screen shots of your Windows control panel dialogs might help, e.g.
http://www.cruisersforum.com/forums/...ml#post1413618

Also, static addressing may be important, instead of DHCP.

Dave

[nohal]

Matt...
May we have a look at the complete output of the two following commands?

ipconfig /all

and

route print

To get it: Start menu -> Run... -> cmd.exe and there issue them and past the output here.

Pavel

[bdbcat]

Pavel...

Pick me, pick me


My net addresses on this (virtual XP) machine are all static, 192.168.37.255 subnet.

Dave

[nohal]

Yep, this is how it should look - the interface has addresses in both the nets assigned and the routing takes care about the rest. Let's see what Matt's configuration is...

[manitu]

I'm following this thread with exitement, awaiting funds for my own radome.

One Q: The cabling..
No hub/direct connection =crossed cable
Hub/Shared connection = Straight cable, right?

But.. If you are doing a direct connection and use the female/female rj45 adapter as PoE injector, I guess you must use the x-over cable from the computer to the adapter, and a straight cable from the adapter to the radome??

.manitu

[Helmsmatt]

As per the Garmin manual, the scanner to Amp Ethernet adapter cable, in our case, is a crossover cable. From the Ethernet adapter to the PC is a straight cable. Of course we are not working....yet. I have high hopes with the great people on this forum.
Matt

[Helmsmatt]

Chuck, is the drain wire the ground/shield? It's not connected. I can connect it to pin 5, like the switch. Is that correct?
Thanks,
Matt

[Helmsmatt]

Dave and Pavel,
Cindy will send the ipconfig /all and route print files today.

I'm going to connect the ground wire on the cable to pin5 as per Chuck. Hardware. I can do that!
Matt

[Helmsmatt]

Major baby step!
Took chuck's tip on connecting the drain wire. Worked wonders. But still no radar image on the screen.
Progress:
The 172.16.1.1 shows up now in the ipconfig /all and route print queries in cmd.
It also responds to a ping.
Can go into master mode without the IP address error
The radar log shows the scanner is responding when it fires up.
Still, the pic log shows no scanner activity.
The red dot on the radar button stays red when clicked, doesn't even go to green for a second,
So Chuck, thanks for the tip.
And Dave, thanks for hanging in there.
What next? I'm working off ver 1.2 of the plug-in, should I load ver1.3 yet?
Still need help.
Thanks all
Matt

[Helmsmatt]

W'hen I open my ethernet adapter window, it no longer says 'network cable unplugged', it says 'unidentified network'
Also, the startup of the pi log with one click on the radar button, staying red:
0: Found network interface: 10.50.10.123/24
1: Found network interface: 172.16.1.1/16
2: Found network interface: 127.0.0.1/8
3: Scanner at 172.16.2.0 is accessible.
4: UpdateState: PluginState [M] Searching (1) Scanner state: Unknown (0)
5: UpdateState: PluginState [M] Searching (1) Scanner state: Unknown (0)
6: UpdateState: PluginState [M] Searching (1) Scanner state: Unknown (0)
7: UpdateState: PluginState [M] Searching (1) Scanner state: Unknown (0)
8: UpdateState: PluginState [M] Searching (1) Scanner state: Unknown (0)
9: UpdateState: PluginState [M] Searching (1) Scanner state: Unknown (0)
10: UpdateState: PluginState [M] Searching (1) Scanner state: Unknown (0)
11: UpdateState: PluginState [M] Searching (1) Scanner state: Unknown (0)
12: UpdateState: PluginState [M] Searching (1) Scanner state: Unknown (0)
13: UpdateState: PluginState [M] Searching (1) Scanner state: Unknown (0)
14: No scanner activity, continuing search
15: UpdateState: PluginState [M] Searching (1) Scanner state: Unknown (0

[Helmsmatt]

ipconfig /all and route print

[ChuckSK]

Matt

In the radar log there should be a message:

3: Successfully added to multicast group 239.254.2.0


Why it is not there, I don't know.

[nohal]

Matt...
Most of the output from ipconfig /all is missing - screenshots are nice, but paste it as text please...
At first sight, your networking is "improved" by a lot of weird stuff, likely coming from the security packages you are using.

Pavel

[Helmsmatt]

Pavel,
Below is ipconfig /all
We haven't made any more progress today.
Tried disabling Windows Firewall, Trend Micro Internet Security, and wireless adaptor. No change to the pi_log. Still shows:
0: Found network interface: 10.50.10.123/24
1: Found network interface: 172.16.1.1/16
2: Found network interface: 127.0.0.1/8
3: Scanner at 172.16.2.0 is accessible.
4: UpdateState: PluginState [M] Searching (1) Scanner state: Unknown (0)
5: UpdateState: PluginState [M] Searching (1) Scanner state: Unknown (0)

Chuck,
Please explain why multicasting is required for gradar and how we can enable it in Windows 7.

Thanks for all of your help.
Matt & Cindy



C:\Users\Cindy>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : Cindy-ASUS
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Atheros AR8151 PCI-E Gigabit Ethernet Con
troller (NDIS 6.20)
Physical Address. . . . . . . . . : C8-60-00-52-01-F4
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::5d54:88f5:25b3:eb91%13(Preferred)
IPv4 Address. . . . . . . . . . . : 172.16.1.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.240.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 298344448
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-17-72-9D-6F-C8-60-00-52-01-F4

DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) Centrino(R) Wireless-N 2230
Physical Address. . . . . . . . . : 68-5D-43-83-6D-64
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::dd08:3c2c:a0b1:c688%14(Preferred)
IPv4 Address. . . . . . . . . . . : 10.50.10.123(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Sunday, December 15, 2013 10:56:19 PM
Lease Expires . . . . . . . . . . : Monday, December 16, 2013 10:56:19 PM
Default Gateway . . . . . . . . . : 10.50.10.254
DHCP Server . . . . . . . . . . . : 10.50.10.254
DHCPv6 IAID . . . . . . . . . . . : 359161155
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-17-72-9D-6F-C8-60-00-52-01-F4

DNS Servers . . . . . . . . . . . : 10.50.10.254
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{6BF76616-3448-4C32-8DB0-B3F097AF951F}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{FB016932-128C-4ECE-B0CB-A57EC6D22C95}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

[Helmsmatt]

Chuck,
I found command below on the topic of joining to a multicast group? Does it help show whether or not join is happening?

Has anyone else tested gradar on Windows 7?

C:\Users\Cindy>netsh interface ip show join

Interface 1: Loopback Pseudo-Interface 1

Scope References Last Address
---------- ---------- ---- ---------------------------------
0 3 Yes 239.255.255.250

Interface 14: Wireless Network Connection

Scope References Last Address
---------- ---------- ---- ---------------------------------
0 0 Yes 224.0.0.1
0 1 Yes 224.0.0.251
0 1 Yes 224.0.0.252
0 1 Yes 224.0.0.253
0 3 Yes 239.255.255.250

Interface 13: Local Area Connection

Scope References Last Address
---------- ---------- ---- ---------------------------------
0 0 Yes 224.0.0.1
0 1 Yes 224.0.0.251
0 1 Yes 224.0.0.252
0 3 Yes 239.255.255.250